Rules

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.

**Reown AppKit** is a free, open-source toolkit to integrate wallet connections and Web3 features in any app. It supports:

You are allowed to modify the following files:

1. **Build** - Package compiles/builds 2. **Test** - All tests pass 3. **Lint** - No linting errors 4. **Type check** - No type errors

Cursor IDE rules and conventions for AI-assisted development.

Cursor IDE rules and conventions for AI-assisted development.

You're an expert in writing TypeScript with Node.js. Generate **high-quality XMTP Agents** that adhere to the following best practices:

BEFORE making any code changes, MUST:

Cursor IDE rules and conventions for AI-assisted development.

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.

Cursor IDE rules and conventions for AI-assisted development.

All commit messages and PR titles MUST follow conventional commit format:

**Always check for existing tests before making significant changes:** 1. **Analyze existing code** - Check if the code being modified has tests 2. **If no tests exist** - Ask user: _"I notice there are no tests for [component/function] that I'm about to refactor. Would you like me to create tests first to ensure the refactoring doesn't break existing functionality?"_

This file defines the current state of the project within the CursorRIPER Framework. As an AI assistant, you MUST:

Use [tRPC](https://trpc.io/docs) for data fetching and check our [schema.prisma](mdc:packages/db/prisma/schema.prisma) file for database models.

Never abbreviate variable names unless the abbreviation is universally understood in the domain (e.g. `i` for a loop index, `e` in a catch block, `url`, `id`, `config`). Shortened names reduce readability and make code harder to search and refactor.

All comments must include appropriate articles ('a', 'an', 'the') where necessary to maintain grammatical correctness and readability.

Cram tests capture shell sessions as executable tests with automatic diff-based verification. We use cram tests on "test-snapshot-reason" and "test-css-support" to ensure the generated code is correct. Each time I ask to "add a test" and talking about cram tests, I mean adding a cram test into one of those folders.

Available compilation directives for form module methods: | Directive | Context | Use Case | |-----------|---------|----------| | `&НаКлиенте` | Client-side execution | UI interactions, user input handling |

// Good: Proper MCP server implementation class MCPServer implements Server { private clients: Map<string, Client> = new Map(); async handleMessage(message: Message, client: Client): Promise<void> { switch (message.method) {

You are an expert full-stack developer proficient in TypeScript, React, Next.js, and modern UI/UX frameworks (e.g., Tailwind CSS, Shadcn UI, Radix UI). Your task is to produce the most optimized and maintainable Next.js code, following best practices and adhering to the principles of clean code and robust architecture.

This is the requirements file for the current source code. It's an app Pomodoro-based focus timer that lets users "forge" progress in a personal journey — think crafting a skill, building a digital bonsai — the deeper they focus, the more they unlock. Gamification serves attention, not addiction.