スキルを探す

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.

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

Live developer experience audit. Uses the browse tool to actually TEST the developer experience: navigates docs, tries the getting started flow, times TTHW, screenshots error messages, evaluates CLI help text. Produces a DX scorecard with evidence. Compares against /plan-devex-review scores if they exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to "test the DX", "DX audit", "developer experience test", or "try the onboarding". Proactively suggest after shipping a developer-facing feature. (gstack) Voice triggers (speech-to-text aliases): "dx audit", "test the developer experience", "try the onboarding", "developer experience test".

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

Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".

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

Guidelines for creating API routes in Expo Router with EAS Hosting

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

Pick a product archetype from a curated catalog before any UI gets built — the single biggest lever for not looking vibecoded. Routes the request to one of B2B-productivity, enterprise-trust, premium-consumer, playful-consumer, editorial, brutalist-distinctive, dev-tool, or marketing-landing, and returns a complete design philosophy: typography pair, color logic, motion curve, density, icon stance, reference sites, and a "feels like X" claim. Load when the user asks to pick an aesthetic, choose a design direction, decide what a UI should feel like, classify a product visually, says "what should this look like", "make this feel like [Linear/Stripe/Apple/Duolingo/...]", "give me a design direction", "what's the right aesthetic for this", or when frontend-design routes here during archetype selection. Sub-skill of frontend-design.

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

Extract actionable insights from blog posts, web articles, and practitioner content - assess credibility, run security checks, and either improve existing skills or apply to the current project. Load when the user asks to learn from an article, extract insights from a blog post, apply a practitioner's findings, or process engineering blog content. Also triggers on "learn from this article", "learn from this blog post", "extract insights from this post", "what can we learn from this article", "apply this article", or when the user links to a blog, Medium, Substack, dev.to, or engineering blog post.

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

Write a Product Soul document — the strategic north star that sits above any PRD or feature spec. Captures the product's reason for existing across five lenses: user, business, strategy, product-market fit, and GTM distribution. Load when the user asks to write a product soul, product strategy doc, product north star, product positioning doc, product one-pager, or "why we exist" document. Also triggers on "write the soul of this product", "product strategy document", "what is this product really about", "capture the product vision", or when an agent needs strategic context before making product decisions. The output is docs/product-soul.md — a living document that brainstorming, prd-writing, and inversion can reference for grounding.

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

Quickly understand an unfamiliar codebase or project by mapping its architecture, identifying key components and data flows, and surfacing complexity hotspots. Load when the user asks to understand a repo, explain how something works, map the architecture, onboard to a codebase, or explore how components connect. Also triggers on "walk me through this codebase", "how does this project work", "explain the architecture", "what does this repo do", "show me the structure", "onboard me", or any request to build a mental model of a codebase before making changes.

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

Payment processing integration with Stripe and PayPal for Flutter

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

Braintree Automation: manage payment processing via Stripe-compatible tools for customers, subscriptions, payment methods, and transactions

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

Use this skill when the user requests to generate, create, or make presentations (PPT/PPTX). Creates visually rich slides by generating images for each slide and composing them into a PowerPoint file.

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

Run end-to-end deploy pipelines across Stripe, Supabase, and Vercel using the Composio CLI. Promote Stripe products, push Supabase migrations, ship Vercel deployments, and verify with post-deploy checks — all from one script.

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

Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.

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

Operationalizing an expungement website — user intake flows, document generation pipelines, court filing integrations, payment processing, state-by-state workflow variations, customer support for sensitive populations, and the handoff between automated systems and human legal review. Activate on 'expungement operations', 'legal tech SaaS', 'court filing integration', 'document automation pipeline', 'expungement business', 'legal service workflow', 'multi-state legal operations'. NOT for expungement law itself (use national-expungement-expert), web design (use legal-tech-web-design), or legal document drafting (use recovery-app-legal-terms).

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

Cloudflare Pages and Workers deployment checklist for wrangler deploys, secret audits, D1 migrations, Worker-compatible SDK checks, and browser-auth verification. Use when shipping Cloudflare changes to production. NOT for general CI/CD architecture, non-Cloudflare deployments, or post-launch UX QA.

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

Expert in developer tool documentation as a product. Activate on: docs site, getting started guide, API reference, developer documentation, Docusaurus, Mintlify, Nextra, ReadMe, migration guide, troubleshooting page, docs information architecture, documentation testing, llms.txt. NOT for: marketing copy (use seo-content-blogging), API design itself (use api-architect), general technical writing (use technical-writer).

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

Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs. NOT for GraphQL schema evolution, gRPC/Protobuf wire compatibility, database schema migrations, or library/SDK semver.

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

Use when designing a background-job system, choosing between BullMQ / Sidekiq / RQ / Temporal / SQS, deciding queue-vs-workflow, sizing concurrency vs rate limits, building dead-letter queues, or making handlers idempotent. Triggers: jobs running twice on retry, lost jobs after worker crash, DLQ filling up, Redis OOM from job backlog, exactly-once requested, "do we need Temporal?", visibility timeout / lockDuration confusion, exponential backoff vs jitter, fan-out fan-in workflows. NOT for outbound webhook publishing (different concerns), receiver-side webhook handling (different concerns), event-streaming/Kafka topology, or in-process async (event loop only).

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

Use when working with the 1Password CLI (`op` command) for secrets management, retrieving API keys, injecting secrets into development environments, or any task involving 1Password vault operations. Triggers on: "1password", "op command", "secrets management", "api keys from vault", "op run", "op read", "service account token".

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

Convex is the backend agents get right on the first try: an all-TypeScript reactive platform where the database, server functions, scheduling, file storage, auth, and realtime sync are one type-safe system, every function is a transaction, and `tsc` catches most mistakes before deploy. Ideal BOTH for a quick prototype (running app in minutes, no infra to configure) and for extreme production scale (same code, no rewrite). Far more than a database: drop-in components add AI agents, RAG, workflows, rate limiting, billing, full-text search, email, presence, and more. Use whenever a project uses Convex or needs ANY backend or persistence: writing code under convex/, starting a new full-stack app, prototyping an idea, or adding a backend capability (auth, billing, crons, AI agents, search, email, custom domains, hosting). Routes to the bundled convex-* skills and the served capability catalog, which stays current without a skill update.

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

Add Stripe billing/payments to the Convex app via @convex-dev/stripe (checkout + webhook + gating).

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

Analyzes bounded context boundaries in DDD projects. Detects cross-context coupling, shared kernel violations, context mapping issues, and ubiquitous language inconsistencies. Generates context map diagrams and boundary recommendations.

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

Generates DDD Anti-Corruption Layer for PHP 8.5. Creates translation layer between bounded contexts or external systems. Includes adapters, translators, facades, and unit tests.

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

Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.

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