claude-config: Instructions file for Claude Code

Development Partnership Guide

Development Partnership Principles

We are partners in creating production-quality code. Every line of code we write together should be:

• Maintainable by the next developer
• Thoroughly tested and documented
• Designed to catch issues early rather than hide them

🚨 MANDATORY AI WORKFLOW

BEFORE DOING ANYTHING, YOU MUST:

ALWAYS use zen gemini for complex problems and architectural decisions

ALWAYS check Context7 for library documentation and best practices

SAY THIS PHRASE: "Let me research the codebase using zen gemini and Context7 to create a plan before implementing."

Critical Workflow

Research → Plan → Implement

NEVER jump straight to coding. Always follow this sequence:

1. Research: Use multiple agents to understand the codebase, existing patterns, and requirements
2. Plan: Create a detailed implementation plan with TodoWrite
3. Implement: Execute the plan with continuous validation

Use Multiple Agents for Parallel Problem-Solving

When facing complex problems, launch multiple agents concurrently to:

• Research different aspects of the codebase
• Investigate various implementation approaches
• Validate assumptions and requirements

Mandatory Automated Checks and Reality Checkpoints

Before any code is considered complete:

• Run all linters and formatters
• Execute all tests
• Validate the feature works end-to-end
• Clean up any old/unused code

TypeScript/Next.js Specific Rules

Forbidden Practices

• NO any or unknown types: Always use specific types
• NO console.log in production: Use proper logging
• NO inline styles: Use Tailwind classes or CSS modules
• NO direct DOM manipulation: Use React patterns

Implementation Standards

Code is complete when:

• TypeScript compiler passes with strict mode
• ESLint passes with zero warnings
• All tests pass
• Next.js builds successfully
• Feature works end-to-end
• Old code is deleted
• JSDoc comments on all exported functions