sc-design
Skill4 starsChanged 8 months agoMITView on GitHub
Design system architecture, APIs, and component interfaces with comprehensive specifications. Use when planning architecture, designing APIs, creating component interfaces, or modeling databases.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Tony363/SuperClaudeword for word, first seen Apr 4, 2026
Other versions1 project uses a version of this.
Word for word · 1
- Tony363/SuperClaude★ 19100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-data-engineerSkill
- agent-fullstack-developerSkill
- agent-kubernetes-specialistSkill
- agent-ml-engineerSkill
- agent-performance-engineerSkill
- agent-react-specialistSkill
- agent-security-engineerSkill
- agent-technical-writerSkill
- ask-multiSkill
- askSkill
- learned-skills-indexSkill
- sc-analyzeSkill
- sc-brainstormSkill
- sc-buildSkill
- sc-cicd-setupSkill
- sc-code-reviewSkill
- sc-documentSkill
- sc-e2eSkill
- sc-estimateSkill
- sc-evaluateSkill
- sc-explainSkill
- sc-gitSkill
- sc-implementSkill
- sc-improveSkill
- sc-log-fixSkill
- sc-mcpSkill
- sc-pr-checkSkill
- sc-pr-fixSkill
- sc-principlesSkill
- sc-pushSkill
- sc-readmeSkill
- sc-researchSkill
- sc-tddSkill
- sc-testSkill
- sc-workflowSkill
- sc-worktreeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Design: - Create specifications with best practices
- Distinctive: line 28
Validate: - Ensure maintainability and scalability
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
System & Component Design Skill
Architecture planning and interface design with industry best practices.
Quick Start
# 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 diagramBehavioral Flow
- Analyze - Examine requirements and existing system context
- Plan - Define design approach based on type and format
- Design - Create specifications with best practices
- Validate - Ensure maintainability and scalability
- Document - Generate diagrams and specifications
Flags
| Flag | Type | Default | Description |
--type | string | architecture | architecture, api, component, database |
--format | string | spec | diagram, spec, code |
Evidence Requirements
This skill does NOT require hard evidence. Deliverables are:
- Design specifications and diagrams
- Interface definitions
- Schema documentation
Design Types
Architecture (--type architecture)
- System structure and component relationships
- Scalability and reliability patterns
- Service boundaries and communication
API (--type api)
- RESTful/GraphQL endpoint design
- Request/response schemas
- Authentication and versioning
Component (--type component)
- Interface contracts and dependencies
- State management patterns
- Integration points
Database (--type database)
- Entity relationships and constraints
- Normalization and indexing
- Performance considerations
Output Formats
Diagram (--format diagram)
- ASCII or Mermaid diagrams
- Component relationship visualization
- Data flow representation
Specification (--format spec)
- OpenAPI/Swagger for APIs
- Detailed interface documentation
- Technical requirements
Code (--format code)
- Interface definitions
- Type declarations
- Skeleton implementations
Examples
System Architecture
/sc:design user-management --type architecture --format diagram
# Component relationships, data flow, scalability patternsAPI Design
/sc:design payment-api --type api --format spec
# OpenAPI spec with endpoints, schemas, auth patternsComponent Interface
/sc:design notification-service --type component --format code
# TypeScript/Python interfaces with clear contractsDatabase Schema
/sc:design inventory-db --type database --format diagram
# ER diagrams with relationships and constraintsMCP Integration
PAL MCP (Design Validation)
| Tool | When to Use | Purpose |
mcp__pal__planner | Architecture planning | Sequential planning with branching for design decisions |
mcp__pal__consensus | Design decisions | Multi-model validation of architectural choices |
mcp__pal__thinkdeep | Complex systems | Deep analysis of system requirements |
mcp__pal__chat | Brainstorming | Collaborative design exploration |
mcp__pal__apilookup | API standards | Get current API design best practices |
PAL Usage Patterns
# 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"]
)Rube MCP (Documentation & Collaboration)
| Tool | When to Use | Purpose |
mcp__rube__RUBE_SEARCH_TOOLS | External tools | Find diagramming, documentation tools |
mcp__rube__RUBE_MULTI_EXECUTE_TOOL | Share designs | Post to Notion, Confluence, Slack |
mcp__rube__RUBE_CREATE_UPDATE_RECIPE | Design workflows | Save reusable design processes |
Rube Usage Patterns
# 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"
}}
])Flags (Extended)
| Flag | Type | Default | Description |
--pal-plan | bool | false | Use PAL planner for systematic design |
--consensus | bool | false | Validate design with multi-model consensus |
--share | string | - | Share via Rube (notion, confluence, slack) |
--create-ticket | bool | false | Create review ticket via Rube |
Tool Coordination
- Read - Requirements analysis
- Grep/Glob - Pattern analysis
- Write - Design documentation
- Bash - External tool integration
- PAL MCP - Design planning, consensus validation, deep analysis
- Rube MCP - Documentation sharing, collaboration, review workflows
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

