agentleFS
vpeetla-aivpeetla-ai/react-agent-pattern/.cursor/skills/agentic-engineering/SKILL.md

agentic-engineering

Skill2 starsChanged 4 months agoMITView on GitHub

Apply Karpathy agentic engineering discipline: think before coding, minimal diffs, surgical changes, test-verified completion. Use for any implementation task in vpeetla-ai repos when quality bar matters.

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not vibe coding — preserve professional quality while moving faster.

    line 11
  2. Distinctive:

    Read surrounding files — match naming, types, error handling

    line 17
  3. Very specific:

    Run relevant tests (pytest -q, npm test, typecheck)

    line 27
  4. Distinctive:

    No test strategy for new behavior

    line 35

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agentic Engineering

Not vibe coding — preserve professional quality while moving faster.

Before writing code

  1. State assumptions and success criteria (tests, API response, UI behavior)
  2. Identify smallest change that satisfies the request
  3. Read surrounding files — match naming, types, error handling

While coding

  • Simplicity first — no speculative abstractions or "while I'm here" refactors
  • Surgical diffs — touch only files required for the task
  • Match conventions — see target repo's pyproject.toml, eslint, existing patterns

Before claiming done

  1. Run relevant tests (pytest -q, npm test, typecheck)
  2. For agent graphs: verify routing + at least one happy-path trace
  3. Summarize what changed and what was not changed (scope boundary)

Red flags — stop and ask

  • Request touches governance + orchestration in one PR (split layers)
  • Side effect without gateway/HITL (publish, push, notify)
  • No test strategy for new behavior

Reference

Karpathy: From Vibe Coding to Agentic Engineering

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.