1.4万 件 ・ 関連度順
概要と使いどころ
Nuxt UI v4 component library for building Nuxt v4 applications. 125+ accessible components with Tailwind v4, Reka UI, dark mode, theming. Use for dashboards, forms, overlays, editors, page layouts, pricing pages, or encountering component, theming, or TypeScript errors.
日本語の概要は準備中です。原文の説明を表示しています。
Maz-UI v4 - Modern Vue & Nuxt component library with 50+ standalone components, composables, directives, theming, i18n, and SSR support. Use when building Vue/Nuxt applications with forms, dialogs, tables, animations, or need responsive design system with dark mode.
日本語の概要は準備中です。原文の説明を表示しています。
Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on "/html-draft", "сделай blueprint", "технический чертёж", "архитектурная схема", "инженерная схема", "blueprint diagram", "engineering blueprint", "technical spec sheet", "architecture diagram", "system flow diagram".
日本語の概要は準備中です。原文の説明を表示しています。
Med-adapted recent-quarter review: last print financials, pipeline-milestone awareness, and FDA-event context — reads the quarter through the med lens (milestones moved, runway, regulatory updates) rather than generic financials alone.
日本語の概要は準備中です。原文の説明を表示しています。
Select, integrate, and operate multi-model video-generation gateways — hosted inference aggregators such as fal.ai, Replicate, and WaveSpeed that expose many third-party video (and video-adjacent audio) models behind one account, one API surface, and one bill. Use when deciding whether to route video generation through a gateway versus a direct model-provider API; when comparing gateways on catalog, async/queue job design, webhooks, pricing, schema discovery, and version pinning; and when operating gateway workloads in production — spend controls, retries, cross-gateway failover, content- safety differences, data retention, and commercial-rights passthrough of the underlying model. Not for direct model-provider APIs, local/self-hosted inference, model training/fine-tuning, or image-only gateway use.
日本語の概要は準備中です。原文の説明を表示しています。
Produce speech and clone voices with Fish Audio — its hosted TTS API (S2.1-Pro / S2-Pro / S1 model lineup, REST + WebSocket streaming, instant and persistent voice cloning) and its open-weight OpenAudio S1-mini / Fish-Speech models for self-hosting. Use this skill when an agent must generate narration or dialogue through Fish Audio, choose between Fish Audio's hosted models and open weights, clone a voice from reference audio, author emotion/tone/special markers for expressive delivery, estimate cost from UTF-8 bytes, wire real-time streaming for a voice agent, decide whether self-hosting beats the API, or review Fish Audio TTS output for production. Do not use it to pick a different provider — it covers Fish Audio specifically.
日本語の概要は準備中です。原文の説明を表示しています。
Composite any two HTML screens into a locked photo plate of hands holding an open foldable phone — a 1448×1086 still with two blank 495×849 / 498×849 screen slots (left and right) — to make side-by-side meme and comparison videos: TikTok vs Reels, ChatGPT vs Claude, "me vs my friend", before/after, two apps racing. Trigger on: "foldable phone meme", "put X on the left screen and Y on the right", "two-screen comparison video", "the dual-screen phone meme", or any request that names two apps/feeds/chats to show at once. The plate, geometry, and camera are finished — the agent only authors what plays INSIDE the two screens and renders.
日本語の概要は準備中です。原文の説明を表示しています。
Extract any website's design system into an agent-ready DESIGN.md using Firecrawl scrape evidence. Use when the user wants colors, fonts, spacing, components, layout patterns, or brand/UI guidance from a website so AI agents can create new websites, clone a look, or build pages inspired by that design.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for the architecture phases of an MBSE workflow in MATLAB, when writing idempotent buildXxx.m scripts that produce a three-layer RFLPV architecture (Functional, Logical, Physical) with interface dictionaries, stereotype profiles, allocation sets, and requirements Implement links. Trigger for defining stereotype properties, functional-to-logical / logical-to-physical allocation, mapping requirements to components via slreq Implement links, or running quantitative roll-up analysis on the architecture. Do NOT trigger for ad-hoc structural edits to an already-built System Composer model (adding one component, rewiring a port) — use `building-simulink-models` with `model_edit` for that. Works alongside the `system-composer` skill for detailed SC API patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Define how system components connect, establishing boundaries, patterns, and integration approaches during PRD v0.6 Architecture. Triggers on requests to design architecture, create system design, define component relationships, or when user asks "design architecture", "system design", "how do components connect?", "architecture decisions", "technical architecture", "system overview". Consumes TECH- (stack selections), RISK- (constraints), FEA- (features). Outputs ARC- entries documenting architecture decisions with rationale. Feeds v0.6 Technical Specification.
日本語の概要は準備中です。原文の説明を表示しています。
Symfony UX Map for interactive maps with Leaflet or Google Maps in Symfony. Covers markers, polygons, polylines, circles, info windows, and LiveComponent integration. Use when displaying maps, placing markers, drawing shapes or routes, handling map events, building store locators, using custom tile layers, or making maps reactive with LiveComponent. Code triggers: <twig:ux:map />, Map(), Point(), Marker(), Polygon(), Polyline(), Circle(), InfoWindow(), MapOptionsInterface, ComponentWithMapTrait, fitBoundsToMarkers, ux:map:marker:before-create, ux:map:connect, SYMFONY_UX_MAP_DSN. Also trigger when the user asks "how to display a map", "how to add markers", "how to draw a polygon on a map", "how to handle map click events", "how to make a reactive map", "how to use Leaflet in Symfony", "how to use Google Maps in Symfony", "map not showing", "map has zero height". Do NOT trigger for SVG icons (use ux-icons) or general frontend interactivity (use stimulus).
日本語の概要は準備中です。原文の説明を表示しています。
Hotwire Turbo for Symfony UX -- SPA-like speed with zero JavaScript. Covers Drive (navigation), Frames (partial page sections), and Streams (multi-target updates). Use when building ajax navigation, lazy-loaded sections, inline editing, pagination without reload, modals from the server, flash messages via streams, or real-time updates via Mercure/SSE. Code triggers: turbo-frame, turbo-stream, data-turbo-frame, data-turbo, data-turbo-action, turbo-stream-source, TurboStreamResponse, <twig:Turbo:Frame>, <twig:Turbo:Stream:Append>, <twig:Turbo:Stream:Replace>, turbo:before-fetch-request. Also trigger when the user asks "how to update part of the page without reload", "how to make navigation feel like SPA", "how to lazy-load a section", "how to do inline editing", "how to push real-time updates from server", "how to use Mercure with Turbo". Do NOT trigger for client-side JS behavior (use stimulus), server-rendered reactive components (use live-component), or reusable static UI (use twig-component).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to start or reposition a Xiaohongshu account but is asking "what should I post" before clarifying monetization, timing, personal IP direction, or trust path. Trigger phrases: "小红书定位", "不知道做什么赛道", "怎么变现", "个人IP", "账号方向", "XHS positioning", "monetization first". Do not use for drafting a specific post; use topic or copy skills after positioning is clear.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to start or reposition a Xiaohongshu account but is asking "what should I post" before clarifying monetization, timing, personal IP direction, or trust path. Trigger phrases: "小红书定位", "不知道做什么赛道", "怎么变现", "个人IP", "账号方向", "XHS positioning", "monetization first". Do not use for drafting a specific post; use topic or copy skills after positioning is clear.
日本語の概要は準備中です。原文の説明を表示しています。
Ember.js is an opinionated JavaScript framework for large single-page web apps, built on convention over configuration: Glimmer components, tracked state, nested routing, services, Ember Data (WarpDrive) and the ember-cli build tool. Use when someone asks to "build an Ember app", "create an Ember component or route", "upgrade Ember", "use Ember Data", or "convert Ember templates to .gjs/.gts".
日本語の概要は準備中です。原文の説明を表示しています。
Designs automated email sequences end to end: the trigger, branches and exit rules, the full copy of every message, and the sender setup that keeps them out of spam (SPF, DKIM, DMARC, one-click unsubscribe, consent). Covers onboarding and welcome series, lead nurture, abandoned cart, dunning, win-back and sunset flows. Use when someone asks for a "drip campaign", "welcome sequence", "onboarding emails", "nurture sequence", "win-back emails", "lifecycle emails", "email automation", or says "our emails land in spam" or "nobody clicks our onboarding emails". In-app onboarding belongs to onboarding-cro.
日本語の概要は準備中です。原文の説明を表示しています。
Define component variants with CVA. Use when creating variant-based components with Tailwind, building design system tokens, or managing complex conditional class names in React.
日本語の概要は準備中です。原文の説明を表示しています。
Finds the cause of a hard bug by running several read-only subagents in parallel, each attacking it from a different angle (change history, code path, data and state, environment, reproduction), then checking their evidence, ranking the hypotheses and naming the one experiment that would confirm the leader. It diagnoses and does not fix. Use when someone says "hunt this bug with multiple agents", "swarm on this regression", "investigate in parallel", "find the root cause", or when a failure is intermittent, crosses components, or has resisted a first look.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Ant Design (antd) is a React component library of 70+ enterprise UI components (tables, forms, date pickers, modals, menus) with design-token theming through ConfigProvider. Use it to build admin panels, back-office tools and data-heavy dashboards: server-paginated tables with filters and bulk actions, validated forms, dark or branded themes, and antd inside Next.js without a flash of unstyled content. Triggers: "antd table", "Ant Design form validation", "customize antd theme", "antd dark mode", "antd with Next.js App Router", "upgrade antd 5 to 6".
日本語の概要は準備中です。原文の説明を表示しています。
Automate online content creation and monetization with AI — blog posts, videos, social media, affiliate marketing, and digital products. Use when: building passive income streams with AI, automating content marketing, scaling content production.
日本語の概要は準備中です。原文の説明を表示しています。
Expert mobile game developer specializing in iOS and Android game optimization, touch input design, battery and thermal management, device fragmentation handling, and App Store/Play Store submission. Deep knowledge of mobile-specific constraints and best practices for shipping performant, player-friendly mobile games. Use when "mobile game, ios game, android game, touch input, mobile optimization, mobile performance, app store, play store, mobile battery, thermal throttling, mobile porting, tablet game, phone game, mobile monetization, mobile build, mobile, ios, android, touch, optimization, performance, battery, thermal, app-store, play-store, game-development, unity-mobile, godot-mobile, device-fragmentation" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Most startup ideas are bad. Not because founders lack creativity, but because they're solving invented problems instead of lived ones. Paul Graham's essays reveal a pattern: the best ideas come from living in the future and noticing what's missing. Schlep blindness hides gold. Organic ideas beat brainstormed ones. Frighteningly ambitious ideas are often easier. This skill synthesizes PG's idea-finding wisdom into actionable guidance. Use when "keywords, contexts, " mentioned.
日本語の概要は準備中です。原文の説明を表示しています。