上記に当てはまらないスキル（1.4万 件）
Draft a short, honest account of where using Mycelium was confusing or slow, for the user to edit and choose whether to send. Reports experience; never prescribes fixes. Based on Hoskins's friction logging.
日本語の概要は準備中です。原文の説明を表示しています。
Map the Jobs to be Done (functional, emotional, and social) that people are trying to get done. Based on Christensen's JTBD theory — applies to any object, not only software.
日本語の概要は準備中です。原文の説明を表示しています。
Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".
日本語の概要は準備中です。原文の説明を表示しています。
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update the project constitution from interactive or provided principle inputs.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a custom checklist for the current feature based on user requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update the feature specification from a natural language feature description.
日本語の概要は準備中です。原文の説明を表示しています。
Generate high-quality Product Requirements Documents (PRDs) for software systems. Includes an executive summary, personas, functional and non-functional requirements, technical specifications, and risk analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update OMA skills in the SSL-lite human-readable format. Use when adding a new `.agents/skills/{skill-name}/SKILL.md`, converting an existing skill to the standardized Scheduling / Structural Flow / Logical Operations / References structure, or validating whether a skill has enough routing, execution, resource, and safety detail.
日本語の概要は準備中です。原文の説明を表示しています。
Execution plan generation and management — Plan lifecycle as repository artifact
日本語の概要は準備中です。原文の説明を表示しています。
Initialize project harness — AGENTS.md as table of contents, ARCHITECTURE.md as domain map, structured docs/ knowledge base
日本語の概要は準備中です。原文の説明を表示しています。
Ralph - persistent self-referential execution loop wrapping ultrawork with independent verifier verification
日本語の概要は準備中です。原文の説明を表示しています。
Auto-detect project tech stack and generate stack-specific references for domain skills
日本語の概要は準備中です。原文の説明を表示しています。
oh-my-agent project setup verification and configuration
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used only when the user explicitly types "/start-project" (optionally with a slug). It begins a new tracked JellyRock project under docs/projects/, running scaffold-project.sh to create PLAN.md from docs/projects/_TEMPLATE.md and index it in the projects README, then walking the user through the Charter. For multi-session work that crosses a phase boundary or carries a decision worth recording as an ADR in docs/adr/. Do not auto-invoke on vague phrases like "let's start something"; for a single-session fix just do the work and capture any tail via /log followup.
日本語の概要は準備中です。原文の説明を表示しています。
Run JellyRock's docs governance checks (broken markdown links, link anchors that match no heading, broken related-files frontmatter paths, stale tech-debt anchor references, journal-schema gates for progress.md and the decisions.md supersede chain, stale-doc detection) and surface a structured fix list grouped by category. Consumes the --json output of scripts/lint/docs-check.cjs and the human-readable output of scripts/lint/docs-stale.cjs. Use when a commit hits the docs-lint pre-push hook, before pushing a PR that touched docs/ or any CLAUDE.md, or when you want a one-shot pass over doc references.
日本語の概要は準備中です。原文の説明を表示しています。
DEPRECATED, replaced by the `enrich` phase built into /crash-report. The old flow filed crash issues first and enriched them one by one afterward. The new flow (stage, then enrich, then file) pulls the dashboard backtrace before filing, so issues are born complete and architectural-class crashes go to their epic instead of becoming standalone issues. Do not invoke it for new work: run /crash-report and paste the backtraces during its enrich step. It stays only as a redirect; the `enrich-issue` script subcommand still exists as a legacy escape hatch for a crash issue filed before the change.
日本語の概要は準備中です。原文の説明を表示しています。
At the end of a feature or fix, scan docs/architecture/tech-debt.md for entries whose area matches the files this branch touched. Surfaces each candidate for a call (resolved removes the entry, still applies keeps it, defer further narrows it) and asks about new debt the PR defers. Walks the user through each, applies the diffs, and re-runs npm run lint:docs to confirm anchor references still resolve. AGENTS.md's followup-discipline rule routes internal debt with a slug and severity here; /pr runs it as a sub-agent. Use before opening a PR for any non-trivial change.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user explicitly types "/end-session": the mandatory final step of any session started or resumed with /start-project or /resume-project, which the agent prints alone in its own block as the session's last line for the user to type, never invoking it directly. It updates the active project's PLAN.md (Status, kickoff, log), checks the PLAN against itself, and commits+pushes. Do not auto-invoke on vague phrases mid-session.
日本語の概要は準備中です。原文の説明を表示しています。
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management, making interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
日本語の概要は準備中です。原文の説明を表示しています。
Add moments of joy, personality, and surprise through success states, empty states, loading moments, hover details, and celebratory polish once the fundamentals already work. Use when the user wants delight, charm, personality, or memorable micro-interactions—not when the main need is baseline cleanup or stronger visual impact.
日本語の概要は準備中です。原文の説明を表示しています。
Clarify priority and emphasis by fixing unclear primary actions, competing visual weight, loud section titles, and weak label/value treatment. Use when the user mentions hierarchy, prioritization, too much competition, grayscale confusion, loud headings, or unclear primary actions.
日本語の概要は準備中です。原文の説明を表示しています。
Add or refine depth through elevation systems, raised and inset surfaces, layered overlap, and meaningful shadow behavior so interfaces feel structured instead of flat. Use when the user mentions depth, elevation, shadows, layering, flat cards, pressed states, drag feedback, or inset controls.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the work is functionally complete and needs finishing touches—not when the hierarchy, structure, tone, or technical foundation still need major changes.
日本語の概要は準備中です。原文の説明を表示しています。