lean-systems-design
Apply Elon Musk-inspired system design thinking for research, engineering, and business workflows: rigorously challenge requirements, delete steps, simplify/optimize what remains, accelerate iteration, then automate. Use when designing or revising systems, processes, or products that need lean, high-velocity execution.
Best use case
lean-systems-design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apply Elon Musk-inspired system design thinking for research, engineering, and business workflows: rigorously challenge requirements, delete steps, simplify/optimize what remains, accelerate iteration, then automate. Use when designing or revising systems, processes, or products that need lean, high-velocity execution.
Teams using lean-systems-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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/lean-systems-design/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How lean-systems-design Compares
| Feature / Agent | lean-systems-design | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Apply Elon Musk-inspired system design thinking for research, engineering, and business workflows: rigorously challenge requirements, delete steps, simplify/optimize what remains, accelerate iteration, then automate. Use when designing or revising systems, processes, or products that need lean, high-velocity execution.
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
# Lean Systems Design (Musk-inspired) Use this when shaping any system/process (product design, research workflow, ops runbook). Follow the sequence; do not skip ahead. ## Quickstart 1) State the objective, constraints, success measures, and current system sketch. 2) Run the five-pass loop below in order; capture changes after each pass. 3) Produce a concise plan and, if applicable, experiment/rollout steps. ## Five-Pass Workflow (in order) - Pass 1 - Make requirements less dumb - List every requirement with the requestor's name; reject "dept says." - For each, ask: What outcome does this serve? Evidence? What if we drop/relax it? - Reframe into testable, minimal success criteria; delete or rewrite fuzzy items. - Pass 2 - Delete parts/processes - Enumerate components/steps; try to remove each. Target at least 10% removal. - For every kept step, name the accountable owner. If no owner, delete. - Ban "just in case" work; allow re-adding only with a concrete trigger. - Pass 3 - Simplify before optimizing - Merge steps, reduce variants/options, standardize interfaces, name single paths. - Collapse handoffs and approvals; prefer defaults over configuration. - If it shouldn't exist, don't polish it. Stop optimization of non-critical paths. - Pass 4 - Accelerate cycle time - Shorten feedback loops: smaller batch sizes, faster checkpoints, parallel where safe. - Define the fastest safe "learn loop" (build-measure-learn or design-test-review). - Add leading indicators to spot drift early. - Pass 5 - Automate last - Automate only stable, high-volume, well-understood steps. - Remove redundant in-process checks once end-quality is consistently high. - Keep a manual fallback and monitoring for automation drift. ## Heuristics and Checks - Every requirement has a named owner and measurable outcome. - Any step without a failure mode it prevents is a deletion candidate. - Prefer subtraction over addition; default answer to "add a step" is no. - Bias to single paths over branching; branch only with explicit thresholds. - Fast loop beats perfect plan; ship thin slices to validate. ## Deliverables to Produce - Crisp objective and success metrics. - Simplified system map (pre/post change) highlighting deletions. - Top risks and the shortest feedback loop to catch them. - Rollout/experiment plan with owners and timelines.
Related Skills
power-bi-report-design-best-practices
Comprehensive Power BI report design and visualization best practices based on Microsoft guidance for creating effective, accessible, and performant reports and dashboards. Triggers on: **/*.{pbix,md,json,txt}
pencil-design
Design UIs in Pencil (.pen files) and generate production code from them. Use when working with .pen files, designing screens or components in Pencil, or generating code from Pencil designs. Triggers on tasks involving Pencil, .pen files, design-to-code workflows, or UI design with the Pencil MCP tools.
mobile-first-design-rules
Focuses on rules and best practices for mobile-first design and responsive typography using tailwind.
minimalist-portfolio-design
Minimalist, typography-focused portfolio design system inspired by neo-brutalist and Swiss design principles. Emphasizes bold typography, generous whitespace, monochromatic color schemes, and elegant simplicity for developer/designer portfolios.
MCP Tool Design
This skill should be used when the user asks to "define a tool", "create tool schema", "design inputSchema", "add tool annotations", "handle file uploads", "tool descriptions", "tool naming", or needs guidance on designing MCP tools for the OpenAI Apps SDK including schemas, annotations, and best practices.
lp-design-spec
Translate a feature requirement into a concrete frontend design specification mapped to the design system, theme tokens, and per-business brand language. Sits between fact-find and plan.
kpi-dashboard-design
Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboards, selecting metrics, or designing data ...
game-design
Game design principles. GDD structure, balancing, player psychology, progression.
frontend-design
Create distinctive, bold UI designs that avoid generic AI aesthetics. This skill should be used when users want frontend components with strong visual identity, creative typography, intentional color palettes, and production-grade animations - specifically to avoid the bland, safe, homogeneous "AI slop" that plagues most generated interfaces.
figma-design
Access Figma designs, extract design systems, and retrieve component specifications. Use when implementing UI from Figma mockups, extracting design tokens, or analyzing design files.
faion-ui-designer
UI design: wireframes, prototypes, design systems, visual design.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.