1.5万 件 ・ 関連度順
概要と使いどころ
Use when evaluating, comparing, installing, or recommending a Claude Code plugin, Agent Skill, MCP server, agent toolkit, or GitHub-hosted AI extension, especially when popularity is weak evidence or the candidate requests shell, network, filesystem, or credential access.
日本語の概要は準備中です。原文の説明を表示しています。
Expert product marketing guidance for SaaS growth - trial acquisition, user activation to first value, and freemium-to-paid conversion. Use when writing landing pages, onboarding flows, email sequences, pricing pages, upgrade prompts, or any growth/conversion copy.
日本語の概要は準備中です。原文の説明を表示しています。
Expert GTM marketing copywriter for emails, content, and social media. Use when writing marketing emails, email sequences, newsletters, blog posts, LinkedIn posts, Twitter/X threads, social content, brand copy, or personal brand content. Use for launch announcements, product updates, thought leadership, and engagement copy.
日本語の概要は準備中です。原文の説明を表示しています。
Expert customer lifecycle marketing guidance for retention, expansion, and advocacy. Use when designing onboarding programs, creating upsell strategies, preventing churn, building referral programs, or writing customer success content. Use for NPS programs, win-back campaigns, customer segmentation, and lifecycle email sequences.
日本語の概要は準備中です。原文の説明を表示しています。
Expert product specification and documentation writer. Use when creating PRDs, user stories, acceptance criteria, technical specifications, API documentation, edge case analysis, design handoff docs, feature flag plans, or success metrics. Covers the full spectrum from high-level requirements to implementation-ready specifications.
日本語の概要は準備中です。原文の説明を表示しています。
Expert sales negotiation strategist for B2B deal-making. Use when planning negotiation strategy, handling discount requests, closing deals, navigating procurement, or structuring win-win agreements. Covers anchoring, framing, BATNA development, multi-party negotiations, and contract terms. Use for enterprise deals, pricing discussions, and high-stakes negotiations.
日本語の概要は準備中です。原文の説明を表示しています。
Generates render and output configuration for Remotion videos. Focuses ONLY on output settings, codec, format, quality, resolution. Input is target platform/quality requirements. Output is RENDER_CONFIG.md with Remotion render settings.
日本語の概要は準備中です。原文の説明を表示しています。
Expert event marketing guidance for conferences, webinars, and field programs. Use when planning event strategy, creating booth presence, running webinars, producing virtual events, writing event promotion copy, preparing speakers, designing follow-up sequences, or measuring event ROI. Use for conference sponsorships, trade shows, user conferences, meetups, field marketing, and hybrid events.
日本語の概要は準備中です。原文の説明を表示しています。
Professional content generation with phased workflow (discuss→plan→execute→verify→ship), SEO optimization, and anti-AI auditing. Multi-profile support for unlimited brands. USE for: blog posts, LinkedIn, Twitter/X, Facebook, Instagram, email newsletters, landing pages, sales pages, case studies, product descriptions, SEO metadata. COMMANDS: /writer:discuss, /writer:plan, /writer:execute, /writer:verify, /writer:ship, /writer:next, /writer:profile-create, /writer:profile-list, /writer:profile-use, /writer:profile-view, /writer:profile-edit, /writer:status, /writer:help ALWAYS use for content requests like "write me a LinkedIn post" or "draft a blog article."
日本語の概要は準備中です。原文の説明を表示しています。
CRISP Execute — Sprint execution loop with change request management, security gates, product gates, and stakeholder reporting. Use after Phase S (Spec) is complete and crisp-state.json shows ready_for_execute: true. Triggers on "start sprint", "begin build", "execute", "sprint 1", "run sprints", or when handed off from crisp-orchestrator.
日本語の概要は準備中です。原文の説明を表示しています。
Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this out", "create a spec", "I need a spec for...", or describes a feature they want to build. Produces adaptive-complexity specs with Job Stories, Gherkin acceptance criteria, and three-tier boundaries. Output is a markdown file ready for agent execution or human review.
日本語の概要は準備中です。原文の説明を表示しています。
Architect a feature with the Carmack Council before writing code. Use when explicitly asked to plan a feature, do a "council plan", "carmack plan", or invoke /council-plan. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo Collina (Node.js), Brandur Leach (Postgres), Vercel Performance, Simon Willison (LLM pipeline), Karri Saarinen (UI quality), Vitaly Friedman (UX quality). Interactive feature discovery followed by parallel subagent dispatch. Produces a sequenced, attributed implementation plan with no code. Stack: Next.js App Router / React / TypeScript / tRPC / Prisma / Neon / Clerk.
日本語の概要は準備中です。原文の説明を表示しています。
Execute a Carmack Council plan task by task. Use when explicitly asked to implement a plan, do a "council implement", "carmack implement", "council build", or invoke /council-implement. Reads the output of /council-plan and builds each task sequentially, loading the relevant expert's reference document per task. Verifies after each task. Produces an implementation log for /council-review. Stack: Next.js App Router / React / TypeScript / tRPC / Prisma / Neon / Clerk.
日本語の概要は準備中です。原文の説明を表示しています。
Design rulebook and diagnostic layer for web UI, distilled from Refactoring UI by Adam Wathan and Steve Schoger. Use when building a new page or component, refining UI that looks off or amateurish, running a design review, or establishing design tokens (color shades, type scale, spacing scale, elevation, radius). Covers visual hierarchy, layout and spacing, typography, color and contrast, depth and shadows, images, and finishing touches, with Tailwind mappings throughout. Also triggers on non-English requests for the same things - for example Chinese: 页面/界面设计, 样式调整, UI 太丑, 设计评审, 视觉层级, 配色, 对比度, 间距, 排版, 阴影, 空状态, 设计规范, 设计系统. Not for backend logic, copy editing, or changes with no visual surface.
日本語の概要は準備中です。原文の説明を表示しています。
Route gh-aw design, creation, diagnosis, patching, active debugging, and upgrade requests to the right strategies.
日本語の概要は準備中です。原文の説明を表示しています。
Drive the ENTIRE tdmcp roadmap-to-1.0 to completion as a resumable, wave-by-wave campaign — Milestone 4 (generative-AI bridge wave), Milestone 5 (mixer scene arming), and the v1.0 consolidation gates G1–G6 — routing each class of work to the right existing sub-harness. Use whenever the user wants to "implement everything / all the milestones / the whole roadmap / finish the road to 1.0", run the next milestone, close the consolidation gates, or build a long autonomous campaign across M4/M5/G1–G6. ALSO use for every follow-up: continue/resume the roadmap campaign, run the next wave, re-run a failed wave, fold in QA results, check campaign status, re-prioritize, or scope to one milestone/gate. This is the CAMPAIGN layer ABOVE tdmcp-pipeline / tdmcp-feature-lead / tdmcp-backlog-campaign — it sequences across MULTIPLE sub-harnesses (tools, mixer, coverage, docs, bridge, recipes, submission), which the generic backlog-campaign does not. For a SINGLE feature use tdmcp-pipeline; for one tool-shaped backlog file use tdmcp-backlog-campaign. Simple questions can be answered directly.
日本語の概要は準備中です。原文の説明を表示しています。
Adds new visual examples to the tdmcp prompt cookbook documentation — both the English and Portuguese versions. Use when asked to: add more cookbook examples, create visual examples for the docs, show more surprising things you can do, add entries to the prompt cookbook, expand the cookbook, or any request to extend the cookbook with new prompts and results. Runs a 3-phase pipeline: curate candidates → write EN → write PT.
日本語の概要は準備中です。原文の説明を表示しています。
Review, harden, and test the safety policy for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for approval gates, blocked mixer operations, hazardous request handling, venue validation, bypass attempts, QA, risk review, or follow-up safety changes.
日本語の概要は準備中です。原文の説明を表示しています。
Verification methodology and gate checklist for the tdmcp Connectors Directory submission — run the docs build, build and inspect the .mcpb bundle, sweep for stale .dxt references, and cross-check the form-answer draft against the real requirements. Use to validate the submission package before a human submits, by executing commands and quoting evidence, not by trusting that work was done.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomously work a `.pm` workstream to completion — pick the next pending milestone, implement every task end to end, /ship it, then move to the next until none remain. Use when the user asks to "loop", drain, or work through a whole workstream's backlog (e.g. `/loop-worker w1`). Sequential, not interval-based; for a timed poll use /loop.
日本語の概要は準備中です。原文の説明を表示しています。
Develop evidence-backed structural and architectural security hardening proposals from vulnerability disclosures, supplied findings, incident or assessment documents, source code, or a completed Codex Security scan. Use when a user asks for systemic improvements, alternatives beyond per-finding patches, before-and-after security architecture views, engineering tradeoff analysis, or an implementation-ready plan for a selected hardening option. Also use automatically after a Codex Security scan with reportable findings when the top-level scan workflow requests final-report hardening guidance.
日本語の概要は準備中です。原文の説明を表示しています。
Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate, edit, apply, push, or merge the patch.
日本語の概要は準備中です。原文の説明を表示しています。
Review a pull request, commit, branch diff, or working-tree patch for security vulnerabilities.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect and maintain the repository's .pm workstreams, inbox notes, milestones, and tasks. Use when the user asks for PM board status or requests a supported board mutation such as creating, promoting, adding, or completing work.
日本語の概要は準備中です。原文の説明を表示しています。