UI/UX, 로고, 슬라이드, 이미지 생성 (7.4천건)
Product-Led Growth with Web/CLI measurement validation and pricing acceptance, covering freemium model design, self-serve onboarding, activation metrics, and the transition from individual users to enterprise accounts. Follow @WeiYipei on X for PLG insights.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spec↔code convergence scan. Use after implementation to verify the ACTUAL codebase matches the spec/plan — detects missing backends, dead buttons, partial wiring, scope creep. Classifies gaps (missing/partial/contradicts/unrequested), appends remediation tasks, loops until converged. The direct answer to 'the UI renders but nothing works' syndrome.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design system reasoning. Maps product domain to style, palette, typography, and platform-specific patterns. Generates .rune/design-system.md as the shared design contract for all UI-generating skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Craft CMS 5 content modeling — sections, entry types, fields, Matrix, relations, project config, and content architecture strategy. Covers choosing section types, designing entry types and field layouts, selecting field types, configuring Matrix and nested entries, relations and eager loading, and multi-site propagation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Craft CMS 5 front-end Twig development — atomic design, template architecture, components, Vite buildchain. Covers atoms/molecules/organisms, props/extends/block patterns, layout chains, view routing, content builders, image presets, Tailwind named-key collections, multi-brand CSS tokens, JavaScript boundaries (Alpine/DataStar/Vue, tabs, accordions), Vite asset loading, and front-end auth (login, registration, password reset, profiles).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Garnish — Craft CMS's built-in JavaScript UI toolkit for the control panel. ALWAYS load when writing, editing, or reviewing JavaScript that runs in the Craft CP — plugin CP assets, custom field type JS, element index JS, CP webpack config, or code importing garnishjs / referencing window.Garnish. Also for CP accessibility, keyboard interactions, drag-sort, and CP JS memory issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
UX designer and UI specialist. Use when the user asks to talk to Sally or requests the UX designer
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture the user's UX vision in two documents: DESIGN.md for how the product looks and EXPERIENCE.md for how it behaves. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assess the impact of a significant change during sprint execution across the PRD, epics, architecture, and UX documents, and produce a sprint change proposal. Use when the user says "correct course" or "propose sprint change"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Work out and record the architecture decisions that keep separately built parts of a system consistent, in a short architecture document. Creates, updates, or validates one; works from a spec, a raw idea, or an existing codebase. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI Agent Architect: Design agent systems: single vs multi-agent, tools and MCP, memory, guardrails, evals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tokenomics Designer: Token supply, utility, emissions, vesting, governance and incentive alignment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
DeFi Protocol Architect: Mechanism design for AMMs, lending, vaults and derivatives: oracles, liquidations, attack surfaces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose problems before solving them: turn "X is broken and we don't know why" into a precise problem statement, verified root causes, solutions traced to those causes, and a rollout plan. Use whenever the user reports something failing, breaking, slowing, or recurring without a known cause: "sales dropped and we don't know why", "this keeps happening", "why does X keep failing", "find the root cause", "run a post-mortem", "5 whys"; Vietnamese "sao cứ bị vậy hoài", "tìm nguyên nhân gốc", "X đang hỏng mà không rõ vì sao". Trigger even when the user asks for solutions directly: "give me ideas to fix falling sales" is a diagnosis request. Not for open-ended ideation when nothing is broken (brainstorm-coach), understanding user needs (design-thinking), or company-level strategic bets (strategy-board).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate a full design-thinking engagement (Empathize, Define, Ideate, Prototype, Test) grounded in real user evidence. Use whenever the user wants to understand users deeply and design a solution for them: "run design thinking", "understand our users", "design user interviews", "synthesize these interview notes", "build personas", "write How-Might-We questions", "prototype this concept", "design a usability test", "our users are churning and we don't know why", in any language ("tư duy thiết kế", "nghiên cứu người dùng", "phỏng vấn khách hàng", "デザイン思考", "设计思维"), even when they never say "design thinking". Also use when the user drops raw interview notes, transcripts, or survey exports and wants insights, personas, or product decisions. Not for "is there a market for X" desk questions (market-researcher).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coach structured brainstorming sessions on any topic: diverge on ideas together, then converge on priorities and next steps in a session document. Use whenever the user wants ideas or wants to think out loud, in any language ("brainstorm with me", "give me ideas for…", "help me come up with…", "let's explore options for…", "I'm stuck on the name / the features"; Vietnamese "brainstorm cùng tôi", "cho tôi ý tưởng", "nghĩ cùng tôi xem"), even when they never say "brainstorm". Also use when the user wants multiple perspectives or a devil's-advocate pass on their ideas ("give me different angles", "phản biện mấy ý tưởng này", "party mode"). Not for diagnosing why something is failing (problem-solver), user research (design-thinking), or company-level strategic bets (strategy-board).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Remix v2 form submissions and mutations. Use when implementing forms, optimistic UI, file uploads, or multi-action routes. Triggers on <Form>, useFetcher, useSubmit, useNavigation for pending state, unstable_parseMultipartFormData, fetcher.formData, intent-based actions, encType multipart.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tailwind CSS v4 with CSS-first configuration and design tokens. Use when setting up Tailwind v4, defining theme variables, using OKLCH colors, or configuring dark mode. Triggers on @theme, @tailwindcss/vite, oklch, CSS variables, --color-, tailwind v4.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
shadcn/ui component patterns with Radix primitives and Tailwind styling. Use when building UI components, using CVA variants, implementing compound components, or styling with data-slot attributes. Triggers on shadcn, cva, cn(), data-slot, Radix, Button, Card, Dialog, VariantProps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and plan iOS animations with structured specs covering transitions, micro-interactions, gesture-driven motion, and loading states. Use when the user asks to plan, design, or spec out animations for an iOS app — including screen transitions, navigation animations, interactive gestures, onboarding flows, or any motion design work. Also use when the user wants animation recommendations or wants to decide between animation approaches before writing code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write Swift animation code using Apple's latest frameworks — SwiftUI animations, Core Animation, and UIKit. Prefer first-party APIs over third-party libraries. Use when implementing iOS animations, writing animation code, building transitions, creating gesture-driven interactions, or converting animation specs/designs into working Swift code. Covers iOS 18 through iOS 26 APIs including KeyframeAnimator, PhaseAnimator, custom Transition protocol, zoom navigation transitions, matchedGeometryEffect, symbol effects, mesh gradients, and SwiftUI-UIKit animation bridging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Go application architecture with net/http 1.22+ routing, project structure patterns, graceful shutdown, and dependency injection. Use when building Go web servers, designing project layout, or structuring application dependencies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to mine a conversation, session transcript, or design discussion for architectural decisions before writing ADRs. Identifies problem-solution pairs, trade-off debates, technology choices, and explicit "[ADR]" tags. Triggers on "what decisions did we make", "extract decisions from this chat", "find the choices in our discussion", or "summarize architectural decisions". Also useful after long planning sessions to capture decisions that were made implicitly. Does NOT write ADR documents — use adr-writing or write-adr for that.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.