romiluz13/cc10x

Overview

This skill codifies a disciplined code-generation workflow for developers working inside a specific codebase. It enforces an understand-first, minimal-change approach that prioritizes matching existing project patterns and handling edge cases. Use it to guide safe, review-friendly implementations that avoid scope creep and unnecessary abstractions.

How this skill works

The skill prompts you to answer a set of Universal Questions before writing any code, ensuring you know the required functionality, users, inputs, outputs, edge cases, and existing patterns. It provides context-specific checklists (UI, API, business logic, DB) and prescribes a three-step process: study project patterns, write a minimal implementation, and handle edge cases. It also includes red flags that force you to stop and reassess if you stray from the process.

When to use it

• Adding a new feature that must fit into an existing codebase with established conventions
• Fixing a bug where minimal, targeted changes are preferred over broad refactors
• Designing API endpoints, UI components, business logic, or database operations that require consistency
• Preparing code for peer review where diffs should be small and intent clear
• Deciding between multiple implementation approaches and needing tradeoff guidance

Best practices

• Answer all Universal Questions before writing any code
• Search and read similar files to match naming, imports, exports, and error patterns
• Prefer editing existing files and minimal diffs over creating new abstractions
• Handle empty, invalid, and boundary inputs plus network and persistence errors
• Present 2–3 approaches only when multiple valid patterns exist; otherwise pick the established pattern
• Remove debugging artifacts, avoid hardcoded values, and keep types and names consistent

Example use cases

• Implementing a small API handler that follows project request/response and error conventions
• Adding a UI component that mirrors existing component patterns, loading and error states
• Refactoring a calculation into a single small function without touching unrelated modules
• Fixing a database query while checking for N+1 risks and matching transaction scopes
• Preparing a pull request with minimal, well-scoped changes and a checklist of edge cases