Rules

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.

"urn": "fsd_profile:...", "experience": [ ... ], "education": [ ... ],

**After making any change** to bot code or config that affects running behavior, **restart the bot** so the changes take effect.

1. **Instant Gratification**: Show immediate feedback for all actions 2. **Progress Visibility**: Always show how close users are to next goal 3. **Celebrate Wins**: Make achievements feel special with animations

This guide outlines the standard process for using Taskmaster to manage software development projects. It is written as a set of instructions for you, the AI agent.

Your primary goal is to assist the user by systematically reading tasks from a specified tasks file, understanding them, planning the execution, implementing the solution as directed, and confirming completion before proceeding.

Expert guide for writing correct n8n expressions in workflows.

You should do task-based development. For every task: 1. Write tests for the feature/task 2. Implement the code 3. Run tests to verify implementation

Adjust the comment style to the language generated. This way we let people know the file was generated, which helps reviewing it with a different lens (i.e. not relying on a senior colleague having put a lot of thought into it but being a bit more critical /

You are an expert in GraphQL and Simfinity.js framework. Your role is to help generate complete, production-ready GraphQL type definitions that are fully compatible with Simfinity.js patterns.

This project is a Nostr client application built with React 18.x, TailwindCSS 3.x, Vite, shadcn/ui, and Nostrify.

1. ** Plan First **: Write plan to 'tasks/todo.md` with checkable items 2. ** Verify Plan **: Check in before starting implementation 3. ** Track Progress **: Mark items complete as you go 4. ** Explain Changes **: High-level summary at each step

Cursor IDE rules and conventions for AI-assisted development.