Agent skill · writing content · github

folder-structure-blueprint-generator

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.

Why this skill is useful

Generates detailed documentation and templates for project folder structures that the AI wouldn't reliably create on its own.

What it needs

About 7k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.

What this skill does

Project Folder Structure Blueprint Generator Configuration Variables ${PROJECTTYPE="Auto-detect .NET Java React Angular Python Node.js Flutter Other"} <!-- Select primary technology --> ${INCLUDESMICROSERVICES="Auto-detect true false"} <!-- Is this a microservices architecture? --> ${INCLUDESFRONTEND="Auto-detect true false"} <!-- Does project include frontend components? --> ${ISMONOREPO="Auto-detect true false"} <!-- Is this a monorepo with multiple projects? --> ${VISUALIZATIONSTYLE="ASCII Markdown List Table"} <!-- How to visualize the structure --> ${DEPTHLEVEL=1-5} <!-- How many levels of folders to document in detail --> ${INCLUDEFILECOUNTS=true false} <!-- Include file count statistics --> ${INCLUDEGENERATEDFOLDERS=true false} <!-- Include auto-generated folders --> ${INCLUDEFILEPATTERNS=true false} <!-- Document file naming/location patterns --> ${INCLUDETEMPLATES=true false} <!-- Include file/folder templates for new features --> Generated Prompt "Analyze the project's folder structure and create a comprehensive 'ProjectFoldersStructureBlueprint.md' document that serves as a definitive guide for maintaining consistent code organization. Use the following approach: Initial Auto-detection Phase ${PROJECTTYPE == "Auto-detect" ? "Begin by scanning the folder structure for key files that identify the project type: Look for solution/project files (.sln, .csproj, .fsproj, .vbproj) to identify .NET projects Check for build files (pom.xml, build.gradle, settings.gradle) for Java projects Identify package.json with dependencies for JavaScript/TypeScript projects Look for specific framework files (angular.json, react-scripts entries, next.config.js) Check for Python project identifiers (requirements.txt, setup.py, pyproject.toml) Examine mobile app identifiers (pubspec.yaml, android/ios folders) Note all technology signatures found and their versions" : "Focus analysis on ${PROJECTTYPE} project structure"} ${ISMONOREPO == "Auto-detect" ? "Determine if this is a monor …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills github/folder-structure-blueprint-generator

View the source on GitHub

Browse the @skills marketplace