implement · superclaude-org — Claude Code command: what it does, how to install
The /sc:implement command coordinates feature development in Claude Code using specialist personas and MCP tools. It handles planning, code generation, and test prep.
MIT ★ 23,950 updated 2026-09-27
.claude/commands/implement.mdWhat implement does
This command drives a structured development flow: analyze requirements, plan the implementation, write framework-aligned code, and validate results. Depending on the task, Claude activates personas like architect, frontend, backend, security, or QA specialist.
External MCP servers guide the process when present. Context7 supplies framework documentation for React, Vue, or Express, while Magic assists with UI components. Sequential handles multi-step logic, and Playwright sets up test validation. None of these servers are mandatory. When a tool is missing, the command falls back to native reasoning and web lookups.
You configure the run using flags such as --type api, --framework react, --safe, or --with-tests. The flow avoids architectural bypasses without consulting the relevant security persona. Work finishes once code compiles and stands ready for /sc:test.
What it helps with
- Implement an API endpoint with security checks and automated tests
- Generate React or Vue components aligned with design conventions
- Coordinate complex full-stack features across multiple specialist roles
- Prepare completed code for testing with Playwright
Example prompts for the agent
- /sc:implement user profile component --type component --framework react
- /sc:implement user authentication API --type api --safe --with-tests
- /sc:implement dashboard widget --framework vue
How to install implement
Manually: put the files in place
.claude/commands/implement.mdCall it with /implement. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/implement.mdCall it with /prompts:implement. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/implement.prompt.mdManually: put the files in place
.gemini/commands/implement.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about implement
How do I install implement in Claude Code?
Save the command instructions into .claude/commands/implement.md. The /sc:implement command becomes instantly available in your project.
What does the implement command do?
It runs a structured implementation workflow by switching between architect, frontend, backend, security, and QA personas. It generates application code, checks constraints, and prepares files for testing.
Are Context7 and Magic MCP servers required?
No, all listed MCP servers are optional. If Context7, Sequential, Magic, or Playwright are absent, the command degrades gracefully to native reasoning and web lookups.
Source text
implement.md · MIT
--- name: implement description: "Feature and code implementation with intelligent persona activation and MCP integration" category: workflow complexity: standard mcp-servers: [context7, sequential, magic, playwright] personas: [architect, frontend, backend, security, qa-specialist] --- # /sc:implement - Feature Implementation > **Context Framework Note**: This behavioral instruction activates when Claude Code users type `/sc:implement` patterns. It guides Claude to coordinate specialist personas and MCP tools for comprehensive implementation. ## Triggers - Feature development requests for components, APIs, or complete functionality - Code implementation needs with framework-specific requirements - Multi-domain development requiring coordinated expertise - Implementation projects requiring testing and validation integration ## Context Trigger Pattern ``` /sc:implement [feature-description] [--type component|api|service|feature] [--framework react|vue|express] [--safe] [--with-tests] ``` **Usage**: Type this in Claude Code conversation to activate implementation behavioral mode with coordinated expertise and systematic development approach. ## Behavioral Flow 1. **Analyze**: Examine implementation requirements and detect technology context 2. **Plan**: Choose approach and activate relevant personas for domain expertise 3. **Generate**: Create implementation code with framework-specific best practices 4. **Validate**: Apply security and quality validation throughout development 5. **Integrate**: Update documentation and provide testing recommendations Key behaviors: - Context-based persona activation (architect, frontend, backend, security, qa) - Framework-specific implementation via Context7 and Magic MCP integration - Systematic multi-component coordination via Sequential MCP - Comprehensive testing integration with Playwright for validation ## MCP Integration - **Context7 MCP**: Framework patterns and official documentation for React, Vue, Angular, Express - **Magic MCP**: Auto-activated for UI component generation and design system integration - **Sequential MCP**: Complex multi-step analysis and implementation planning - **Playwright MCP**: Testing validation and quality assurance integration - **Availability fallback**: The MCP servers named here are preferred tooling, not hard requirements — when one is not installed, degrade gracefully (native reasoning in place of Sequential, official docs via web lookup in place of Context7, native tools otherwise) instead of routing work to absent servers. ## 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**: Framework/tech stack → appropriate persona and MCP activation - **Implementation Flow**: Requirements → code generation → validation → integration - **Multi-Persona Coordination**: Frontend + Backend + Security → comprehensive solutions - **Quality Integration**: Implementation → testing → documentation → validation ## Examples ### React Component Implementation ``` /sc:implement user profile component --type component --framework react # Magic MCP generates UI component with design system integration # Frontend persona ensures best practices and accessibility ``` ### API Service Implementation ``` /sc:implement user authentication API --type api --safe --with-tests # Backend persona handles server-side logic and data processing # Security persona ensures authentication best practices ``` ### Full-Stack Feature ``` /sc:implement payment processing system --type feature --with-tests # Multi-persona coordination: architect, frontend, backend, security # Sequential MCP breaks down complex implementation steps ``` ### Framework-Specific Implementation ``` /sc:implement dashboard widget --framework vue # Context7 MCP provides Vue-specific patterns and documentation # Framework-appropriate implementation with official best practices ``` ## Boundaries **Will:** - Implement features with intelligent persona activation and MCP coordination - Apply framework-specific best practices and security validation - Provide comprehensive implementation with testing and documentation integration **Will Not:** - Make architectural decisions without appropriate persona consultation - Implement features conflicting with security policies or architectural constraints - Override user-specified safety constraints or bypass quality gates ## COMPLETION CRITERIA **Implementation is DONE when**: - Feature code is written and compiles - Basic functionality verified - Files saved and ready for testing **Post-Implementation Checklist**: 1. Code compiles without errors 2. Basic functionality works 3. Ready for `/sc:test` **Next Step**: After implementation, use `/sc:test` to run tests, then `/sc:git` to commit.
© SuperClaude-Org · MIT · SuperClaude-Org/SuperClaude_Framework
Similar slash commands
All slash commands for Agent setup: memory, context, orchestration →implement by other authors comes first.