Loading...
Loading...
Design system architecture, APIs, and component interfaces with comprehensive specifications. Use when planning architecture, designing APIs, creating component interfaces, or modeling databases.
npx skill4agent add tony363/superclaude sc-design# Architecture design
/sc:design [target] --type architecture
# API specification
/sc:design payment-api --type api --format spec
# Database schema
/sc:design e-commerce --type database --format diagram| Flag | Type | Default | Description |
|---|---|---|---|
| string | architecture | architecture, api, component, database |
| string | spec | diagram, spec, code |
--type architecture--type api--type component--type database--format diagram--format spec--format code/sc:design user-management --type architecture --format diagram
# Component relationships, data flow, scalability patterns/sc:design payment-api --type api --format spec
# OpenAPI spec with endpoints, schemas, auth patterns/sc:design notification-service --type component --format code
# TypeScript/Python interfaces with clear contracts/sc:design inventory-db --type database --format diagram
# ER diagrams with relationships and constraints| Tool | When to Use | Purpose |
|---|---|---|
| Architecture planning | Sequential planning with branching for design decisions |
| Design decisions | Multi-model validation of architectural choices |
| Complex systems | Deep analysis of system requirements |
| Brainstorming | Collaborative design exploration |
| API standards | Get current API design best practices |
# Architecture planning
mcp__pal__planner(
step="Designing microservices architecture for e-commerce platform",
step_number=1,
total_steps=4,
more_steps_needed=True
)
# Validate design with consensus
mcp__pal__consensus(
models=[
{"model": "gpt-5.2", "stance": "for"},
{"model": "gemini-3-pro", "stance": "against"},
{"model": "deepseek", "stance": "neutral"}
],
step="Evaluate: Should we use event sourcing for the order management system?"
)
# Deep system analysis
mcp__pal__thinkdeep(
step="Analyzing scalability requirements for real-time notification system",
hypothesis="WebSocket with Redis pub/sub will handle 100k concurrent users",
confidence="medium",
focus_areas=["scalability", "reliability", "performance"]
)| Tool | When to Use | Purpose |
|---|---|---|
| External tools | Find diagramming, documentation tools |
| Share designs | Post to Notion, Confluence, Slack |
| Design workflows | Save reusable design processes |
# Create design document in Notion
mcp__rube__RUBE_SEARCH_TOOLS(queries=[
{"use_case": "create notion page", "known_fields": "database:Architecture"}
])
mcp__rube__RUBE_MULTI_EXECUTE_TOOL(tools=[
{"tool_slug": "NOTION_CREATE_PAGE", "arguments": {
"title": "Payment API Design v2",
"content": "## Overview\n..."
}}
])
# Share design for review
mcp__rube__RUBE_MULTI_EXECUTE_TOOL(tools=[
{"tool_slug": "SLACK_SEND_MESSAGE", "arguments": {
"channel": "#architecture",
"text": "New design ready for review: Payment API v2"
}},
{"tool_slug": "JIRA_CREATE_ISSUE", "arguments": {
"project": "ARCH",
"summary": "Review: Payment API Design",
"issue_type": "Task"
}}
])| Flag | Type | Default | Description |
|---|---|---|---|
| bool | false | Use PAL planner for systematic design |
| bool | false | Validate design with multi-model consensus |
| string | - | Share via Rube (notion, confluence, slack) |
| bool | false | Create review ticket via Rube |