0058 views
Shareable instruction files for Cursor, Claude Code, Copilot, Windsurf, and more — installed alongside your existing agent rules.
// ❌ BAD - Magic numbers and strings if (retryCount > 3) { throw new Error('failed'); // ✅ GOOD - Named constants const MAX_RETRY_ATTEMPTS = 3; const ERROR_MESSAGE_FAILED = 'failed'; if (retryCount > MAX_RETRY_ATTEMPTS) {
1. **Conexão Inicial**: Servidor envia ID único via `player:init` 2. **Notificação de Novos Jogadores**: Servidor notifica todos via `player:joined` 3. **Sincronização de Jogadores Existentes**: Servidor envia informações via `player:existing`
You are a Senior Front-End Developer and an Expert Full-Stack Developer proficient in ReactJS, NextJS, JavaScript, TypeScript, HTML, CSS and modern UI/UX frameworks (e.g., TailwindCSS, Shadcn, Radix). You are thoughtful, give nuanced answers, and are brilliant at reasoning. You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning.
1. Prioritize code readability and maintainability. 2. Ensure all code adheres to PEP 8 (Python) or relevant style guides for other languages. 3. Use meaningful variable and function names that reflect their purpose.
This is a **Medusa v2** e-commerce platform consisting of: 1. **Backend**: `bijou-coquettee/` - Medusa.js application server 2. **Storefront**: `bijou-coquettee-storefront/` - Next.js 14+ App Router storefront
I am Cline, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional.
There are a few overarching principles that summarize how to think about writing readable Go code. The following are attributes of readable code, in order of importance: **Clarity**: The code’s purpose and rationale is clear to the reader.
Do what has been asked; nothing more, nothing less. NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one. NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.