スキルを探す

Refactor given method `${input:methodName}` to reduce its cognitive complexity to `${input:complexityThreshold}` or below, by extracting helper methods. Use when a method exceeds a cognitive-complexity threshold flagged by a linter or review.

日本語の概要は準備中です。原文の説明を表示しています。

Produces a concrete plan before a multi-file refactor: scope, sequence, risks, and verification for each step. Use when the user asks to plan, sequence, or safely execute a refactor across several files, before any code changes are made.

日本語の概要は準備中です。原文の説明を表示しています。

Refactors code surgically without changing behavior: extract functions, rename, break up large functions and classes, reduce complexity, and remove code smells. Use when code is hard to understand or extend, or the user asks to clean up, refactor, or improve existing code.

日本語の概要は準備中です。原文の説明を表示しています。

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

日本語の概要は準備中です。原文の説明を表示しています。

Reviews and refactors code according to the project's own instruction and guideline files, keeping behavior intact. Use when the user asks for a cleanup pass that must follow repository conventions (for example .github/instructions) rather than generic best practices.

日本語の概要は準備中です。原文の説明を表示しています。

Interactive onboarding that learns your communication style, audiences, and data sources to configure personalized status briefings. Paste in examples of updates you already write, answer a few questions, and roundup calibrates itself to your workflow. Use the first time Roundup is used, or to recalibrate its style and sources.

日本語の概要は準備中です。原文の説明を表示しています。

Generate personalized status briefings on demand. Pulls from your configured data sources (GitHub, email, Teams, Slack, and more), synthesizes across them, and drafts updates in your own communication style for any audience you define

日本語の概要は準備中です。原文の説明を表示しています。

AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing new API endpoints, defining module boundaries or contracts between teams, creating component prop interfaces, or changing an existing public interface. Covers naming, versioning, error shapes, and designing surfaces that are hard to misuse.

日本語の概要は準備中です。原文の説明を表示しています。

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

日本語の概要は準備中です。原文の説明を表示しています。

Use when setting up a project's CI pipeline, adding or changing automated checks, configuring deployment pipelines, or debugging CI failures. Covers quality gates, pipeline stages, and what to verify automatically on every change.

日本語の概要は準備中です。原文の説明を表示しています。

Conducts a multi-axis code review (correctness, readability, architecture, security, performance) before merging. Use before merging any change, after finishing a feature or bug fix, when reviewing code another agent or person wrote, or when asked to review a diff or pull request.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working code feels heavier than it needs to be — deeply nested logic, long functions, unclear names, duplication after a merge, or a review that flagged complexity. Reduces complexity while preserving behavior exactly. Not for code you do not yet understand, or code you are about to rewrite.

日本語の概要は準備中です。原文の説明を表示しています。

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

日本語の概要は準備中です。原文の説明を表示しています。

Use when starting a coding session, setting up a project for AI-assisted development, switching between parts of a codebase, or when agent output quality degrades — hallucinated APIs, wrong patterns, ignored project conventions. Structures what the agent loads and when.

日本語の概要は準備中です。原文の説明を表示しています。

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

日本語の概要は準備中です。原文の説明を表示しています。

Use when replacing an old system, API, or library, sunsetting a feature, consolidating duplicate implementations, removing dead code nobody owns, or deciding whether to maintain a legacy system versus migrate off it. Covers deprecation timelines, migration paths, and safe removal.

日本語の概要は準備中です。原文の説明を表示しています。

Use when making an architectural decision, choosing between competing approaches, adding or changing a public API, shipping a user-facing behavior change, or repeatedly explaining the same thing. Captures the why — context, constraints, alternatives — as ADRs and project docs. Not for restating obvious code.

日本語の概要は準備中です。原文の説明を表示しています。

Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.

日本語の概要は準備中です。原文の説明を表示しています。

Use when building or modifying user-facing interfaces: new components and pages, responsive layouts, interactivity and state management, or fixing visual and UX issues. Covers component architecture, styling, accessibility, and state boundaries.

日本語の概要は準備中です。原文の説明を表示しています。

Use on every code change — commit structure, branching, history hygiene, and versioning. Apply when committing work, opening or splitting a branch, writing commit messages, cutting a release, or recovering from a bad history state.

日本語の概要は準備中です。原文の説明を表示しています。

Reverse-engineers and debugs macOS and iOS binaries with Hopper Disassembler and LLDB: ObjC/Swift symbols, dyld loading, framework internals, and crash investigation from disassembly. Use when private API behavior or a runtime crash needs to be understood at the binary level.

日本語の概要は準備中です。原文の説明を表示しています。

Use when refining a vague idea through divergent expansion, convergent focus, and assumption stress-testing before planning or implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

日本語の概要は準備中です。原文の説明を表示しています。