Custom Modes for Cursor

โ† Back to Main | Use Cases โ†’

Use Cursor AI efficiently for your workflow with custom modes. Think of modes as different "hats" your AI wears depending on what you're doing.

How to create an efficient custom mode?

Pro tip: Start with Dev mode as your default. It works for 80% of coding tasks.

What is MCP?

MCP (Model Context Protocol) gives your AI access to external tools like databases, browsers, or Jira. Only enable what you need - too many tools confuse the AI.

Available Custom Modes

Here are the ready-made modes in Tadien Framework. Feel free to copy and edit them for your needs:

Dev Mode

When to use: Default for all coding tasks (Cmd + I), this should includes your daily workflow to do the task.

Tools: None or only sequential-thinking (keeps it simple)

Best for: Adding features, fixing bugs, refactoring code

SQL Mode

When to use: Database work

Tools: PostgreSQL MCP

Best for: Writing queries, database migrations, data analysis

QA Mode

When to use: Testing your features

Tools: Browser automation with Playwright

Best for: End-to-end testing, UI validation, bug reproduction

Confluence/Jira Mode

When to use: Project management and issue tracking

Tools: Atlassian MCP

Best for: Creating tickets, managing backlogs, organizing sprints

Bug Fix Agent ๐Ÿšง Work in Progress

When to use: Autonomous bug fixing workflows

Tools: Jira integration + Playwright testing

Best for: End-to-end bug resolution from ticket to tested fix

Creating Your Own Modes

Examples of other useful modes you might create:

Quick Setup Guide

Step 1: Choose your mode

Step 2: Copy the mode content

Step 3: Switch when your task changes

Pro Tips

Remember: The best mode is the one you actually use consistently!


๐Ÿงญ Navigation

๐Ÿ  Main Guide - Framework overview
๐Ÿ’ก Use Cases - See these modes in action
๐Ÿ“ Cursor Rules - Project-specific guidelines

Individual Modes: