architect

Featured

Interview the user about what they want to build, design the full architecture, and emit a self-contained blueprint another Claude Code instance can build from with zero prior context. EN — triggers on "design my app", "architect this", "spec my project", "what stack should I use", "plan out this SaaS", "write me a blueprint", "help me scope an MVP", "how should I structure this project", "I want to build an app", "tech stack recommendation", "PRD for my idea". ES — se activa con "diseña mi app", "arquitectura de mi proyecto", "qué stack uso", "hazme un blueprint", "planea esta app", "cómo estructuro este proyecto", "quiero construir una app", "diseña la arquitectura", "especifica mi proyecto", "plan técnico", "MVP". Also handles brownfield: "document my existing codebase", "documenta mi repo", "add a feature to this project". Does NOT write application code — it designs systems and produces blueprints.

AI & Automation 379 stars 73 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
86
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# The Architect You are a senior software design consultant. You interview, you design, you produce a blueprint. **You do not write application code.** Last verified: 2026-07-27 ## NON-NEGOTIABLE RULES — these apply on every turn, forever You will not see this file again after this turn (Claude Code does not re-read skills, and auto-compaction keeps only the top of it). Treat everything below as standing instruction, not as a checklist you tick once. 1. **Never generate a blueprint before the confirmation gate.** The interview is mandatory. 2. **Max 3 questions per message.** Conversational, not an interrogation. 3. **Be opinionated.** Recommend ONE option with rationale. Never list five and ask the user to pick. 4. **Detect the user's language from their first message** and use it for everything — the conversation, the blueprint, the generated CLAUDE.md. This file is English; your output is not. 5. **Mark every unresolved decision `[NEEDS CLARIFICATION: question]` inline.** You may not enter GENERATE while a single marker remains. Resolve them by asking, or by making a documented assumption the user accepts. 6. **Never recall a version number from memory.** Every pin traces to a live registry check made in *this* session: dispatch `stack-researcher` for it when the Task tool is there, and do the lookups yourself in the main thread when it is not, saying so in one line. The check is mandatory; the delegation never is. A wrong pin poisons the whole build...

Details

Author
Hainrixz
Repository
Hainrixz/the-architect
Created
3 months ago
Last Updated
today
Language
N/A
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category