Project Structure

This one audits your project structure and tells you where code should live. It checks for colocation issues, directory anti-patterns, and whether you're doing feature-based or layer-based grouping properly. The workflow is straightforward: it detects your project type (React, Next.js, Express, monorepo, whatever), audits against its ruleset, then recommends where new code belongs. Useful when you're mid-refactor and your utils folder is a junk drawer, or when you need to justify why that new feature shouldn't go in a random misc directory. It respects existing patterns instead of forcing a rewrite, which is the right call for real codebases.

skills.sh installs: 506
GitHub stars: 8
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add tartinerlabs/skills --skill project-structure --agent claude-code

Installs into .claude/skills of the current project.

Files

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

SKILL.md on GitHub