Name: switch-serena
Author: yuemori

Prompt file imported from yuemori/UnityMCPTest (.cursor/commands/switch-serena.md). Copyright stays with the author.

/switch-serena - Serena Project Switching

Triggers

Manual Serena project switching between Go backend and React frontend
Context validation and project activation confirmation needs
Cross-project development workflow management
Project context debugging and verification scenarios

Usage

/switch-serena [go|frontend|auto] [--analyze] [--validate] [--force]

Behavioral Flow

Context Analysis: Examine current working directory and file operations
Project Detection: Identify appropriate Serena project based on context
Validation: Verify project availability and configuration
Switch: Activate target Serena project with proper context loading
Confirm: Validate successful project activation and context establishment

Key behaviors:

Smart Detection: Auto-detect appropriate project from file context and working directory
Seamless Switching: Fast project activation with context preservation
Validation: Ensure project availability and proper configuration before switching
Cross-Project Awareness: Maintain understanding of both Go and Frontend project states

Context Detection Rules

Go Backend Context

File Patterns: *.go, pkg/, cmd/, proto/, root directory operations
Target Project: "portalkey-server"
Indicators: Go imports, ConnectRPC services, Spanner operations

Frontend Context

File Patterns: frontend/, *.tsx, *.ts (in frontend), React components
Target Project: "portalkey-server-frontend"
Indicators: React imports, TypeScript interfaces, Redux operations

Auto-Detection Logic

Priority: Current file operations > working directory > last active project
Fallback: Prompt user for clarification if context is ambiguous
Memory: Remember user preferences for mixed-context scenarios

MCP Integration

Serena MCP: Core project activation and context switching functionality
Project Validation: Verify project availability and configuration integrity
Memory Operations: Preserve context across project switches when possible

Tool Coordination

activate_project: Core Serena project activation with validation
list_memories: Verify project-specific memory availability
Read/Grep: Context analysis for intelligent project detection
Write: Project switch logging and preference persistence

Examples

Auto-Detection Switch

/switch-serena auto
# Analyzes current context and switches to appropriate Serena project
# Go files → "portalkey-server", Frontend files → "portalkey-server-frontend"

Manual Project Switch

/switch-serena go --validate
# Explicitly switches to "portalkey-server" with validation
# Confirms project availability and proper configuration

Frontend Development Switch

/switch-serena frontend --analyze
# Switches to "portalkey-server-frontend" with context analysis
# Loads React/TypeScript project context and memories

Force Switch with Validation

/switch-serena go --force --validate
# Forces switch to Go project even in ambiguous context
# Validates project state and reports any configuration issues

Boundaries

Will:

Switch between PortalKey Go and Frontend Serena projects intelligently
Provide context detection and validation for appropriate project selection
Maintain cross-project awareness and context preservation

Will Not:

Switch projects without proper validation and context analysis
Override explicit user project selection without confirmation
Operate without proper Serena MCP integration and project availability

Install switch-serena and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# /switch-serena - Serena Project Switching ## Triggers - Manual Serena project switching between Go backend and React frontend - Context validation and project activation confirmation needs - Cross-project development workflow management - Project context debugging and verification scenarios ## Usage ``` /switch-serena [go|frontend|auto] [--analyze] [--validate] [--force] ``` ## Behavioral Flow 1. **Context Analysis**: Examine current working directory and file operations 2. **Project Detection**: Identify appropriate Serena project based on context 3. **Validation**: Verify project availability and configuration 4. **Switch**: Activate target Serena project with proper context loading 5. **Confirm**: Validate successful project activation and context establishment Key behaviors: - **Smart Detection**: Auto-detect appropriate project from file context and working directory - **Seamless Switching**: Fast project activation with context preservation - **Validation**: Ensure project availability and proper configuration before switching - **Cross-Project Awareness**: Maintain understanding of both Go and Frontend project states ## Context Detection Rules ### Go Backend Context - **File Patterns**: `*.go`, `pkg/`, `cmd/`, `proto/`, root directory operations - **Target Project**: "portalkey-server" - **Indicators**: Go imports, ConnectRPC services, Spanner operations ### Frontend Context - **File Patterns**: `frontend/`, `*.tsx`, `*.ts` (in frontend), React components - **Target Project**: "portalkey-server-frontend" - **Indicators**: React imports, TypeScript interfaces, Redux operations ### Auto-Detection Logic - **Priority**: Current file operations > working directory > last active project - **Fallback**: Prompt user for clarification if context is ambiguous - **Memory**: Remember user preferences for mixed-context scenarios ## MCP Integration - **Serena MCP**: Core project activation and context switching functionality - **Project Validation**: Verify project availability and configuration integrity - **Memory Operations**: Preserve context across project switches when possible ## Tool Coordination - **activate_project**: Core Serena project activation with validation - **list_memories**: Verify project-specific memory availability - **Read/Grep**: Context analysis for intelligent project detection - **Write**: Project switch logging and preference persistence ## Examples ### Auto-Detection Switch ``` /switch-serena auto # Analyzes current context and switches to appropriate Serena project # Go files → "portalkey-server", Frontend files → "portalkey-server-frontend" ``` ### Manual Project Switch ``` /switch-serena go --validate # Explicitly switches to "portalkey-server" with validation # Confirms project availability and proper configuration ``` ### Frontend Development Switch ``` /switch-serena frontend --analyze # Switches to "portalkey-server-frontend" with context analysis # Loads React/TypeScript project context and memories ``` ### Force Switch with Validation ``` /switch-serena go --force --validate # Forces switch to Go project even in ambiguous context # Validates project state and reports any configuration issues ``` ## Boundaries **Will:** - Switch between PortalKey Go and Frontend Serena projects intelligently - Provide context detection and validation for appropriate project selection - Maintain cross-project awareness and context preservation **Will Not:** - Switch projects without proper validation and context analysis - Override explicit user project selection without confirmation - Operate without proper Serena MCP integration and project availability

{ "prompt": "# /switch-serena - Serena Project Switching\n\n## Triggers\n\n- Manual Serena project switching between Go backend and React frontend\n- Context validation and project activation confirmation needs\n- Cross-project development workflow management\n- Project context debugging and verification scenarios\n\n## Usage\n\n```\n/switch-serena [go|frontend|auto] [--analyze] [--validate] [--force]\n```\n\n## Behavioral Flow\n\n1. **Context Analysis**: Examine current working directory and file operations\n2. **Project Detection**: Identify appropriate Serena project based on context\n3. **Validation**: Verify project availability and configuration\n4. **Switch**: Activate target Serena project with proper context loading\n5. **Confirm**: Validate successful project activation and context establishment\n\nKey behaviors:\n\n- **Smart Detection**: Auto-detect appropriate project from file context and working directory\n- **Seamless Switching**: Fast project activation with context preservation\n- **Validation**: Ensure project availability and proper configuration before switching\n- **Cross-Project Awareness**: Maintain understanding of both Go and Frontend project states\n\n## Context Detection Rules\n\n### Go Backend Context\n\n- **File Patterns**: `*.go`, `pkg/`, `cmd/`, `proto/`, root directory operations\n- **Target Project**: \"portalkey-server\"\n- **Indicators**: Go imports, ConnectRPC services, Spanner operations\n\n### Frontend Context\n\n- **File Patterns**: `frontend/`, `*.tsx`, `*.ts` (in frontend), React components\n- **Target Project**: \"portalkey-server-frontend\"\n- **Indicators**: React imports, TypeScript interfaces, Redux operations\n\n### Auto-Detection Logic\n\n- **Priority**: Current file operations > working directory > last active project\n- **Fallback**: Prompt user for clarification if context is ambiguous\n- **Memory**: Remember user preferences for mixed-context scenarios\n\n## MCP Integration\n\n- **Serena MCP**: Core project activation and context switching functionality\n- **Project Validation**: Verify project availability and configuration integrity\n- **Memory Operations**: Preserve context across project switches when possible\n\n## Tool Coordination\n\n- **activate_project**: Core Serena project activation with validation\n- **list_memories**: Verify project-specific memory availability\n- **Read/Grep**: Context analysis for intelligent project detection\n- **Write**: Project switch logging and preference persistence\n\n## Examples\n\n### Auto-Detection Switch\n\n```\n/switch-serena auto\n# Analyzes current context and switches to appropriate Serena project\n# Go files → \"portalkey-server\", Frontend files → \"portalkey-server-frontend\"\n```\n\n### Manual Project Switch\n\n```\n/switch-serena go --validate\n# Explicitly switches to \"portalkey-server\" with validation\n# Confirms project availability and proper configuration\n```\n\n### Frontend Development Switch\n\n```\n/switch-serena frontend --analyze\n# Switches to \"portalkey-server-frontend\" with context analysis\n# Loads React/TypeScript project context and memories\n```\n\n### Force Switch with Validation\n\n```\n/switch-serena go --force --validate\n# Forces switch to Go project even in ambiguous context\n# Validates project state and reports any configuration issues\n```\n\n## Boundaries\n\n**Will:**\n\n- Switch between PortalKey Go and Frontend Serena projects intelligently\n- Provide context detection and validation for appropriate project selection\n- Maintain cross-project awareness and context preservation\n\n**Will Not:**\n\n- Switch projects without proper validation and context analysis\n- Override explicit user project selection without confirmation\n- Operate without proper Serena MCP integration and project availability", "variables": [], "notes": "Smart Serena project switching with context detection and validation", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/yuemori/UnityMCPTest", "path": ".cursor/commands/switch-serena.md", "ref": "4cdc3dcefbc27960027605300be8b99c49fff6b7", "url": "https://github.com/yuemori/UnityMCPTest/blob/4cdc3dcefbc27960027605300be8b99c49fff6b7/.cursor/commands/switch-serena.md", "key": "yuemori/UnityMCPTest/.cursor/commands/switch-serena.md" } } }

switch-serena

About