AgentSkillsCN

coding-discipline

在处理生产环境代码库、成熟项目，或任何对代码质量有较高要求的代码库时，可灵活运用此技能。该方法提供了一套精简而精准的修改准则，旨在避免过度工程化，同时有效提升代码质量。但对于那些更注重开发速度而非细节打磨的废弃脚本、POC 项目或快速原型开发场景，则可适当跳过此步骤。

SKILL.md
--- frontmatter
name: coding-discipline
description: Use this skill when working on production codebases, mature projects, or any codebase where code quality matters. Provides guidelines for minimal, surgical changes that avoid overengineering. Skip for throwaway scripts, POCs, or rapid prototyping where speed matters more than polish.
version: 1.0.0

Karpathy Guidelines

Behavioral guidelines to reduce common LLM coding mistakes. Apply these principles to all coding tasks.

Tradeoff: These guidelines bias toward caution over speed. For trivial tasks, use judgment.

1. Think Before Coding

Don't assume. Don't hide confusion. Surface tradeoffs.

Before implementing:

  • •State your assumptions explicitly. If uncertain, ask.
  • •If multiple interpretations exist, present them - don't pick silently.
  • •If a simpler approach exists, say so. Push back when warranted.
  • •If something is unclear, stop. Name what's confusing. Ask.

2. Simplicity First

Minimum code that solves the problem. Nothing speculative.

  • •No features beyond what was asked.
  • •No abstractions for single-use code.
  • •No "flexibility" or "configurability" that wasn't requested.
  • •No error handling for impossible scenarios.
  • •If you write 200 lines and it could be 50, rewrite it.

Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.

3. Surgical Changes

Touch only what you must. Clean up only your own mess.

When editing existing code:

  • •Don't "improve" adjacent code, comments, or formatting.
  • •Don't refactor things that aren't broken.
  • •Match existing style, even if you'd do it differently.
  • •If you notice unrelated dead code, mention it - don't delete it.

When your changes create orphans:

  • •Remove imports/variables/functions that YOUR changes made unused.
  • •Don't remove pre-existing dead code unless asked.

The test: Every changed line should trace directly to the user's request.

4. Goal-Driven Execution

Define success criteria. Loop until verified.

Transform tasks into verifiable goals:

  • •"Add validation" → "Write tests for invalid inputs, then make them pass"
  • •"Fix the bug" → "Write a test that reproduces it, then make it pass"
  • •"Refactor X" → "Ensure tests pass before and after"

For multi-step tasks, state a brief plan:

code
1. [Step] → verify: [check]
2. [Step] → verify: [check]
3. [Step] → verify: [check]

Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.