プロセスの変化
1. 計画の品質はタイピングスピードより重要。 2. 評価のカバレッジは個人的な自信より重要。 3. レビューの焦点は構文からシステムの動作へ。
affaan-m/ECC
Use it for engineering tasks; the detail page covers purpose, installation, and practical steps.
npx skills add https://github.com/affaan-m/ECC --skill "docs/ja-JP/skills/ai-first-engineering"Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Limited to facts supported by the pinned source
AI 支援コード生成でリリースするチームのプロセス、レビュー、アーキテクチャを設計する際にこのスキルを使用します。
npx skills add https://github.com/affaan-m/ECC --skill "docs/ja-JP/skills/ai-first-engineering"The pinned source contains about 7 English words and 5 usable sections. That evidence supports a source profile, not a complete guide.
7 source words · 5 usable sections
What the source actually contains
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
1. 計画の品質はタイピングスピードより重要。 2. 評価のカバレッジは個人的な自信より重要。 3. レビューの焦点は構文からシステムの動作へ。
エージェントフレンドリーなアーキテクチャを優先する: - 明示的な境界 - 安定したコントラクト - 型付きインターフェース - 決定論的なテスト
レビュー対象: - 動作のリグレッション - セキュリティの前提 - データの整合性 - 障害処理 - ロールアウトの安全性
Choose a different workflow
Engineering operating model for teams where AI agents generate a large share of implementation output.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailUse it for engineering tasks; the detail page covers purpose, installation, and practical steps.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailWhen the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
The source record exposes this install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/ja-JP/skills/ai-first-engineering". Inspect the command and pinned source before running it.
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Compare before choosing
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
Engineering operating model for teams where AI agents generate a large share of implementation output.
Use it for engineering tasks; the detail page covers purpose, installation, and practical steps.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.
AI 支援コード生成でリリースするチームのプロセス、レビュー、アーキテクチャを設計する際にこのスキルを使用します。
エージェントフレンドリーなアーキテクチャを優先する:
隠れた慣習に広がる暗黙の動作を避ける。
レビュー対象:
自動化によって既にカバーされているスタイルの問題に費やす時間を最小化する。
AI ファーストの強いエンジニア:
生成されたコードのテストバーを引き上げる: