183 件 ・ 関連度順
概要と使いどころ
Analyze and design control flows and data structures. Produces compact ASCII tree diagrams showing triggers, call chains, payload shapes, state mutations, and re-render effects. Use when user asks to diagram, trace, visualize, or design a flow or data structure.
日本語の概要は準備中です。原文の説明を表示しています。
Local development guide for the Happy monorepo. How to build, install, test, and run the CLI, server, mobile app, and desktop (Tauri) locally. Use when the user types /dev, asks how to "build", "start dev", "install locally", or "run the ___ package".
日本語の概要は準備中です。原文の説明を表示しています。
Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior sessions, previous attempts, or past investigations — even without saying 'sessions' explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Browser automation CLI for AI agents. Use this when asked to test something in a real browser.
日本語の概要は準備中です。原文の説明を表示しています。
MANUAL TRIGGER ONLY: invoke only when user types /office-hours. YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written.
日本語の概要は準備中です。原文の説明を表示しています。
Query and manage Grafana dashboards and Prometheus metrics for Happy infrastructure. Covers grafanactl CLI usage, direct Prometheus queries through Grafana proxy, and dashboard-as-code workflows. Use when user asks about metrics, dashboards, monitoring, Grafana, Prometheus, or wants to add/modify panels.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a project directory or a website URL into a short, shareable launch video with music, motion, and share copy. One file, no bundled assets — built entirely by the model with the tools already on the machine. Use when someone says "/brag-slim", "let's /brag about this", "brag about a website", "make a launch video", or wants to show off what they built. If the /brag skill is also installed, let /brag handle those phrases; it hands off here on Opus 5.5.
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through writing a systematic literature review (SLR) following the PRISMA 2020 framework. Use this skill whenever the user mentions 'systematic review', 'systematic literature review', 'SLR', 'PRISMA', 'PRISMA 2020', 'PRISMA flow diagram', 'PRISMA checklist', or asks for help writing, structuring, or auditing a literature review that follows reporting guidelines. Also trigger when the user asks about inclusion/exclusion criteria for a review, search strategies for databases like Scopus/WoS/PubMed, study selection processes, risk of bias assessment, or narrative synthesis for a review paper. This skill covers the full PRISMA 2020 checklist (27 items), produces a Word document manuscript in strict journal article format, generates an annotated PRISMA flow diagram, and enforces APA 7th Edition referencing throughout. It does NOT cover meta-analysis or statistical pooling. By Chuah Kee Man.
日本語の概要は準備中です。原文の説明を表示しています。
Starter: compare model costs for a described task — maps task shape to the cheapest adequate seat and shows the price spread
日本語の概要は準備中です。原文の説明を表示しています。
Build a behavior change with observed red, minimal green, and measured test consolidation
日本語の概要は準備中です。原文の説明を表示しています。
Manage tasks with Claude Code native tools — use to track TODOs, delegate work, and monitor progress
日本語の概要は準備中です。原文の説明を表示しています。
Starter: one-screen provider health summary — availability, auth method, version drift, and cost posture for every seatable provider
日本語の概要は準備中です。原文の説明を表示しています。
Starter: frame a decision as a multi-model debate — picks sides, seats providers, and launches /octo:debate with a well-formed motion
日本語の概要は準備中です。原文の説明を表示しています。
Process screenshot-based UI/UX feedback to fix visual issues — use when users share screenshots of bugs
日本語の概要は準備中です。原文の説明を表示しています。
Use when a nontrivial change needs end-to-end verification before committing or shipping
日本語の概要は準備中です。原文の説明を表示しています。
Multi-AI research using available external providers (Double Diamond Discover phase) - Questions about best practices, patterns, or ecosystem research PRIORITY TRIGGERS (always invoke): "octo research", "octo discover", "co-research", "co-discover" DO NOT use for: simple file searches (use Read/Grep), questions Claude can answer directly, debugging issues (use skill-debug), or "what are my options" for decision support.
日本語の概要は準備中です。原文の説明を表示しています。
Starter: interpret a council run's verdict artifacts — quorum, dissent, cross-lab validity, and what to do next
日本語の概要は準備中です。原文の説明を表示しています。
Create zero-context implementation plans with bite-sized tasks — use for multi-step feature planning
日本語の概要は準備中です。原文の説明を表示しています。
Use when about to declare work complete, fixed, passing, or done
日本語の概要は準備中です。原文の説明を表示しています。
Break a plan or spec into vertical slices that each declare what blocks them — use when work is agreed but not yet cut into fileable pieces
日本語の概要は準備中です。原文の説明を表示しています。
Brainstorm creatively with pattern spotting and paradox hunting — use for ideation and exploration
日本語の概要は準備中です。原文の説明を表示しています。
Multi-AI implementation using available external providers (Double Diamond Develop phase). DO NOT use for simple code edits, reading/reviewing code, built-in commands, or trivial single-file changes.
日本語の概要は準備中です。原文の説明を表示しています。
GitHub Copilot CLI as optional zero-cost provider via copilot -p programmatic mode
日本語の概要は準備中です。原文の説明を表示しています。
NLSpec authoring — use when you need a structured specification from multi-AI research and consensus
日本語の概要は準備中です。原文の説明を表示しています。