2.3천건 · 관련도순
Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Solves UI lock-in. Reverse engineers your existing UI, strips all layout/token decisions, preserves every hook, handler, and API call untouched, then rebuilds the UI from scratch with a fresh design system. Use /ui-restructure to fully redesign, --style apple|linear|minimal|dashboard for named styles, --mode layout|theme|grid for partial rebuilds, --god-mode to redesign from the user's perspective using 100-user mindset simulation and 6 UX principles, --keep-tokens to preserve your token system, --prompt for custom redesigns. Applies mandatory world-class polish: spring motion, 5-state micro-interactions, 8pt spacing grid, WCAG accessibility. Supports Next.js, React, Vue 3, Tailwind, CSS Modules, styled-components, shadcn.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a look brief and reference images into a finished social clip: concept, TouchDesigner look and palette, ComfyUI stills, a recorded take, a cut in DaVinci Resolve or Remotion, 9:16 and 16:9 exports, publish only after GO. Use for "moodboard to clip", "make a social clip from these references", "look brief to video".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a live app or landing page into a short launch video: composition brief, render in Hyperframes or Remotion, an ffprobe check per format, publish hand-off only after GO. Use for "launch video", "make a video of the shipped app", "promo clip for the landing page".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when acting as the authoritative design lead for all frontend work, enforcing brand discovery, Anti-Slop rules, DTCG design tokens, fluid motion, and data-driven design generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Liquid Glass material best practices for SwiftUI, UIKit, and AppKit on iOS 26+/macOS 26+ (Tahoe) through iOS 27/macOS 27. Use when implementing, reviewing, or migrating to glass: glassEffect, Glass variants (.regular/.clear/.identity), tint, interactive(), GlassEffectContainer, glassEffectUnion, toolbar glass, ToolbarSpacer, scrollEdgeEffectStyle, sharedBackgroundVisibility, tabBarMinimizeBehavior, backgroundExtensionEffect, NSGlassEffectView, UIGlassEffect, Tahoe window chrome, glass accessibility (Reduce Transparency/Increase Contrast), pre-26 Material fallbacks, UIDesignRequiresCompatibility. Also fires on symptoms: glass renders dark or muddy, glass looks like a flat tinted rectangle, glass button doesn't register taps, tap passes through glass, "'glassEffect' is only available in iOS 26.0 or newer", "ambiguous use of 'opacity'", "'cornerRadius' was deprecated", glass looks different in simulator vs device, screenshots of glass UI don't match. For glass animation, morphing, glassEffectID, transitions, Metal shaders, or performance profiling use the liquid-glass-motion skill instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply platform accessibility best practices to SwiftUI, UIKit, and AppKit code. Essential companion to any SwiftUI, UIKit, or AppKit skill — always use together. Use whenever writing, editing, or reviewing ANY SwiftUI views, UIKit view controllers, AppKit views/window controllers, or platform UI — even when the user doesn't mention accessibility. Also use when the user mentions VoiceOver, Voice Control, Dynamic Type, Reduce Motion, screen reader, a11y, WCAG, accessibility audit, Nutrition Labels, accessibilityLabel, UIAccessibility, NSAccessibility, assistive technologies, or Switch Control. Not for server-side Swift, non-UI packages, or CLI tools.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate engaging, localized App Store release notes (What's New) from git log, bullet points, or free text using canonical metadata under `./metadata`. Optionally pairs with promotional text updates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement, review, or improve in-app purchases and subscriptions using StoreKit 2. Use when building paywalls with SubscriptionStoreView or ProductView, processing transactions with Product and Transaction APIs, verifying entitlements, handling purchase flows (consumable, non-consumable, auto-renewable), implementing offer codes or promotional/win-back/introductory offers, managing subscription status and renewal state, setting up StoreKit testing with configuration files, or integrating Family Sharing, Ask to Buy, refund handling, and billing retry logic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement, review, or improve SwiftUI animations and transitions. Use when adding explicit animations with withAnimation, configuring implicit animations with .animation(_:body:) or .animation(_:value:), configuring spring animations (.smooth, .snappy, .bouncy), building phase or keyframe animations with PhaseAnimator/KeyframeAnimator, creating hero transitions with matchedGeometryEffect or matchedTransitionSource, adding SF Symbol effects (bounce, pulse, variableColor, breathe, rotate, wiggle), implementing custom Transition or CustomAnimation types, or ensuring animations respect accessibilityReduceMotion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build iOS App Clips with invocation URLs, NFC, QR codes, App Clip Codes, Safari banners, Maps, Messages, and shared App Group data handoff to the full app. Covers target setup, experience configuration, size limits, NSUserActivity handling, SKOverlay promotion, location confirmation, and capability limits. Use when creating App Clips or wiring App Clip invocation and full-app migration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when: 'intake this repo/skill', 'evaluate external skill', 'should we adopt X', a candidate repo URL plus an adoption question, or any external skill/workflow/tool surfaces as a possible fit for Agistra. Structured front-door evaluation of external skills, workflows, and similar capability artifacts before any install, promotion, or adaptation decision. Ends in exactly one classification: Install candidate, Adapt concept, or Reject. Never install first — intake first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flow with sub-800ms latency while handling interruptions, background noise, and emotional nuance. This skill covers two architectures: speech-to-speech (OpenAI Realtime API, lowest latency, most natural) and pipeline (STT→LLM→TTS, more control, easier to debug). Key insight: latency is the constraint. Hu
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, audit, and improve accessibility and inclusive user experiences. Use when Codex is asked about WCAG, keyboard navigation, focus states, screen readers, ARIA, contrast, captions, reduced motion, forms, semantic HTML, accessible UI, game accessibility, inclusive design, accessibility QA, or compliance-sensitive accessibility work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing inclusive animations, addressing vestibular disorders and motion sensitivity, or ensuring animation accessibility compliance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Kelly Retail Intel: App-in-Skill daily industry intelligence cockpit for retail stores and consumer brands (Busabase App-in-Skill). Use when the user asks about retail, stores, promotions, merchandising, shopping trends, weather/event sales opportunities,零售, or门店 scenes. Prepares news/source signals, buyer-intent interpretation, approved sales actions, and channel drafts for review before any external handoff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Short-drama and product-video development skill for planning drama projects through a bundled Busabase App-in-Skill UI, with each project linked to a specified HyperFrame project and each episode linked to a HyperFrame composition for final motion/video tuning. Use when the user asks to create, edit, organize, or review short-drama scripts, product explainer episodes, character consistency cards, series bibles, episode beat sheets, storyboard shots, HyperFrame project/composition links, production checklists, or a drama planning workbench.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates the monthly revenue-accountable marketing report that B2B SaaS marketing leaders deliver to CEOs, CFOs, executive teams, and boards. Use when preparing the monthly CEO report, drafting the marketing section of a board deck, defending budget decisions, diagnosing pipeline gaps, or transitioning marketing from MQL/SQO reporting to revenue, CAC payback, and forward pipeline coverage. Designed for B2B SaaS demand generation leaders who own pipeline targets across segments, geos, and motions, and need to explain marketing's revenue contribution in executive language.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end ABM program design and orchestration for B2B SaaS mid-market and enterprise motions. Use when building a target account list, designing account tiering criteria, planning ABM channel orchestration, coordinating BDR outreach with marketing campaigns, defining ABM measurement frameworks, or running an ABM program review. Also use when asked to "build an ABM program," "set up account-based marketing," "design a target account strategy," "plan ABM campaigns," or "measure ABM results." Designed for demand gen teams selling to Mid-Market companies with $10K-$50K+ ACV, multi-persona buying committees, and 3-6 month sales cycles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates sourced, BDR-ready account research briefs for named target accounts in B2B SaaS ABM and outbound motions. Use after a target account list is built and before outreach sequences are written. Best for Tier 1, Tier 2, and intent-qualified accounts where BDRs need a clear "why this account, why now, why this persona" hypothesis. Designed for B2B SaaS teams selling compliance, security, GRC, risk, or other technical platforms into mid-market and enterprise buyers. Not intended for broad list building or mass enrichment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Finish an existing Japanese creator, challenge, comeback, vlog, or community-building vertical social rough cut as an evidence-grounded short-form story. Use for strong opening declarations, identity and struggle arcs, crisis-to-goal recovery, multi-source B-roll and evidence stills, emotional typography, semantic punch-ins, pinned SFX, dialogue-first audio, platform-added music delivery, and creator-short retention QA.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
当使用者说"给这张照片写图注"、"帮我写一段作品说明"、"这张照片配一句什么文字"、"展览标签怎么写"时使用。Write a factual short photo caption or a longer artist statement from photographer-provided context and optional EXIF metadata. Use when a user asks for a caption, wall label, portfolio note, or brief statement for an existing photograph. Do not infer emotions, intent, place, identity, or circumstances from the image alone.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.