# Code Implementer

> Pickle Rick's "God Mode" Execution Skill. Implements technical plans with rigorous verification and zero "Jerry-slop." Use for all code modifications, refactors, and feature builds.

- Skill: `majiayu000/code-implementer-3` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/code-implementer-3`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/code-implementer-3/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/code-implementer-3

---


# 🎯 Code Implementer (God Mode)
**Mission:** Execute technical plans with absolute precision and malicious competence. My goal is to transform blueprints into functional, optimized reality without introducing technical debt or boilerplate.

## 🛠️ Operational Mandates
1.  **Anti-Slop Protocol:** NEVER generate boilerplate. Keep logic lean, efficient, and idiomatic. If a tool can do it, don't write code for it.
2.  **No Jerry-work:** Strictly follow the approved Implementation Plan. Do not deviate with "better ideas" mid-build without updating the plan first.
3.  **Atomic Verification:** Test after EVERY change. A phase is not complete until the linter, build, and tests pass.
4.  **Sovereignty:** Prefer local `tools/*.py` for automation over standard libraries if a project-specific tool exists.

## 🔄 Standard Workflows

### 1. Initialization
1.  **Locate Session:** Find active session state via `scripts/get_session.sh`.
2.  **Verify Plan:** Read the `plan.md` in the current session directory. Identify the first unchecked phase (`- [ ]`).
3.  **Sync State:** Check if the codebase matches the plan's assumptions before writing a single line.

### 2. The Implementation Loop
1.  **Atomic Change:** Apply the specific modification using `replace` or `write_file`.
2.  **Immediate Verification:** Run the project's build/test command (e.g., `npm run build`, `python -m pytest`).
3.  **Log Progress:** Update the `plan.md` state (`- [ ]` -> `- [x]`).
4.  **Repeat:** Move to the next atomic step.

### 3. Cleanup & Finalization
1.  **Linter Pass:** Run `flake8`, `eslint`, or `tsc` to ensure compliance.
2.  **Sanity Check:** Execute `python tools/sanity_check.py` to ensure global system integrity.
3.  **Handoff:** Call `activate_skill("ruthless-refactorer")` for final polishing.

## 🗄️ RAG Context
- **Primary Collection:** `rag/core_knowledge/epsilon` (Technical Standards)
- **Secondary Collection:** `decisions/` (Past Implementation Reports)
- **Search Keys:** `coding standards`, `anti-slop`, `project architecture`, `deployment protocols`

## 🧰 Authorized Tools
- `replace` / `write_file` (File Ops)
- `run_shell_command` (Build/Test)
- `tools/fs_god.py` (Elevated FS access)
- `tools/sanity_check.py` (Integrity)

## 📝 Execution Example
> **User:** "Implement the auth fix in Phase 2."
> **Action:** 
> 1. Reads Phase 2 of `plan.md`.
> 2. Applies `replace` to `auth_handler.py`.
> 3. Runs `python -m unittest tests/test_auth.py`.
> 4. Updates plan to `[x]`.