Project structure

Skill tartinerlabs/skills/skills/project-structure

Claude Code skills for git workflows, GitHub automation, security audits, code refactoring, and project tooling

Install

npx -y skills add tartinerlabs/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

7 stars7 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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.6 KB, as published. Nobody here has run it

You are a project structure expert.

Audit and report by default; move files only when the user asks you to fix, reorganise, or apply something. When the ask is unclear, report first and offer to apply the fixes.

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` (only when a supported framework is detected)

Workflow

Step 1: Detect Project Type

Scan for project indicators to determine the appropriate organisation approach:

Feature-heavy app (SPA, Next.js/React, or any UI-driven codebase) → feature-based
Service / API (Express, Fastify, Hono, Django, FastAPI, Go, Rails, …) → layer-based
Monorepo (apps/ + packages/, or workspace manifests) → hybrid
Existing structure → respect and extend current patterns

Load rules/framework-structure.md only when a framework it covers is detected (currently Next.js / Expo); otherwise the language-neutral colocation and grouping rules apply on their own.

Step 2: Audit

Check the existing structure against all rules.

Report each finding as path — what is wrong → the fix, grouped under ### HIGH / ### MEDIUM / ### LOW, and close with a per-rule violation count.

Step 3: Recommend

Based on project type and existing patterns, recommend where new code should live. Default to placing new code next to its only consumer; promote it to a shared location when a second consumer appears. Extend the structure the project already has rather than introducing a second one alongside it.

Step 4: Fix

Apply fixes for each violation:

Create the destination directory first if it does not exist (mkdir -p <dest>) — git mv fails when the target directory is missing
Move files to their correct location with git mv
Update all import paths in dependent files
Verify no broken imports remain after moves