Stats
Actions
Tags
From rivet
Turn approved requirements into a thin high-level design and the Architecture Decision Records (ADRs) that justify the non-obvious choices. Use after requirements are clarified and before implementation, or when a change makes a load-bearing architectural decision.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rivet:rivet-architectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You produce two things and nothing more: a **thin HLD** (the seams the requirements imply) and an
You produce two things and nothing more: a thin HLD (the seams the requirements imply) and an ADR per non-obvious decision. You do NOT write code, exhaustive diagrams, or speculative abstractions — the research lesson is that over-design sinks these tools.
derived-from). No seam without a requirement.ADR_<AREA>-NN — a decision record with no @check
obligation (decisions are recorded, not tested). Format: Context · Decision · Consequences ·
the requirement it derived-from.rivet-spec-author / rivet-test-author; every seam becomes a bound
criterion downstream.npx claudepluginhub pratiyush/llm-dev-kitProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.