@mrzacsmith/cursor-rules

# @mrzacsmith/cursor-rules

Interactive CLI to install Cursor AI rules for your project.

## Usage

Run with npx (recommended):
```bash
npx @mrzacsmith/cursor-rules
```

Or install globally:
```bash
npm install -g @mrzacsmith/cursor-rules
cursor-rules
```

## Features

- 🎯 Interactive rule selection
- 📁 Organized by categories:
  - Setup
  - Code Style
  - Frontend
  - Backend
  - Database
  - Mobile
  - Desktop & Extension Development
  - MCP Servers
    - Browser Tools
- 🔄 Safe installation - won't overwrite existing rules without permission
- 📝 Each rule includes:
  - Description
  - Recommended glob patterns
  - Detailed guidelines

## How it Works

1. Run `npx @mrzacsmith/cursor-rules`
2. Select a category using arrow keys
3. Choose rules using space bar
4. Navigate back to categories with enter
5. Select "Done" when finished
6. Rules are installed to `.cursor/rules/`

## Available Rules

### Setup
- **[✓] Create Feature PRD**: Guide for generating a detailed Product Requirements Document (PRD) based on user prompts
  - Structured process for gathering requirements through clarifying questions
  - Standardized PRD format with 9 sections (Introduction, Goals, User Stories, etc.)
  - Targets junior developers as the audience
  - Saves files as `prd-[feature-name].md` in `/tasks/` directory
  - Clear workflow from initial prompt to complete PRD
- **[✓] Generate Tasks**: Guide for creating detailed task lists from Product Requirements Documents (PRDs)
  - Two-phase process: parent tasks first, then detailed sub-tasks
  - Requires user confirmation between phases for better control
  - Structured output format with relevant files section
  - Saves as `tasks-[prd-file-name].md` for easy tracking
  - Junior developer-friendly task breakdown
- **[✓] Linear Issue Management**: Standardizes Linear issue creation with automatic project and team detection
  - Self-configuring setup on first use - builds `.cursor/linear-config.md` after prompting for defaults
  - Automatic team, project, and assignee detection from configuration
  - Manual setup trigger: say **"initiate linear issue rule"** or **"setup linear config"**
  - Simple single-file configuration (no complex directory structures)
  - Override defaults on a per-issue basis when needed
  - No maintenance required - static configuration
- **[✓] Process Task List**: Guidelines for managing task lists in markdown files to track progress on completing a PRD
  - One sub-task at a time workflow with user approval gates
  - Clear completion protocol with checkbox marking system
  - File maintenance requirements and progress tracking
  - AI instructions for proper task execution
  - Structured approach to feature implementation
- **[✓] Semgrep MCP Security Scan**: Mandatory security scanning of all generated code using Semgrep MCP server
  - Automatic security vulnerability detection in all generated code
  - Integration with Semgrep MCP server tools
  - Mandatory scan before task completion
  - Clear workflow for handling security findings
  - Support for multiple programming languages
  - Best practices for secure code generation

### Code Style
- **[✓] Commit Messages**: Standardized commit message format for consistent version control history
  - Enforces semantic commit messages
  - Includes type, scope, and description
  - Example: `Feat(component): add new component`
- **[✓] NPM Package Check**: Best practices for checking and installing NPM packages before use
  - Package dependency verification
  - Automatic installation commands
  - Dependency management
  - Error handling
  - Development workflow optimization
- **[✓] Python Development**: Modern Python development practices with type hints and testing
  - Type annotations and docstrings
  - Project structure and organization
  - Testing with pytest
  - Error handling and logging
  - Environment configuration
  - CI/CD with GitHub Actions
- **[✓] Terminal Path Verification**: Best practices for verifying paths and locations before executing terminal commands
  - Directory verification with pwd and ls
  - Path existence checks
  - File operation safety
  - Error prevention
  - Automated verification in scripts
- **[✓] Yoda Quote Endings**: End each Cursor chat with wisdom
  - Adds personality to coding sessions
  - Provides Yoda-style encouragement
  - Example: "Debug or debug not. There is no try-catch."

### Frontend
- **[✓] Tailwind Standards**: Best practices for Tailwind CSS v4+ implementation
  - Version compatibility and migration
  - Performance optimization
  - React integration
  - Accessibility and internationalization
- **[✓] React GraphQL Apollo**: Best practices for React development with GraphQL and Apollo Client
  - Project structure and organization
  - Apollo Client setup and configuration
  - Custom hooks and components
  - GraphQL operations and caching
  - Error handling and performance
- **[✓] Mobile First Web Development**: Best practices for mobile-first web development using Tai

... (truncated)