AI Product Team Modes for Cursor

Say hello to your very own multidisciplinary product team! This repository provides ready-to-use Custom Mode definitions for the Cursor AI chat sidebar. Each Markdown file in the root directory represents a specialised role that you can switch the assistant into depending on the task at hand.

File	Mode Name (what you'll see in Cursor)	Purpose
architect.md	Principal Software Architect	Guides you through high-level system & architecture design. Produces design docs & implementation plans – never code.
product_manager.md	Senior Product Manager	Collaboratively drafts or refines detailed, developer-ready PRDs.
developer.md	Implementation Assistant	Executes an existing implementation plan task-by-task, asking for your approval between steps, and keeps task lists up to date.
marketer.md	Brand & Growth Architect	Crafts branding, marketing strategy, and visual identity assets. Outputs brand documents & creative deliverables – never code (except SVG/images).

---

Quick-Start: Loading a Custom Mode

1. Enable Custom Modes by navigating to Settings -> Beta -> Toggle "Custom Modes"
2. Open Cursor Chat in the workspace you're working on.
3. In the select menu down the bottom of the chat windoe, click the current mode name (e.g. Agent), then scroll down and choose "Custom Mode".
4. Enter the title of you mode. For e.g. "Architect"
5. Click on "Advanced Settings" in the custom mode menu, and copy+paste in the instructions for the role from this repo.
6. Start chatting! The assistant will now follow the responsibilities, constraints, and outputs defined by the selected role.

You can switch modes at any time by repeating the steps. This is handy when you need to move from PRD writing (product_manager) to architecture design (architect), for instance.

Tip: Keep multiple chat tabs open, each in a different mode, to parallelise work across your virtual team.

---

Recommended Workflow

1. Define the product – Load product_manager.md and co-create a PRD.
2. Design the system – Switch to architect.md to plan the technical architecture.
3. Execute the plan – Use developer.md to incrementally implement the tasks while tracking progress.
4. Go-to-market – Finally, shift into marketer.md to craft branding, growth experiments, and launch assets.

Feel free to deviate—these modes are flexible building blocks.

---

Contributing

If you refine a role or add a new one, open a pull request! Please keep each mode in its own Markdown file following the same structure:

1. Role Definition & Objective
2. Core Responsibilities
3. Expected Outputs
4. Working Instructions

---