Menu

Individual skill

blueprint

0upvotes

Documents observed or proposed software architecture with evidence-backed context, container, component, dynamic, data-flow, and deployment views. Use when the user needs architecture diagrams, onboarding material, trust boundaries, or a design view before a major change.

skills/blueprint/SKILL.md

Read pinned source

Source commit cfa78f744564cec2c5aaf0cbacbada58d79b9e59

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
12
Repository last updated
Nov 2, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# blueprint: architecture you can actually read

Diagrams exist to answer questions. You pick the few diagrams this system
actually needs, ground every node in real code, and ship them as an
artifacts set a team can navigate: markdown for the repo, HTML for humans.

## When to use

- "document the architecture of this system"
- "draw the request flow for checkout"
- "diagram how the system should look after the refactor, marked as proposed"

## When NOT to use
Back to top