sefaertunc

How to structure implementation plans as files, progressive implementation, plan review process

Test philosophy, coverage strategy, test-first patterns, what to test and what not to

Domain-specific verification beyond tests, closing the feedback loop for web, API, CLI, data

Agent Routing Guide — when to spawn each installed agent

Branch naming, commit message format, PR workflow, worktree conventions, versioning policy

Session ending protocol, HANDOFF document format, seamless continuation between sessions

Core behavioral principles: when to ask, when to push back, when to simplify, how to make surgical changes

CLI-specific conventions: npm registry interaction, filesystem operations, JSON handling, settings merge, and configuration patterns for worclaude

Context budget awareness, when to compact, when to clear, subagent offloading

Terminal UI patterns: display.js visual system, Chalk styling, Ora spinners, Inquirer prompts, and CLI output conventions for worclaude

Effective prompting patterns for working with Claude, demanding quality, writing specs

When to use subagents, how many, context hygiene, worktree isolation patterns

How Claude writes rules for itself, when to update CLAUDE.md, keeping it lean and effective

Multi-agent orchestration patterns: when to use coordinator mode, worker prompts, parallel execution

Five-layer memory architecture: where each fact lives, how layers interact, when to promote learnings

Architectural patterns, naming conventions, file organization, and error handling for the worclaude CLI project

OWASP-based security checklist any agent can reference when reviewing or writing code