project-init
Interview-based project setup — generates CLAUDE.md, ROADMAP, .gitignore, .env.example from scratch. Use when: user says '/project-init', 'new project', 'project creation', 'project setup', 'project setup', 'new project', 'create project'. NOT for AI agent/harness configuration (use setup for that). Conversational, one question at a time.
AlexZio00 · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add AlexZio00/sovereign-skills --skill project-initAbout this skill
skill_type: infrastructure tools: Read, Write, Bash triggers:
- "/project-init"
- "새 프로젝트"
- "프로젝트 생성"
- "project setup" name: project-init description: "Interview-based project setup — generates CLAUDE.md, ROADMAP, .gitignore, .env.example from scratch. Use when: user says '/project-init', 'new project', 'project creation', 'project setup', 'project setup', 'new project', 'create project'. NOT for AI agent/harness configuration (use setup for that). Conversational, one question at a time." user_invocable: true depends_on: skills: [] agents: [] files: [] concurrency_profile: read_only: false concurrency_safe: false destructive: medium not_for:
- "AI agent/harness setup -> setup skill"
- "Existing project audit -> project-check" see_also:
- skill: setup relation: "project-init=project scaffolding, setup=AI harness/agent team setup (separate skill)"
Project Init — New Project Design Interview
Dominant Variable
Do interview decisions map exactly to generated files? — If interview answers conflict with CLAUDE.md/ROADMAP content, the project starts on a false premise.
Purpose
Capture every critical decision before writing a single line of code. Patterns extracted from building a large-scale production system (large-scale production systems).
Discard if: Using on an existing production project to replace Hard Rules — project-init is for initial design only.
Trigger
/project-init- "새 프로젝트"
- "프로젝트 생성"
- "project setup"
Key Assumptions
- Empty or new project directory — if broken: existing file conflicts need resolution.
- Write tool accessible — if broken: output file contents as code blocks and user saves manually.
Phase 0: Context Check
0-1. Existing CLAUDE.md Detection
Check if CLAUDE.md exists in the current working directory.
- Not found → proceed to Phase 1 normally.
- Found → read it, then ask:
CLAUDE.md already exists. What would you like to do? 1. Update — enhance based on existing content (keep Hard Rules, add missing sections) 2. Rewrite — start fresh from scratch (delete existing content) 3. Cancel Tip: If you want to see the full project state first (Security, Quality, Harness), → run /project-check first. Then come back here and select Update mode.- Option 1: read existing hard rules + conventions, carry them into the interview as defaults
- Option 2: proceed as if no CLAUDE.md exists
- Option 3: stop
0-2. Brief / Context File
If the user provides a file path or pastes a project brief, read it first. Extract any stack decisions or constraints to pre-fill interview answers.
0-3. Smart Defaults
After Phase 0, check for context clues before asking each Q.
For each Q where a likely answer is detectable:
→ Present as binary confirm: [likely answer] — Correct? (Y/n)
→ Y: accept and move to next Q immediately
→ N: ask the full open-ended question
If no context available → ask all questions open-ended as normal.
Default signals by Q:
- Q2 (Language): file extensions in directory —
.py→ Python,.ts/.tsx→ TypeScript,go.mod→ Go,Cargo.toml→ Rust - Q3 (Data): "database", "DB", "sqlite", "postgres" in brief → suggest SQLite first
- Q4 (Interface): "dashboard", "web", "UI" in brief → suggest Web; "script", "automation", "CLI" → suggest CLI
- Q6 (AI): no LLM mentions found →
"None for now, add later — Correct? (Y/n)" - Q8 (Scope): default to "1 month+, solo" unless team or deadline mentioned
Phase 1: Interview (one question at a time)
Ask the questions below one at a time. Confirm understanding before moving to the next. Adjust later questions based on earlier answers.
Q1 — Core Definition
Describe the project in one sentence.
[What] [Who uses it] [Why they need it]
Q2 — Language / Runtime
What language are you thinking? (If undecided, say so — let's choose together)
Decision guide:
- Python: data, ML, automation, scripting → unbeatable ecosystem
- TypeScript: web UI, API server → full-stack unification
- Java/Kotlin: Spring Boot backend, Android app → enterprise/mobile
- Go: high-performance server, CLI tools, concurrency → single binary deploy
- Rust: systems-level, embedded, extreme performance
- Swift: native iOS/macOS apps
Q3 — Data Layer
Where does data come from, and where does it live?
- Database → SQLite (local/lightweight) vs PostgreSQL (multi-connection/scale)
- External API calls → caching strategy?
- Files only → what format?
- None (pure computation/transformation)
Principle: UI should only read from DB — never call external APIs directly.
Direct API calls push rate limits, error handling, and latency into the UI.
Q4 — Interface
How do users interact with it?
- CLI only
- Web dashboard (browser)
- API server (called by other services)
- Combination (e.g. CLI + dashboard)
- None (background service / daemon)
Q5 — Deployment
Where does it run?
- Local only (your machine)
- Server / cloud (always-on)
- Hybrid (local dev + cloud deploy)
- Mobile app (iOS/Android)
Principle: Even for local-only projects, decide on scheduler registration
and restart policy upfront — retrofitting this requires major restructuring.
Q6 — AI / LLM
Any AI features?
- None (pure code)
- Cloud LLM: Claude API / OpenAI / OpenRouter (cost per call)
- Local LLM: Ollama, LM Studio (hardware-dependent)
- Maybe later
Principles:
- Always gate LLM features behind a feature flag (default OFF)
- Daily cost cap + budget guard required
- Design cloud fallback before local hardware is available
Q7 — Hard Rules (Invariants)
Are there rules that must never be broken?
Examples:
- Finance: "No live trade execution (paper-only)", "Missing data → REJECT, no guessing"
- Finance: "Any action with loss potential must prompt for confirmation"
- Privacy: "PII stays in local DB only — no external transmission"
- Medical: "Diagnosis results mus
Read the complete source ↗