implement — Claude Code rule: what it does, how to install
implement enforces a strict coding protocol with dependency checks, step-by-step edits, simulation passes, and automated test coverage before finalizing changes.
no license ★ 1,054 updated 2025-07-17
.cursor/rules/implement.mdcWhat implement does
This rule establishes a disciplined execution workflow for coding sessions. Before editing anything, the assistant must inspect materials under docs/ and tasks/, trace data pathways end-to-end, and prepare an explicit plan covering potential blast radiuses and tradeoffs. Modifying functioning components without direct necessity is forbidden.
Changes follow a staged routine: the assistant tests its assumptions via simulation runs before altering application files. Each feature rollout stays focused on a single logical slice. The agent writes test suites into dedicated files and must run them independently rather than asking you to verify the results. Once code changes succeed, it syncs updates back into docs/ and tasks/.
Without docs/ or tasks/ directories and a referenced @memory.mdc file in your workspace, the agent wastes context looking for missing documentation targets.
What it helps with
- prevent unexpected regressions inside established codebase areas
- enforce modular code composition with smaller functions and files
- compel the assistant to run test suites on its own
- keep architecture notes in
docs/andtasks/aligned with code
Example prompts for the agent
- Implement the payment processing endpoint following the execution protocol and verify it with tests.
- Refactor the monolithic sync handler into smaller units and test edge cases.
How to install implement
Manually: put the files in place
.cursor/rules/implement.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.claude/rules/implement.mdThe paths frontmatter field limits the files: move globs from the source into paths
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.github/instructions/implement.instructions.mdThe applyTo field sets which files it applies to: move globs from the source into applyTo
Manually: put the files in place
.devin/rules/implement.mdManually: put the files in place
.clinerules/implement.mdStep by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules
Questions about implement
How to install implement in Claude Code?
Create the file .claude/rules/implement.md in your project root and save the rule content there.
What does the implement rule enforce?
It commands the model to inspect architecture dependencies, draft an impact analysis, apply isolated changes, and execute unit tests before stopping.
Does the rule require specific files in the repository?
Yes, it expects docs/ and tasks/ folders for project tracking, along with a @memory.mdc reference for state documentation.