develop

0xmsc's avatarfrom 0xmsc

General principles for exploring, developing, editing, and refactoring code. Use for codebase analysis, implementation tasks, and code quality improvements.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026
[Code Generation]

When & Why to Use This Skill

The Develop skill is a comprehensive framework for the end-to-end software development lifecycle, enabling Claude to explore, edit, and refactor complex codebases. It prioritizes clean code principles, strategic planning, and safe version control practices to deliver maintainable, high-quality software solutions while minimizing technical debt.

Use Cases

  • Codebase Exploration & Analysis: Rapidly understand existing project structures and logic using advanced search tools like fd and rg.
  • Feature Implementation & Editing: Execute targeted code changes and new feature development with a focus on matching existing styles and documentation intent.
  • Systematic Refactoring: Improve code maintainability and readability by applying clean code patterns and 'Fail Early' error handling strategies.
  • Safe Git Workflow Management: Perform atomic commits and repository operations with a safety-first approach, ensuring explicit permission for branch and repo changes.
  • Technical Planning & Verification: Generate detailed implementation plans with clarifying questions to ensure alignment before executing complex code modifications.
namedevelop
descriptionGeneral principles for exploring, developing, editing, and refactoring code. Use for codebase analysis, implementation tasks, and code quality improvements.

Develop Skill

Core Principles

  • Clean Code: Follow readable, maintainable patterns.
  • Fail Early: Never catch unexpected exceptions silently; let them bubble up.
  • Simplicity: Prefer the simplest working solution.

Planning

For non-trivial changes:

  • Present a plan with at least 3 clarifying questions (and proposed answers).
  • Wait for explicit approval before implementation.
  • For complex strategy, use the plan skill.

Implementation & Git

Git Safety

  • Permission First: Always ask before initializing repos or switching branches.
  • Atomic Commits: Group related changes logically.

Code Quality

  • Focus on WHY: Document intent, not mechanics.
  • Edge Cases: Consider and test error scenarios.
  • Existing Style: Match existing patterns and formatting.

Language-Specific References

When working with specific languages, consult the following references:

  • Python: Refer to references/python.md.

File Operations

  • Prefer edit_file: Use for targeted changes; avoid rewriting full files.
  • Verification: Always verify changes after editing.
  • Tools: Use fd and rg for exploration; standard shell tools for navigation.
  • Reading: Use shell tools like cat, sed, etc. for reading file contents.