8,143 件 ・ 関連度順
Produces a compact KPI digest showing how key metrics changed over a period and what's driving the movement. Use this skill when someone asks for a performance summary, a weekly recap, a morning briefing, a KPI update, or any variation of "how did we do this week/month." Also trigger for requests like "give me a performance overview," "what moved in the last 7 days," "pull our KPI report," or "summarize our metrics."
日本語の概要は準備中です。原文の説明を表示しています。
Identifies which items (pages, campaigns, products, channels, regions) had the biggest increases or decreases for a key metric between two time periods. Use this skill when someone asks "what's up and what's down," "which campaigns moved the most," "top gainers and losers," "what pages are trending," "show me what changed by channel," or any variation of identifying the biggest movers and decliners for a metric.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch up-to-date, version-specific documentation for any major library (Next.js 16, Sanity, LangGraph, React, Tailwind CSS, Vitest, Framer Motion) via the Context7 MCP server. Use when writing code against unfamiliar or recently-changed framework APIs, when training data may be stale, when resolving deprecations or version-specific syntax, or when the repo warns about framework drift (e.g. the nextjs-agent-rules block in portfolio-v1/AGENTS.md). Invokes the resolve-library-id and get-library-docs MCP tools.
日本語の概要は準備中です。原文の説明を表示しています。
Edits the heroSection singleton in the Sanity studio. Use when the user wants to change the homepage hero copy, name, title, role rotator, or contact email.
日本語の概要は準備中です。原文の説明を表示しています。
Syncs blog posts between local MD files and Sanity CMS. Use when the user wants to push local posts to Sanity, pull from Sanity, or see what would change.
日本語の概要は準備中です。原文の説明を表示しています。
Migrate from Next.js 15 to Next.js 16 and handle breaking changes
日本語の概要は準備中です。原文の説明を表示しています。
Review code changes for correctness, consistency, performance, accessibility, and adherence to repo conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews all blog posts, shows sync status, and validates content. Use when the user wants to see what posts exist, their publish status, or what's changed.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Sanity content -- schema changes, data migrations, debugging queries, batch operations, and revalidation.
日本語の概要は準備中です。原文の説明を表示しています。
Silent failure hunting routing. Use when a change might pass while skipping work, swallowing errors, losing evidence, weakening gates, or reporting false success; do not use for broad code review.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve one exact official/current documentation gap when the user requests source verification or a version-sensitive API/SDK/provider/framework question can materially change the current decision; do not trigger for every implementation decision, ordinary framework code, local business logic, or broad research.
日本語の概要は準備中です。原文の説明を表示しています。
Run a bounded red-green-refactor feedback loop only when the user explicitly requests TDD, accepts reproduction-first proof for a bug, or an accepted high-risk behavior specifically requires red/green evidence; do not trigger for every logic, bug, behavior, or implementation change.
日本語の概要は準備中です。原文の説明を表示しています。
Optional focused post-implementation review routing. Use only when the user requests review or the changed surface has a clear specialist evidence need that direct diff inspection and the smallest relevant check cannot cover. Never creates an automatic review swarm.
日本語の概要は準備中です。原文の説明を表示しています。
PR test analysis routing. Use for pull request or diff test impact, changed-test review, CI failure interpretation, and focused test matrix recommendations; do not use for general code review or editing tests.
日本語の概要は準備中です。原文の説明を表示しています。
Produce or apply an approved report-first proposal for workflow, ROSE, skill, command, subagent, memory, install, or harness-doc changes; use after harness-issue-triage localizes a harness problem or when the user explicitly requests harness maintenance, and do not edit core harness files without explicit human approval.
日本語の概要は準備中です。原文の説明を表示しています。
Handle an explicit Git intent such as branch/worktree setup, commit organization, history archaeology, conflict resolution, PR preparation, or versioning; do not trigger as a process skill for every code or file change.
日本語の概要は準備中です。原文の説明を表示しています。
Build or modify production UI components, layouts, client state, responsive behavior, accessibility, or UX inside an app when that frontend surface is the primary deliverable; do not trigger for rich campaign/media pages, backend integration, every user-facing text change, delegated browser QA, or review alone.
日本語の概要は準備中です。原文の説明を表示しています。
Simplify a bounded code area when the user explicitly requests behavior-preserving refactoring or a named complexity/readability problem is the accepted task; do not trigger automatically after implementation, during every review, for adjacent cleanup, or when behavior may change.
日本語の概要は準備中です。原文の説明を表示しています。
AI regression scouting routing. Use when agents, prompts, skills, model/tool routing, harness fixtures, or generated-output expectations change and need regression scenarios; do not use for ordinary product-code regressions.
日本語の概要は準備中です。原文の説明を表示しています。
Perform direct, bounded browser inspection through the `browser.qa` capability when the user requests runtime UI evidence or one browser-specific claim needs DOM/accessibility/console/network/visual verification; do not trigger for every UI change, backend work, delegated QA, or durable E2E artifact routing.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update source-grounded documentation when the user explicitly asks for docs/ADR/onboarding material, a public contract change requires docs, or an accepted hard-to-reverse decision meets the ADR gate; do not trigger for every feature, architecture discussion, implementation, review, or SHIP request.
日本語の概要は準備中です。原文の説明を表示しています。
Turns npm audit/Snyk results into prioritized patch plans with severity assessment, safe upgrade paths, breaking change analysis, and rollback strategies. Use for "dependency security", "vulnerability patching", "npm audit", or "security updates".
日本語の概要は準備中です。原文の説明を表示しています。
Plans safe API evolution with versioning strategies, client migration guides, deprecation timelines, and backward compatibility considerations. Use for "API versioning", "deprecation planning", "API evolution", or "breaking changes".
日本語の概要は準備中です。原文の説明を表示しています。
Implements API contract testing to ensure provider-consumer compatibility using Pact or similar tools. Prevents breaking changes with contract specifications and bi-directional verification. Use for "contract testing", "API contracts", "Pact", or "consumer-driven contracts".
日本語の概要は準備中です。原文の説明を表示しています。