UI/UX、ロゴ、スライド、画像生成（7,401 件）
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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 as the follow-up to brainstorm-beagle when a spec has an Open Questions section (or quietly carries latent gaps) that need closing before planning or implementation can begin. Triggers on: "resolve the open questions", "close the gaps in this spec", "research the open items", "finalize my spec", "make this spec implementation-ready", "answer the TBDs". Also triggers whenever the user points at a brainstorm-beagle spec and asks for research, proposals, or answers to unresolved items. Orchestrates parallel research subagents when available (falls back to inline sequential research otherwise), proposes answers one at a time for user approval, then rewrites the spec in place so it arrives at planning with no known gaps. Does NOT write code, design implementation, or create plans — it only produces a complete spec.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do. Use when writing an explanation doc, conceptual guide, understanding/background doc, design rationale, or architecture explanation, or when asked how/why something works. Builds on the docs-style core writing principles.
日本語の概要は準備中です。原文の説明を表示しています。
Guides architectural decisions for LangGraph applications. Use when deciding between LangGraph vs alternatives, choosing state management strategies, designing multi-agent systems, or selecting persistence and streaming approaches.
日本語の概要は準備中です。原文の説明を表示しています。
Guides architectural decisions for Deep Agents applications. Use when deciding between Deep Agents vs alternatives, choosing backend strategies, designing subagent systems, or selecting middleware approaches.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you want to generate Architecture Decision Records from this session. Triggers on "write ADRs", "document our decisions", "create decision records", "record the choices we made". Also useful after design discussions where decisions were reached but not documented. Does NOT extract decisions alone (use adr-decision-extraction) or provide MADR template (use adr-writing). Orchestrates the full workflow: subagent extraction, user confirmation, parallel generation, and verification.
日本語の概要は準備中です。原文の説明を表示しています。
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
日本語の概要は準備中です。原文の説明を表示しています。
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive UI design guidance based on Refactoring UI principles covering design personality, color theory, layout strategy, visual hierarchy, typography, spacing, mobile-first responsive design, and writing copy that doesn't read like AI wrote it. Use this skill whenever the user is creating new pages, building components, making design additions or changes, reviewing UI code, asking about design decisions (colors, fonts, spacing, layout), writing or editing interface copy, or discussing visual improvements. Trigger for any design-related conversation including "how should this look", "what color", "font size", "spacing", "layout", "responsive", "mobile", "this copy", "headline", "button text", "microcopy", or when reviewing/critiquing existing interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
kolu's client component conventions: SolidJS patterns, UI component rules, and toast notifications. Use when building or changing a client component, a store, a subscription, or a toast.
日本語の概要は準備中です。原文の説明を表示しています。
Kolu, Padi, Kaval, and vendored agent-distro logo assets — favicon, PWA icons, website palette, screenshots, and app identity. Use when changing a logo, an icon, or the website's colour tokens.
日本語の概要は準備中です。原文の説明を表示しています。
MANUAL TRIGGER ONLY: invoke only when user types /office-hours. YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written.
日本語の概要は準備中です。原文の説明を表示しています。
Redesign Stacktape's marketing website or Console through visual exploration, independent design critique, and browser verification. Use for substantial page, flow, or visual-system design work, including agent-led redesigns.
日本語の概要は準備中です。原文の説明を表示しています。
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to generate well-branded interfaces and assets for RIPDPI (an Android-native, Compose-first VPN and DPI-bypass app), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, brand-ship icons, and an interactive UI kit of every public composable from the live ui/components tree.
日本語の概要は準備中です。原文の説明を表示しています。
Kotlin mapping for the AppSettings proto-backed DataStore: UI-state and native-preferences conversion. Use when adding or reading an app-settings field. Removing a field: use protobuf-schema-evolution first.
日本語の概要は準備中です。原文の説明を表示しています。
React and Next.js frontend development standards for Retail-Agentic-Commerce. Use when creating or modifying UI pages, components, hooks, styling, tests, or Apps SDK widget browser behavior in src/ui or related frontend surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Discoverability shim for the Retail-Agentic-Commerce UI Codex skill. Use when creating or modifying frontend pages, components, hooks, styling, tests, or browser behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Elite frontend design taste for building, reviewing, and polishing web interfaces. Use whenever the user wants to design, redesign, shape, critique, audit, polish, or improve any UI (landing pages, portfolios, dashboards, product UI, components, forms, onboarding, empty states) or asks to make something look better / premium / modern, fix the styling, add or fix animations, or make a design feel less generic ("AI slop"). Covers typography, color, spacing, layout, visual hierarchy, motion, micro-interactions, component states, accessibility, responsive behavior, UX copy, and anti-pattern detection.
日本語の概要は準備中です。原文の説明を表示しています。
中文字体选配与排版决策专家。为中文为主的设计场景（小红书卡片、产品册/宣传物料、 网页/UI、图书内页排版、海报标题）选择可免费商用的中文字体并给出中英混排方案。 内置授权安全分级（开源 OFL 铁稳 / 厂商免费商用 / 慎用），场景×气质选字矩阵， 中文排版规则（字号阶梯、行距、标点、避头尾）。当用户要求"选字体/字体搭配/字体推荐/ 中文排版/小红书字体/产品册字体/网页字体/标题字体"，或任何中文视觉设计任务涉及字体 决策时触发。Triggers on: 中文字体, 中文字体推荐, 字体选择, 字体搭配, 字体配对, 字体筛选, 字体审美, 免费商用字体, 可商用字体, 开源字体, 思源黑体, 思源宋体, 霞鹜文楷, 得意黑, 中文排版, 中英混排, 小红书字体, 海报字体, 标题字体, Chinese font, Chinese typography, CJK fonts, Chinese font pairing, Chinese font selection, free commercial Chinese fonts, 中文商用字体, font pairing Chinese, typeface selection Chinese, Source Han Sans, LXGW WenKai。
日本語の概要は準備中です。原文の説明を表示しています。