メニュー
Design metrics that measure architecture health (coupling, modularity, scalability). Automate fitness function checks in CI/CD. Use when establishing quality gates or measuring architectural degradation.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/sethdford/claude-skills --skill fitness-function-designコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Identify and avoid common architectural mistakes. Recognize patterns of failure. Use when reviewing designs or learning from mistakes.
Practice architectural design with structured problems. Time-limited design challenges. Use for skill development, interviews, team exercises.
Reference catalog of proven architecture patterns. Know when to apply each pattern, tradeoffs, and examples. Use as reference when designing systems.
SOC 職業分類に基づく
SKILL.md を表示中
| name | fitness-function-design |
| description | Design metrics that measure architecture health (coupling, modularity, scalability). Automate fitness function checks in CI/CD. Use when establishing quality gates or measuring architectural degradation. |
Design quantifiable metrics to measure architecture health and automatically enforce quality standards.
You are designing fitness functions to measure architectural quality. Create metrics for coupling, modularity, scalability, performance. Automate checks in CI/CD for continuous feedback.
Based on evolutionary architecture and fitness function research (Thoughtworks):
Identify Key Quality Attributes: What matters most? Scalability? Security? Testability? Maintainability? Pick 3-4.
Define Metrics for Each Attribute: Scalability: p99 latency < 200ms, peak RPS capacity. Security: zero secrets in code, all dependencies scanned. Testability: > 80% test coverage, no untestable dependencies.
Set Thresholds: Below threshold: pass. Above: fail (blocks merge). Make thresholds achievable but stretch. Too strict: teams bypass. Too loose: no effect.
Automate Checks: Integrate into CI/CD. Run on every PR. Parse test coverage reports, dependency scanners, performance benchmarks. Fail PR if fitness functions breach.
Monitor and Adjust: Track metrics over time. Are they trending right? Do developers understand why they matter? Adjust thresholds based on feedback and organizational priorities.
