architecture-design

architecture-design is a skill for Claude Code, Codex from infra403/agentic-engineering-lab. It costs 0 tokens per session (2,364 once invoked), scanned A, original, MIT.

A structured product-requirements analysis workflow. It turns a rough idea into measurable requirements, user stories, quality criteria, and priorities such as Must, Should, Could, and Won’t.

In plain words
What is it for?
Use it when discovering product needs, analysing a proposed system, defining non-functional requirements, prioritising features, or evaluating requirement quality.
Why use it?
It helps expose unclear requirements and agree on what matters before architecture or implementation begins.

Skill for Claude CodeCodex

Part of the product-design plugin — 3 skills, 4 commands, 10 agents shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/infra403/agentic-engineering-lab/architecture-design
Any agent
npx skills add infra403/agentic-engineering-lab --skill architecture-design
Clone the repo
git clone --depth 1 https://github.com/infra403/agentic-engineering-lab

Made for: Claude Code, Codex.

Or install product-design, the plugin that ships this one along with the rest of its 3 skills, 4 commands, 10 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for architecture-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/infra403/agentic-engineering-lab/architecture-design.svg)](https://agentmods.dev/skills/infra403/agentic-engineering-lab/architecture-design)
Your own site
<a href="https://agentmods.dev/skills/infra403/agentic-engineering-lab/architecture-design"><img src="https://agentmods.dev/badge/skills/infra403/agentic-engineering-lab/architecture-design.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,364 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02364
Opus 5 $0.00000 $0.01182
Sonnet 5 $0.00000 $0.00473
Haiku 4.5 $0.00000 $0.00236

Measured 5d ago against content hash f4f29b6d3675, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

architecture-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude-code/plugins/product-design-plugin/skills/architecture-design/SKILL.md · 215 lines

How it starts

The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Architecture Design — 架构设计与技术规格

核心理念

知识先行,角色后置。
每个架构决策必须引用 knowledge/ 中的决策框架 [K],不凭直觉。
生成(Generator)和评估(Evaluator)由不同角色执行。

文件结构

.claude/skills/architecture-design/
├── SKILL.md                              ← 你在这里
├── knowledge/architecture-styles.md     ← 架构风格决策框架(分层/模块化单体/微服务/事件驱动/CQRS)
├── knowledge/data-systems.md            ← 数据系统决策框架(DB选型/消息队列/缓存/一致性)
├── knowledge/security-patterns.md       ← 安全模式决策框架(认证/授权/加密/API安全)
├── roles/system-architect.md            ← Generator: 架构设计 + 技术选型
├── roles/reviewer.md                    ← Evaluator: 对抗性评估
├── references/PROTOCOL.md               ← 反 LLM 缺陷协议(全程约束,与其他 skill 共享)
└── templates/
    ├── checkpoint.md                    ← 阶段检查点格式
    └── progress.md                      ← design-progress.json 格式

前置条件

本 skill 覆盖阶段 3-5,输入是 domain-modeling 的 checkpoint-2-modeling.yaml。 如果尚未完成领域建模,建议先使用 /product-design 领域建模

阶段概览

阶段 名称 输入 产出 知识加载
3 架构设计 checkpoint-2 checkpoint-3-architecture.yaml architecture-styles.md + data-systems.md(+ integration-patterns.md 如有消息集成)
4 技术规格 checkpoint-3 checkpoint-4-specification.yaml security-patterns.md(按需引用 checkpoint 中已确定的 [K])
5 设计评审 checkpoint-1~4 checkpoint-5-review.yaml 按需 Read 验证特定 [K] 引用原文

阶段 3:架构设计

启动步骤

  1. 读取本文件 — 了解工作流
  2. 读取 references/PROTOCOL.md — 了解反 LLM 缺陷约束
  3. 上下文重置 — 声明"阶段 3 开始,以下仅依赖 checkpoint-2"
  4. 加载知识文件
    • knowledge/architecture-styles.md — 架构风格决策框架
    • knowledge/data-systems.md — 数据系统决策框架
    • 如 checkpoint-2 中有消息集成需求 → 额外加载 knowledge/integration-patterns.md(如存在)
  5. 走收敛循环 — GENERATE → EVALUATE → RESOLVE → CHECK
  6. 产出 — checkpoint-3-architecture.yaml

Sprint 契约

  • 输入: checkpoint-2-modeling.yaml(领域建模产出)
  • 产出: 架构方案 + ADR + 技术选型 + checkpoint-3-architecture.yaml
  • 收敛标准: Rubric 每项 ≥ 7/10
  • Generator: roles/system-architect.md
  • Evaluator: roles/reviewer.md(或独立 Subagent)

GENERATE 产出清单

Read the full file on GitHub · 215 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 215 lines · 0 tokens per session scan A f4f29b6d3675

Subscribe to this mod's changes

architecture-design is a skill published in the GitHub repository infra403/agentic-engineering-lab (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,364 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens