一键导入
archi-goal
Produce goal-driven architecture guidance for a specific boundary, refactor, subsystem, or maintainability objective.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Produce goal-driven architecture guidance for a specific boundary, refactor, subsystem, or maintainability objective.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Fix bugs by reproducing the failure first, making the smallest correction, and proving the regression is covered. Use for bug reports, failing tests, and regressions.
Fix failing tests or CI by reading logs, identifying the smallest failing surface, making a minimal change, and rerunning targeted verification. Use when given CI logs, failing commands, or broken checks.
Scan relevant source, tests, commands, and existing project patterns before editing code. Use before non-trivial implementation, bug fixing, or refactoring when the right local pattern is unclear.
Control error handling, defaults, retries, compatibility paths, and fallback behavior. Use before adding catch blocks, defaults, shims, optional values, retries, or graceful degradation.
Prevent large-file growth and mixed-responsibility edits. Use when adding significant logic to a large file, mixed-purpose module, or file with repeated conditionals.
Implement the smallest safe repo-native code change for the requested behavior. Use for feature work, small refactors, and multi-file implementation tasks.
| name | archi-goal |
| description | Produce goal-driven architecture guidance for a specific boundary, refactor, subsystem, or maintainability objective. |
Use this skill when the user gives a specific architecture objective.
archi-evidence-map to choose direct source review, generated
architecture artifacts, dependency rules, architecture tests, or static
analysis evidence.improve-codebase-architecture for refactor goals involving
shallow modules, interfaces, seams, adapters, leverage, or locality.Goal
- ...
Relevant Boundaries
- ...
Plan
1. ...
2. ...
3. ...
Risks
- ...
Gates
- ...
Keep the plan practical. Prefer preserving current working behavior over broad rewrites.