UI/UX, 로고, 슬라이드, 이미지 생성 (7.3천건)
Import Figma content into a HyperFrames composition — rendered assets, brand tokens, components, storyboard sections → reconstructed motion (frames read as states, not slides) (REST/CLI), connector-assisted motion when available, and shaders from a connector or native export. Use when the user pastes a figma.com link or asks to bring a Figma design, frame, logo, brand, or animation into a video/composition.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks for a visual or UI quality review of frontend code that already shipped, or passes a phase number. Produces {phase_num}-UI-REVIEW.md with a graded 1-4 assessment across six pillars.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a HyperFrames composition needs seek-safe 2D/3D keyframes, GSAP timelines, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to make an existing website or app look premium, remove generic AI-looking design, or polish a UI without changing functionality. Audits the stack, lists the generic AI patterns, and upgrades in place.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture. Use when building with Tailwind v4 or migrating from v3.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Your product + design brain trust and decision partner. Named personas across 8 cells spanning product strategy, discovery/research, growth/metrics, design foundations/usability, design leadership/craft, UX/content, design systems, and a…
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing, building or reviewing UI/UX for a web or mobile app: picking styles, color palettes, typography, layout, animation or charts, or checking accessibility and touch targets. Priority-ranked rules ordered by impact.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing, reviewing, or debugging Apple Liquid Glass: iOS 26+ adoption, Regular vs Clear variants, tinting, scroll edge effects, or an iOS-native redesign review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks for a landing page, marketing site, portfolio, or redesign, not dashboards or data tables. Infers a design read, sets the three dials, picks a real design system, and blocks generic AI patterns at pre-flight.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing a new REST or GraphQL API, reviewing an API spec before implementation, setting team API standards, or migrating REST to GraphQL. Covers resources, HTTP semantics, pagination, error handling, and pitfalls.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a packaging design brief — structure, visual direction, hierarchy, materials, and unboxing experience. Use when the user says "packaging design", "packaging brief", "product packaging", "packaging direction", "label design", "packaging identity", "unboxing experience", "packaging look and feel", "brief my packaging designer", "packaging for my product", "packaging strategy", "retail packaging", "e-commerce packaging", "what should my packaging look like", or is briefing a designer, agency, or manufacturer on packaging requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a comprehensive brand standards document — covering logo usage, color, typography, voice, messaging, and application rules. Use when the user says "brand guidelines", "brand standards", "brand book", "style guide", "brand guide", "brand manual", "brand rules", "brand documentation", "brand toolkit", "onboarding designers or copywriters", "need a document for the team", "brand consistency across teams", or wants to codify all brand decisions into a reusable reference document.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a visual identity brief for a brand — logo direction, color palette, typography, imagery style, and design system foundations. Use when the user says "visual identity", "brand identity", "logo brief", "logo direction", "design brief", "brand design", "color palette for my brand", "typography for my brand", "visual language", "design system", "brand look and feel", "what should my brand look like", or is briefing a designer or design agency. Also use when the user has a brand strategy and wants to translate it into visual design direction.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
设计、诊断和迭代产品或品牌 Logo，从定位与审美反馈收敛方向，完成应用图标适配、品牌组合和可直接使用的资产。适用于“做个 logo”“这些版本不好看”“沿这个方向精修”“导出可用图标”；不用于普通页面 UI、整站设计或单纯插画。需在 Codex 中使用（依赖其图像生成）。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
和用户一起把一个功能「看不见的部分」敲定：数据存哪、谁写谁读、怎么加载、怎么保存、默认值和升级、核心执行规则、出问题时怎么办、旧东西怎么迁。每条规则带编号、案例和状态（已定 / 方案里有但你没拍板 / 待你定 / AI 定），用户只回答带案例的新选择题、过目没拍过板的规则；给用户看的是按「你会问的问题」分组的问答卡片（最绕的逻辑配可点的模拟器）；最后请另一家模型只读查边界，问题闭环后封成后端逻辑包，PRD、测试用例和代码审核按规则编号追溯。触发：前端交互已定、用户说「还有很多后端逻辑 / 加载 / 配置要讲清楚」「有没有遗漏的边界条件」「规则讲清楚」；或没有界面但规则复杂的功能（调度、同步、配置、额度、迁移）。分三档用：规则多且互相影响出完整包；少量清楚的变化只出规则表；行为不变的技术修复跳过。不适用于：页面长什么样、怎么排（用 page-solution-design）；写 PRD / 测试用例（本 skill 的规则包是它们的输入）；纯代码重构、性能调优、架构巡检报告。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
和用户一起敲定一个前端页面的整页方案（三层法：先定这页给用户什么，再定含哪几样怎么排，最后才是长什么样），最后打成一个定稿包（含高保真全状态与交互流程图）交给开发。触发：用户对一个页面说「想重做 / 重新设计 / 整页不对 / 太满 / 说不清具体改哪」，或「我们讨论一下这页怎么设计」。覆盖三种情形：① 已有页面整页重做；②「替换」——新方案占用同一个入口（同一路由 / 同一侧栏条目）且用户拿着现行页面在说话，功能变不变不作判据；把几个同性质页面合成一页、占其中一个入口，也算替换；③ 从零的新页面，走同一套流程，第 0 步的问法按「新页面」那一栏改。不适用于：只改一两处具体元素的具体属性（间距大一点、按钮换色、换个图标）——这种直接改，不必起流程；照着截图或设计图 1:1 复刻；写 PRD / 测试用例（本 skill 的定稿包是它们的输入）；没有界面的架构 / 数据 / 流程方案；跨页的信息架构 / 导航分组 / 侧栏结构——本 skill 的作用域限单个页面之内。已有页面补状态（加载 / 空 / 错误 / 未设置）：只补一两个且常态布局不动 → 直接改；要成套补齐、或补状态时发现常态布局本身要改 → 用本 skill。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
网页设计与部署。生成精美的单页 HTML 网页（报告、落地页、数据可视化等），支持一键部署到 Cloudflare Pages。使用 Tailwind CSS + Chart.js + Font Awesome 技术栈。当用户要求制作网页、生成报告页面、创建落地页、数据可视化展示、部署网页到线上时使用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Upload a CSV of leads + a variants YAML (produced by /campaign-copywriting) to Smartlead as a DRAFT campaign. Handles tag-scoped inbox selection, A/B/C variant assembly, custom field mapping, schedule config, and batch lead upload. ALWAYS creates in DRAFT — you review in Smartlead UI and hit Start manually. Use after /campaign-copywriting, just before the campaign goes live.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Framework for running single-variable cold email experiments. Defines experiment types (list-only, copy-only, combined), confidence weighting, minimum sample sizes, and success criteria. Use when the user wants to improve a campaign, test a new list vs old one, or compare copy variants. Prevents the
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs products around price using the 9 rules from Ramanujam and Tacke - WTP conversations, needs-based segmentation, Good/Better/Best configuration, monetization models, behavioral pricing, and price integrity. Use when designing new products, validating pricing for SaaS/B2B/B2C launches, choosing between subscription/usage/freemium models, fixing post-launch sales below plan, diagnosing failed launches as Feature Shock/Minivation/Hidden Gem/Undead, or when product teams say 'let's price it later'. Not for pure commodities or cost-plus regulated environments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.