Sketch proposed code changes visually with Mermaid diagrams before implementation.
npx skills add https://github.com/Yassimba/loom --skill blueprint-yassimba
Please help me install this Agent Skill. Skill: blueprint Source: https://github.com/Yassimba/loom/tree/main/skills/blueprint Command: npx skills add https://github.com/Yassimba/loom --skill blueprint-yassimba
:::red removed, :::green added, :::orange changed). - Code Contract Integration: Runs the code-contracts skill's obligation sweep during design and materializes approved contracts into target declarations or CONTRACTS files, validated with cc-check format and cc-check list. - Reuse-First Planning: Loads the ponytail skill when available and prioritizes reusing existing code and interfaces before adding abstractions or dependencies. - Use Case: Before refactoring a payment module, generate a blueprint showing structure, input/output flow, interface dependencies, and contract status so reviewers can approve the direction before implementation begins. ## Quick Start Use the blueprint skill to sketch the proposed caching layer change with Mermaid diagrams before we start implementing it.High-intent search queries and answers about installing and using this skill.
Use Mermaid diagrams to show the goal, current versus proposed behavior, affected code, and key trade-offs. This Skill generates fenced mermaid blocks covering structure, input/output flow, interface dependencies, and a snippet of the main interfaces.
Run the code-contracts skill's obligation sweep while designing, then write each approved contract into its target declaration or CONTRACTS file. Validate contract-only edits with cc-check format and cc-check list before implementation.
Yes, Mermaid supports class-based styling for change marking. This Skill uses :::red for removed elements, :::green for added elements, and :::orange for changed elements so reviewers can see the delta at a glance.
Leave a contract in the blueprint when the target code does not exist yet or an assumption still needs approval. The blueprint lists unmaterialized proposals with their intended path, exact @cc text, and blocker.
Diagrams communicate structure and flow but cannot verify runtime behavior or catch implementation bugs. They must be grounded in actual source code, and proposals must be clearly distinguished from verified facts to remain trustworthy.
sumpalabsInterrogate plan and design decision trees to surface hidden gaps.
markus41Review linked commits and pull requests for a Jira issue against acceptance criteria.
hanh-ndImplements WBS plans and investigation reports by editing files, running tests, and logging decisions.
JaviMontanoGenerate syntactically valid Mermaid diagrams for architecture, flows, and technical documentation.