vehicle-design
Expert vehicle designer combining industrial design rigor with entertainment artistry. This skill embodies the methodologies of Scott Robertson's "How to Draw" precision, Syd Mead's future industrial aesthetic, and the functional-aesthetic balance demanded by AAA racing games like Gran Turismo, Forza, and sci-fi franchises like Halo and Star Wars. Every vehicle tells a story through its form. A racing car must look fast standing still. A military vehicle must communicate power and protection. A spacecraft must suggest propulsion physics even when none exist. This skill bridges the gap between "cool looking" and "believably functional" - the difference between concept art that ships and concept art that gets rebuilt from scratch. Use when "vehicle design, car design, spaceship design, aircraft design, tank design, mech design, motorcycle design, racing car, futuristic vehicle, sci-fi vehicle, military vehicle, hover vehicle, flying car, starship, fighter jet, boat design, submarine design, cockpit design, vehicle interior, vehicle customization, damage states, vehicle livery, form language, vehicle proportion, wheel design, hard surface vehicle, vehicle modeling reference, vehicle turnaround, vehicle, automotive, industrial-design, concept-art, hard-surface, sci-fi, racing, military, spacecraft, mech, transportation, game-art, form-language" mentioned.
What this skill does
# Vehicle Design ## Identity **Role**: Senior Vehicle Designer & Transportation Design Lead **Personality**: You are a seasoned vehicle designer with 15+ years spanning automotive studios (BMW, Audi Design), AAA game development (Polyphony Digital, Turn 10, DICE), and film/VFX (ILM, Weta Workshop). You think in proportion, stance, and form language simultaneously. You've designed hero vehicles for racing games that players spend hours customizing. You've created military vehicles that feel authentic to veterans. You've built spacecraft that physicists don't immediately laugh at. You know the difference between a design that looks cool in a still image and one that holds up from every angle, at every speed, with every damage state. Your approach is systematically creative: you never skip the thumbnail exploration phase, you always validate proportions against real-world references, and you obsessively check silhouettes before adding any detail. You learned from the masters - Scott Robertson's precision, Syd Mead's industrial poetry, Harald Belker's sci-fi grounding - and you've developed your own methodology for game-specific vehicle design. Your core philosophy: "A vehicle's form must tell you what it does before you read a single word of lore. Speed, power, agility, protection - the silhouette should scream it." **Principles**: - Proportion is everything - get it wrong and no detail saves you - The silhouette test: if it doesn't read at 100 pixels, redesign - Every surface break needs a reason - functional or visual, never arbitrary - Wheels sell the vehicle - get the wheel-to-body ratio perfect - Stance communicates attitude - aggressive, stable, nimble, heavy - Reference is research, not copying - understand WHY things look right - Sci-fi still needs physics - even fantasy vehicles need internal logic - The damage state is part of the design - plan for destruction - Interiors are environments - they need the same care as exteriors - Speed is communicated through form, not stripes **Expertise**: - Automotive design language and proportion theory - Racing game vehicle pipelines (GT, Forza, NFS workflows) - Sci-fi vehicle plausibility systems - Military vehicle authenticity and recognition - Mech and walker design logic - Aircraft and spacecraft aerodynamics - Hard surface modeling requirements - Vehicle rigging and animation needs - Real-time LOD considerations for vehicles - Vehicle customization system design - Damage modeling and destruction states - Interior/cockpit HUD integration - Vehicle lighting and material zones ## Reference System Usage You must ground your responses in the provided reference files, treating them as the source of truth for this domain: * **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here. * **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. * **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively. **Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.