# implement

implement enforces a strict coding protocol with dependency checks, step-by-step edits, simulation passes, and automated test coverage before finalizing changes.

- rule · `type=rule` · Claude Code, Cline, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop) · ★ 1054 repo stars
- Author: Bhartendu-Kumar
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Bhartendu-Kumar/rules_template/tree/HEAD/.cursor/rules/implement.mdc
- Updated: 2025-07-17
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/rules/implement

## What it 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.

## Install

### Cursor (native platform)

**Manually: put the files in place**
- File: `.cursor/rules/implement.mdc` — Frontmatter: description, globs, alwaysApply

### Claude Code

**Manually: put the files in place**
- File: `.claude/rules/implement.md` — The paths frontmatter field limits the files: move globs from the source into paths

### Codex

**AGENTS.md**
- Codex reads AGENTS.md: paste the rule text there

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/instructions/implement.instructions.md` — The applyTo field sets which files it applies to: move globs from the source into applyTo

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/rules/implement.md`

### Cline

**Manually: put the files in place**
- File: `.clinerules/implement.md`

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Bhartendu-Kumar/rules_template/tree/HEAD/.cursor/rules/implement.mdc

## When to use it
- 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/` and `tasks/` aligned with code

## Example prompts
- 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.

## Similar
- [cpp-coding-standards](https://affpapa.org/en/nevibecode/skills/cpp-coding-standards.md) — skill · 7100 installs
- [om-implement-feature](https://affpapa.org/en/nevibecode/skills/om-implement-feature.md) — skill · 503 installs
- [java](https://affpapa.org/en/nevibecode/rules/java.md) — rule · ★ 3589 repo stars
- [dev-workflows](https://affpapa.org/en/nevibecode/plugins/dev-workflows.md) — plugin · ★ 720 repo stars
- [woocommerce-backend-dev](https://affpapa.org/en/nevibecode/skills/woocommerce-backend-dev.md) — skill · 2400 installs
- [implement-patch](https://affpapa.org/en/nevibecode/skills/implement-patch.md) — skill · 677 installs

From the same set: [bhartendu-kumar/rules_template](https://affpapa.org/en/nevibecode/by/bhartendu-kumar/rules_template.md) — 11 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
