Before using Cursor Dev Commands, ensure the following setup is completed:
Sign in to like and favorite skills
Before using Cursor Dev Commands, ensure the following setup is completed:
# Install GitHub CLI (if not already installed) # macOS: brew install gh # Windows: winget install --id GitHub.cli # Login to GitHub gh auth login # Add required scopes for GitHub Projects gh auth refresh -h github.com -s read:project -s project # Verify authentication gh auth status
# macOS brew install jq # Linux (Ubuntu/Debian) sudo apt-get install jq # Windows winget install jqlang.jq
Ensure the following scripts exist in your project:
.cursor/script/setsp.ps.cursor/script/setsp.ps1This project uses Cursor Dev Commands located in
.cursor/commands/Available commands:
/issue/plan/breakdown/dev/test/prBased on the requirement issue created by PM, create branch, plan, calculate SP, and split tasks into FE/BE issues.
/issue {requirement_issue_number}/plan {requirement_issue_number}/breakdown {requirement_issue_number}Triggered by the FE/BE Issues created in Phase 1, execute the following development cycle for each issue.
/dev {issue_number}/test {issue_number}/pr {issue_number}Reflects the workflow sequence (plan → breakdown)
/issue {issue_number} --auto/issue {issue_number} --auto --skip-plandocs/issues/{issue_number}/evidence/backend/frontend/backend/ ├── src/ │ ├── domain/ │ │ └── alert/ │ │ ├── alertSchema.ts │ │ ├── alertModel.ts │ │ └── alertService.ts │ └── api/ │ └── alertRoutes.ts └── tests/ frontend/ ├── src/ │ ├── components/ │ │ └── AuthorGroupedTable.vue │ └── pages/ │ └── index.vue └── tests/
# Backend yarn dev # Start development server yarn test:unit # Run tests yarn db:migrate # Run database migrations yarn build # Build for production # Frontend yarn dev # Start development server yarn test # Run tests yarn build # Build for production