architecture

Solid

Create or update docs/blueprint/architecture.md — the system shape and machine-readable Project Registry that blueprint and plan parse.

AI & Automation 1 stars 0 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 78/100

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

Skill Content

You are a **Senior Systems Architect**. You think in project boundaries, data flow, deployment topology, and shared-code strategy. You never invent a project, stack, or capability the user did not confirm. **Boundary exemption.** The product-doc boundaries (no technology names, no API shapes) do not apply here. `docs/blueprint/architecture.md` deliberately records stacks, frameworks, and infrastructure. ## Doc Path | Doc | Path | | ------------ | -------------------------------------------------------- | | Architecture | `docs/blueprint/architecture.md` | | Template | `${CLAUDE_PLUGIN_ROOT}/assets/templates/architecture.md` | There is exactly one architecture doc per workspace; it describes every project. --- ## Step 1 — Setup Invoke `/vwf:git-workflow` to ensure an isolated local worktree before making any changes. Never push a worktree branch directly. --- ## Step 2 — Detect Mode Read `docs/blueprint/architecture.md`. - **Exists → update/reconcile mode.** Preserve confirmed content. Ask only about genuine deltas — a new project, a changed stack, a new capability or cross-cutting decision. Do not re-elicit everything. - **Absent → create mode.** Run the full elicitation below. **Format check.** Run the preflight in `${CLAUDE_PLUGIN_ROOT}/assets/format-check.md`; if the repo's blueprint format is behind what vwf ships, **nudge** `/vwf:setup` and **always proceed — never ha...

Details

Author
virajp
Repository
virajp/ai-plugins
Created
2 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

blueprint

Human-facing documentation, architecture docs, and mermaid diagrams for a codebase, a module, or a feature — "draw me the architecture, with receipts." Fans out read-only sub-agents to build a grounded component graph first: every node is a real path, every edge backed by a grep-verified import or call — unverifiable edges are dropped, not drawn. Diagrams render from that verified table per a fixed checklist (never freehand mermaid), capped at 5–8 top-level components with drill-down pages; every doc section cites its sources as file:line. Drafts in chat, writes docs/blueprint/ only on your yes, and stamps a manifest with date + commit so /blueprint refresh regenerates only what the diff touched. Use for "generate an architecture diagram", "document this codebase or module for people", "create a mermaid diagram of this feature" — e.g. "/blueprint", "/blueprint the payment flow", "/blueprint refresh". For agent-facing orientation (AGENTS.md) use map; blueprint is the human-facing sibling.

6 Updated today
duthaho
AI & Automation Solid

product

Create or update docs/blueprint/product.md — the problem, target users, success metrics, and slice priority the whole blueprint serves. The Phase −1 foundation; blueprint halts without it.

1 Updated yesterday
virajp
AI & Automation Solid

architect

Produces Alon's design-doc system BEFORE code: SOURCE_OF_TRUTH, ARCHITECTURE_ROADMAP, TODO_WORKFLOW, CLAUDE.md (+ modular docs/architecture). Model first: data + invariants → core enforcement → failure paths → API contracts → phased workstream. Use proactively when a new app, feature, or workstream is starting and code hasn't been written, or docs may have drifted (audit). Also on "architect", "design doc", "spec this out", "roadmap". Not for small fixes inside a current design.

6 Updated 2 days ago
alonbaron