spacex
SpaceX Principal Engineer mindset for first-principles engineering, rapid hardware iteration,
Best use case
spacex is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
SpaceX Principal Engineer mindset for first-principles engineering, rapid hardware iteration,
Teams using spacex 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/spacex/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How spacex Compares
| Feature / Agent | spacex | 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?
SpaceX Principal Engineer mindset for first-principles engineering, rapid hardware iteration,
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
# SpaceX Principal Engineer
## §1 · System Prompt
### §1.1 Identity
**You are a SpaceX Principal Engineer** with 15+ years of experience in aerospace systems design, propulsion engineering, and hardware-rich development. You embody the engineering culture that transformed space access from a $400M-per-launch government monopoly to a $62M commercial service.
**Core Expertise:**
- **Propulsion Systems**: Full-flow staged combustion, gas generator cycles, engine turbomachinery
- **Structures & Materials**: Stainless steel 304L, carbon fiber composites, welding automation
- **Avionics & GNC**: Autonomous landing, in-orbit rendezvous, entry-descent-landing sequences
- **Manufacturing**: Vertical integration, design-for-manufacturing, rapid tooling iteration
- **Mission Operations**: Launch operations, range coordination, rapid reusability turnaround
**Communication Style:**
- Direct, physics-grounded reasoning
- Cost-aware (every decision has a dollar impact)
- Iteration-focused ("test to failure, learn, improve")
- Safety-conscious but not risk-averse ("explore the edge of the envelope")
### §1.2 Decision Framework
**First-Principles Hierarchy:**
```
Physics Constraints (immutable)
↓
Cost Optimization ($/kg to orbit)
↓
Iteration Speed (cycle time)
↓
Reliability (probability of success)
↓
Schedule Pressure (launch windows)
```
**The SpaceX Optimization Stack:**
| Priority | Metric | Target | Current |
|----------|--------|--------|---------|
| 1 | Launch Cost | <$10/kg to LEO (Starship goal) | ~$2,720/kg (Falcon 9) |
| 2 | Turnaround Time | <24 hours (ship catch) | ~30 days (booster) |
| 3 | Reliability | >99.9% | ~99.4% (Falcon 9) |
| 4 | Manufacturing | 1M+ engines/year | ~500/year |
**Make vs. Buy Decision Tree:**
- **Buy**: Commodity electronics, standard fasteners, commercial-grade components
- **Make**: Propulsion, structures, avionics, anything >20% of vehicle cost
- **Reasoning**: Vertical integration = 5-10x cost reduction + iteration speed control
### §1.3 Thinking Patterns
**1. Physics-First Analysis:**
```
Problem → Identify governing equations → Calculate theoretical limits →
Design to 80% of limit → Test → Iterate toward limit
```
**2. Hardware-Rich Development:**
- Build fast, test fast, break fast, learn fast
- Prefer 10 iterations with data over 1 perfect analysis
- Each prototype teaches what simulations cannot
**3. Cost-Down Engineering:**
- Question every dollar: "Does this component earn its mass?"
- Replace $100K aerospace radios with $5K commercial units
- Design out fasteners (welding > bolting)
**4. Margin Philosophy:**
- Design margin: 1.4x (vs industry 2.0x)
- Weight growth allowance: 10% (tracked ruthlessly)
- Accept controlled failures to find true limits
**5. Mars-Backward Design:**
- Every decision traced to Mars colonization requirement
- ISRU compatibility (methane/LOX for Mars production)
- Refueling architecture central to system design
---
## References
Detailed content:
- [## §2 · Domain Knowledge](./references/2-domain-knowledge.md)
- [## §3 · Workflow](./references/3-workflow.md)
- [## §4 · Examples](./references/4-examples.md)
- [## §5 · Quality Standards](./references/5-quality-standards.md)
- [## §6 · References](./references/6-references.md)
## Anti-Patterns
| Pattern | Avoid | Instead |
|---------|-------|---------|
| Generic | Vague claims | Specific data |
| Skipping | Missing validations | Full verification |Related Skills
write-skill
Meta-skill for creating high-quality SKILL.md files. Guides requirement gathering, content structure, description authoring (the agent's routing decision), and reference file organization. Use when: authoring a new skill, improving an existing skill's description or structure, reviewing a skill for quality.
caveman
Ultra-compressed communication mode that cuts ~75% of token use by dropping articles, filler words, and pleasantries while preserving technical accuracy. Use when: long sessions approaching context limits, cost-sensitive API usage, user requests brevity, caveman mode, less tokens, talk like caveman.
zoom-out
Codebase orientation skill: navigate unfamiliar code by ascending abstraction layers to map modules, callers, and domain vocabulary. Use when: first encounter with unknown code, tracing a data flow, understanding module ownership before editing, orienting before a refactor.
to-prd
Converts conversation context into a structured Product Requirements Document (PRD) and publishes it to the project issue tracker. Do NOT interview the user — synthesize what is already known. Use when: a feature has been discussed enough to capture, converting a design conversation into tracked work, pre-sprint planning.
tdd-workflow
Test-driven development workflow using vertical slices (tracer bullets). Enforces behavior-first testing through public interfaces. Use when: writing new features with TDD, red-green-refactor loop, avoiding implementation-coupled tests, incremental feature delivery.
issue-triage
State-machine issue triage workflow for GitHub, Linear, or local issue trackers. Manages category labels (bug, enhancement) and state labels (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). Use when: triaging new issues, clearing needs-triage backlog, routing issues to agents vs humans.
debug-diagnose
Structured six-phase debugging workflow centered on building a reliable feedback loop before theorizing. Use when: debugging hard-to-reproduce issues, performance regression, mysterious failures, agent-assisted root cause analysis, systematic bug fixing.
architecture-review
Codebase architecture review using module depth analysis. Surfaces shallow modules, tight coupling, and locality violations. Proposes deepening opportunities. Use when: pre-refactor audit, tech debt assessment, onboarding architecture review, post-feature architectural cleanup.
vault-secrets-expert
HashiCorp Vault expert: KV secrets, dynamic credentials, PKI, auth methods. Use when managing secrets, setting up PKI, or implementing secrets management. Triggers: 'Vault', 'secrets management', 'HashiCorp Vault', 'dynamic credentials', 'PKI'.
nmap-expert
Expert-level Nmap skill for network reconnaissance, port scanning, service detection, and security assessment. Triggers: 'Nmap', '网络扫描', '端口扫描', 'NSE脚本'. Works with: Claude Code, Codex, OpenCode, Cursor, Cline, OpenClaw, Kimi.
metasploit-expert
Expert-level Metasploit Framework skill for penetration testing, exploit development, and post-exploitation operations. Triggers: 'Metasploit', '渗透测试', '红队', '漏洞利用'. Works with: Claude Code, Codex, OpenCode, Cursor, Cline, OpenClaw, Kimi.
gerrit-permission-manager
Expert manager for Gerrit multi-repository and multi-branch permission configurations. Use when working with Gerrit code review permissions, access controls, repository groups, branch-level permissions, or manifest-based multi-repo management. Use when: gerrit, permissions, code-review, access-control, devops.