4,099 件 ・ 関連度順
概要と使いどころ
Contract document for the binding test verdict file at .claude/state/last_test_result. Format spec for callers (integrate, simplify, chore, the verify-tick worker) that inline the four mechanical operations. Not Skill-tool-invocable.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 10.5 — move the slug's workflow artifacts (intake, scout, research, spec, approvals, swarm state, security reports, rendered diagrams) to docs/archive/<YYYY-MM-DD>/<slug>/. Runs before /commit so the committed tree is clean of work-in-flight files. workflow.json stays live and gets archived as the first step of /commit.
日本語の概要は準備中です。原文の説明を表示しています。
Draft or revise English prose for any brief — documentation body, intake problem statements, spec context, RCA summaries, marketing copy, README sections, PR descriptions. Mandatorily invokes `Skill(humanizer)` as the final pass on every draft. Conditionally invokes `copywriting` for persuasive register, `documentation` for reference docs, `technical-tutorials` for tutorials. Used when any phase needs human-readable prose written or rewritten. Composition only — research and register-picking happen in the caller's context.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 10.6 — sync the project's execution roadmap (project.json → roadmap.path, default docs/roadmap-execution-plan.md) to the just-landed work. Flips the tasks named in workflow.json → roadmap_tasks[] from ⬜ to ✅ and promotes their epic headings ⬜→🟡→✅, preserving the standup parser format contract. On the epic track it appends instead — the epic's heading plus one row per slice — and stamps roadmap_epic back into the epic state. Also hosts the ad-hoc backfill that puts every epic already on disk onto the roadmap. Fail-open: never throws, no-ops when roadmap.path is unset/absent or no task matches, and never blocks a commit. Runs after /archive and before /memory-sync on every committing track.
日本語の概要は準備中です。原文の説明を表示しています。
Use ane for ALL file exploration, discovery, reading, and editing unless the user states otherwise. `ane exec <file> --chord "<chord>"` handles reads (Yank), searches (List), and edits (Change, Delete, Replace, Append, Prepend, Insert). Prefer ane over builtin file tools and shell utilities like grep, sed, and cat.
日本語の概要は準備中です。原文の説明を表示しています。
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate and install ecosystem tools (Hermes plugins, skills, integrations) — assess complexity vs. benefit before installation, show examples for visual tools, and avoid "cloned but not configured" states.
日本語の概要は準備中です。原文の説明を表示しています。
Build monitoring bots that poll APIs and send notifications on state changes (new listings, price alerts, status updates)
日本語の概要は準備中です。原文の説明を表示しています。
Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
日本語の概要は準備中です。原文の説明を表示しています。
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.
日本語の概要は準備中です。原文の説明を表示しています。
Capture baseline evidence from a live website URL: screenshots, scroll states, hover/click behavior, parallax, timers, and transition recordings. Use when reference artifacts are needed before implementation or comparison; not to build or diagnose a clone.
日本語の概要は準備中です。原文の説明を表示しています。
Replace this with a precise trigger description. State the Amazon PPC workflow, user intent, required data, and when Codex or Claude should use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Forces Claude to extract exact quotes from files before making claims about them. Prevents hallucinations by grounding every statement in actual text from the codebase. Use when working with large files or unfamiliar code.
日本語の概要は準備中です。原文の説明を表示しています。
Run or resume a deliverable active-outreach workflow across lead discovery, screening, customer intel, and outreach email. Use when an operator or system pipeline needs durable run state, visible intermediate artifacts, evidence gates, report-bound human approval, and a final editable email draft that is never auto-sent.
日本語の概要は準備中です。原文の説明を表示しています。
Turns a plan phase into a PhaseSpec v1 and dispatches it to a specialist subagent via the Agent tool. Subagent reads files itself, returns a structured result, the result is logged into progress.md. Markdown is the shared state; no in-memory shared store across agents.
日本語の概要は準備中です。原文の説明を表示しています。
Package completed data analysis and ML work so an independent recipient can reproduce the claimed results, verify artifact lineage, and operate the handoff within its stated scope. Use when finalizing a project, study, model package, or review bundle; not for deploying to a live system.
日本語の概要は準備中です。原文の説明を表示しています。
Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.
日本語の概要は準備中です。原文の説明を表示しています。
端到端交付纯编排层：调用 forge-* 子 skill 从需求一路编排到发布和文档，.deliver/state.json 检查点，支持 --auto / --resume。 触发方式：用户说"forge-deliver"、"端到端交付"、"全自动交付"。
日本語の概要は準備中です。原文の説明を表示しています。
Report the current development environment: Node, Python, OS, git state. Use when debugging environment issues, onboarding, or checking system compatibility.
日本語の概要は準備中です。原文の説明を表示しています。
Subagent flow for deep-reading GitHub issues + their linked/closing PRs to the bottom. Captures CURRENT state, maintainer status updates, reporter repro, blocking reviewer concerns, hidden second bugs, cross-repo duplicates. Invoked by weekly-report orchestrator; runs as a general-purpose subagent so the orchestrator's context stays small.
日本語の概要は準備中です。原文の説明を表示しています。
Builds the "Report Sources" child page for a finished Weekly Community Signal report — an evidence-backed defense of WHY every item landed in the column/section/rank it did. The agent argues each placement like a lawyer (claim → evidence → rule → rebuttal) but is under oath: it CANNOT invent, spin, or overstate — every claim ties to a verifiable fact (issue #, label, PR type, quoted comment, npm output, the front-door test). Not CYA — it's so Nathan can defend the report with facts and see the exact reasoning behind each call. Runs after the report (invoked by weekly-report, last steps) and on "report sources", "defend the report", "why is this here".
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate any address for home buyers and renters.
日本語の概要は準備中です。原文の説明を表示しています。