Awesome-omni-skill project-scaffolder
Guide for setting up Claude Code infrastructure in new or existing projects
install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/project-scaffolder" ~/.claude/skills/diegosouzapw-awesome-omni-skill-project-scaffolder && rm -rf "$T"
manifest:
skills/development/project-scaffolder/SKILL.mdsource content
Project Scaffolder
Overview
This skill guides the process of setting up Claude Code infrastructure in a project. It handles stack detection, template selection, and file generation. Use this when setting up Claude Code for a new project or adding it to an existing codebase.
Quick Reference
| Stack | Detection Files | Primary Use |
|---|---|---|
| TypeScript | , , | React/Node fullstack |
| Python | , | FastAPI/Django backend |
| Rust | , | Axum/Actix backend |
Stack Detection
TypeScript Detection
Look for:
tsconfig.json package.json (with "typescript" in dependencies/devDependencies) *.ts or *.tsx files in src/
Indicators of specific frameworks:
→ Next.jsnext.config.js
→ Vitevite.config.ts
in package.json → Express backendexpress
directory → Prisma ORMprisma/
Python Detection
Look for:
pyproject.toml requirements.txt setup.py *.py files
Indicators of specific frameworks:
in dependencies → FastAPIfastapi
in dependencies → Djangodjango
in dependencies → Flaskflask
directory → Alembic migrationsalembic/
Rust Detection
Look for:
Cargo.toml Cargo.lock src/main.rs or src/lib.rs
Indicators of specific frameworks:
in Cargo.toml → Axumaxum
in Cargo.toml → Actix-webactix-web
in Cargo.toml → Diesel ORMdiesel
in Cargo.toml → SQLxsqlx
Skill Selection Matrix
Based on detected stack, select appropriate skills:
Universal Skills (All Stacks)
| Skill | Purpose |
|---|---|
| Git conventions, branching |
| Context management |
| Review checklists |
| Creating new skills |
Domain Skills (Cross-Cutting)
| Skill | Purpose | When to Include |
|---|---|---|
| Request validation | Any API project |
| Security patterns | Auth features |
| Error patterns | All projects |
| Sentry integration | Production apps |
TypeScript-Specific Skills
| Skill | Purpose |
|---|---|
| Express/Node patterns |
| React/MUI patterns |
| Prisma patterns |
| Jest/Vitest patterns |
| TanStack/Zustand |
Python-Specific Skills
| Skill | Purpose |
|---|---|
| FastAPI/Django patterns |
| SQLAlchemy patterns |
| pytest patterns |
Rust-Specific Skills
| Skill | Purpose |
|---|---|
| Axum/Actix patterns |
| Diesel/SQLx patterns |
| cargo test patterns |
| Result/Option patterns |
| Borrow checker patterns |
CLAUDE.md Generation
Template Variables
| Variable | Source | Example |
|---|---|---|
| Directory name | "my-app" |
| Constant | "1.0.0" |
| Manifest displayName | "TypeScript/React/Node" |
| Manifest version | "1.0.0" |
| Current date | "2025-12-07" |
Required Sections
Every CLAUDE.md should include:
- Quick Commands - Build, test, lint, format
- Project Structure - Directory layout
- Tech Stack - Technologies used
- Dev Docs Workflow - How to use /dev-docs
- Available Skills - Listed by category
- Available Agents - With usage examples
- Coding Conventions - Project-specific rules
Directory Structure
After initialization:
project/ ├── CLAUDE.md # Generated from template ├── .claude/ │ ├── settings.json # Hook configurations │ ├── hooks/ # Automation hooks │ ├── skills/ # Skill files │ ├── commands/ # Slash commands │ ├── agents/ # Specialized agents │ ├── templates/ # Scaffolding templates │ └── cache/ # Session cache └── dev/ └── active/ # Dev docs workspace
Customization Points
After scaffolding, users should customize:
In CLAUDE.md
- Project structure section
- Coding conventions
- Quick commands (if different from defaults)
In skill-rules.json
- Add project-specific keywords
- Adjust enforcement levels
- Add custom file triggers
Create Custom Skills
For project-specific patterns not covered by standard skills.
Workflow
New Project
- Create project directory
- Initialize stack (npm init, cargo init, etc.)
- Run
/init-claude-code - Customize CLAUDE.md
- Start developing with skills
Existing Project
- Navigate to project root
- Run
/init-claude-code - Review detected stack (confirm or override)
- Review generated CLAUDE.md
- Merge with existing documentation if needed
Troubleshooting
Multiple Stacks Detected
If project has multiple config files:
- Ask user which is primary
- Consider monorepo setup
- May need custom configuration
No Stack Detected
If no config files found:
- Ask user to specify stack
- Or create minimal config first
Missing Skills
Some skills may not exist yet:
- Note which are missing
- Continue with available skills
- Create missing skills as needed
Resources
| Topic | Link |
|---|---|
| Stack Detection | [mdc:resources/detection-patterns.md] |
| Skill Matrix | [mdc:resources/skill-matrix.md] |
| Template Guide | [mdc:resources/template-guide.md] |