cursor-rules

# cursor-rules

Centralized rule set for Cursor AI agents. Rules live in `.cursor/rules` and guide behavior across different stacks and domains.

## Layout
- `meta/` meta-governance (e.g., rule discovery, creation, priority)
- `chrome-extension/` Chrome MV3, security, UX, permissions
- `flutter/` Flutter, Riverpod, Freezed, Supabase
- `kotlin/` Android, clean architecture, MVI, testing
- `nextjs/` React/Next, TypeScript, UI/UX
- `python/` data, deep learning, web scraping, Jupyter
- `tailwindcss/` styling conventions
- `typescript/` JS/TS best practices
- `wordpress/` WordPress/PHP standards

## Active meta rules
- Always apply all rules according to their `alwaysApply` flag; never skip applicable rules.
- If rules conflict, prefer the more specific rule.
- Discover relevant rules by browsing `.cursor/rules/` before implementing changes.

## Creating or updating rules
- Place each new rule in the correct category; only add a new category when none fits.
- File naming: lowercase with dashes, `.mdc` extension only.
- Required frontmatter (in this order):
  ```
  ---
  alwaysApply: true | false
  description: concise description
  author: Himel Das
  ---
  ```
- Content must be concise, generic, and free of project-specific code or secrets.

## Using the rules
- Apply all `alwaysApply: true` rules for every task.
- Apply `alwaysApply: false` rules when the task matches the category/context.
- Follow cumulative guidance (security, style, testing, accessibility) from relevant categories.

## Contribution notes
- Keep changes minimal, documented, and consistent with existing tone.
- Do not add TODOs or placeholders; ensure rules are complete and actionable.