684 件 ・ 関連度順
概要と使いどころ
Create companion Codex workflows from book chapters, reader exercises, prompts, field notes, and teaching material. Use when Codex needs to turn a chapter excerpt, 書籍練習, AI 提示詞, worksheet, or author note into a reusable Skill-style workflow, GitHub-shareable companion artifact, or book link resource for readers.
日本語の概要は準備中です。原文の説明を表示しています。
Build efficient Blender repetition, Array-driven stairs/modules/openings, instancing, scattering, Bezier/NURBS curve-profile geometry, Geometry Nodes fields, repeat zones, simulation zones, particle-like systems, and collective motion. Use for stairs, railings, trim, pipes, cables, repeated windows/panels, vegetation, debris, crowds, rain, snow, modular structures, or any request involving dependent elements or reusable parameters.
日本語の概要は準備中です。原文の説明を表示しています。
Build, inspect, audit, and refactor Blender Geometry Nodes systems for procedural models, instancing, modular effects, curves, scattering, flocks, data visualization, fields, simulation zones, and node-graph cleanup. Use whenever a Blender task specifically calls for Geometry Nodes, reusable procedural node graphs, node connections/layout, or a scalable procedural asset.
日本語の概要は準備中です。原文の説明を表示しています。
Search and inspect the installed Blueish Blender Asset Library without mutating it. Use when a user asks for a local Blender asset, node preset, Blueish asset, Asset Browser entry, or named source, or when the Router has selected a node-centric/reusable Geometry Nodes, material, simulation, rigging, compositor, or NPR route with eligible local catalogs; return compatible, attributable candidates for the Router-approved workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.
日本語の概要は準備中です。原文の説明を表示しています。
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a complete repository skill from a user's idea, including the workflow instructions, references, scripts or assets, agent metadata, skill-card artwork, cinematic banner artwork, README links, discovery metadata, and validation. Use when the user asks to create a new skill, add a skill to this collection, turn a workflow into a reusable skill, or make a skill's documentation and artwork consistent with the repository.
日本語の概要は準備中です。原文の説明を表示しています。
Learn reusable 2D motion-generation knowledge from user-specified action resources with `/img2mo-learn <resource>`. Use when the user provides videos, extracted frame sequences, spritesheets, Spine assets, generated outputs, failed attempts, or reference motion folders and wants to summarize animation timing, pose beats, style traits, prompt patterns, extraction/cropping rules, or failure lessons into the project `img2mo-knowledge/` folder for later `/img2motion` generation.
日本語の概要は準備中です。原文の説明を表示しています。
Production guidance for reusable layered 2D character rigs in browser-rendered and video media. Use for SVG hierarchies, pivots and constraints, FK/IK planning, pose and facial libraries, acting, cycles, deterministic handoff, crop variants, and rig QA; not for character concept continuity, 3D armatures, or motion-capture solving.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a research-paper figure Skill Factory: build, patch, package, or use reusable specialized paper-figure-making skills from lawful literature/corpus evidence. Generated skills must use a specialized-skill-first workflow, full-feasible local PDF coverage where available, startup-plan-only first replies, target-paper candidate/final image isolation, mandatory image-embedded visual-structure explanation, mandatory non-target concept/modeling example display for abstract visual decisions, saved subtype/style illustration atlases, ChatGPT web Create image / ChatGPT Images 2.0 rendering, Codex $imagegen-first rendering, sample-image transfer rules, all-step/current-position state footers, and a mandatory first-round diverse candidate board followed by P6b/P6c paper-local best-practice optimization before final prompt construction.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use for creating, reviewing, or debugging GitHub Copilot reusable prompt files and slash commands in Visual Studio Code, including .github/prompts/*.prompt.md, inputs, context links, agent selection, and tool selection. Do not use for always-on rules, multi-step Agent Skills, custom personas, or VS Code extension commands.
日本語の概要は準備中です。原文の説明を表示しています。
Identifies reusable UI patterns, components, and design tokens, then extracts and consolidates them into a design system for systematic reuse.
日本語の概要は準備中です。原文の説明を表示しています。
Use when we want to turn a just-finished Formax workflow (e.g. commands, overlays, tools, hooks, permissions, UI parity) into a reusable Codex Skill under .codex/skills, including scaffolding, guardrails, and the minimum test checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a reusable rolling execution pattern (README + TODO-INDEX) like plans/web-reference-react-refactor, and wants to run delivery in small validated loops.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when authoring reusable, idempotent MATLAB scripts that build System Composer architecture models via the architecture-modeling API — `systemcomposer.createModel`, `addComponent`, `addPort`, `setInterface`, `connect(srcPort, dstPort)`, interface dictionaries (.sldd) with `addInterface`/`addElement`, profiles/stereotypes with `Profile.createProfile` and `addStereotype`, or `systemcomposer.allocation.createAllocationSet`. Also trigger when debugging these APIs (connections that don't appear, interfaces that don't resolve, profile save errors, `createAllocationSet` signature-mismatch errors). Do NOT trigger for ad-hoc structural edits to an already-built model (adding one SubSystem, rewiring a port) — use `building-simulink-models` with `model_edit` for that.
日本語の概要は準備中です。原文の説明を表示しています。
Creates new Skills following Anthropic best practices. Use when discovering reusable workflows or repetitive patterns. Triggers on: create skill, new workflow, codify this process, standardize workflow.
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
Symfony UX LiveComponent for reactive server-rendered UI -- components that re-render via AJAX on user interaction, zero JavaScript required. Use when building live search, real-time filtering, dynamic forms, inline validation, dependent selects, auto-save, polling, deferred/lazy rendering, or any UI that updates itself based on user input. Code triggers: AsLiveComponent, LiveProp, LiveAction, data-model, data-loading, data-live-action-url, ComponentWithFormTrait, LiveListener, emit, defer, lazy, polling. Also trigger when the user asks "how to build a search that filters as I type", "how to validate a form in real-time", "how to make a reactive component in PHP", "how to build dependent selects", "how to defer component rendering", "how to communicate between components via emit", "how to bind a form to a LiveComponent". Do NOT trigger for static reusable UI without reactivity (use twig-component), pure client-side JS behavior (use stimulus), or page-level navigation (use turbo).
日本語の概要は準備中です。原文の説明を表示しています。
Stimulus JS framework for Symfony UX -- client-side behavior via HTML data attributes, zero server round-trips. Use when creating controllers for DOM manipulation, handling click/input/submit events, managing targets and values, wiring outlets between controllers, wrapping third-party JS libraries, or building toggles, dropdowns, modals, tabs, clipboard interactions. Code triggers: data-controller, data-action, data-target, data-*-value, data-*-class, data-*-outlet, stimulusFetch lazy, connect(), disconnect(), static targets, static values. Also trigger when the user asks "how do I add a click handler", "how to toggle a class", "how to build a dropdown/modal/tabs", "how to wrap a JS library in Symfony", "add keyboard shortcuts", "lazy-load a controller", "listen to global events", "communicate between controllers". Do NOT trigger for partial page updates without JS (use turbo), server-rendered reactivity (use live-component), or reusable Twig templates (use twig-component).
日本語の概要は準備中です。原文の説明を表示しています。
Capture durable, project-specific learnings from the work just done into the knowledge/ base — gotchas, implementation quirks, things looked up or web-searched, live-API behaviours, and design decisions (as ADRs). Use before opening a PR (it runs automatically in /deliver), or any time you've learned something worth remembering. Records only non-obvious, reusable facts; skips anything already in the repo, CLAUDE.md, or git history.
日本語の概要は準備中です。原文の説明を表示しています。
Редполитика проекта на русском языке: короткое интервью, извлечение голоса из примеров и файл `.agents/redpolitika.md` для редакторских скиллов. Use this skill whenever the user asks to create, update, remember, formalize, or apply a project editorial policy, tone of voice, style guide, vocabulary, forbidden words, or reusable writing context. Триггеры: «настрой редполитику», «редполитика», «запомни мой стиль», «создай гайд по стилю», «tone of voice», «ToV», «настрой скилл под наш проект», «как нам писать», «зафиксируй голос», «добавь в редполитику», «обнови правила тона», «словарь проекта», «запрещённые слова», «пиши в нашем стиле», «сохрани правила редакции». Also suggest this skill when redaktura, statya, or ux-copy lacks project context and the user will keep working with the same product. Для редактуры готового текста см. skill redaktura; для статей с нуля — statya; для интерфейса — ux-copy.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user has positioning and wants a reusable Xiaohongshu topic/title bank instead of asking AI to freely brainstorm, especially to map topics to user needs such as emotional resonance, growth proof, new insight, learning value, or identity expression. Trigger phrases: "选题库", "标题公式", "每天发什么", "批量选题", "爆款需求", "XHS topic bank", "title formulas". Do not use before account positioning and target audience are known.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user has a Xiaohongshu niche and needs to find, compare, and extract reusable content structures from low-follower high-performing posts, or diagnose why a post did or did not become a breakout using click rate, retention, and interaction signals. Trigger phrases: "找对标", "低粉爆款", "拆爆款", "内容骨架", "点击率", "停留时长", "互动率", "competitor pattern", "viral post structure". Do not use before the monetization direction is clear.
日本語の概要は準備中です。原文の説明を表示しています。