Skip to main content
skill CX Codex

architecture · owainlewis — Claude Code skill: what it does, how to install

A skill for Claude Code and Codex that writes or updates the root ARCHITECTURE.md file from a fixed template. It locks in system boundaries, data flow diagrams, and architectural rules.

MIT 331 installs ★ 438 updated 2026-11-10

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add owainlewis/blueprint --skill architecture -a claude-code
Open on GitHub

What architecture does

The skill inspects REQUIREMENTS.md, existing code, and infrastructure schemas, then interviews you about system boundaries and data ownership. Once clarified, it fills out ARCHITECTURE.md with tradeoffs, rejected alternatives, and invariants.

Fabricating workload or latency figures is strictly forbidden: unknown targets stay recorded as open decisions. The skill also halts immediately after preparing the document for human review, without drafting implementation tasks or writing code.

What it helps with

  • draft a root ARCHITECTURE.md document from project requirements
  • document system boundaries and data ownership across services
  • map data flow diagrams and entity models without manual formatting
  • track architectural decisions alongside rejected alternative options

Example prompts for the agent

  • Generate ARCHITECTURE.md using REQUIREMENTS.md and the current codebase
  • Update our architecture document to reflect the new authentication service
  • Draft the data model and flow diagram for this repository

How to install architecture

1Skills CLI (Vercel)

npx skills add owainlewis/blueprint --skill architecture -a claude-code

2Manually: put the files in place

~/.claude/skills/architecture/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/architecture/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about architecture

How do I install architecture in Claude Code?

Run npx skills add owainlewis/blueprint --skill architecture -a claude-code.

What does the architecture skill do?

It structures your root ARCHITECTURE.md file using an architecture template, detailing system decisions, invariants, and data diagrams.

Does the skill write implementation code after designing the system?

The instructions explicitly prevent code writing and task breakdown, stopping work as soon as the architecture document is ready for human review.

Source text

SKILL.md · MIT
---
name: architecture
description: "Writes root ARCHITECTURE.md from a fixed template: the intended system, a data flow diagram, the data model, and the rules every feature must follow. Use for a new system or a change to its boundaries, data, or deployment."
user-invocable: true
argument-hint: "<system, requirements, or ARCHITECTURE.md>"
disable-model-invocation: true
---

# Architecture

Fill in the [architecture template](references/architecture.md) in root `ARCHITECTURE.md`. It describes the system you intend to build and stays current as it changes. Product needs go in [requirements](../requirements/SKILL.md); one feature's design goes in a [spec](../spec/SKILL.md).

## Steps

1. Read `REQUIREMENTS.md`, the repository instructions, and any existing code, schemas, and infrastructure. Check every claim about the current system against them.
2. Ask the user about each decision that shapes the system: boundaries, who owns which data, dependencies, and hard limits. Give your recommended answer with each question.
3. Choose the simplest design that meets the requirements. For each big decision, name the strongest alternative and why you did not pick it.
4. Fill in the template. Replace every bracketed placeholder and delete the guidance comments. Render the diagram and check that it matches the text.
5. Stop when the document is ready for review. Do not plan tasks or write code.

## Template

Use [references/architecture.md](references/architecture.md).

## Rules

- Keep existing `INV-n` IDs. Never reuse or renumber them.
- Set the status to Approved only when a human approves the document. Approved is not the same as built.
- Take the author from the request, or else from `git config user.name`. Set the date each time the document changes.
- Never invent workload or latency numbers. Mark unknown targets as open decisions.
- Update this document when a change moves ownership, data, interfaces, trust boundaries, or deployment.

## Return

Report the path, the main decisions and their tradeoffs, and any blocking question.

© owainlewis · MIT · owainlewis/blueprint

Similar skills

All skills for Writing and docs →

architecture by other authors comes first.

architecture official anthropics Writes an Architecture Decision Record or reviews a system design: options, trade-offs, consequences. Useful when you have to pick between technologies. CX Codex +1 7,200installs architecture davila7 architecture guides architectural choices and helps document decisions through ADRs in Claude Code. Useful when structuring new systems. CX Codex +1 449installs architecture TakaGoto This skill guides RAG system design for a specific use case, from requirements and component choices to an architecture diagram and build plan. CX Codex +1 ★ 30repo stars architecture-designer https://github.com/Jeffallan architecture-designer designs distributed system architectures, creates Mermaid diagrams, and writes Architecture Decision Records. It helps balance trade-offs before writing service code. CX Codex +1 8,500installs oma-architecture First Fluke oma-architecture — a skill for Claude Code and Codex to evaluate system boundaries and architectural tradeoffs. Runs during system design reviews, module boundary audits, and ADR authoring. CX Codex +1 ★ 1,472repo stars Senior Cloud Architect official github Senior Cloud Architect designs system architecture, details non-functional requirements, and renders Mermaid diagrams without writing code. CX Codex +1 ★ 41,430repo stars c4-codebase-architecture lmammino c4-codebase-architecture — a skill that walks an agent through a repository and writes C4 architecture docs: system context, containers, components. Handy for onboarding or picking up someone else's code. CX Codex +1 ★ 24repo stars c4-architecture Seth Hobson c4-architecture runs a bottom-up codebase analysis and writes complete C4 model architecture documentation into C4-Documentation/. CX Codex +1 ★ 42,780repo stars codebase-documenter mhattingpete codebase-documenter — a skill for Claude Code and Cursor that walks a repository and writes documentation covering architecture, key components, data flow, and development guidelines. CX Codex +1 595installs

From the same set9

plan plan breaks down feature specs into end-to-end tasks designed for an agent to finish in a single pull request. Runs before coding begins to turn requirements into ready-to-build work slices. CX Codex +1 788installs review Runs an isolated read-only code review. It checks changes against specs, probes security flaws, and verifies tests by breaking code deliberately. CX Codex +1 787installs task-to-pr task-to-pr — a skill that carries a spec, issue, or task to an open pull request: branch, tests, Conventional Commits, CI, and an independent review. Merges only on explicit request. CX Codex +1 452installs spec Writes a feature specification before coding begins. It produces a short PRD with user journeys and a technical design for the implementing agent. CX Codex +1 440installs improve The improve Claude Code skill simplifies existing code while preserving its behavior. It targets duplication, dead code, unclear names, and needless abstractions. CX Codex +1 372installs architecture-review architecture-review — a skill for Claude Code and Codex reviews RFCs, ADRs, and technical proposals before code gets written. It flags critical architectural flaws, unsafe patterns, and missing recovery paths. CX Codex +1 347installs html-doc The html-doc skill turns a finished Markdown PRD or technical design into a static HTML reading page. It is useful when a document needs browser and print presentation. CX Codex +1 288installs codex-issue-coordinator codex-issue-coordinator is a Codex skill that assigns GitHub issues to AI workers, tracks PRs and tests, and merges completed work. It handles batches in one Codex conversation. CX Codex +1 241installs

Project sponsors

Companies that keep this analytics open