OpenSkillIndex← back to search
claude-code

Skills project-structure

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

install
source · Clone the upstream repo
git clone https://github.com/amanahmed2222/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/amanahmed2222/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/project-structure" ~/.claude/skills/amanahmed2222-skills-project-structure && rm -rf "$T"
manifest: skills/project-structure/SKILL.md
source content

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

RuleImpactFile
ColocationHIGH
rules/colocation.md
Anti-patternsHIGH
rules/anti-patterns.md
Feature-based groupingMEDIUM
rules/feature-based.md
Layer-based groupingMEDIUM
rules/layer-based.md
Framework structureMEDIUM
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.