vibe-architectlisted

Architecture planning workflow for establishing code structure, patterns, and principles before any code is written. Runs after brainstorm: and before new: on every project. Triggers on "architect:" prefix, "plan the architecture", "architect this", "how should we structure this", "what patterns should we use". Runs on every project — architecture is never skipped (it can proceed without BRIEF.md by asking the stack questions directly, but the architecture step itself is not optional). Reads BRIEF.md stack decisions and confirms them explicitly before asking any questions — prevents scaffolding with wrong framework (e.g. Next.js when React+Vite is specified). Produces ARCHITECTURE.md from canonical template — structurally consistent so review:, fix-bug:, and add-feature: can parse it reliably every session. review: uses ARCHITECTURE.md as its primary reference for drift detection. Handles gracefully if BRIEF.md is missing. Detects existing ARCHITECTURE.md before overwriting.
aakashdhar/vibe-skill · ★ 7 · Data & Documents · score 68

Install: claude install-skill aakashdhar/vibe-skill

# Vibe Architect Skill Establishes the architectural foundation before a single line of spec or code is written. Every pattern, convention, and structural decision made here becomes the law for the entire build. **Always run in Plan Mode (Shift+Tab). No code. No project files.** --- ## The O'Reilly principle this enforces Spec before code — and architecture before spec. Without deliberate architecture decisions, agents make reasonable but unconsidered defaults. Folder structure, naming conventions, state management, error handling — these just happen, inconsistently. ARCHITECTURE.md is the agent's constitution for the project. Not what gets built (SPEC.md does that) — how everything gets built. Every task from Phase 1 through Phase 3 is measured against it. `review:` detects drift from it at every phase gate. Good architecture on a small project costs 20 minutes. Bad architecture on a small project costs days of refactoring. --- ## Step 0 — Read BRIEF.md, confirm stack, classify project type **Check for existing ARCHITECTURE.md first:** If ARCHITECTURE.md already exists at the project root: > "An ARCHITECTURE.md already exists for this project. > Do you want to update it (add new decisions) or start fresh (replace it entirely)?" Wait for answer before proceeding. **Check for BRIEF.md:** If BRIEF.md does not exist: > "BRIEF.md not found. Ideally run `brainstorm:` first — it captures the problem, > user, stack preferences, and constraints that make architecture decis