Design e Frontend

The technology design process from needs assessment through iteration, covering empathy mapping, design briefs, concept development, prototyping, user testing, and iterative refinement. Integrates design thinking methodology (Stanford d.school) with engineering design process (ITEEA) and Don Norman's human-centered design principles. Use when designing technology solutions, evaluating existing des

Test real system boundaries, not mocks of mocks. Integration tests verify that components work together, not that they work in isolation.

Esta skill é para criar transições personalizadas no Remotion, como estilos 'legais', 'cinematográficos', 'listrados' ou 'com falhas', e para construir transições de cena a cena além da biblioteca padrão. Também atende a perguntas sobre 'como fazer transições no Remotion', 'transição personalizada' ou 'transições de alta energia'.

Graceful degradation and meaningful error messages. Errors are first-class citizens, not afterthoughts. Every error path is designed, not discovered.

Designs and coordinates multi-agent pipelines where specialized agents collaborate to complete complex tasks. Includes communication protocols, failure handling, and state management.

Accessible, performant, responsive UI patterns. Component design, state management discipline, and Core Web Vitals compliance.

Use when starting any conversation, when the user asks "what should I do", "help me", "how do I use shipyard", or "where do I start". Establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions. Also use when unsure which skill or command applies to the current situation.

Import a handwritten spec document into Shipyard, replacing brainstorming. Use when a freeform spec, requirements, or design document exists.

Use when you have a written implementation plan to execute, either in the current session with builder/reviewer agents or in a separate session with review checkpoints. Also use when the user says "build this", "implement this", "execute the plan", "run the plan", or when a plan file has been loaded with independent tasks suitable for agent dispatch.

Use when you have a spec, requirements, or design for a multi-step task — before touching code. Also triggers on "plan this", "break this down", "create tasks", "decompose this feature", or when a task clearly needs more than 2-3 steps to implement. If you're about to start building without a plan, or writing vague tasks like "implement feature X" without file paths and verification commands, this

You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design through Socratic dialogue before implementation. Also use when the user says "I want to add", "let's design", "what if we", "I have an idea", or when a design discussion is happening. Invoked by /shipyard:brainstorm for req

Low-ticket tripwire funnel that converts cold leads into buyers with an irresistible $7–$47 offer, then upsells to the core product. Best for building a buyer list and offsetting ad spend.