Claude Cursor Skill

incremental-approach

Build in verified increments rather than one speculative block: smallest viable change first, verify, then extend; prototype the risky part before committing to a design; batch edits to one file into a single operation. Load when planning a large or multi-file change, when uncert

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download goldziher-ai-rulez-internal_builtins_universal_token-efficiency_skills_incremental-approach-ca967ad.zip · 0 KB

goldziher/ai-rulez 162 16 forks MIT Updated 5h ago

Part of goldziher/ai-rulez — 151 skills

Install

skills CLI

npx skills add https://github.com/Goldziher/ai-rulez/tree/main/internal/builtins/universal/token-efficiency/skills/incremental-approach

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install goldziher-ai-rulez@llmmart

Git git clone https://github.com/Goldziher/ai-rulez.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole goldziher/ai-rulez collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Start with the smallest viable change, verify it works, then extend. Implement one piece, test, move on.
Avoid generating large blocks of speculative code.
When uncertain about an approach, prototype the critical part before committing to the full implementation.
Batch multiple edits to the same file into one operation, and prefer multi-file search over reading files one by one when exploring.

Files (ai-rulez)

SKILL.md 850 B

---
name: incremental-approach
description: "Build in verified increments rather than one speculative block: smallest viable change first, verify, then extend; prototype the risky part before committing to a design; batch edits to one file into a single operation. Load when planning a large or multi-file change, when uncertain which of several approaches will work, or when tempted to generate a whole subsystem before running anything."
---

- Start with the smallest viable change, verify it works, then extend. Implement one piece, test, move on.
- Avoid generating large blocks of speculative code.
- When uncertain about an approach, prototype the critical part before committing to the full implementation.
- Batch multiple edits to the same file into one operation, and prefer multi-file search over reading files one by one when exploring.