Project Rules

Guidelines for solid-principles

TailwindCSS and styling guidelines for the Resource Collection project

Guidelines for unit, integration, and lifecycle tests in Go projects

This file provides guidelines for writing effective, maintainable tests using xUnit and related tools.

UI Styling Standards using Radix UI and Tailwind CSS

Guidelines for vcspull-pytest

Vertical Slice Architecture

Vision Camera Permission Handling

This is for documentation

Styles used in our application

Siren is a bewitching frontend for multiple linting tools that makes maintaining code quality a delightful experience. This file defines core architecture, key directories, and main constraints.

Apply this rule when creating new files, organizing code, or restructuring the PepperPy codebase to maintain consistent file structure and naming conventions

ORGANIZE rules in .cursor/rules with NNN-name.mdc format and MAINTAIN consistent structure

Guidelines for 009-virtualenv-usage

Guidelines for 033-client-style

MUST use LLM validation WHEN assessing rule quality TO ensure comprehensive evaluation

Guidelines for 08-dependencies

ENFORCE safe Rust practices and proper usage of unsafe code

ALWAYS check back-links.json for correct redirect URLs when adding links in markdown documents

MCP Server - MemoryMesh

MUST use comments WHEN writing complex code TO enhance readability and understanding.

Used when asked to enter 'Documentation Mode'

Used when asked to enter 'Security Auditor Mode'

ENFORCE a modular NestJS backend architecture with defined patterns

APPLY Remix framework standards WHEN developing with Remix TO ensure consistent and maintainable full-stack applications

MUST conduct integration testing WHEN components interact TO ensure system functionality.

ALWAYS use when writing or updating Markdown files to ensure consistent formatting and readability. This rule enforces standardized Markdown practices across all documentation.

MUST include technical documentation WHEN creating new features TO enhance code understandability.

ALWAYS use when creating a new PRD or modifying an existing one to ensure consistent structure and completeness. This rule enforces standardized PRD format with all required sections and proper documentation hierarchy.

Project Analysis - How we analyze and understand project content and structure