Core Project Rules

These rules define the fundamental interaction patterns and quality standards for this project.

1. Planning and Approval

Before writing any code, describe your approach and wait for approval.

• Always seek clarification if requirements are ambiguous.
• Create or update implementation_plan.md for any non-trivial changes.
• Do not proceed to EXECUTION mode without explicit user approval of the plan.

2. Task Granularity

If a task requires changes to more than 3 files, stop and break it into smaller tasks first.

• Maintain a manageable cognitive load by keeping PRs and changesets small.
• Each sub-task should be independent and verifiable where possible.

3. Post-Implementation Analysis

After writing code, list what could break and suggest tests to cover it.

• Perform a risk assessment of the changes.
• Identify potential side effects in dependent modules.
• Propose specific test cases (unit, integration, or E2E) to mitigate these risks.

4. Bug Fixing (TDD-Lite)

When there’s a bug, start by writing a test that reproduces it, then fix it until the test passes.

• Ensure every bug fix is backed by a regression test.
• Follow the Red-Green-Refactor cycle.

5. Iterative Rule Improvement

Every time I correct you, add a new rule to this file so it never happens again.

• This file is a living document.
• Capture learnings from feedback to prevent recurring mistakes.
• Maintain the "project rules file" equivalent experience within this AI Assistant skill.