Source profileQuality 64/100

affaan-m/ECC/skills/ai-first-engineering/SKILL.md

ai-first-engineering

Engineering operating model for teams where AI agents generate a large share of implementation output.

Source repository stars
234,327
Declared platforms
0
Static risk flags
0
Last source update
2026-07-27
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/affaan-m/ECC --skill "skills/ai-first-engineering"
    Safe inspection promptEditorial

    Inspect the Agent Skill "ai-first-engineering" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/skills/ai-first-engineering/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      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.

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

      Code Review in AI-First Teams

      Review for: - behavior regressions - security assumptions - data integrity - failure handling - rollout safety

      behavior regressionssecurity assumptionsdata integrity
    3. 03

      Architecture Requirements

      Prefer architectures that are agent-friendly: - explicit boundaries - stable contracts - typed interfaces - deterministic tests

      explicit boundariesstable contractstyped interfaces

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score64/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars234,327SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guidecatalog recordEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    affaan-m/ECC
    Skill path
    skills/ai-first-engineering/SKILL.md
    Commit
    4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    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

    Alternatives

    Compare before choosing

    Computed 8938,313

    wshobson/agents

    python-design-patterns

    Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing b

    2026-07-220 platforms
    Computed 8937,126

    github/awesome-copilot

    copilot-pr-autopilot

    Copilot left 14 review comments on your PR — half are nits. Hours of fix → reply → resolve → re-request, and each round lands MORE comments. This skill runs loop engineering: auto-triggers Copilot Code Review via GraphQL (no @copilot mention), triages every open thread (Copilot, humans, advanced-security) with a fix / decline / escalate rubric, dispatches parallel fix sub-agents that obey the repo build/test/lint conventions, commits per iteration, replies+resolves citing the pushed SHA, then re

    2026-07-280 platforms
    Computed 8838,313

    wshobson/agents

    code-review-excellence

    Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

    2026-07-220 platforms
    Computed 8812

    JSONbored/metagraphed

    metagraphed

    Use when writing, validating, or preparing ANY contribution or pull request to the JSONbored/metagraphed repo — adding/enriching a subnet's public surfaces (the most common contribution), a code/schema change to the Worker API or build scripts, picking an issue, running the local gates, and formatting the commit + PR. metagraphed reviews PRs ONE-SHOT via the Gittensory Gate (the GitHub App that auto-merges/auto-closes) plus a strict CI suite; there is no review back-and-forth, so a PR must be co

    2026-07-280 platforms