PluginBench
Skill
Pass
Audit score 90

ai-first-engineering

affaan-m/ecc

Engineering operating model for teams shipping with AI-assisted code generation.

What is ai-first-engineering?

AI-First Engineering is an operating model for teams where AI agents generate a significant portion of implementation output. It shifts focus from typing speed to planning quality, emphasizes evaluation coverage over anecdotal confidence, and reframes code review around system behavior rather than syntax.

  • Define process shifts prioritizing planning quality and evaluation coverage over traditional metrics
  • Establish architecture requirements favoring explicit boundaries, stable contracts, and typed interfaces
  • Refocus code review on behavior regressions, security, data integrity, and failure handling rather than style
  • Identify hiring signals for engineers who decompose work cleanly and produce high-signal prompts and evals
  • Raise testing standards with required regression coverage, edge-case assertions, and integration checks

How to install ai-first-engineering

npx skills add null --skill ai-first-engineering
Claude Code
Cursor
Windsurf
Cline

How to use ai-first-engineering

  1. 1.Review the process shifts section to understand how planning and evaluation priorities change with AI-assisted development
  2. 2.Assess your current architecture against the agent-friendly requirements (explicit boundaries, stable contracts, typed interfaces)
  3. 3.Adapt your code review checklist to focus on behavior, security, data integrity, and failure handling rather than syntax
  4. 4.Update hiring rubrics to evaluate decomposition skills, acceptance criteria definition, and prompt/eval quality
  5. 5.Implement the raised testing standard with regression coverage requirements and integration checks

Use cases

Good for
  • Designing engineering processes for teams using Claude or other AI agents for code generation
  • Establishing code review practices that account for AI-generated implementation
  • Setting architecture standards that work well with AI-assisted development workflows
  • Defining evaluation criteria for engineers working primarily with AI code generation tools
  • Establishing testing and quality standards for AI-generated code
Who it's for
  • Engineering managers building AI-assisted teams
  • Architects designing systems for AI-first development
  • Tech leads establishing code review practices with AI tooling
  • Teams adopting Claude Code, Cursor, or similar AI coding assistants

ai-first-engineering FAQ

How does code review change in AI-first teams?

Review shifts from syntax and style issues (handled by automation) to behavior regressions, security assumptions, data integrity, failure handling, and rollout safety.

What architecture patterns work best with AI agents?

Prefer explicit boundaries, stable contracts, typed interfaces, and deterministic tests. Avoid implicit behavior spread across hidden conventions.

What should hiring focus on for AI-first engineers?

Look for ability to decompose ambiguous work cleanly, define measurable acceptance criteria, produce high-signal prompts and evals, and enforce risk controls under delivery pressure.

Why does testing need to be stricter for generated code?

AI-generated code requires higher testing bars including required regression coverage for touched domains, explicit edge-case assertions, and integration checks for interface boundaries.

How does planning change with AI-assisted development?

Planning quality becomes more important than typing speed, since clear requirements and decomposition directly improve AI agent output quality.

Full instructions (SKILL.md)

Source of truth, from affaan-m/ecc.


name: ai-first-engineering description: Engineering operating model for teams where AI agents generate a large share of implementation output. metadata: origin: ECC

AI-First Engineering

Use this skill when designing process, reviews, and architecture for teams shipping with AI-assisted code generation.

Process Shifts

  1. Planning quality matters more than typing speed.
  2. Eval coverage matters more than anecdotal confidence.
  3. Review focus shifts from syntax to system behavior.

Architecture Requirements

Prefer architectures that are agent-friendly:

  • explicit boundaries
  • stable contracts
  • typed interfaces
  • deterministic tests

Avoid implicit behavior spread across hidden conventions.

Code Review in AI-First Teams

Review for:

  • behavior regressions
  • security assumptions
  • data integrity
  • failure handling
  • rollout safety

Minimize time spent on style issues already covered by automation.

Hiring and Evaluation Signals

Strong AI-first engineers:

  • decompose ambiguous work cleanly
  • define measurable acceptance criteria
  • produce high-signal prompts and evals
  • enforce risk controls under delivery pressure

Testing Standard

Raise testing bar for generated code:

  • required regression coverage for touched domains
  • explicit edge-case assertions
  • integration checks for interface boundaries