Skill/Coding/Methodology Inspired

Karpathy Guidelines

Four always on instincts preventing common agent coding failures.

What It Does

A compact behavioral posture enforcing verified assumptions, minimal surgical diffs, explicit completion definitions, and deletion of speculative code.

Origin and Adaptation Notes

Distills the primary failure modes of agent coding sessions into concise standing rules small enough to remain active in context indefinitely.

Attribution: Distilled from public reflections and engineering commentary by Andrej Karpathy.

When to Activate

•Active coding, debugging, refactoring, and reviewing tasks
•Maintaining surgical pull request diffs during agent sessions

When to Avoid

•Non coding writing requests

Skill Specification and Runtime Setup

Full Instruction Specification

# Karpathy Guidelines Specification

## Overview
A compact behavioral posture enforcing verified assumptions, minimal surgical diffs, explicit completion definitions, and deletion of speculative code.

## Rationale
Distills the primary failure modes of agent coding sessions into concise standing rules small enough to remain active in context indefinitely.

## Core Principles
* Always verify environment constraints and dependencies before executing.
* Enforce negative constraints and reject speculative abstractions.
* Validate output against stated acceptance rubrics.

## Execution Workflow
1. Discovery: Map requirements and inspect active context.
2. Decomposition: Break down the task into discrete, verifiable phases.
3. Execution: Implement surgical changes preserving existing code architecture.
4. Verification: Test all criteria before declaring completion.