8,429 件 ・ 関連度順
Applies Chesterton's Fence, Occam's Razor, the Peter Principle, and Dunning-Kruger to technical decisions. Use before refactoring, architectural changes, or any task where changing existing behavior carries risk or requires judgment about what the user actually needs.
日本語の概要は準備中です。原文の説明を表示しています。
Write a polished git commit message from my staged changes following Conventional Commits, with an optional emoji and the related issue key.
日本語の概要は準備中です。原文の説明を表示しています。
Attach review scores to recorded Whalesong traces and build comparison pairs — mark a session good/bad/regressed, then diff two runs deterministically. Use when evaluating agent changes, reviewing a run after the fact, or building a small eval set.
日本語の概要は準備中です。原文の説明を表示しています。
Review a GitHub pull request with the GitHub MCP tools - read the description, diff, checks and existing discussion, then report findings in chat. Posts nothing to GitHub unless the user asks for that exact post and approves the text. Use for "review this PR", PR links, or "what changed in
日本語の概要は準備中です。原文の説明を表示しています。
Explain an unfamiliar repository, find where to make a change, and maintain source-cited documentation. Use for repo onboarding, wiki questions, documentation impact, or updating and sharing a WhaleWiki.
日本語の概要は準備中です。原文の説明を表示しています。
Write a clear git commit message from the staged changes. Use when the user asks for a commit message, or to summarize what they are about to commit.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Vercel environment variables safely. Environments, vercel env ls/add/update/rm/pull/run, sensitive variables, NEXT_PUBLIC exposure, when changes take effect. Use when adding, rotating, auditing or pulling Vercel env vars.
日本語の概要は準備中です。原文の説明を表示しています。
Write or update repository/product documentation: README, user guides, API docs, architecture, migration notes, and changelog material. This is not the Word-document artifact skill.
日本語の概要は準備中です。原文の説明を表示しています。
Review a change, module, or surface for exploitable defects — trust boundaries, authn/authz, injection, secret exposure, filesystem and network reach, dependency risk. Use when the user asks for a security review, audit, or vulnerability check of concrete code. Not for general code review, lint, or compliance paperwork.
日本語の概要は準備中です。原文の説明を表示しています。
Full-stack Convex development guidelines covering React, Vite, TypeScript, mutations, auth, design system, and documentation practices. Use when building features, writing Convex functions, or making code changes in this project.
日本語の概要は準備中です。原文の説明を表示しています。
Critical Git safety rules to prevent destructive operations. Use whenever performing git operations, reverting changes, or managing commits. Prevents accidental loss of work.
日本語の概要は準備中です。原文の説明を表示しています。
Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev/migrations. Use for breaking schema changes, backfills, table reshaping, or zero-downtime rollouts.
日本語の概要は準備中です。原文の説明を表示しています。
Reflection-first problem solving methodology for Convex development. Use before implementing any solution to ensure proper root cause analysis, 98% code confidence, and minimal change scope.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute Convex schema migrations safely, including adding fields, creating tables, and data transformations. Use when schema changes affect existing data.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says /update, @update, update project docs, or asks to sync task.md, changelog.md, and files.md after completing work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building or changing Skyline UI (apps/syn-ui, packages/syn-ui/*) from a design - "build this screen from the board", "implement the design", "match the canvas", "new board landed", "build the Eval trend panel", "port this screen to Skyline", "does this match the design", "update the Shipped table", "snapshot the boards". Covers reading a `*.dc.html` board and the Skyline spec, building from them, comparing 1440px and 390px screenshots against the board, and recording the shipped screen. Do NOT use for small tweaks to a screen that has already shipped (change the code directly, no board needed), for the frozen React app apps/syn-dashboard-ui (never edit it), or for refreshing the CI screenshot baselines alone (see design/README.md).
日本語の概要は準備中です。原文の説明を表示しています。
new step of mspec workflow — bootstrap a change directory and readme.md
日本語の概要は準備中です。原文の説明を表示しています。
Use when: implement a scoped ticket, fix a bug, add tests, prepare a PR-ready code change, or reuse a standard builder workflow across software engineer agents.
日本語の概要は準備中です。原文の説明を表示しています。
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: ticket lifecycle, state transitions, ready for QA, changes requested, QA passed, role-based workflow policy, Developer to QA handoff, or relay routing across delivery agents.
日本語の概要は準備中です。原文の説明を表示しています。
Activate for any ticket that changes React components, user-facing flows, or UI state. Ensures all five observable UI states are verified before state:ready-for-qa.
日本語の概要は準備中です。原文の説明を表示しています。
Activate for any ticket that adds or changes a Supabase migration, environment variable, edge function deployment, or runtime configuration. Ensures infrastructure is live in the target QA environment before state:ready-for-qa.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: Router bridges your team and the remote team across Telegram. Classifies inbound messages from the remote agent, dispatches Builder or Tester as subagents, composes replies, and posts outbound state-change notifications.
日本語の概要は準備中です。原文の説明を表示しています。
Review Codex/Claude agent skills, profile manifests, and skill-related deploy changes before they ship. Use when creating, editing, importing, installing, or reviewing SKILL.md files, agent manifests, optional third-party skills, or plugin skill bundles. Checks trigger quality, progressive disclosure, evidence gates, security, hallucination risk, validation, and deployment impact.
日本語の概要は準備中です。原文の説明を表示しています。