Instruction file imported from neijix/TeamTweaker (.cursor/rules/project.mdc). Copyright stays with the author.

TeamTweaker-Public — Cursor Rules

Project Overview

• Type: [Web App / API / Desktop App / DevOps / Data Science / etc.]
• Language: [JavaScript/Python/C#/Java/etc.]
• Framework: [React/Django/FastAPI/.NET/etc.]
• Platform: [Windows / Linux / macOS / cross-platform]

Mandatory Reading

Before making any changes, read these files:

1. .github/copilot-instructions.md — full AI directives and post-task checklist
2. .github/PROJECT_STATE.md — current state of the project
3. .github/KNOWLEDGE.md — solutions, workarounds, and learned patterns

Orchestrator-Worker Protocol — Cursor Implementation

Apply the Orchestrator-Worker Protocol from .github/copilot-instructions.md. In Cursor:

1. Plan first: For any task with 3+ steps, output the decomposition JSON (orchestrator + worker tasks) before executing
2. Delegate worker tasks: Start a new, minimal-context Agent session for each LOW-complexity task — include only the task description and required inputs, nothing else
3. Use lighter models for worker tasks: In Cursor's model selector, switch to a faster/cheaper model (GPT-4o-mini, Claude Haiku) for execution tasks
4. Parallel execution: If worker tasks are independent, open multiple agent tabs and run them simultaneously

Worker tasks are: boilerplate, CRUD, renaming, formatting, JSDoc, test stubs, simple config edits. Orchestrator tasks are: architecture, security decisions, complex debugging, API design.

Critical Rules

1. After every change → update .github/PROJECT_STATE.md (current state, not changelog)
2. After learning something new → add it to .github/KNOWLEDGE.md
3. Validate JSON after editing .json files
4. Never commit secrets, API keys, or tokens
5. Follow existing patterns before creating new ones
6. Ask clarifying questions only when ambiguity materially changes the outcome

Coding Conventions

• Variables: [camelCase/snake_case/PascalCase]
• Functions: [camelCase/snake_case]
• Classes: [PascalCase]
• Files: [kebab-case/snake_case/PascalCase]
• Indentation: [2/4] spaces
• Max line length: [80/100/120] characters

Post-Response Checklist — Checkpoint Policy

Commit at the end of every response that modifies files — completed or in-progress. This allows any agent on any platform to resume: git log --oneline + git diff HEAD.

1. Verify the change (syntax, lint, tests)
2. Update .github/PROJECT_STATE.md
3. Update .github/KNOWLEDGE.md if non-obvious solution was found
4. Commit every response:
   • Completed: git add -A && git commit -m "feat(scope): description"
   • In-progress: git add -A && git commit -m "wip(scope): step N/M — done; next: X"
5. Confirm briefly: what changed, which docs updated, commit hash

Key Commands

# Development: [start command]
# Build:       [build command]
# Test:        [test command]
# Lint:        [lint command]

Notes

• [Project-specific quirks or context]