Menu
Settle types, module shape, and boundaries before implementation. Trigger: 'architect this', 'design module structure', 'settle types first'. For multi-module changes.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | architect-first |
| description | Settle types, module shape, and boundaries before implementation. Trigger: 'architect this', 'design module structure', 'settle types first'. For multi-module changes. |
| when_to_use | Activate BEFORE writing code that crosses function/module boundaries or changes public APIs. Do NOT use for single-function fixes or when types are obvious. |
| argument-hint | [feature or change to architect] |
| disable-model-invocation | true |
| license | Apache-2.0 |
| compatibility | ["opencode-native","claude-standalone","cursor-native","codex"] |
| metadata | {"author":"controlkeel","version":"1.1","category":"planning","ck_mcp_tools":["ck_memory_record","ck_memory_search","ck_review_submit"],"related_skills":["align","plan-slice","investigate"]} |
Settle types, module shape, and boundaries before writing code. Cheaper to fix the design now than rewrite callers later.
tdd-bugfix)ck_memory_search for prior decisions about the affected area.investigate skill if needed).[DECISION NEEDED].ck_memory_record (type: decision).ck_review_submit (review_type: plan, plan_phase: design_options). Wait for approval.ck_review_submit plan awaiting approvalck_memory_record with the designRun objective, repeatable improvement work under an immutable verifier and hard iteration, cost, time, and no-progress limits. Use for approved experiments with an automated metric and sandboxed worker.
Write concise, calm technical responses whose structure matches the decision, evidence, or sequence being communicated. Use when drafting substantial plans, reviews, findings, documentation, or completion summaries.
Operate inside a ControlKeel-governed session. Use this before code edits, shell execution, delegation, deploy work, or any task that needs CK validation, findings, budget, proof, or routing context.
Keep a governed session within budget. Use this before long-running agent work, bulk processing, or any task where spend pressure could change the plan.
Close a governed work session with validation, proof, findings, budget, digest, learning, and handoff checks. Use when the user asks to wrap up, stop for the day, or leave work ready for another agent.
Audit tests that may pass without proving the claimed behavior. Use for periodic test-quality reviews or when coverage looks healthy but regressions still escape.