Folder structure blueprint skill for Claude: document how a project is organised
Makes Claude scan a project and write a blueprint file that explains its folders, naming rules and where new code goes.
- Installs
- 9.5K
- on skills.sh
- Stars
- 40.7K
- on GitHub
- Updated
- Oct 2026
- last repo commit
Claude scans the project for signature files such as .sln, pom.xml, package.json, pubspec.yaml or pyproject.toml, works out the project type, and writes a document called Project_Folders_Structure_Blueprint.md.
The document covers the folder layout, what each key folder is for, file placement and naming conventions, build output and how the structure is enforced. It can end with templates for adding a new feature, component, service or test. SKILL.md is one file with no scripts; the settings are variables inside it.
Good for
- Teams onboarding people to a large codebase
- Developers who want a written guide to where files belong
- Maintainers of .NET, Java, React, Angular, Python, Node.js or Flutter projects
Install folder-structure-blueprint-generator
Claude Code
- 1
Copy this prompt.
Install the folder-structure-blueprint-generator skill in Claude Code. Run this command: npx skills add https://github.com/github/awesome-copilot --skill folder-structure-blueprint-generator Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js.
From its listing on skills.sh. Source.
What's in the skill
When it loads
Comprehensive technology-agnostic prompt for analyzing and documenting project folder structures. Auto-detects project types (.NET, Java, React, Angular, Python, Node.js, Flutter), generates detailed blueprints with visualization options, naming conventions, file placement patterns, and extension templates for maintaining consistent code organization across diverse technology stacks.
Sections in SKILL.md
- Configuration Variables
- Generated Prompt
- Initial Auto-detection Phase
- 1. Structural Overview
- 2. Directory Visualization
- 3. Key Directory Analysis
- 4. File Placement Patterns
- 5. Naming and Organization Conventions
- 6. Navigation and Development Workflow
- 7. Build and Output Organization
- 8. Technology-Specific Organization
- 9. Extension and Evolution
- ${INCLUDE_TEMPLATES ? "11" : "10"}. Structure Enforcement
Key facts
- License
- MIT
- Installs on skills.sh
- 9,455 (Nov 2, 2026)
- Last repo commit
- Oct 30, 2026
- Audits on skills.sh
- Gen Agent Trust Hub: pass, Socket: pass, Snyk: pass
- What it includes
- 1 file: SKILL.md (bundles no scripts)
What it includes
Ten settings: project type, depth, style and extras
PROJECT_TYPE, INCLUDES_MICROSERVICES, INCLUDES_FRONTEND, IS_MONOREPO, VISUALIZATION_STYLE (ASCII, Markdown List or Table), DEPTH_LEVEL 1 to 5, INCLUDE_FILE_COUNTS, INCLUDE_GENERATED_FOLDERS, INCLUDE_FILE_PATTERNS and INCLUDE_TEMPLATES.
Try: “Make a folder blueprint of this repo, depth 3, as a table, with templates.”
Read ·
Configuration variablesFinds project type, monorepo, microservices and frontend
Looks for .sln and .csproj, pom.xml and build.gradle, package.json, angular.json, requirements.txt and pyproject.toml, pubspec.yaml, workspace files such as nx.json, Dockerfiles and web asset folders.
Files ·
Auto-detection phaseOverview, tree, key folders, placement, naming, workflow, build, tech notes, extension
Nine analysis sections: structural overview, directory visualization, key directory analysis, file placement patterns, naming conventions, navigation and workflow, build and output, technology-specific organization, and extension and evolution.
Files ·
Sections 1 to 9Adds templates for new features, components, services and tests
Included only when INCLUDE_TEMPLATES is true.
Read ·
Structure templates (optional)Documents how the structure is checked and kept
Covers validation tools, build checks, linting rules and where structural decisions are recorded, and ends with a note on maintaining the blueprint.
Read ·
Structure enforcementSaves Project_Folders_Structure_Blueprint.md
The prompt asks Claude to create that document.
Write ·
Write the blueprint file
From the official docs
Permissions
Low risk
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It reads the whole project tree
The scan opens build files, configs and folders across the project, including workspace and Docker files. Keep it away from folders with secrets you do not want in the chat. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | No read-only mode. Use version control. |
|---|---|
| Sign-in and keys | No key or account. |
| Scopes |
|
Questions
What does it do?
It makes Claude scan your project and write Project_Folders_Structure_Blueprint.md, a guide to what each folder holds, how files are named and where new code should go.
How do I install it?
Use the install box at the top of this page. The skill is one file.
Which project types does it detect?
.NET, Java, React, Angular, Python, Node.js and Flutter by default, with an Other setting. It also checks for monorepos, microservices and frontend parts.
Can I control how much it writes?
Yes. SKILL.md defines settings for depth (1 to 5), tree style (ASCII, Markdown list or table), file counts, generated folders, file patterns and templates. Say what you want in the prompt.
Is it safe?
The skill is one text file that asks Claude to read your project and create one document. It reads many files, so avoid pointing it at folders with secrets you do not want in the conversation.
Does it change my code?
SKILL.md asks for a new blueprint document. It does not describe edits to your source files.
Information
updated Nov 2, 2026
- Repository
- github/awesome-copilot
- Folder
skills/folder-structure-blueprint-generator
Sources
Docs, issue trackers and discussions this page is built from.
Show all 1Hide
- folder-structure-blueprint-generator SKILL.md · github.com