cursor-team-marketplace-template

Guide PMs and designers in creating comprehensive wireframes and mockups that accurately represent all backend API responses and data states. Use when creating wireframes or mockups for new features.

Summarize board, backlog, or sprint status for stakeholders with risks, blockers, and delivery confidence. Use for weekly PM updates and planning checkpoints.

Write high-quality tickets from product requests, incidents, or discovery notes. Use when drafting or refining implementation-ready work items.

Check whether README documentation should be updated when code changes affect setup, usage, commands, configuration, environment variables, workflows, or user-visible behavior. Use when making changes that may invalidate existing README content or require new documentation.

Generate or update a repository README with startup instructions and a Mermaid architecture diagram. Use when creating a README, updating project documentation, onboarding new contributors, or when the user mentions README, startup guide, or architecture overview.

Generate weekly commit summaries and categorize work. Use for weekly retrospectives or progress reviews.

Verify product behavior with Cursor browser automation by driving real UI flows, capturing failures, and turning findings into actionable repro steps or follow-up tests. Use when the user asks for browser automation, in-browser verification, UI smoke checks, or manual flow testing in Cursor.

Write end-to-end tests for real user journeys using the repository's existing browser or application test stack. Use when the user asks for E2E tests, workflow coverage, UI regression protection, or multi-step journey validation.

Write focused unit tests that match the repository's existing test stack and conventions. Use when the user asks for unit tests, logic coverage, regression coverage for functions or modules, or fast isolated test cases.

Create production-ready UI mockups tied to real API states and design system constraints. Use when the user asks for polished screen mockups, stateful UI explorations, or handoff-ready visual specs.

Names Cursor cloud and local agents consistently. When starting an agent from a ticket or issue, uses TICKET-ID plus a short Title Case description after a colon. When there is no ticket, uses Title Case with at most four words. Use whenever naming a new agent, cloud agent, background agent, or when the user mentions agent titles or agent naming. Applies to any agent that appears in the Agents sidebar.

Create commits with conventional commit messages. Analyzes staged changes, generates a short one-line message, and runs git commit. Use when the user asks to commit, write a commit message, or create a commit.

Keep git history clean and reviewable with branch naming, branch upkeep, merge conflict handling, and pull request prep. Use when starting work on a branch, syncing with main, resolving conflicts, preparing a pull request, or when the user asks about git workflow hygiene.

Learn an unfamiliar codebase—structure, entry points, how to run and test, and where to change things safely. Use when joining a project, switching teams, or ramping on a new repo.

Naming conventions for markdown files across the project, including Cursor configuration files and general documentation. Use when creating or renaming any .md or .mdc files.

Shape implementation plans into a concise, execution-ready format with problem, scope, acceptance criteria, risks, steps, and verification. Use in Plan mode or when the user asks for a plan.