Files
ECC/pi/core/skills/ai-first-engineering/SKILL.md
T
Affaan Mustafa c70874fae9 feat(pi): curated pi/core skills+prompts profile, CI load test, and 2.2.2 release sync (#3264)
Adds a curated, Pi-native, skills+prompts-only profile at pi/core/ for downstream packagers that mirror GitHub Releases.

- manifests/pi-core.json: explicit include lists, per-item exclusion reasons, curation rules, safety allowlists; every root skill and command must be classified.
- scripts/build-pi-core.js regenerates pi/core deterministically (package.json from VERSION, LICENSE, README.md, CURATION.md, skills/, commands/); --check fails CI on drift. council is renamed ecc-council inside pi/core only.
- Safety checks: no callable endpoints outside the allowlist, no npx/curl|sh/pip install, no secrets, no absolute home paths, no symlinks, valid frontmatter, no duplicate names.
- CI: build + drift check and an offline Pi CLI load test of pi/core.
- Release: VERSION, package.json and pi/core/package.json at 2.2.2, CHANGELOG, tag-triggered release verification, and a two-week cadence in CONTRIBUTING.md.

pi/core: 123 of 293 skills and 24 of 94 commands; 35,006 characters of skill description text.
2026-09-29 20:24:05 -05:00

1.4 KiB

name, description, metadata
name description metadata
ai-first-engineering Engineering operating model for teams where AI agents generate a large share of implementation output. Use when setting team process, review gates, or ownership rules for a codebase largely written by agents.
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