preparing-design-handoff
Prepare a Bitwarden design handoff — the Figma file in Ready-for-Dev state and the Jira state transitions that go with it. The end-of-In-Design gate / checklist.
What this skill does
# Preparing a Design Handoff This skill is the end-of-In-Design gate. Engineering relies on a consistent set of signals to know a design is ready to pick up. A handoff missing any of those signals creates downstream questions and slows the epic into development. ## The handoff is two things, not one A handoff is finished when both are in place: 1. **The Figma file in Ready-for-Dev state.** Final designs grouped on a single page, with sections named to match the engineering stories that will consume them. Sections marked "Ready for Dev" in Figma. User-visible strings (toasts, error messages, form verifications, email body copy) annotated on the frames. Annotated prototype available. 2. **The Jira state aligned.** Figma file linked in the Epic's "Design" field, sections marked Ready for Dev in Figma, and the EM transitions the Epic to `Ready for Dev`. The full choreography is in `navigating-design-jira-process`. If either is missing, the handoff isn't done. ## Prep checklist (before declaring handoff) - The product initiative or PRD page exists and is current. - The engineering Epic exists in Jira and the designer is or has been assigned to it. - Designs have been through critique at 30%, 60%, and 90% and the 90% review has been addressed. - Real-user testing has happened where applicable (this is what 90% is for). - The Figma file's final-designs page is curated — no scratch pages, no unused frames in the Ready-for-Dev surface. - All user-visible strings are annotated in Figma alongside the frames they apply to. If any item is missing, surface that before declaring the handoff ready — handoff is not the moment to discover the 90% review never happened. ## Figma readiness check Before marking sections Ready for Dev, confirm: - **Sections aligned to stories.** Each named section maps to a single engineering story. Avoid sections that span stories or stories that span multiple sections. - **Tokens are library-bound.** No raw hex values where a design-system variable exists. Compose `using-figma` with `get_variable_defs` to verify. - **Strings annotated.** Every user-visible string — button labels, error messages, toasts, empty states, helper text — is present in the Figma frames or annotations. - **Edge cases covered.** Empty, error, partial-success, offline, and premium-gated states exist on the relevant frames (or are explicitly out of scope and noted). ## Composing with other skills - **`using-figma`.** Use `get_metadata` to confirm the Ready-for-Dev sections exist with the expected names; use `get_variable_defs` to confirm tokens are library-bound rather than raw values; use `search_design_system` if a component in the design is suspiciously close to one that already exists. - **`navigating-design-jira-process`.** The Jira moves that go with handoff — link Figma to Epic "Design" field, mark Ready for Dev in Figma, EM transitions Epic — live there. - **`content-style-guide`.** Walk every annotated string through the style guide before declaring handoff. Toasts, errors, and form-verification text are the highest-leverage place to catch content-style issues before engineering localizes them. ## Common omissions to catch - **Figma file with no Ready-for-Dev marks.** Engineering can't find what's final. This is the most-skipped step. - **Sections not aligned to stories.** Each story should map to a Figma section whose content is _only_ that story. Mismatch creates ambiguity at review time. - **Missing string annotations.** Engineering will ask for strings the moment they pick the Epic up. Annotate them in Figma alongside the frames before declaring handoff — don't defer to engineering to invent copy. - **Edge states absent.** Empty, error, partial-success, offline, premium-gated. If they're out of scope, say so explicitly on the frames or in the dev-support comments. ## Output format When asked to help prep a handoff: 1. **Prep checklist** — what's in place, what's missing. 2. **Figma readiness check** — section-to-story alignment, token binding, string annotations, edge states. 3. **Jira moves** — the specific status transitions and Figma links to apply (link to Epic "Design" field, mark sections Ready for Dev, EM transitions Epic). Defer to `navigating-design-jira-process` for the canonical choreography. Always end with the explicit go/no-go: _is this handoff actually ready?_
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.