Folder Architecture
Define and enforce best-practice folder architecture whenever creating or modifying files. Use whenever the AI adds or edits code to prevent structural clutter, directory bloat, misplaced files, naming inconsistencies, and deep nesting.
Install
/plugin marketplace add Drakaniia/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Drakaniia/skills --skill folder-architecturegit clone --depth 1 https://github.com/Drakaniia/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/folder-architecture ~/.claude/skills/folder-architecturePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Folder Architecture Use this skill to act as a **Structure Guardian** — proactively enforcing clean folder organization and best-practice file placement **before** every file creation or modification. This skill prevents structural decay at the point of change. ## Core Principles - **Language-agnostic**: Every check applies to any language. Language-specific details are in [references/ORGANIZATION-PATTERNS.md](references/ORGANIZATION-PATTERNS.md). - **Prevention over cleanup**: Check structure BEFORE creating or modifying files — not after. - **Follow existing conventions**: When the project already has a pattern (even if imperfect), match it for new files. Only proactively restructure when clear rules are violated. - **Respect framework defaults**: Don't fight established conventions (Rails MVC, Django apps, Next.js App Router, Go's `internal/`). - **Feature-first by default**: Prefer grouping by domain/feature over technical layering. Let the AI choose the best architecture pattern based on project size and complexity. - **Project rules win**: The thresholds below are defaults for projects that have no rules of their own. Anything the project already enforces — linter/formatter config (ESLint, Ruff, golangci-lint, Checkstyle, rustfmt…), framework structure, or written conventions (`AGENTS.md`, `CLAUDE.md`, `CONTRIBUTING.md`, ADRs) — takes precedence, and these checks must never contradict it.
Details
- Skill name
folder-architecture- Repository
- Drakaniia/skills
- Path
skills/folder-architecture/SKILL.md- License
- MIT
- Repo updated
- 7 November 2026
FAQ
What does the Folder Architecture skill do?
Define and enforce best-practice folder architecture whenever creating or modifying files. Use whenever the AI adds or edits code to prevent structural clutter, directory bloat, misplaced files, naming inconsistencies, and deep nesting.
How do I install the Folder Architecture skill?
Claude Code plugin: /plugin marketplace add Drakaniia/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Folder Architecture popular?
It lives in Drakaniia/skills, which has 9 GitHub stars and 0 forks.
Related skills
Audit Codebase
9Drakaniia/skills
Scan any codebase (language-agnostic) and flag structural health issues including folder bloat, oversized files, deep nesting, naming inconsistencies, orphaned files, doc sprawl, and empty directories. Generates a markdown report with ASCII tree diagrams for folder structure issues and Mermaid graphs for file-level diagrams. Use when a codebase feels cluttered, disorganized, or hard to navigate.
Code Design
9Drakaniia/skills
Use when writing or reviewing functions that are deeply nested, do too many things, have unclear side effects, or are hard to follow linearly. Also when an agent produces code with high cognitive load — nested if-else pyramids, functions mixing validation+business logic+IO, mutable state leaks, or control flow that jumps around. Complements folder-architecture (file/dir level) with function-level design principles.
Codebase Health
9Drakaniia/skills
Use when starting any session, or when unsure which codebase-health skill applies. Routes to audit-codebase, folder-architecture, code-design, and implement-folder-architecture. Establishes that codebase health is continuous practice, not a one-time audit.
Graphql Expert Best Practices
9wispbit-ai/skills
GraphQL performance optimization and best practices for building scalable APIs. This skill should be used when writing, reviewing, or refactoring GraphQL schemas, resolvers, or query execution code. Triggers on tasks involving GraphQL APIs, resolver optimization, query performance, or data fetching patterns.
Implement Folder Architecture
9Drakaniia/skills
Execute a large-scale folder architecture refactor based on an audit report or user-defined architecture. Moves files into correct locations, splits oversized folders, refactors imports, updates barrel files, and verifies builds after each phase. Use after audit-codebase has generated its structural report, or when a systematic folder reorganization is needed.
Postgresql Expert Best Practices Code Review
9wispbit-ai/skills
PostgreSQL database design, migration, and performance optimization best practices. This skill should be used when writing, reviewing, or refactoring database schemas, migrations, or query patterns. Triggers on tasks involving PostgreSQL databases, schema design, migration optimization, or data modeling.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.