Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Designs and maintains root ARCHITECTURE.md for the intended system, including its data model and shared technical rules.
Install Architecture
$ npx skills add owainlewis/blueprint --skill architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install owainlewis/blueprint architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/owainlewis/blueprint.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/architecture .claude/skills/architecture && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "architecture" agent skill from https://github.com/owainlewis/blueprint/tree/main/skills/architecture into .claude/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/owainlewis/blueprint/tree/main/skills/architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add owainlewis/blueprint --skill architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install owainlewis/blueprint architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/owainlewis/blueprint.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/architecture .agents/skills/architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "architecture" agent skill from https://github.com/owainlewis/blueprint/tree/main/skills/architecture into .agents/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add owainlewis/blueprint --skill architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install owainlewis/blueprint architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/owainlewis/blueprint.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/architecture .cursor/skills/architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "architecture" agent skill from https://github.com/owainlewis/blueprint/tree/main/skills/architecture into .cursor/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/owainlewis/blueprint.git --path skills/architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add owainlewis/blueprint --skill architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install owainlewis/blueprint architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/owainlewis/blueprint.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/architecture .gemini/skills/architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "architecture" agent skill from https://github.com/owainlewis/blueprint/tree/main/skills/architecture into .gemini/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install owainlewis/blueprint architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add owainlewis/blueprint --skill architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/owainlewis/blueprint.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/architecture .github/skills/architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "architecture" agent skill from https://github.com/owainlewis/blueprint/tree/main/skills/architecture into .github/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add owainlewis/blueprint --skill architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install owainlewis/blueprint architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/owainlewis/blueprint.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/architecture .opencode/skills/architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "architecture" agent skill from https://github.com/owainlewis/blueprint/tree/main/skills/architecture into .opencode/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
architecture- GitHub stars
- 412
- Token cost
- ~1.3k tokens
- SKILL.md length
- 646 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Designs and maintains root ARCHITECTURE.md for the intended system, including its data model and shared technical rules.
- Works in 6 steps: Read the requirements, repository… → Identify the decisions that shape the… → Choose the simplest structure that… → …
- Changes to system boundaries
- SKILL.md covers Process, Document shape, Diagram and Return
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Architecture is an agent skill from owainlewis/blueprint. Designs and maintains root ARCHITECTURE.md for the intended system, including its data model and shared technical rules. Use for new systems or changes to system boundaries, ownership, storage, or deployment.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: The best agent skills in the world for software development. The licence is MIT.
When your agent uses it
- Changes to system boundaries
Example prompts
- “Use the architecture skill to design and maintains root ARCHITECTURE.md for the intended system, including its data model and shared technical rules”
- “/architecture”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Read the requirements, repository instructions, existing architecture, and relevant code, schemas, tests, and infrastructure. A new system…
- Identify the decisions that shape the system: boundaries, responsibilities, data ownership, dependencies, and quality constraints. Ask for…
- Choose the simplest structure that satisfies the requirements. For consequential decisions, explain the chosen approach, strongest…
- Write the architecture using the shape below. Always include an architecture and data flow diagram. Reference requirements instead of…
- Trace critical success and failure flows. Check ownership, contracts, data consistency, security, recovery, and measurable limits against…
- Stop with the architecture ready for review. Do not plan tasks or implement it.
What it can do on your machine
Read from SKILL.md and the folder at commit 1d74745. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Architecture loads about 1.3k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 646 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from owainlewis/blueprint at commit 1d74745, republished under its MIT licence (© owainlewis). 646 words, ~1,270 tokens.
Download SKILL.mdSave it as
.claude/skills/architecture/SKILL.md (or your agent's skills folder).- name
- architecture
- description
- Designs and maintains root ARCHITECTURE.md for the intended system, including its data model and shared technical rules. Use for new systems or changes to system boundaries, ownership, storage, or deployment.
- user-invocable
- true
- argument-hint
- <system, requirements, or ARCHITECTURE.md>
Architecture
Create or update root ARCHITECTURE.md. Design the system we intend to build.
Keep this as a long-running system document alongside REQUIREMENTS.md.
Use /requirements for product needs and /spec for a feature's technical change.
Process
- Read the requirements, repository instructions, existing architecture, and relevant code, schemas, tests, and infrastructure. A new system may have no code yet.
- Identify the decisions that shape the system: boundaries, responsibilities, data ownership, dependencies, and quality constraints. Ask for missing consequential decisions; recommend an answer with its tradeoff when evidence supports one.
- Choose the simplest structure that satisfies the requirements. For consequential decisions, explain the chosen approach, strongest alternative, reason, and main cost. Consider keeping the existing system when relevant. Skip comparisons that cannot change the choice.
- Write the architecture using the shape below. Always include an architecture and data flow diagram. Reference requirements instead of copying them.
- Trace critical success and failure flows. Check ownership, contracts, data consistency, security, recovery, and measurable limits against the requirements.
- Stop with the architecture ready for review. Do not plan tasks or implement it.
Document shape
- Summary and goals: the system, its main parts, source of truth, and the requirements driving the design.
- System boundary: users, outside systems, components, and important interfaces. Include the required architecture and data flow diagram.
- Responsibilities and dependencies: what each part owns, what it does not own, and which way dependencies may point.
- Data model: core entities, relationships, identifiers, ownership, lifecycle, constraints, consistency rules, retention, and storage choices. Include an entity diagram when useful. Link larger schemas rather than repeating them.
- Runtime flows: important execution order, data movement, transactions, side effects, failures, retries, and recovery.
- Security and operations: trust boundaries, authorization, deployment, observability, resource limits, and operator recovery where they affect the design.
- Operating expectations: expected workload, latency, availability, recovery, and cost constraints where they shape the design. Use supported targets; record consequential unknowns and their effects instead of inventing numbers. Link requirements for product limits.
- Path to the intended system: for an existing system, explain important gaps, compatibility constraints, migration, and rollback where needed. Keep feature details in specs and delivery tasks in
/plan. - Decisions and status: mark decisions proposed or accepted. Separately state what is implemented, missing, or different in the current system. Acceptance does not mean implementation.
- Risks and proof: unresolved decisions, assumptions, quality scenarios, and checks needed to validate the design.
Show full SKILL.md (248 more words)Show less
Diagram
Always include a Mermaid diagram showing the main components, external actors, data stores, and data flow. A single diagram may cover architecture and flow; use a second when combining them would make either hard to read.
Use clear labels, labeled arrows, and groups for system or trust boundaries. Show what moves between parts, not just which parts connect. Keep spacing generous and the layout easy to follow. Use a restrained, consistent palette with readable contrast. Avoid crossing arrows and decorative detail. Split crowded diagrams by flow and keep an overview.
Render the diagram and inspect it before finishing. Check labels, arrow direction, legibility, and agreement with the written design. Include a caption explaining the main flow and any boundary the reader needs to understand.
The diagram is required. Use other sections only when they help explain this system; combine related points and omit empty sections. Describe shared rules here; put feature-specific schema changes and migrations in its spec.
Verify claims about existing implementation against authoritative files or runtime evidence. Label future behavior and assumptions clearly. Do not mark a proposal accepted without human approval. Give important architectural rules stable INV-n IDs and name their intended enforcement and proof.
Update this document when an accepted change alters ownership, dependencies, interfaces, stored data, trust boundaries, deployment, or hard limits. Keep this document current. Preserve useful content and stable references; retain feature decision history in specs.
Return
Report the path, main decisions and tradeoffs, implementation gaps, and any blocking question.
© owainlewis, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/architecture of owainlewis/blueprint.
Open the folder on GitHubat commit 1d74745
Compare with similar skills
Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Architecture this skillowainlewis/blueprint | 412 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 59 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from owainlewis/blueprint
All 11 skills in this repoMarkdown PRD to HTML Renderer
owainlewis/blueprint
Converts a complete Markdown PRD or technical design into one verified, static HTML reading page without changing what it says.
Codex Issue Coordinator
owainlewis/blueprint
Lets one Codex thread run a batch of GitHub issues through separate worker threads, each with its own worktree, branch, tested pull request and gated merge.
Vertical-Slice Task Planner
owainlewis/blueprint
Breaks a reviewed spec into ordered, vertical-slice tasks that each fit one agent run and one pull request, grouped into milestones when useful.
Independent Implementation Review
owainlewis/blueprint
Has a separate agent review a code change without editing it, checking behavior, security, regressions, complexity, tests and docs before merge.
Architecture Review
owainlewis/blueprint
Reviews a technical proposal before implementation through an independent subagent, returning findings, open questions and a verdict without rewriting it.
Product Requirements Document
owainlewis/blueprint
Creates or updates a long-running REQUIREMENTS.md that defines a system's users, outcomes, capabilities, business rules, scope and acceptance conditions.
Related
Categories
Questions about Architecture
What does Architecture do?
Designs and maintains root ARCHITECTURE.md for the intended system, including its data model and shared technical rules. Architecture is an agent skill from owainlewis/blueprint.md for the intended system, including its data model and shared technical rules.
When should I use Architecture?
Architecture fits situations like: changes to system boundaries.
How do I install Architecture in Claude Code?
Run `npx skills add owainlewis/blueprint --skill architecture -a claude-code`. Or copy the skill folder (skills/architecture in owainlewis/blueprint) into .claude/skills/architecture in your project. Claude Code loads it when a task matches its description.
How do I install Architecture in Codex?
Run `npx skills add owainlewis/blueprint --skill architecture -a codex`. Or copy the skill folder (skills/architecture in owainlewis/blueprint) into .agents/skills/architecture in your project. Codex loads it when a task matches its description.
Can I use Architecture in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add owainlewis/blueprint --skill architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture, .gemini/skills/architecture, .github/skills/architecture and .opencode/skills/architecture in your project.
What does Architecture need to run?
SKILL.md names no scripts, command-line tools or credentials: Architecture is instructions for the agent only.
Does Architecture access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Architecture safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Architecture use?
Architecture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Architecture use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Architecture?
Skills that share tags, products or a category with Architecture: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Architecture?
owainlewis (a GitHub user) maintains it in owainlewis/blueprint, which has 412 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 6, 2026.
Source: owainlewis/blueprint on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.