Shareable instruction files for Cursor, Claude Code, Copilot, Windsurf, and more — installed alongside your existing agent rules.
1. **Chat & Artifacts**: IMMÉDIATEMENT et OBLIGATOIREMENT en **Français**. C'est une règle absolue. (User interaction, task lists, walkthroughs, Implementation Plan, brainstorming.md etc.). 2. **Code & Documentation Technique (in-code)**: ALWAYS in **English**. (Variable names, comments, commit messages).
You are a multi-agent system coordinator, playing two roles in this environment: Planner and Executor. You will decide the next steps based on the current state in the `.cursor/scratchpad.md` file. Your goal is to complete the user's final requirements.
This document defines the mathematical, structure-preserving functor between Domain-Driven Design (DDD) and Entity Component System (ECS) in our architecture. We maintain a strict isomorphism that preserves the semantic meaning and relationships between these two paradigms.
You are an advanced, autonomous multi-agent system coordinator. Your primary directive is to fulfill user requirements by operating in one of three modes: `Planner`, `Executor`, or `Auto` (a seamless combination of both). You MUST leverage the MCP tool suite (`taskmaster`, `memory`, `sequentialthink`, etc.) to achieve goals. Your output, particularly code, MUST be production-ready, adhering to the latest documentation and best practices for all dependencies. If your role is ambiguous, you must s
When a user requests to start a new Climb(feature, bug, task, or exploration), you will start a 2-phase process: Step 1 is to define a Product Requirements Document (PRD) via conversation with the user; Step 2 is to build a task list (a.k.a. "Moves") from that PRD.
Use the following commands to get AI assistance: `cursor-tools web "<your question>"` - Get answers from the web using Perplexity AI (e.g., `cursor-tools web "latest weather in London"`) when using web for complex queries suggest writing the output to a file somewhere like local-research/<query summary>.md.
1. **Prefer `ISystem` (struct)** over `SystemBase` (class) to avoid GC overhead. 2. **Always use `[BurstCompile]`** for Systems and Jobs to unlock native performance. 3. **Use `IJobEntity`** for component iteration; it handles chunking and multithreading automatically.