shivanandasai-altir/cursor-workflow-commands

Cursor Workflow Commands Skill

This skill describes how to use and adapt the workflows defined in this repository:

• High-level philosophy and workflows overview in README.md
• Concrete prompt files in .cursor/commands/react/**

Always base explanations on what is actually written in these files.

When to use this skill

• The user is inside the cursor-commands repo.
• The user wants to add these workflows to another React + TypeScript project.
• The user asks which workflow or command to run (e.g. investigate, feature-clarity, implement, pr-review, test-checklist, ui-scan, design-ui, feature-plan).
• The user wants to enforce plan-before-code or anti-hallucination rules.

Installing into another project

When the user wants to use these workflows in their own repo:

1. Copy the react commands folder:
   • From this repo: .cursor/commands/react/
   • Into the target project: .cursor/commands/react/
2. (Optional but recommended) Copy this SKILL.md or create a similar skill in the target project, updating the name and description to reference that repo.
3. Ask the user to restart Cursor or reload commands so /react commands appear when they type / in chat.
4. Remind the user to fill all User will provide {…} placeholders in the copied prompts with project-specific content before running any command.

Do not assume anything about the target project beyond what the user says; default to React + TypeScript since these prompts are written for that stack.

Choosing the right workflow

Use the workflows table in README.md to select the sequence:

• UI scan: run react/design-ui/1-ui-scan.md once per project before using design-ui.
• Bug fix (something used to work and is now broken):
  • react/bug-fix/1-investigate.md
  • react/bug-fix/2-plan.md
  • react/bug-fix/3-implement.md
  • react/pr-review/pr-review.md
  • react/bug-fix/5-test-checklist.md
• Enhancement (small feature or UI change, ~1–5 files):
  • react/enhancement/feature-clarity.md
  • react/design-ui/2-design-ui.md (optional, requires 1-ui-scan run once)
  • react/enhancement/implement.md
  • react/pr-review/pr-review.md
  • react/enhancement/test-checklist.md
• Epic / large feature (6+ files or multiple PRs):
  • react/epic/feature-clarity.md
  • react/design-ui/2-design-ui.md (optional, requires 1-ui-scan run once)
  • react/epic/feature-plan.md
  • react/epic/implement.md
  • react/pr-review/pr-review.md
  • react/epic/test-checklist.md

Explain to the user which workflow you chose and why, then follow the steps in order unless they explicitly accept skipping them.

Plan-before-code discipline

When using these commands, apply the principles from README.md:

• No code is written before requirements and root cause are understood.
• No implementation starts before a plan is approved.
• No file is touched that was not listed in advance and confirmed.
• Every claim about the codebase must be backed by reading actual files; list all files you opened.
• Mark any guesses clearly as assumptions and stop when you would need to guess.

If the user asks to "just implement", explain the trade-offs and only relax these rules if they agree.

PR review and test checklist

When reviewing or testing changes using these workflows:

• Use react/pr-review/pr-review.md in a fresh Cursor instance focused on the diff.
• Categorize findings as blocker, warning, or suggestion, matching README.md.
• Use the relevant *test-checklist.md file to generate a manual browser test checklist that:
  • Confirms the main path,
  • Covers adjacent flows and edge cases,
  • Includes regression checks for touched code.

You can adapt this structure to other projects even if they do not use this exact command set.