**Description**: Standardized project structure patterns with backend/frontend separation templates
Inherits all available tools
Additional assets for this skill
This skill inherits all available tools. When active, it can use any tool Claude has access to.
scripts/create-structure.shtemplates/backend-only-structure.txttemplates/frontend-only-structure.txttemplates/full-stack-monorepo-structure.txtDescription: Standardized project structure patterns with backend/frontend separation templates
Use this skill when: Projects need clean organization with proper backend/frontend separation, test isolation, and documentation structure
Template Location: @templates/full-stack-monorepo-structure.txt
This is the standardized structure for full-stack projects with backend and frontend:
Reference: plugins/foundation/skills/project-structure/templates/full-stack-monorepo-structure.txt
Key features:
Template Location: @templates/backend-only-structure.txt
For API-only or backend services:
Reference: plugins/foundation/skills/project-structure/templates/backend-only-structure.txt
Template Location: @templates/frontend-only-structure.txt
For frontend applications or static sites:
Reference: plugins/foundation/skills/project-structure/templates/frontend-only-structure.txt
Template Location: @templates/microservices-structure.txt
For distributed microservices architecture:
Reference: plugins/foundation/skills/project-structure/templates/microservices-structure.txt
Location: scripts/create-structure.sh
Purpose: Creates standardized project structure automatically
Usage:
bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/foundation/skills/project-structure/scripts/create-structure.sh <type> [path]
Project Types:
full-stack - Backend + Frontend monorepobackend-only - API/Service onlyfrontend-only - Web app/static sitemicroservices - Multiple services architectureWhat it creates:
Example:
# Create full-stack structure in current directory
bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/foundation/skills/project-structure/scripts/create-structure.sh full-stack .
# Create backend-only structure in new project
bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/foundation/skills/project-structure/scripts/create-structure.sh backend-only my-api
# Create microservices structure
bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/foundation/skills/project-structure/scripts/create-structure.sh microservices my-services
Output: Displays created structure with tree view and next steps
Location: examples/nextjs-fastapi-example.md
Real-world example showing:
Reference: @examples/nextjs-fastapi-example.md
Location: examples/microservices-example.md
Shows:
Reference: @examples/microservices-example.md
Location: examples/migration-example.md
Step-by-step migration showing:
Reference: @examples/migration-example.md
# Use create-structure script directly
bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/foundation/skills/project-structure/scripts/create-structure.sh full-stack my-project
# Or use /foundation:init-structure command (which calls this script)
SlashCommand(/foundation:init-structure my-project)
# Create full-stack structure
bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/foundation/skills/project-structure/scripts/create-structure.sh full-stack .
# Create backend-only structure
bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/foundation/skills/project-structure/scripts/create-structure.sh backend-only .
# Create microservices structure
bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/foundation/skills/project-structure/scripts/create-structure.sh microservices .
# Validate current structure (uses /foundation:validate-structure)
SlashCommand(/foundation:validate-structure)
# Review compliance report and fix issues
/foundation:init-structure - Uses templates from this skill/foundation:validate-structure - Uses validation logic from this skill/testing:generate-tests - Follows structure patterns from this skill/deployment:deploy - Recognizes standardized structureUse this checklist when validating or creating structure:
Required Directories:
Separation:
Dependencies:
Documentation:
Configuration:
❌ Root tests/ directory - Tests should be in backend/tests/ or frontend/tests/ ❌ Mixed dependencies - Keep backend and frontend dependencies separate ❌ Scattered configs - Configuration files should be in appropriate directories ❌ No separation - Backend and frontend code must be in separate directories ❌ Hardcoded secrets - Use .env.example with placeholders only