3,307 件 ・ 関連度順
概要と使いどころ
Analyzes your Claude Code conversation history to identify patterns, common mistakes, and opportunities for workflow improvement. Use when user wants to understand usage patterns, optimize workflow, identify automation opportunities, or check if they're following best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Review uncommitted code changes to find unreasonable design, unfinished requirements, potential bugs, missed reuse opportunities, and optimization opportunities. Use when the user asks for a review of pending, uncommitted, or unpublished code changes and expects both findings and concrete improvements.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a PERSONAL brand needs to make money — three funnel versions for founder, coach, and creator, an offer ladder from free to low to mid to high ticket, pricing psychology, inbound versus outbound outreach, and brand deal and sponsorship negotiation, with tax and legal variants for US LLC, EU per country, SEA Pte Ltd, and LATAM MEI. Trigger on 'monetize my personal brand', 'offer ladder', 'launch my course', 'coaching packages', 'sponsorship rates', 'I have an audience and no income'. Not for — a company product offer, see `31-offer-design-global` and `17-pricing-strategy-global`; the strategy that comes first, see `23-personal-brand-strategy-global`; running the community, see `28-community-building-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Dung khi mot CA NHAN muon xay CONG DONG quanh minh — Zalo Group, Telegram, Facebook Group, Skool, Mighty Networks, Discord: blueprint 3 lop public / member / inner, luong onboarding 7 ngay, nghi thuc tuong tac hang tuan, playbook kiem duyet, chi so kich hoat va cac loi thuong gap o VN. Kich hoat khi user nhac 'xay cong dong', 'Zalo group', 'Facebook group rieng', 'Skool community', 'membership site', 'group im lang khong ai noi', 'gom nguoi theo doi vao mot cho'. Khong dung cho — kiem tien tu cong dong thi dung skill 27-personal-brand-monetize; rai seeding duoi bai dang thi dung skill 38-seeding-plan; giu chan khach da mua cua doanh nghiep thi dung skill 69-giu-chan-khach-hang.
日本語の概要は準備中です。原文の説明を表示しています。
Use when someone outside the marketing team has to film — a customer for UGC, an employee for EGC, or a paid creator or KOC — and needs a brief: talking points, shooting guide, do and do-not list, usage rights, deliverables, and batch management. Trigger on 'UGC brief', 'creator brief', 'KOC brief', 'brief for employee videos', 'what do I tell the influencer', 'we hired a creator to film'. Also use when the user asks how to get customers to make videos for the brand. Not for — a script the team writes and shoots itself, see `04-script-video-global`; edit direction for footage already shot, see `44-video-editor-brief-global`; posting inside communities, see `38-community-seeding-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates new product opportunities through demand, channels and economics before committing to build.
日本語の概要は準備中です。原文の説明を表示しています。
Write unit, integration, and slice tests for Spring Boot 3 applications. Use when writing unit tests, integration tests, or slice tests for Spring Boot 3 applications.
日本語の概要は準備中です。原文の説明を表示しています。
Write Unit and E2E tests with Jest, mocking strategies, and database isolation in NestJS. Use when writing NestJS unit tests, E2E tests with supertest, or mock providers.
日本語の概要は準備中です。原文の説明を表示しています。
Write unit tests with table-driven patterns and interface mocking in Go. Use when writing Go unit tests, table-driven tests, or using mock interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Run evaluations for Hugging Face Hub models using inspect-ai and lighteval on local hardware. Use for backend selection, local GPU evals, and choosing between vLLM / Transformers / accelerate. Not for HF Jobs orchestration, model-card PRs, .eval_results publication, or community-evals automation.
日本語の概要は準備中です。原文の説明を表示しています。
Define evidence-first table schemas for a survey: what each table must answer, row unit, columns, and which evidence-pack fields are required to fill it.
日本語の概要は準備中です。原文の説明を表示しています。
Run a research Workflow end to end when the user requests a survey, brief, review, tutorial, or idea exploration; route an unbound goal, execute one eligible Unit at a time, and stop at checkpoints or diagnosed failures.
日本語の概要は準備中です。原文の説明を表示しています。
Write survey prose into per-section files under `sections/` so each unit can be QA'd independently before merging.
日本語の概要は準備中です。原文の説明を表示しています。
Polish a single H3 unit file under `sections/` into survey-grade prose (de-template + contrast/eval/limitation), without changing citation keys.
日本語の概要は準備中です。原文の説明を表示しています。
Review and record one pending human checkpoint in a research Workspace; use when a HUMAN Unit is blocked on an `Approve C*` decision, and never treat silence or artifact existence as approval.
日本語の概要は準備中です。原文の説明を表示しています。
Audit one research Workspace for declared Unit outputs and Pipeline target Artifacts, writing `output/CONTRACT_REPORT.md`; use for mid-Run coverage snapshots or final delivery completeness, not deep provenance integrity.
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS USE for test work that requires changes: write, add, generate, repair, or strengthen tests for existing code in xUnit, MSTest, NUnit, pytest, Vitest/Jest, Go, or another framework. Includes regression cases, failing or flaky tests, coverage-driven additions, and audit-then-fix requests. Focused work stays direct; broad or multi-stage work invokes test-engineer. DO NOT USE for only running tests, analysis-only audits, framework/platform migrations, a test blocked on a missing production seam (testability-obstacle), or MSTest API/configuration corrections that do not design new cases (writing-mstest-tests). Within an active test-engineer pipeline, reuse supplied guidance and do not re-enter this skill.
日本語の概要は準備中です。原文の説明を表示しています。
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero", exact solution wiring, xUnit/NUnit/MSTest, and central packages. DO NOT USE to only author tests in an already-wired project (code-testing), run tests, migrate, or correct MSTest syntax/configuration without changing project or CI files (writing-mstest-tests).
日本語の概要は準備中です。原文の説明を表示しています。
Write, run, or repair .NET tests that use MSTest. Use when a repo uses `MSTest.Sdk`, `MSTest`, `[TestClass]`, `[TestMethod]`, `DataRow`, or Microsoft.Testing.Platform-based MSTest execution. USE FOR: the repo uses MSTest; you need to add, run, debug, or repair MSTest tests; the repo is moving between VSTest and Microsoft.Testing.Platform. DO NOT USE FOR: xUnit projects; TUnit projects. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
日本語の概要は準備中です。原文の説明を表示しています。
Guidance for configuring dependency injection in .NET MAUI apps — service registration in MauiProgram.cs, lifetime selection (Singleton / Transient / Scoped), constructor injection, Shell navigation auto-resolution, platform-specific registrations, and testability patterns. USE FOR: "dependency injection", "DI setup", "AddSingleton", "AddTransient", "AddScoped", "service registration", "constructor injection", "IServiceProvider", "MauiProgram DI", "register services", "BindingContext injection". DO NOT USE FOR: data binding (use maui-data-binding), Shell route configuration (use maui-shell-navigation), unit-test mocking frameworks (use standard xUnit and NSubstitute patterns).
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to add or review Mongock MongoDB data migrations in a Quarkus application — including the Quarkiverse Mongock extension, Quarkus MongoDB client configuration, migrate-at-start, @ChangeUnit classes, lock/transaction settings, and Quarkus test verification. This should trigger for requests such as Add Mongock migrations in Quarkus; Configure quarkus-mongock; Review Quarkus MongoDB data migrations; Create Mongock change units for Quarkus MongoDB; Review Mongock migration ordering in a Quarkus service. Part of Plinth Toolkit
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a consultative, question-driven approach that adds only what you actually need. This should trigger for requests such as Add Maven dependencies; Add JSpecify nullness dependencies; Add Error Prone NullAway dependencies; Add VAVR functional dependencies; Add ArchUnit architecture testing dependencies; Add JavaMoney dependencies. Part of Plinth Toolkit
日本語の概要は準備中です。原文の説明を表示しています。