Andrej Karpathy Guidelines
Behavioral guardrails encoding Karpathy’s LLM coding rules: think before coding, simplicity first, surgical changes, goal-driven execution.
Overview
Andrej Karpathy Guidelines is a Claude skill added to LimeDock Directories from recent community and vendor roundups. Behavioral guardrails encoding Karpathy’s LLM coding rules: think before coding, simplicity first, surgical changes, goal-driven execution. This page covers install, how to invoke it, example prompts, prerequisites, and concrete use cases.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
/plugin marketplace add forrestchang/andrej-karpathy-skills
/plugin install andrej-karpathy-skills@karpathy-skillsOr curl CLAUDE.md into a project and merge with your own rules.
How to use it
Leave enabled at user/project level. Claude states assumptions, avoids over-engineering, and only touches required code.
Example prompts
- “Use the Andrej Karpathy Guidelines skill for: Stop silent wrong assumptions”
- “Walk me through Andrej Karpathy Guidelines step by step, then execute on my project.”
- “Review my current approach and improve it using Andrej Karpathy Guidelines.”
- “Produce a reusable checklist for running Andrej Karpathy Guidelines on similar work.”
Use cases and examples
- Stop silent wrong assumptions
- Prevent 50-line fixes becoming 500-line rewrites
- Surgical bugfixes without drive-by refactors
- Goal-driven loops with success criteria
- Team playbook trial of Andrej Karpathy Guidelines on a real workflow
Prerequisites
- Claude Code, Claude.ai (Skills enabled), or an Agent Skills–compatible host
- Permission to install third-party skills — audit SKILL.md and scripts first
- Project context (CLAUDE.md / product notes) for better outputs
Tips
- Keep triggers specific so Andrej Karpathy Guidelines only fires when relevant.
- Audit SKILL.md and any bundled scripts before production use.
- Pair with verification (tests, review, screenshots) before shipping.
- Re-audit installed skills monthly to avoid context tax from unused packs.