菜单
Design architecture, components, and data flows
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Review dimension for naming, idiom, comment debt, and AI tells against the codified per-language and prose standards. Invoked by reviewer agents over one module shard.
Recipe for writing C in the runtime, module placement and the ownership and control-flow discipline. Invoked by writer agents when a C unit is dispatched.
Recipe for writing Clojure, Functional Core / Imperative Shell at the function level (namespaces by domain), native wrappers, and the boundary discipline. Invoked when writing Clojure for the project.
Recipe for writing Elixir, pure functions in modules as the core and GenServer plus OTP as the shell, supervision trees, and NIF discipline for the C and Zig edge. Invoked when writing Elixir for the project.
Recipe for any English the agent produces in this project, commits, comments, docstrings, ADRs, design docs, skill bodies, changelog, error messages, project guides. Optimizes for terse, humanized prose with no em dashes and no AI tells. Invoke for any prose-writing activity.
Recipe for writing Zig, native bodies and edge wrappers, the allocator and lifetime discipline, and the hot-path rules. Invoked when writing or editing any Zig source.
| name | design-technical |
| description | Design architecture, components, and data flows |
| user-invocable | false |
Design a simple, evolvable system with clear boundaries and data flows. Prefer operational simplicity; make tradeoffs explicit and recorded. Express the design in Functional Core / Imperative Shell terms for the project's active languages (C, Zig, Clojure, Elixir).
project-meta.md, problem-description.md, product-requirements.md,
risk-assumption-review.md, decision-log.md, and open-questions.md.
The ux-design-guide.md is optional; proceed without it when the UX step
was skipped. If a required prerequisite is missing, return
blocked: <which artifact>.[Blocking] items affecting technical-design.md.decision-log.md with date, decision, rationale,
tradeoff.~/.agentic-sdk/<project>/artifacts/planning/technical-design.md with: Metadata,
System Shape, Domain Boundaries, Components, Key Flows, Data Model,
Integrity Strategy, Audit and Compliance, Integrations, Technology Stack
(backend, frontend if applicable, data, infrastructure, observability,
testing), Repository and Delivery Conventions (structure, command surface,
CI outline, environment model), Evolution Strategy, Known Tradeoffs. Split
components and modules along the FC/IS line.Owns system architecture, components, data flows, and the stack. create-backlog owns the work breakdown; design-ux owns the interface. Reached by plan-system.
One line: the artifact written and a terse status, or blocked: <reason>.