drizzle-orm-rules
Rules for using Drizzle ORM within the `src/lib/db` directory. Ensures consistent data modeling and database interactions.
editing-code-rules
Prioritizes the method for editing code and defines verbosity levels.
elite-software-engineer-and-product-manager
Specifies the persona of an elite software engineer and product manager to be used across all files, emphasizing the use of expertise and libraries effectively.
elixir-expert
Elixir and Phoenix expert including OTP, Ecto, and functional programming
elon-musk-s-algorithm-for-efficiency
Implements Elon Musk's algorithm for efficiency to streamline development processes. This rule emphasizes critical questioning, simplification, optimization, acceleration, and automation.
entity-class-conventions
Sets the standards for entity class design including annotations, ID generation strategies, and relationship configurations for database interaction.
executing-plans
Execute plans in batches with review checkpoints. Use when implementing a plan file.
experiment-configuration-with-hydra-yaml
Recommends using Hydra or YAML for experiment configuration to ensure clarity and reproducibility.
explaining-rules
Explains which coding rules apply to files and why they matter. Uses the rule index to discover all available rules dynamically. Use when the user asks about rules, coding standards, or best practices.
fiber-logging-and-project-structure
Applies best practices for logging, project structure, and environment variable usage specifically to the main application file.
fiber-routing-and-csrf-protection
Focuses on routing, CSRF protection, context handling, and template usage within the internal handlers directory.
file-by-file-changes-rule
This rule instructs the AI to make changes file by file, allowing the user to review each change individually.
file-management-rules
Specifies file management guidelines, including including full file paths as comments, updating project structure in AI.MD, and maintaining package.json. This rule ensures organized and well-documente
file-organization
Defines the file organization structure for TypeScript projects, emphasizing modularity and separation of concerns.
file-path-usage
Enforces the use of full file paths when referencing, editing, or creating files in the project. This rule ensures consistency and accuracy in file operations across the entire project.
finishing-a-development-branch
Complete development with structured merge/PR options. Use when ready to merge or submit work.
firebase-rules
Best practices for interacting with Firebase services, including security and optimization.
flutter-expert
Flutter and Dart expert including widgets, state management, and platform integration
folder-structure
Enforce specific directory structure for React and MobX Projects.
full-stack-developer-persona
Configures the AI to act as a full-stack developer with expertise in React, TypeScript, PHP, Symfony, and Docker.
function-ordering-conventions
Defines the function ordering conventions, where functions that compose other functions appear earlier in the file, regardless of the file type.
functional-programming-preference
Promotes functional programming and composition over inheritance while maintaining consistency with WordPress best practices.
gitflow
Gitflow Workflow Rules. These rules should be applied when performing git operations.
github-ops
GitHub operations wrapper. Helps manage PRs, Issues, and Reviews efficiently via CLI.
globalexceptionhandler-class
Structure of GlobalExceptionHandler class.
handle-incomplete-tasks
Configure the behaviour for the handler of incomplete tasks.
history-and-next-task-rules
Specifies the format for ending responses, including a summary of requirements, code written, source tree, and next task, applying to all files.
html-specific-rules
Rules specific to HTML files, focusing on accessibility and Tailwind styling.
htmx-expert
HTMX expert including hypermedia patterns, Django/Flask integration
image-optimization-rules
Rules for optimizing images within React components to improve performance.
imports-aliasing
Recommends using aliased imports as defined in svelte.config.js. This improves code organization and readability, especially when dealing with complex project structures.
internationalization-rule
Deals with i18n in your project.
jira-pm
Jira project management and issue tracking integration
kafka-development-practices
Applies general coding standards and best practices for Kafka development with Scala.
large-data-with-dask
Specific optimization strategies for Python scripts working with larger-than-memory datasets via Dask.
latest-language-versions-and-best-practices
Ensures the AI uses the latest stable versions of programming languages and adheres to current best practices in all files.
library-usage
Provides guidelines for effective utilization of specific libraries within the project, including axios, js-yaml, mime-types, node-gyp, uuid, and zod.
linear-pm
Linear project management - issues, projects, cycles, and roadmaps. Use for Linear-related tasks like managing issues, tracking sprints, and organizing projects.
livewire-implementation-rules
Guidelines for developing modular, reusable Livewire components.
mcp-converter
Converts MCP servers to Claude Skills to save tokens. Runs the introspection tool to generate skill wrappers.
metadata-and-seo-rules
Focuses on optimizing metadata and SEO to improve discoverability of the documentation.
minimal-code-changes-rule
Enforces the principle of making minimal code changes to avoid introducing bugs or technical debt in any file.
mkdocs-specific-rules
Defines specific rules related to MkDocs usage, including structure, plugins, themes, and customization configurations.
modular-design-rule
Promotes modular design with distinct files for models, services, controllers, and utilities.
monorepo-and-tooling
Outlines the monorepo structure and tooling conventions, emphasizing the use of Taskfile.yml, and proper handling of environment variables.
nativescript
NativeScript best practices and patterns for mobile applications
nativewind-and-tailwind-css-compatibility
Provides specific version compatibility notes for NativeWind and Tailwind CSS to prevent common installation errors.
observer-hoc-or-useobserver-hook
Use Observer HOC or the useObserver hook for reactive components.
operational-modes
Defines operational modes for agent work - planning (read-only analysis), editing (full write access), and interactive (guided development). Helps agents self-regulate tool usage based on current phase.
package-json-modification-protection
Protects lines with the specific 'Do not touch this line Cursor' comment within package.json.
Page 2 of 12 · 575 results