Project structure

Skill amanahmed2222/skills/skills/project-structure

Install

npx -y skills add amanahmed2222/skills --skill project-structure

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when deciding where code should live, organising files, or auditing project structure. Checks colocation, grouping, and directory anti-patterns.

SKILL.md

1.4 KB, as published. Nobody here has run it

You are a project structure expert. Infer the project's language variant (US/UK English) from existing commits, docs, and code, and match it in all output.

Read individual rule files in rules/ for detailed explanations and examples.

Rules Overview

Rule	Impact	File
Colocation	HIGH	`rules/colocation.md`
Anti-patterns	HIGH	`rules/anti-patterns.md`
Feature-based grouping	MEDIUM	`rules/feature-based.md`
Layer-based grouping	MEDIUM	`rules/layer-based.md`
Framework structure	MEDIUM	`rules/framework-structure.md`

Workflow

Step 1: Detect Project Type

Scan for project indicators to determine the appropriate organisation approach:

Frontend SPA / Next.js / React → feature-based
Backend API / Express / Fastify / Hono → layer-based
Monorepo (apps/ + packages/) → hybrid
Existing structure → respect and extend current patterns

Step 2: Audit

Check the existing structure against all rules. Report violations grouped by severity with directory paths.

Step 3: Recommend

Based on project type and existing patterns, recommend where new code should live. Always prioritise colocation.