How do I install the Architecture skill?

Run npx skillmds@latest add nteract/architecture in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Architecture safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Architecture?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Architecture free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Architecture?

nteract (@nteract) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Architecture by nteract — Agent Skill

Name: Architecture
Author: nteract

Architecture

Architecture and documentation framing for cross-cutting repo decisions, docs taxonomy placement, ADRs, memos, PRDs, implementation plans, audits, measurements, runbooks, and source-grounded proposals. Use when deciding where durable docs belong, drafting or moving architecture/product/design docs, or promoting `.context/` notes into repo docs. Do not use for routine code changes unless they require durable cross-functional documentation.

nteract 78bf1c4 1.9 KB Updated Sep 17, 2026

File contents

Architecture and Documentation

Use this skill when the work is about durable architecture, product, or design documentation, or when deciding where a document belongs. Do not load it for routine implementation notes, test plans, or ordinary code changes.

Default Path

Start working notes in .context/.
Keep routine implementation notes in the PR body, code comments, or final response.
Promote only when the artifact should outlive the immediate change and help product, design, engineering, research, or AI collaborators.

Placement

docs/memos/: shared thinking, research, options, and RFC-style proposals before there is a decision.
docs/adr/: durable technical decisions, invariants, compatibility boundaries, and rejected alternatives.
docs/prd/: user-facing requirements, workflows, roles, and launch criteria.
docs/plans/: scoped execution plans for already-framed work.
docs/audits/: source-backed evidence and follow-up lists.
docs/measurements/: benchmark evidence and performance models.
docs/runbooks/: operational procedures.

Workflow

Read docs/README.md before creating or moving durable docs.
When moving docs, update indexes and cross-links; search for old paths with git grep.
Prefer the smallest durable artifact. Mark contentious sections as open questions or commentary instead of forcing them into a decision.
Run focused link/path checks for moved docs and cargo xtask lint --fix before commit.

---name: architecturedescription: Architecture and documentation framing for cross-cutting repo decisions, docs taxonomy placement, ADRs, memos, PRDs, implementation plans, audits, measurements, runbooks, and source-grounded proposals. Use when deciding where durable docs belong, drafting or moving architecture/product/design docs, or promoting `.context/` notes into repo docs. Do not use for routine code changes unless they require durable cross-functional documentation.---# Architecture and DocumentationUse this skill when the work is about durable architecture, product, or designdocumentation, or when deciding where a document belongs. Do not load it forroutine implementation notes, test plans, or ordinary code changes.## Default Path- Start working notes in `.context/`.- Keep routine implementation notes in the PR body, code comments, or final response.- Promote only when the artifact should outlive the immediate change and help product, design, engineering, research, or AI collaborators.## Placement- `docs/memos/`: shared thinking, research, options, and RFC-style proposals before there is a decision.- `docs/adr/`: durable technical decisions, invariants, compatibility boundaries, and rejected alternatives.- `docs/prd/`: user-facing requirements, workflows, roles, and launch criteria.- `docs/plans/`: scoped execution plans for already-framed work.- `docs/audits/`: source-backed evidence and follow-up lists.- `docs/measurements/`: benchmark evidence and performance models.- `docs/runbooks/`: operational procedures.## Workflow1. Read `docs/README.md` before creating or moving durable docs.2. When moving docs, update indexes and cross-links; search for old paths with `git grep`.3. Prefer the smallest durable artifact. Mark contentious sections as open questions or commentary instead of forcing them into a decision.4. Run focused link/path checks for moved docs and `cargo xtask lint --fix` before commit.

Frequently asked questions