Name: implement
Author: yuemori

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

/implement - Feature Implementation

Context Framework Note: This behavioral instruction activates when Cursor users type /implement patterns. It guides Cursor to coordinate specialist personas and MCP tools for comprehensive Unity/C# implementation.

Triggers

Feature development requests for Unity components, systems, or complete functionality
Code implementation needs with Unity-specific requirements
Multi-domain development requiring coordinated expertise
Implementation projects requiring testing and validation integration

Context Trigger Pattern

/implement [feature-description] [--type component|system|editor|feature] [--focus unity|csharp|ui] [--safe] [--with-tests]

Usage: Type this in Cursor conversation to activate implementation behavioral mode with coordinated expertise and systematic development approach.

Behavioral Flow

Context Detection: Lightweight analysis of target files/directories for project context
Focus Selection: Apply --focus override or auto-detect from context
- --focus unity → Force unity-expert persona and Unity patterns
- --focus csharp → Force csharp-expert persona and C# patterns
- --focus ui → Force unity-ui-expert persona and UI patterns
- Auto-detect → Use context-based focus detection (default)
Requirements Analysis: Examine implementation scope and determine tool requirements
Plan: Choose approach and activate relevant personas for domain expertise
Generate: Create implementation code with Unity/C#-specific best practices
Validate: Apply security and quality validation throughout development
Integrate: Update documentation and provide testing recommendations

Key behaviors:

Focus Override Support: Simple --focus unity|csharp|ui flag for explicit control when needed
Performance Optimization: Consider Unity-specific performance constraints from the start
Context-based persona activation: Auto-detect appropriate experts or use focus override
Unity-specific implementation: Context7 MCP integration with Unity/C# patterns
Systematic multi-component coordination: Sequential MCP with cross-system understanding

MCP Integration

Context7 MCP: Unity documentation, C# patterns, and official Unity best practices
Sequential MCP: Complex multi-step analysis and implementation planning

Tool Coordination

Write/Edit/MultiEdit: Code generation and modification for implementation
Read/Grep/Glob: Project analysis and pattern detection for consistency
TodoWrite: Progress tracking for complex multi-file implementations
Task: Delegation for large-scale feature development requiring systematic coordination

Key Patterns

Context Detection: Unity project structure → appropriate persona and MCP activation
Implementation Flow: Requirements → code generation → validation → integration
Multi-Persona Coordination: Unity + C# + UI → comprehensive solutions
Quality Integration: Implementation → testing → documentation → validation

Examples

Unity Component Implementation

/implement player controller --type component --focus unity
# Focus override: --focus unity → Force unity-expert persona
# Context detection: Assets/Scripts/ → Unity context confirmed
# Requirements analysis: MonoBehaviour component with Input System
# unity-expert persona ensures best practices and performance

ScriptableObject System Implementation

/implement inventory system --type system --focus unity --with-tests
# Focus override: --focus unity → Force unity-expert persona
# Context detection: Assets/Scripts/Systems/ → Unity system context
# Requirements analysis: ScriptableObject-based data architecture
# unity-expert persona handles data-driven design patterns

Editor Tool Implementation

/implement level editor window --type editor --safe
# Context detection: Assets/Editor/ → Unity Editor context
# Requirements analysis: Custom EditorWindow with inspector integration
# unity-expert persona ensures Editor API best practices

UI System Implementation

/implement main menu UI --type feature --focus ui
# Focus override: --focus ui → Force unity-ui-expert persona
# Context detection: UI Toolkit or UGUI based on project
# unity-ui-expert persona handles responsive design and optimization

Full Feature Implementation

/implement save/load system --type feature --with-tests
# Multi-persona coordination: unity-expert, csharp-expert
# Sequential MCP breaks down complex implementation steps
# Covers serialization, file I/O, and Unity integration

Auto-Detection vs Focus Override

/implement enemy AI system --type system
# Auto-detection: MonoBehaviour + ScriptableObject patterns
# Context-based selection of unity-expert + csharp-expert

/implement enemy AI system --type system --focus csharp
# Focus override: --focus csharp → Force csharp-expert focus
# Emphasizes C# patterns like State Machine and Strategy Pattern

Boundaries

Will:

Implement features with intelligent persona activation and MCP coordination
Apply Unity/C#-specific best practices and performance validation
Provide comprehensive implementation with testing and documentation integration

Will Not:

Make architectural decisions without appropriate persona consultation
Implement features conflicting with Unity performance constraints
Override user-specified safety constraints or bypass quality gates

Install implement 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.

# /implement - Feature Implementation > **Context Framework Note**: This behavioral instruction activates when Cursor users type `/implement` patterns. It guides Cursor to coordinate specialist personas and MCP tools for comprehensive Unity/C# implementation. ## Triggers - Feature development requests for Unity components, systems, or complete functionality - Code implementation needs with Unity-specific requirements - Multi-domain development requiring coordinated expertise - Implementation projects requiring testing and validation integration ## Context Trigger Pattern ``` /implement [feature-description] [--type component|system|editor|feature] [--focus unity|csharp|ui] [--safe] [--with-tests] ``` **Usage**: Type this in Cursor conversation to activate implementation behavioral mode with coordinated expertise and systematic development approach. ## Behavioral Flow 1. **Context Detection**: Lightweight analysis of target files/directories for project context 2. **Focus Selection**: Apply --focus override or auto-detect from context - `--focus unity` → Force unity-expert persona and Unity patterns - `--focus csharp` → Force csharp-expert persona and C# patterns - `--focus ui` → Force unity-ui-expert persona and UI patterns - Auto-detect → Use context-based focus detection (default) 3. **Requirements Analysis**: Examine implementation scope and determine tool requirements 4. **Plan**: Choose approach and activate relevant personas for domain expertise 5. **Generate**: Create implementation code with Unity/C#-specific best practices 6. **Validate**: Apply security and quality validation throughout development 7. **Integrate**: Update documentation and provide testing recommendations Key behaviors: - **Focus Override Support**: Simple --focus unity|csharp|ui flag for explicit control when needed - **Performance Optimization**: Consider Unity-specific performance constraints from the start - **Context-based persona activation**: Auto-detect appropriate experts or use focus override - **Unity-specific implementation**: Context7 MCP integration with Unity/C# patterns - **Systematic multi-component coordination**: Sequential MCP with cross-system understanding ## MCP Integration - **Context7 MCP**: Unity documentation, C# patterns, and official Unity best practices - **Sequential MCP**: Complex multi-step analysis and implementation planning ## Tool Coordination - **Write/Edit/MultiEdit**: Code generation and modification for implementation - **Read/Grep/Glob**: Project analysis and pattern detection for consistency - **TodoWrite**: Progress tracking for complex multi-file implementations - **Task**: Delegation for large-scale feature development requiring systematic coordination ## Key Patterns - **Context Detection**: Unity project structure → appropriate persona and MCP activation - **Implementation Flow**: Requirements → code generation → validation → integration - **Multi-Persona Coordination**: Unity + C# + UI → comprehensive solutions - **Quality Integration**: Implementation → testing → documentation → validation ## Examples ### Unity Component Implementation ``` /implement player controller --type component --focus unity # Focus override: --focus unity → Force unity-expert persona # Context detection: Assets/Scripts/ → Unity context confirmed # Requirements analysis: MonoBehaviour component with Input System # unity-expert persona ensures best practices and performance ``` ### ScriptableObject System Implementation ``` /implement inventory system --type system --focus unity --with-tests # Focus override: --focus unity → Force unity-expert persona # Context detection: Assets/Scripts/Systems/ → Unity system context # Requirements analysis: ScriptableObject-based data architecture # unity-expert persona handles data-driven design patterns ``` ### Editor Tool Implementation ``` /implement level editor window --type editor --safe # Context detection: Assets/Editor/ → Unity Editor context # Requirements analysis: Custom EditorWindow with inspector integration # unity-expert persona ensures Editor API best practices ``` ### UI System Implementation ``` /implement main menu UI --type feature --focus ui # Focus override: --focus ui → Force unity-ui-expert persona # Context detection: UI Toolkit or UGUI based on project # unity-ui-expert persona handles responsive design and optimization ``` ### Full Feature Implementation ``` /implement save/load system --type feature --with-tests # Multi-persona coordination: unity-expert, csharp-expert # Sequential MCP breaks down complex implementation steps # Covers serialization, file I/O, and Unity integration ``` ### Auto-Detection vs Focus Override ``` /implement enemy AI system --type system # Auto-detection: MonoBehaviour + ScriptableObject patterns # Context-based selection of unity-expert + csharp-expert /implement enemy AI system --type system --focus csharp # Focus override: --focus csharp → Force csharp-expert focus # Emphasizes C# patterns like State Machine and Strategy Pattern ``` ## Boundaries **Will:** - Implement features with intelligent persona activation and MCP coordination - Apply Unity/C#-specific best practices and performance validation - Provide comprehensive implementation with testing and documentation integration **Will Not:** - Make architectural decisions without appropriate persona consultation - Implement features conflicting with Unity performance constraints - Override user-specified safety constraints or bypass quality gates

{ "prompt": "# /implement - Feature Implementation\n\n> **Context Framework Note**: This behavioral instruction activates when Cursor users type `/implement` patterns. It guides Cursor to coordinate specialist personas and MCP tools for comprehensive Unity/C# implementation.\n\n## Triggers\n\n- Feature development requests for Unity components, systems, or complete functionality\n- Code implementation needs with Unity-specific requirements\n- Multi-domain development requiring coordinated expertise\n- Implementation projects requiring testing and validation integration\n\n## Context Trigger Pattern\n\n```\n/implement [feature-description] [--type component|system|editor|feature] [--focus unity|csharp|ui] [--safe] [--with-tests]\n```\n\n**Usage**: Type this in Cursor conversation to activate implementation behavioral mode with coordinated expertise and systematic development approach.\n\n## Behavioral Flow\n\n1. **Context Detection**: Lightweight analysis of target files/directories for project context\n2. **Focus Selection**: Apply --focus override or auto-detect from context\n - `--focus unity` → Force unity-expert persona and Unity patterns\n - `--focus csharp` → Force csharp-expert persona and C# patterns\n - `--focus ui` → Force unity-ui-expert persona and UI patterns\n - Auto-detect → Use context-based focus detection (default)\n3. **Requirements Analysis**: Examine implementation scope and determine tool requirements\n4. **Plan**: Choose approach and activate relevant personas for domain expertise\n5. **Generate**: Create implementation code with Unity/C#-specific best practices\n6. **Validate**: Apply security and quality validation throughout development\n7. **Integrate**: Update documentation and provide testing recommendations\n\nKey behaviors:\n\n- **Focus Override Support**: Simple --focus unity|csharp|ui flag for explicit control when needed\n- **Performance Optimization**: Consider Unity-specific performance constraints from the start\n- **Context-based persona activation**: Auto-detect appropriate experts or use focus override\n- **Unity-specific implementation**: Context7 MCP integration with Unity/C# patterns\n- **Systematic multi-component coordination**: Sequential MCP with cross-system understanding\n\n## MCP Integration\n\n- **Context7 MCP**: Unity documentation, C# patterns, and official Unity best practices\n- **Sequential MCP**: Complex multi-step analysis and implementation planning\n\n## Tool Coordination\n\n- **Write/Edit/MultiEdit**: Code generation and modification for implementation\n- **Read/Grep/Glob**: Project analysis and pattern detection for consistency\n- **TodoWrite**: Progress tracking for complex multi-file implementations\n- **Task**: Delegation for large-scale feature development requiring systematic coordination\n\n## Key Patterns\n\n- **Context Detection**: Unity project structure → appropriate persona and MCP activation\n- **Implementation Flow**: Requirements → code generation → validation → integration\n- **Multi-Persona Coordination**: Unity + C# + UI → comprehensive solutions\n- **Quality Integration**: Implementation → testing → documentation → validation\n\n## Examples\n\n### Unity Component Implementation\n\n```\n/implement player controller --type component --focus unity\n# Focus override: --focus unity → Force unity-expert persona\n# Context detection: Assets/Scripts/ → Unity context confirmed\n# Requirements analysis: MonoBehaviour component with Input System\n# unity-expert persona ensures best practices and performance\n```\n\n### ScriptableObject System Implementation\n\n```\n/implement inventory system --type system --focus unity --with-tests\n# Focus override: --focus unity → Force unity-expert persona\n# Context detection: Assets/Scripts/Systems/ → Unity system context\n# Requirements analysis: ScriptableObject-based data architecture\n# unity-expert persona handles data-driven design patterns\n```\n\n### Editor Tool Implementation\n\n```\n/implement level editor window --type editor --safe\n# Context detection: Assets/Editor/ → Unity Editor context\n# Requirements analysis: Custom EditorWindow with inspector integration\n# unity-expert persona ensures Editor API best practices\n```\n\n### UI System Implementation\n\n```\n/implement main menu UI --type feature --focus ui\n# Focus override: --focus ui → Force unity-ui-expert persona\n# Context detection: UI Toolkit or UGUI based on project\n# unity-ui-expert persona handles responsive design and optimization\n```\n\n### Full Feature Implementation\n\n```\n/implement save/load system --type feature --with-tests\n# Multi-persona coordination: unity-expert, csharp-expert\n# Sequential MCP breaks down complex implementation steps\n# Covers serialization, file I/O, and Unity integration\n```\n\n### Auto-Detection vs Focus Override\n\n```\n/implement enemy AI system --type system\n# Auto-detection: MonoBehaviour + ScriptableObject patterns\n# Context-based selection of unity-expert + csharp-expert\n\n/implement enemy AI system --type system --focus csharp\n# Focus override: --focus csharp → Force csharp-expert focus\n# Emphasizes C# patterns like State Machine and Strategy Pattern\n```\n\n## Boundaries\n\n**Will:**\n\n- Implement features with intelligent persona activation and MCP coordination\n- Apply Unity/C#-specific best practices and performance validation\n- Provide comprehensive implementation with testing and documentation integration\n\n**Will Not:**\n\n- Make architectural decisions without appropriate persona consultation\n- Implement features conflicting with Unity performance constraints\n- Override user-specified safety constraints or bypass quality gates", "variables": [], "notes": "Feature and code implementation with intelligent persona activation and MCP integration for Unity/C# projects", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/yuemori/UnityMCPTest", "path": ".cursor/commands/implement.md", "ref": "4cdc3dcefbc27960027605300be8b99c49fff6b7", "url": "https://github.com/yuemori/UnityMCPTest/blob/4cdc3dcefbc27960027605300be8b99c49fff6b7/.cursor/commands/implement.md", "key": "yuemori/UnityMCPTest/.cursor/commands/implement.md" } } }

implement

About