Loading...
Loading...
Found 21 Skills
Audit design documents for missing decisions, compatibility risks, rollout gaps, and observability omissions. Use whenever the user asks to review a design doc, architecture proposal, implementation-facing design, plan, or design-adjacent markdown file for completeness, migration strategy, rollback, data handling, or suggested additions without directly editing the document. Also trigger on short requests such as `review <file>.md` or `audit <file>.md` when the target looks like a design, plan, architecture, proposal, or decision document.
Use when any request arrives, and especially when it touches a screen, component, flow, brand, layout, typography, colour, motion, copy, icon, form, table, dashboard, navigation, onboarding, pricing, checkout, notification, accessibility, design system, or brief. Use when choosing between directions, when shaping something unbuilt, when reviewing, critiquing, or shipping work, and during ordinary design conversation. A request that holds no design surface costs one command and nothing else. Keywords: design, redesign, review, crit, critique, feedback, mockup, wireframe, prototype, trade-off, decision, rationale, pre-ship, ready to ship, looks generic, which direction, style guide, design token.
Audits existing surface against lower-layer decisions and produces a surface decision inventory — vocabulary, object consistency, completeness, feedback, hierarchy, accessibility
Turns a jackin' roadmap item's intent into concrete design decisions through freeform discussion, written into its Design section. Use when the operator runs /jackin-dev:brainstorm.
Use when making design decisions, reviewing UI for HIG compliance, choosing colors/backgrounds/typography, or defending design choices - quick decision frameworks and checklists for Apple Human Interface Guidelines
Trace what else a UX, flow, component, content, or design-system change could affect. Use when a designer asks "if we change this, what else moves?", "what else could this affect?", or wants to understand downstream UX impact before committing to a change.
This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning. Triggers on "let's brainstorm", "help me think through", "what should we build", "explore approaches", ambiguous feature requests, or when the user's request has multiple valid interpretations that need clarification.
Synthesizes research findings into design decisions via codebase investigation. Use when (1) translating research into implementation approaches, (2) selecting between design alternatives, (3) executing after /research or deep-research, or (4) preparing input for /plan phase.
Construir protótipos descartáveis para responder uma pergunta técnica, de interação ou visual específica, com a fidelidade mínima suficiente e sem herdar dívida técnica para produção. Use para spikes, provas de conceito e exploração de alternativas antes de uma decisão cara; não promover código de protótipo a produção sem reimplementação e validação completa; não use quando a pergunta já tem resposta documentada, use `$specsfy-specialist-technical-research` para isso.
Evaluate options for a specific design decision node and recommend one with explicit trade-offs. Use when the design already exposes a concrete choice such as architecture style, state management approach, auth model, storage pattern, sync strategy, multi-agent coordination model, language or runtime, UI framework, data-layer library, or tooling selection. Trigger when the user needs structured comparison and recommendation for a bounded design decision. Do not use for broad design discovery, full-system decomposition, or final readiness review.
Choose between competing concepts against criteria fixed in advance, and record what each rejected concept was testing. Use when several directions are alive and one has to win. For picking which problem to work on, use `opportunity-framework` (ux-strategy); for deciding by production traffic, use `a-b-test-design`.
Language-agnostic guidance for selecting and applying Gang of Four (GoF) design patterns to recurring object-oriented design problems. Use when deciding among design alternatives, evaluating applicability and tradeoffs, or refactoring rigid/conditional-heavy designs toward better extensibility and lower coupling. Do not use for trivial bug fixes, framework/tool setup, or tasks with no architectural decision. Any TypeScript examples are illustrative only and must be translated to the project's language and constraints.