Skip to content

ComeOnOliver/skillshub / skills/affaan-m/everything-claude-code/ai-first-engineering

ai-first-engineering

Verified

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

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
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall