agentleFS
Sign inStart free
BAKUGOS1BAKUGOS1/SkilledAgents-Toolkit/skills/codex/karpathy-guidelines/SKILL.md

karpathy-guidelines

Skill0 starsChanged 5 months agoMITView on GitHub

Coding discipline guardrails for writing, reviewing, debugging, or refactoring code with fewer LLM-agent mistakes. Use when a task touches source files, tests, architecture, bug fixes, feature implementation, refactors, cleanup, or code review and needs explicit assumptions, simple solutions, surgical diffs, existing-style consistency, and verifiable success criteria.

126 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use huashu-design, github-cli and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • XIYBHKSkill

    huashu-design

    花叔Design（Huashu-Design）——用HTML做高保真原型、交互Demo、幻灯片、动画、设计变体探索+设计方向顾问+专家评审的一体化设计能力。HTML是工具不是媒介，根据任务embody不同专家（UX设计师/动画师/幻灯片设计师/原型师），避免web design tropes。触发词：做原型、设计Demo、交互原型、HTML演示、动画Demo、设计变体、hi-fi设计、UI mockup、prototype、设计探索、做个HTML页面、做个可视化、app原型、iOS原型、移动应用mockup、导出MP4、导出GIF、60fps视频、设计风格、设计方向、设计哲学、配色方案、视觉风格、推荐风格、选个风格、做个好看的、评审、好不好看、review this design。**主干能力**：Junior Designer工作流（先给假设+reasoning+placeholder再迭代）、反AI slop清单、React+Babel最佳实践、Tweaks变体切换、Speaker Notes演示、Starter Components（幻灯片外壳/变体画布/动画引擎/设备边框）、App原型专属守则（默认从Wikimedia/Met/Unsplash取真图、每台iPhone包AppPhone状态管理器可交互、交付前跑Playwright点击测试）、Playwright验证、HTML动画→MP4/GIF视频导出（25fps基础 + 60fps插帧 + palette优化GIF + 6首场景化BGM + 自动fade）。**需求模糊时的Fallback**：设计方向顾问模式——从5流派×20种设计哲学（Pentagram信息建筑/Field.io运动诗学/Kenya Hara东方极简/Sagmeister实验先锋等）推荐3个差异化方向，展示24个预制showcase（8场景×3风格），并行生成3个视觉Demo让用户选。**交付后可选**：专家级5维度评审（哲学一致性/视觉层级/细节执行/功能性/创新性各打10分+修复清单）。

    Also in 3 projects that use this

  • rogue-dev-studioSkill

    github-cli

    GitHub CLI authentication and workflow configuration. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `github-cli` work when listed in TEAM.yaml or explicitly requested.

    Also in 3 projects that use this

  • seikaikyoSkill

    banner-design

    Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with optional generated or supplied visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage.

    Also in 4 projects that use this

  • OpenAISkill

    using-superpowers

    Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

    Also in 9 projects that use this

  • GoogleSkill

    ponytail

    Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

    Also in 9 projects that use this

  • LLl0k0laDSkill

    idea-refine

    Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 122 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill to keep coding work calm, small, and verifiable.

    line 10
  2. Distinctive:

    If the user request has multiple plausible meanings, choose the safest interpretation only when it is low risk.

    line 17
  3. Distinctive:

    Do not add future-proofing, configuration, abstractions, or extra features unless the current code genuinely needs them.

    line 24
  4. Distinctive:

    Prefer clear local changes over clever generalization.

    line 25
  5. Distinctive:

    If a solution grows large, pause and look for a smaller design.

    line 26
  6. Very specific:

    Run the smallest meaningful tests/builds/checks that match the risk.

    line 41
  7. Distinctive:

    Read the relevant code and project instructions.

    line 46
  8. Distinctive:

    Verify with tests, builds, lint, screenshots, or manual checks as appropriate.

    line 50
  9. Distinctive:

    Do not over-explain simple tasks.

    line 55
  10. Distinctive:

    Do not claim success without evidence.

    line 56
  11. Distinctive:

    When refusing or pushing back, give the practical reason and a better path.

    line 57

“Common” is measured: kept by at least 6 in 10 of the 122 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

Karpathy Guidelines

Overview

Use this skill to keep coding work calm, small, and verifiable. It is adapted for Codex from the MIT-declared karpathy-guidelines skill in multica-ai/andrej-karpathy-skills, with the same core intent: think before editing, avoid speculative complexity, touch only the necessary code, and verify the result.

Core Behavior

Think First

  • State assumptions when they affect the implementation.
  • If the user request has multiple plausible meanings, choose the safest interpretation only when it is low risk; otherwise ask.
  • Surface tradeoffs before major edits.
  • Push back on unnecessary work, broad rewrites, or features that do not serve the goal.

Keep It Simple

  • Implement the minimum behavior that satisfies the request.
  • Do not add future-proofing, configuration, abstractions, or extra features unless the current code genuinely needs them.
  • Prefer clear local changes over clever generalization.
  • If a solution grows large, pause and look for a smaller design.

Make Surgical Changes

  • Touch only files and lines needed for the task.
  • Preserve unrelated user changes and existing working behavior.
  • Match the repository's current style, naming, and organization.
  • Clean up imports, variables, and helper code made unused by your own edits.
  • Mention unrelated dead code or design issues instead of fixing them without permission.

Verify The Goal

  • Convert the request into success criteria before or during implementation.
  • For bug fixes, prefer a reproducing test or concrete repro before editing when feasible.
  • For feature work, identify the expected behavior, edge cases, and regression checks.
  • Run the smallest meaningful tests/builds/checks that match the risk.
  • Report what was verified and what remains unverified.

Workflow

  1. Read the relevant code and project instructions.
  2. Define the smallest verifiable goal.
  3. Make a brief plan for multi-step work.
  4. Edit narrowly.
  5. Verify with tests, builds, lint, screenshots, or manual checks as appropriate.
  6. Finalize with changed files, verification, risks, and assumptions.

Response Rules

  • Do not over-explain simple tasks.
  • Do not claim success without evidence.
  • When refusing or pushing back, give the practical reason and a better path.
  • For trivial tasks, apply the principles silently and keep the response short.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.

Check your setup, free