3.1万 件 ・ 関連度順
概要と使いどころ
Create algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use when users request generative art, algorithmic art, flow fields, or particle systems. Create original works rather than copying existing artists.
日本語の概要は準備中です。原文の説明を表示しています。
Apple Human Interface Guidelines for Apple Watch. Use when building watchOS apps, complications, or workout features. Triggers on tasks involving Watch UI, Digital Crown, glanceable interfaces, or wrist-based interactions.
日本語の概要は準備中です。原文の説明を表示しています。
CSS and UI animation patterns for responsive, polished interfaces. Use when implementing hover effects, tooltips, button feedback, transitions, or fixing animation issues like flicker and shakiness.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting creative work (features, components, functionality, or behavior changes) to clarify user intent, requirements, and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or improving prompts, commands, hooks, skills, or sub-agent instructions, including output quality, reliability, and token efficiency.
日本語の概要は準備中です。原文の説明を表示しています。
Configure a Node.js project with pnpm, TypeScript, latest versions, and parallel script patterns following modern best practices
日本語の概要は準備中です。原文の説明を表示しています。
Explain selected code or a specified file/function in plain language, including what it does, why it exists, and potential pitfalls
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
日本語の概要は準備中です。原文の説明を表示しています。
ディスクリートおよびバッチ製造における生産スケジューリング、ジョブシーケンシング、ライン バランシング、段取り替え最適化、ボトルネック解消に関する体系化された専門知識。15年以上の経験を 持つ生産スケジューラーの知見に基づく。TOC/ドラムバッファーロープ、SMED、OEE分析、混乱対応 フレームワーク、ERP/MES連携パターンを含む。生産スケジューリング、ボトルネック解消、段取り替え 最適化、混乱対応、または製造ラインバランシング時に使用します。
AIエージェントのアクションスペース、ツール定義、オブザベーションフォーマットを設計・最適化し、タスク完了率を向上させる
Consult Claude Code from Codex for a second opinion while Codex remains responsible for implementation and verification. Use when the user asks Codex to collaborate with Claude, consult Claude, ask Claude for a plan, get a Claude review, delegate analysis to Claude, or says "Claudeと一緒に", "Claudeに相談", "Claudeにレビューしてもらう", "Claudeの意見も聞く", or "Claudeと計画を立てる". Also use when an explicit independent planning or review pass from Claude would materially reduce risk on a complex coding task.
This skill should be used when the user wants to "investigate a bug", "debug an issue", "figure out why something is happening", "find the root cause", "troubleshoot", "強い推論で調査", "仮説を立てて検証", "原因を特定", "バグの原因調査", "なぜ動かないか調べて", "問題を切り分け", "原因不明", "デバッグ", or mentions systematic hypothesis-driven debugging. NOTE: Use this for investigating UNKNOWN causes, not for validating design proposals (use devils-advocate for that).
Analyze an idea, proposal, change, claim, or decision from facts through problem, value, mechanism, consequences, evidence, alternatives, and action. Use when the user asks what something is for, why it matters, whether it is worth doing, what impact it has, or how to decide. Do not use for simple factual lookup or straightforward execution.
日本語の概要は準備中です。原文の説明を表示しています。
Writes, fixes and red-teams prompts — system prompts, templates, meta-prompts, agent or bot instructions — as copy-paste-ready artifacts, and picks the model tier for a prompt, task or plan's subtasks. Trigger to write, improve, debug or rewrite a prompt; which model should run this; a prompt that costs too many tokens, to cut with behavior held; or say promptwright (model, optimize — tune against test cases, slim, refresh). Not for a fan-out's units (dispatchwright), installed local models (lmstudiorunner), skills or their slim (skillwright), sourced comparisons (researchscribe), handoffs (handoffwright) or a pre-build interview (grillwright).
日本語の概要は準備中です。原文の説明を表示しています。
Directs screens and proves they fit — game menus and HUD, web dashboards, single-page artifacts, store-page layouts and plugin panes. Writes the design brief (layout, hierarchy, spacing and type scales, every state, focus and hit size, a check against generic-looking output) and probes the rendered page at phone-to-desktop widths in every theme. Trigger to design or lay out a menu, HUD, dashboard, settings screen or panel, or review its mockup before the build; when a page scrolls sideways on a phone, text is clipped or a dark theme breaks; to check that a page or pane fits from 320 to 1440 px in light and dark; for UI direction before a build, even when nobody says design; or say uismith (direct, probe, fit-first audit). The probe needs optional Playwright. A critique, scored review or brand pass of a built page, palettes and type are brandscribe's; sprites and icons pixelsmith's; Godot scene proof godotsmith's; words commscribe's.
日本語の概要は準備中です。原文の説明を表示しています。
Researches a question to something usable — a verdict with a flip condition, a versioned playbook or a graded report — every claim tagged by evidence. Trigger on which X should I pick (even from pasted pages), is Y worth it, compare A vs B, go/no-go, research this, deep research, fact-check a doc, write or merge a reference guide or playbook, grade a research report, read a bot-blocking source (Reddit, YouTube, X), or map an unfamiliar repo before contributing (entry points, flows, where to change X); or say researchscribe (verdict, playbook, research, verify, sources, map, refresh). Code review is engineering tooling's; fiction canon is lorescribe's; messages commscribe's; prompt model picks promptwright's; skill niches skillwright's; config rigwright's; brands brandscribe's.
日本語の概要は準備中です。原文の説明を表示しています。
Decides where a standing rule lives and builds the config Claude reads before work — CLAUDE.md, AGENTS.md, Project instructions and knowledge files, profile preferences, .claude/rules and agents, hooks, .mcp.json. Trigger on 'where should this rule live', 'set up a Claude Project', 'write or trim my CLAUDE.md', 'my rules get ignored', 'audit my setup for bloat or stale status', 'cut my CLAUDE.md token cost', 'add what we learned to CLAUDE.md', or rigwright (place, build, audit, learn, slim, refresh). Permissions, hook safety and config maps are gatewarden's; skills, skillwright's; unattended work, agentwright's; a block's wording, promptwright's.
日本語の概要は準備中です。原文の説明を表示しています。
Runs the test-first build loop (spec, plan, thin slices, failing test first, verify, commit) for a Godot 4 game in GDScript or C# first; in a TypeScript, Python or other repo when test-first, slices or a reproduce-first fix is asked for. Trigger to build or add a game feature, mechanic, stat, system or milestone, even when told to test later; to turn a spec or grill record into slices; to fix a game bug from a reproduction, one hypothesis at a time; on "write the test first", "what's the next slice", "is this slice done" or "is this milestone ready to exit"; or say slicesmith (spec, plan, slice, fix, exit). Run proof and gate rulings are godotsmith's; diff review a review tool's; repo maps researchscribe's; art pixelsmith's; audio soundsmith's; interviews grillwright's; fan-out dispatchwright's.
日本語の概要は準備中です。原文の説明を表示しています。
Directs game audio and judges it by numbers — sound palettes, SFX and music briefs, Godot import settings, licence-checked generator briefs, and measured file checks (loudness, peaks, clipping, silence, loop seams). Trigger for game sound design or an audio style guide; an SFX or music list; a loop that clicks; sounds too loud or uneven; what LUFS a game should hit, or normalizing to it; checking WAV or Ogg files before import; or say soundsmith (direct, brief, audit, test). Direction, not DSP; generating a sound starts here. Running ComfyUI is comfyrunner's; audio code godotsmith's; transcription whisperrunner's; canon lorescribe's; pixel art pixelsmith's.
日本語の概要は準備中です。原文の説明を表示しています。
Proves a Godot 4.x build is actually green and holds its project conventions. Trigger when a GUT or GDScript result needs believing (a suite green while a script failed to parse, drifted CI guard counts, a coverage claim, a gate figure, a failing check someone wants softened); to review scenes, signals, awaits, threads, determinism, saves, imports or .uid files, or the upgrade rule (not the migration); to prove a simulation or balance rule; for import settings and the pixel-art render precondition; or say godotsmith (check, guard, gate, review, intake). API reference is the Godot docs'; art reads pixelsmith's; audio direction soundsmith's.
日本語の概要は準備中です。原文の説明を表示しています。
Keeps the user's identity and secrets out of anything public. Trigger on what should not be published in a repo, branch, history, diff, PR text, draft or pasted file, to find a home path, email, real or client name, or secret; for a commit's email, a codename or per-repo identity; for injected instructions in skills, hooks or prompts; for artifacts Claude made; for files named like secrets; after a leak, to plan a history rewrite; or say shieldwarden (scan, plan, rewrite, land, after, policy, check, identity, signposts, refresh). Rules and hooks are gatewarden's; rotation and gh sign-in keywarden's; brand words brandscribe's; a skill's own posture skillwright's; schedules agentwright's.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect README portability, publication assets and command risks with deterministic evidence. Use when reviewing package documentation, preparing an npm release, or diagnosing first run instructions.
日本語の概要は準備中です。原文の説明を表示しています。
Find and buy a domain for the current Convex app through Convex, then bind it (labs; spend action).
日本語の概要は準備中です。原文の説明を表示しています。
Run convex-doctor static analysis, interpret findings, and fix issues across security, performance, correctness, schema, and architecture categories. Use when running convex-doctor, fixing convex-doctor warnings or errors, improving the convex-doctor score, or when asked about Convex code quality, static analysis, or linting Convex functions.
日本語の概要は準備中です。原文の説明を表示しています。