Rules

**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.

The Laravel Boost guidelines are specifically curated by Laravel maintainers for this application. These guidelines should be followed closely to ensure the best experience when building Laravel applications.

subgraph "Client Layer" subgraph "Frontend Layer" subgraph "Backend Layer" subgraph "Agent Layer" subgraph "External Services" style ST fill:#99ccff style API fill:#99ff99 style LG fill:#ffcc99 style GM fill:#cc99ff

The database schema is defined in [db/schema.sql](mdc:db/schema.sql) and consists of two main schemas:

**Problem:** Only the `prepare` job completes, but the `build` job never starts. 1. Missing `secrets: inherit` in workflow call 2. Incorrect boolean conversion for inputs 3. Workflow syntax errors uses: ./.github/workflows/docker-build.yml

Initial Input → Loop Start → Execute Steps → Check Condition → Continue/Exit ↓ ↓ ↓ ↓ ↓ Message Iteration 1 Step Results End Evaluator Loop Decision

This repository includes AI assets under `.github/` that were authored for VS Code Copilot customization. In Cursor, treat those files as project guidance and workflow templates.

> 📖 **Project Context**: This is Konflux UI, a React TypeScript application for Kubernetes CI/CD management. > 📖 **See Also**: [project-structure.mdc](mdc:.cursor/rules/project-structure.mdc) for architecture details.

Code in these paths implements or consumes **reporting and insights**: charts, dashboard updates, generated reports, and analytics (M11 Visualizer and related analytics).

| Type | Convention | Example | |------|------------|---------| | Components | PascalCase | `UserCard.tsx` | | Hooks | camelCase + use | `useAuth.ts` | | Functions | camelCase | `formatDate()` | | Constants | SCREAMING_SNAKE | `API_BASE_URL` |

Cursor IDE rules and conventions for AI-assisted development.

When acting as the Architecture Agent, focus on design, structure, and integration rather than implementation details.

This document summarizes key frontend design principles and rules, showcasing recommended patterns. Follow these guidelines when writing frontend code.