Kartik-Doye/Ravengard-AI-Recruiter / .agents/skills/blueprint
blueprint
VerifiedDocuments 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.2 KB |
| assets/template.html | other | 5.3 KB |
| references/diagram-guide.md | markdown | 3.2 KB |
| references/research.md | markdown | 3.1 KB |
| scripts/validate-mermaid | other | 3.4 KB |
references/research.md
View on GitHub# blueprint research ledger
## Source 1
Title: C4 model diagrams
Author / Organization: Simon Brown
Publication date: Living documentation
Version: Current website
URL: https://c4model.com/diagrams
Source type: official docs
What it establishes:
C4 offers hierarchical architecture views and says teams need only the diagram levels that add value.
What this skill adopts:
Default to context and container views, adding component, dynamic, or deployment views only when they answer a real question.
What it does NOT establish:
It does not require all architecture evidence to live in source code or require all four levels.
Numbers taken from source:
Four core static diagram levels are defined; no project diagram count is adopted.
Reverify when:
The C4 model guidance changes.
## Architecture abstractions
Title: Abstractions
Author / Organization: C4 model
Publication date: 2026
Version: Current website
URL: https://c4model.com/abstractions
Source type: official docs
What it establishes:
A software system contains applications and data stores called containers;
containers contain components, which are implemented by code elements.
What this skill adopts:
Use consistent abstraction labels and avoid calling every folder, class, or
deployment unit a C4 component or container.
What it does NOT establish:
It does not prescribe a repository layout, cloud topology, or diagram count.
Numbers taken from source:
None.
Reverify when:
The selected architecture notation or reader needs change.
## Decision records
Title: Architectural Decision Records
Author / Organization: ADR GitHub organization
Publication date: 2026
Version: Current website
URL: https://adr.github.io/
Source type: official docs
What it establishes:
An ADR captures one architecturally significant design choice with rationale,
trade-offs, and consequences as part of a maintained decision log.
What this skill adopts:
Create ADRs only for load-bearing decisions and include alternatives,
consequences, status, authority, and supersession information.
What it does NOT establish:
It does not establish who may decide, require an ADR for every implementation
choice, or prove a proposal is accepted.
Numbers taken from source:
None.
Reverify when:
The project decision-record convention or architecture governance changes.
## Diagram-as-code limits
Title: About Mermaid
Author / Organization: Mermaid project
Publication date: 2026
Version: 12 documentation
URL: https://mermaid.js.org/intro/
Source type: official docs
What it establishes:
Mermaid renders text definitions into diagrams and supports multiple diagram
types, enabling diagrams to be versioned alongside documentation.
What this skill adopts:
Keep source-controlled Mermaid as the portable default, distinguish syntax
validation from visual rendering, and preserve source alongside HTML output.
What it does NOT establish:
It does not ensure a diagram is accurate, legible, secure for arbitrary input,
or rendered consistently by every host.
Numbers taken from source:
Version 12 is the reviewed documentation major version.
Reverify when:
Mermaid syntax, renderer, hosting environment, or security configuration
changes.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |