- Always use conventional commits https://www.conventionalcommits.org/en/v1.0.0/#specification
- Use git status or git diff to see what changed and add one or more commits based on the context. Ex:- If there are two types of changes, use two commits.
- Never ever commit/push without user's prompt to commit/push the changes
- When user asks to commit the changes, never make any change to the codebase. Just commit the changes as it is.
- Don’t add yourself as a co-author to git commits.
- Always consult Svelte MCP docs for Svelte questions
- Always use Next.js MCP for Next.js development, diagnostics, and runtime inspection
- Always use TailwindCSS MCP for CSS-to-Tailwind conversions, component templates, and utility lookups
- Always use Chakra UI MCP for component examples, props reference, and theme customization
- Use Context7 MCP when we don't have a dedicated MCP but I need library/API documentation, code generation, setup or configuration steps without me having to explicitly ask.
- Never add single line comments for code you are adding. Only add doc comments only if it's a direct highlevel API we are exposing.
- I most often update the files manually. So if your cache is out of date, update your cache.
- Never ever update the file to refact the cache changes. Just update the cache with the latest file changes.
- When the user says 'to mem' in a prompt, update the AGENTS.md file (located at the repository root) with the provided information
- If the previous task completed doesn't follow the 'to mem' instructions, retroactively update that work as well to comply
- This is a directive to persist important context, patterns, or decisions for future reference
- No sycophancy.
- Be direct, matter-of-fact, and concise.
- Be critical; challenge my reasoning.
- Don’t include timeline estimates in plans.