system-design

Use when designing system architecture, APIs, components, or data models - provides a structured design workflow with validation and documentation outputs.

13 stars

Best use case

system-design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when designing system architecture, APIs, components, or data models - provides a structured design workflow with validation and documentation outputs.

Teams using system-design should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/system-design/SKILL.md --create-dirs "https://raw.githubusercontent.com/NickCrew/Claude-Cortex/main/skills/system-design/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/system-design/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How system-design Compares

Feature / Agentsystem-designStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when designing system architecture, APIs, components, or data models - provides a structured design workflow with validation and documentation outputs.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# System Design

## Overview
Create clear system, API, component, or data model designs with explicit requirements, constraints, and validation steps.

## When to Use
- Designing system architecture or components
- Specifying APIs or data models
- Producing design docs or diagrams

Avoid when:
- You only need implementation tasks (use implementation-workflow)

## Quick Reference

| Task | Load reference |
| --- | --- |
| System design workflow | `skills/system-design/references/system.md` |

## Workflow
1. Gather requirements and constraints.
2. Load the system design reference.
3. Define structure, interfaces, and data flows.
4. Validate against constraints and best practices.
5. Deliver spec/diagram/code artifacts.

## Output
- Design spec or diagram
- Validation notes and follow-ups

## Common Mistakes
- Designing without constraints
- Mixing implementation details with spec scope

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.