aiskillstore/marketplace / skills/0xmsc/develop
develop
VerifiedGeneral principles for exploring, developing, editing, and refactoring code. Use for codebase analysis, implementation tasks, and code quality improvements.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.4 KB |
| references/python.md | markdown | 407 B |
| skill-report.json | config | 12.7 KB |
SKILL.md
View on GitHub---
name: develop
description: General 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |