w-architecture
Plan an implementation structure; durable decisions belong in ADRs and architecture docs.
Install
npx skills add https://github.com/blockmatic/basilic-skills --skill w-architectureSKILL.md
Produce an implementation-structure plan for the user's question. Durable system decomposition belongs in existing ADRs and architecture MDX. Do not mint a second ADR tree. Do not create a branch.
- If this turn has no reconciled exploration for the area, follow council steps 1–3, then continue.
- Read the matching architecture MDX and ADRs. If the change is a durable boundary, stop and document it in the existing ADR/docs system.
- State implementation goals vs nice-to-haves. Stay inside the existing architecture unless the user already authorized a durable architecture decision.
- List constraints, trade-offs, and alternatives that affect this change. Flag high-risk items for a human. State 3–5 assumptions.
- Add Mermaid only when structure or flow is otherwise unclear.
- Save only if the user gave a path; otherwise return in chat. Include Assumptions and References (plain paths). Commands and generated-source owners come from inspected docs.
Related skills
improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".