「redesign」の検索結果

Use for frontend code and UI fixes. Triggers: CSS, responsive, animation, React, Vue, Svelte, Tailwind, redesign, anti-slop, 프론트엔드, UI 작업, 반응형, 디자인 수정.

日本語の概要は準備中です。原文の説明を表示しています。

Design, structure, or improve form interfaces for clarity, completion rates, and user confidence. Use when the user asks to build a form, redesign a form flow, improve form conversion, add multi-step forms, fix form UX, or structure field layouts and validation.

日本語の概要は準備中です。原文の説明を表示しています。

Design or improve search experiences, result presentation, and filtering interfaces. Use when the user asks to add search, redesign search results, improve findability, build autocomplete, add filters, or fix zero-results dead ends.

日本語の概要は準備中です。原文の説明を表示しています。

Generate 5 distinct, production-grade UI variations for a requested new or existing section, component, page, flow, or shell, then help the user preview and apply one. Use when the user asks to add or redesign UI like a hero, pricing, navbar, auth flow, dashboard shell, ecommerce surface, or data component.

日本語の概要は準備中です。原文の説明を表示しています。

Create distinctive, production-grade frontend interfaces with strong hierarchy, thoughtful systems, and polished implementation that avoid generic AI aesthetics. Use when the user wants to build or redesign web pages, flows, components, or full app surfaces, or when another better-web-ui skill needs shared project design context before other better-web-ui skills.

日本語の概要は準備中です。原文の説明を表示しています。

Scrape pages locally with anti-bot bypass, TLS impersonation, and adaptive element tracking — no API keys, no cloud. Handles Cloudflare protection, CSS/XPath element extraction, and survives site redesigns. Complements firecrawl (cloud) with 100% local execution. Triggers on Cloudflare bypass, anti-bot scraping, stealth fetch, local scraping, Scrapling.

日本語の概要は準備中です。原文の説明を表示しています。

Map user journeys, onboarding paths, entry points, first actions, trust points, accessibility risks, and SEO/LLM handoffs for public websites without redesigning the visual system. Use this skill when the user asks how new readers, returning users, project reviewers, community members, buyers, or AI agents should move through a site and what each page must make clear before layout implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Design and build cinematic websites, interactive portfolios, product stories, and real-time 3D experiences with subject-specific art direction and scroll choreography. Use for new builds, redesigns, motion improvements, scroll audits, or storyboards in standalone HTML and existing apps; includes responsive, reduced-motion, and static fallbacks. Not for ordinary dashboards or unrelated animation.

日本語の概要は準備中です。原文の説明を表示しています。

Generate production-ready React/Next.js code from Figma designs. Instructs proper Figma MCP tool usage, component reuse strategies, and variant mapping. **CRITICAL: ALWAYS use this skill when user provides a Figma link or mentions implementing/redesigning from Figma design.** Never attempt manual implementation without invoking this skill first.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a SaaS founder needs to set, audit, or redesign pricing — choosing a value metric, structuring tiers and packaging, setting price points, designing discounts, planning a price increase, or optimizing a pricing page. Also for monetization questions like free-to-paid conversion, expansion revenue, willingness-to-pay research, or per-seat vs usage-based. Not for which acquisition channels to use (use channel-expert) or the wording of the pricing page (use copywriter-skill).

日本語の概要は準備中です。原文の説明を表示しています。

arXiv論文URLからスライドを作成する。(1)論文取得・分析(内部処理)→(2)JSONで保存しダイジェスト提示→(3)確認後スライド生成。分析結果はJSONファイルに保存し、ユーザーにはダイジェストのみ見せる。

ACPXを使ってClaude CodeとCodexへ読み取り専用の調査を依頼し、人間の回答を挟んで最終レポートをまとめる

arXiv論文URLからスライドを作成する。論文を取得・分析し、スライド構成JSONを保存、ユーザー確認後にgenerate_pptxツールでスライドを生成する。

Create or redesign product UI in an existing codebase, including a wireframe, substantive visual variations, and an interactive prototype. Use for requests about UI layout, visual direction, screens, flows, components, a landing page, dashboard, or making an interface feel polished. Do not use for backend work, system architecture, decks, or logic-only UI fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Map a confirmed platform-neutral website Design System to a local Elementor Site Settings and Widget inheritance contract. Use for a new or rebuilt Elementor site that needs Global Style setup guidance, or an existing site that must preserve its current visual system. Do not redesign the site, implement Widgets, or modify WordPress, Elementor, themes, or remote data.

日本語の概要は準備中です。原文の説明を表示しています。

Refresh the NowStack Mobile public landing page style. Use for `/ns web landing-page`, landing redesigns, CapWords/Screen Studio inspired references, and web-app/app/components/landing edits.

日本語の概要は準備中です。原文の説明を表示しています。

Route NowStack Mobile UI work to the right design/build skill while enforcing a clear, user-first UX bar. Use for any "build/design/redesign/polish the UI" request on the mobile app, web app, landing, or admin — when the surface or the right skill is underspecified.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Safely audit, classify, deduplicate, and reorganize bookmarks or favorites in Google Chrome and Microsoft Edge while preserving intentional toolbar shortcuts, signed-in profiles, and sync state. Use when asked to organize browser bookmarks/favorites, clean duplicate bookmarks, redesign bookmark folders, classify login/reference/self-hosted links, or fix an overgrown bookmark tree.

日本語の概要は準備中です。原文の説明を表示しています。

"Apply Service-Dominant Logic (Vargo and Lusch, 2004) and value co-creation principles to reframe exchange and value creation. Use this skill when the user needs to redesign value propositions around service exchange, analyze co-creation dynamics between firms and customers, shift from goods-dominant to service-dominant thinking, or when they ask 'how is value created with customers', 'what is our service logic', or 'how do we enable co-creation'.".

日本語の概要は準備中です。原文の説明を表示しています。

"Apply Cognitive Load Theory to optimize instructional design by managing intrinsic, extraneous, and germane load within working memory limits. Use this skill when the user needs to diagnose why learners are overwhelmed, redesign training or documentation for better comprehension, evaluate UI/UX information architecture for cognitive burden, or when they ask 'why is this tutorial confusing', 'how to simplify complex instructions', or 'what causes information overload'.".

日本語の概要は準備中です。原文の説明を表示しています。

"Apply Blue Ocean Strategy to create uncontested market space through value innovation. Use this skill when the user needs to differentiate beyond price competition, find new market opportunities, or redesign a product's value proposition using the Strategy Canvas and Four Actions Framework (Eliminate-Reduce-Raise-Create). Also use when the user says 'how do we stop competing on price', 'create a new category', or 'escape the red ocean'.".

日本語の概要は準備中です。原文の説明を表示しています。

Format recurring KPI snapshots, exception flags, and owner follow-ups for weekly operations reviews. Use when the work is routine packaging of operational metrics and exceptions. Do not use for root cause analysis, process redesign, or full performance diagnosis.

日本語の概要は準備中です。原文の説明を表示しています。

Frappe DocType creation and form UX guidance. Use when creating, reviewing, or redesigning DocTypes, including field choice, tabs, sections, columns, required fields, naming, child tables, and form usability.

日本語の概要は準備中です。原文の説明を表示しています。