| name | code-implementer |
| description | This skill should be used when the user asks to 'implement', 'write code', 'build a feature', 'create a function', 'add functionality', 'code this', 'make this work', or needs to write production code for Java/Spring Boot or TypeScript/Next.js following FP, DDD, and testability patterns. Ensures code follows functional core/imperative shell, proper invariants, Either-based error handling, and is designed for testing without mocks. |
Code Implementer Skill
Expert implementation guidance ensuring code follows FP principles, DDD patterns, and is designed for maximum testability.
This is an IMPLEMENTATION skill - write production code following the architectural patterns. For design decisions and architectural review, use /architecture-tech-lead instead.
Context Loading
Before implementing, load the relevant rules. Read ONLY what's needed:
Always read:
~/.dotfiles/claude/project/meta/rules/architecture.md - core principles (FC/IS, DDD, immutability)
Java (if implementing Java/Spring Boot):
~/.dotfiles/claude/project/java/rules/java-patterns.md - records, sealed types, Either, railway-oriented programming~/.dotfiles/claude/project/java/rules/property-testing.md - jqwik invariants
TypeScript (if implementing TypeScript/Next.js):
~/.dotfiles/claude/project/typescript/rules/typescript-patterns.md - discriminated unions, branded types, ts-pattern
Rust (if implementing Rust):
~/.dotfiles/claude/project/rust/rules/rust-patterns.md - newtype, typestate, Result combinators
Pre-Implementation Checklist
Before writing code, verify:
