verify-proposed-diag
Verify a proposed architecture diagram against the actual codebase, selectively checking existing vs new components. Use when user says "verify proposed diagram", "verify proposed diag", "check proposed architecture", or after running /plan-arc.
npx skills add majiayu000/claude-skill-registry --skill verify-proposed-diag --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Verify Proposed Diagram Skill Verify a proposed architecture diagram's factual accuracy against the actual codebase. Understands that proposed diagrams contain a mix of existing components (fully verifiable), modified components (partially verifiable), and new components (only integration points verifiable). ## When to Use - After `/plan-arc` produces a proposed architecture document - User says "verify proposed diagram", "verify proposed diag", "check proposed architecture" - Any time a diagram mixes existing and proposed elements using `★`/`●` annotations ## Critical Constraints **NEVER:** - Modify source code files - Modify the diagram during verification (report findings only) **ALWAYS:** - Respect the `★`/`●` annotation system — apply verification selectively - Trace actual code paths for every connection involving existing components - Determine read/write directionality for every verifiable connection - Report findings to terminal, not to files --- ## Verification Workflow ### Step 0: Validate Mermaid Syntax (Rendering Check) **This step runs BEFORE semantic verification.** Extract every mermaid code block and check for syntax errors that would prevent rendering. This appl
- When to Use
- Critical Constraints
- Verification Workflow
- Step 0: Validate Mermaid Syntax (Rendering Check)
- Proposed Diagram Verification: {diagram name}
- Element Summary
- Rendering Errors (if any — BLOCKING)
- Corrections Needed
- Directionality Findings
- Integration Point Verification
- Missing
- Phantom Components
- Directionality Quick Reference
What does the verify-proposed-diag skill do?
Verify a proposed architecture diagram against the actual codebase, selectively checking existing vs new components. Use when user says "verify proposed diagram", "verify proposed diag", "check proposed architecture", or after running /plan-arc.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill verify-proposed-diag --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.