2,968 件 ・ 関連度順
概要と使いどころ
Aceternity UI is a collection of animated React components (3D cards, spotlight, background beams, moving borders, wavy backgrounds) built with Tailwind CSS and the motion library, installed into your project as source through the shadcn CLI. Use when someone asks for "animated hero section", "3D tilt card", "spotlight effect", "moving border button", "Aceternity component", or "glowing background" in a React or Next.js app.
日本語の概要は準備中です。原文の説明を表示しています。
I am a veteran print production specialist with 15+ years in tabletop game manufacturing. I've shepherded hundreds of games from digital files to retail-ready products, working with manufacturers from The Game Crafter to Panda GM to Cartamundi. My expertise spans the entire production pipeline: color management, dieline creation, paper selection, finishing techniques, component nesting, insert design, and the critical art of the unboxing experience. I've learned the hard way about RGB-to-CMYK disasters, registration drift, humidity warp, and minimum font sizes that become illegible smudges. I know the difference between 280gsm blue-core and 320gsm black-core card stock by feel. I can tell you why your rich black needs to be C60-M40-Y40-K100, not just K100. I understand why your box needs 15mm clearance on each dimension, and why that gorgeous neon green in your design will become a muddy olive in print. Use when "print my game, packaging design, prepare files for print, dieline, print specifications, board game manufacturing, card game printing, box design, bleed and safe area, CMYK conversion, paper stock, card finish, foil stamping, embossing, unboxing experience, thermoform insert, punchboard design, component manufacturing, Panda GM, Game Crafter, Cartamundi, print-production, packaging, manufacturing, board-games, card-games, cmyk, dieline, die-cutting, offset-printing, tabletop" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
World-class frontend engineering - React philosophy, performance, accessibility, and production-grade interfacesUse when "frontend, react, vue, svelte, next.js, nuxt, component, state management, redux, zustand, client side, spa, ssr, hydration, bundle size, web vitals, accessibility, a11y, responsive, css, tailwind, frontend, react, typescript, performance, accessibility, components, state, architecture" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Angular UI Patterns workflow skill. Use this skill when the user needs Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Angular UI Patterns workflow skill. Use this skill when the user needs Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Design Apple-style iOS/macOS interfaces following Human Interface Guidelines. Creates HIG-compliant components with SF Symbols, San Francisco typography, and proper accessibility. Supports optional modern effects. Use when designing Apple-style UI, iOS/macOS interfaces, HIG-compliant components, or implementing design system specifications.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building game UI (menus, HUD, dialogue box, settings/save screens) on top of Pixi'VN with an external JS framework (React, Vue) or with plain PixiJS components — mounting HTML or PixiJS UI layers over the canvas, navigating between UI screens/routes, theming a shadcn/ui-based template, and connecting UI components to game storage/settings. Covers `canvas.htmlLayers.add`/`get`/`remove` and the PixiJS-only layer helpers `canvas.layers.add`/`get`/`remove`.
日本語の概要は準備中です。原文の説明を表示しています。
Decision guide for antd 6.x, Ant Design Pro 5/ProComponents, Ant Design X v2, and the offline `@ant-design/cli`. Use for component selection, theming/tokens, SSR, a11y, performance, routing/access/CRUD, AI/chat UI patterns, local API lookup, debugging, migration, and usage analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
日本語の概要は準備中です。原文の説明を表示しています。
Write a detailed component specification including props, states, variants, accessibility requirements, and usage guidelines.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate.
日本語の概要は準備中です。原文の説明を表示しています。
Define component boundaries, props and slots.
日本語の概要は準備中です。原文の説明を表示しています。
Build component behavior and presentation.
日本語の概要は準備中です。原文の説明を表示しています。
Suede AI design skill for making an interface feel intentional instead of templated: design tokens, color strategy, OKLCH ramps, type scale, fluid type, visual hierarchy, dark mode, spacing, component laws, motion, and source-to-implementation visual QA. Use when asked to design, restyle, polish, or audit a screen; pick colors or fonts; define, fix, or document design tokens; build or repair a dark mode; review a component or a whole design system; or compare a mock, Figma frame, or reference screenshot against a rendered implementation. NOT FOR: a full design-plus-copy build, launch surface, or reference-to-target restyle (use johnny-suede-design); conversion and funnel architecture (use suede-site-alchemy); writing the words themselves (use suede-copy).
日本語の概要は準備中です。原文の説明を表示しています。
Build, maintain, and audit design systems — tokens, component libraries, style guides, and cross-project consistency. Use when asked to create a design system, define tokens, audit component consistency, generate a style guide, or sync design tokens with code.
日本語の概要は準備中です。原文の説明を表示しています。
Manage design work in Penpot — create projects, organize pages, build components, export assets, review designs visually, and handle design-to-code handoff. Use when asked to create designs, manage Penpot projects, build components, export tokens, set up a new design project, review a design, take screenshots, or show what something looks like.
日本語の概要は準備中です。原文の説明を表示しています。
Encode Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great. From the creator of Sonner (13M+ weekly npm downloads), Vaul, animations.dev, and Linear's web team. Use when user wants to polish UI, audit animations, review component interactions, add micro-feedback, or elevate motion quality.
日本語の概要は準備中です。原文の説明を表示しています。
Design multi-device layouts with Container Queries, clamp() fluid typography, :has() selector, subgrid, and modern CSS units (dvh/svh/lvh). Use when user asks to make a layout responsive, handle mobile/tablet/desktop breakpoints, create fluid typography, or use Container Queries. Do NOT use for full-page layouts (use landing-craft), component design (use component-forge), or animation-specific responsive (use motion-craft).
日本語の概要は準備中です。原文の説明を表示しています。
Use on every UI change - Atomic Design levels, reuse-before-build, correct placement, and import direction through the shared component library.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding or reusing Flutter UI - organize widgets as atoms, molecules, and organisms in a shared library and never hand-roll a component that already exists
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing or changing any React component - React Testing Library tests are behavior-focused (byRole first), use user-event, assert on accessible output, one behavior per test, and run in npm test
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing React + TypeScript components - functional components, explicit typed props, derived state over effects, and no any/unsafe casts
日本語の概要は準備中です。原文の説明を表示しています。
Create comprehensive design systems, brand identities, and UI component libraries. Use when the user says "create design system", "build brand identity", "design UI components", "generate design tokens", "create figma specs", "review my design", "analyze design trends", "audit accessibility", "convert design to code", or "create presentation deck". Covers 10 specialized roles from system architecture to executive presentations.
日本語の概要は準備中です。原文の説明を表示しています。
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
日本語の概要は準備中です。原文の説明を表示しています。