4,339 件 ・ 関連度順
概要と使いどころ
When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions. Also use when the user mentions "track competitors", "what are competitors doing", "competitor alerts", or "market watch".
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to analyze, categorize, or extract actionable insights from customer feedback across multiple sources, especially feature requests.
日本語の概要は準備中です。原文の説明を表示しています。
When a founder needs demo scripts, discovery call frameworks, objection handling, RFP/RFI responses, competitive feature matrices, POC planning, or closing playbooks. Activate for sales calls, demo prep, talk tracks, bid responses, competitor comparisons, or pre-sales engineering.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to decide what to build, cut, and defer for a first release or minimum viable version of a product or feature.
日本語の概要は準備中です。原文の説明を表示しています。
Fix a reported bug with a regression test that demonstrably fails on the original behavior and passes after the fix. Use when implementing a bug fix or checking whether a proposed fix actually addresses a reported failure. Not a general coverage audit or new-feature workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Property development lifecycle in OpenConstructionERP: lead to SPA to handover — feasibility, budgeting from cost bases, sales tracking and construction handover. Use for residential/commercial development projects.
日本語の概要は準備中です。原文の説明を表示しています。
Databricks documentation reference via llms.txt index. Use when other skills do not cover a topic, looking up unfamiliar Databricks features, or needing authoritative docs on APIs, configurations, or platform capabilities.
日本語の概要は準備中です。原文の説明を表示しています。
Writes and restructures technical documentation - READMEs, tutorials, how-to guides, user guides, architecture docs, onboarding guides, runbooks and SOPs, troubleshooting guides, release notes, and knowledge base articles - grounded in the actual code or product, with commands and examples verified where possible. Use when the user asks to document a project, feature, system, or process, write or fix a README, explain a codebase to new developers, turn notes into a guide, or make existing docs clearer. For endpoint-by-endpoint API reference or OpenAPI specs, use api-documentation-writer; for CLAUDE.md or AGENTS.md files, use claude-md-writer.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates which SaaS tools can be replaced with AI agents. Takes a list of current SaaS subscriptions with costs, assesses replacement feasibility, estimates build vs buy economics, identifies Claude+MCP alternatives, and generates a comprehensive replacement plan with priority matrix, ROI analysis, implementation timeline, and risk assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Use for any task that spans more than a couple of steps, files, or sessions — refactors, migrations, multi-file features, anything that must survive a context reset or crash. Trigger when the user asks for a plan, says "keep track of this", "don't lose the thread", or when a task is large enough that forgetting step four is likely.
日本語の概要は準備中です。原文の説明を表示しています。
Wire a System One model (Jev, or an open reproduction like Von) into a product feature — routing, guardrails, scoring, classification. Use when replacing an LLM call that returns a label rather than prose, when adding a typed decision to an agent loop, or when deciding between the hosted Jev API and a local open model. Covers question design, the eval-set-first workflow, threshold calibration, confidence gates, and the traps measured on real data.
日本語の概要は準備中です。原文の説明を表示しています。
Build and run a labelled eval set for a System One model (Jev, Von, or any typed-decision config), then sweep criteria wordings and thresholds against it. Use when a Jev/Von classification is wrong or unreliable, when choosing between the hosted API and a local open model, when tuning noul thresholds, or before shipping any typed-decision feature. Produces an accuracy-by-wording matrix and a calibrated threshold.
日本語の概要は準備中です。原文の説明を表示しています。
Writes conversion-focused landing page copy - headlines, subheads, value propositions, feature and benefit blocks, social proof, FAQs, and CTA button text - using PAS, AIDA, or StoryBrand. Use when the user wants words for a landing page, sales page, product or pricing page, waitlist page, homepage hero, or ad-to-page flow, including rewriting weak copy, generating headline or CTA variants for A/B tests, or turning a product description into page sections. Use landing-page-optimizer instead for auditing an existing page's performance, and a frontend skill for building the page itself.
日本語の概要は準備中です。原文の説明を表示しています。
Use before building anything from a vague request — a feature, an app, an agent, an automation, a page. Trigger when the user says "build me X" without specifics, when a brief could be read two ways, or when the user asks to be challenged, interrogated, or pushed on requirements before code gets written.
日本語の概要は準備中です。原文の説明を表示しています。
Designs relational and document database schemas from requirements or an existing app - tables and collections, keys, relationships, constraints, indexes driven by real query patterns, ERDs, and reversible migration scripts - with PostgreSQL (including Supabase) as the default and MySQL, SQLite, and MongoDB supported. Use when the user wants to model data for a new app or feature, review or fix an existing schema, choose keys or indexes, plan multi-tenancy, normalize or denormalize, or write CREATE TABLE statements or migrations, even if they just describe their app and ask "how should I store this". For moving data between database providers, use database-migrator.
日本語の概要は準備中です。原文の説明を表示しています。
Build a panel of your real buyer personas (from a deep scan of any tools you allow it to connect to) and have them debate any decision you bring — a marketing launch, a price increase, a new product, a positioning change, a feature cut. Returns a structured debate, the strongest objections, and a clear recommendation. Use when you want your actual customers in the room before you commit.
日本語の概要は準備中です。原文の説明を表示しています。
Identifies upsell and cross-sell opportunities within existing customer accounts. Analyzes product usage, feature gaps, team growth, industry benchmarks, and competitive pressure to surface revenue expansion plays scored by potential, effort, and likelihood. Generates an expansion-playbook.md with account-by-account opportunities, recommended pitch, timing, and approach.
日本語の概要は準備中です。原文の説明を表示しています。
Aggregate and analyze customer reviews from G2, Capterra, Trustpilot, App Store, and other platforms. Performs sentiment analysis, identifies pain points, extracts feature feedback, generates marketing claims, and compares competitor reviews. Use when users need review analysis, competitive intelligence, or customer feedback insights.
日本語の概要は準備中です。原文の説明を表示しています。
Fixes broken decks/PDFs exported from Claude's "Design" feature (or similar AI deck generators) — cut-off or clipped text, wrong/substituted fonts, and corrupted .pptx package structure that shows up only once you export to PDF, not while looking at it in the app. Use this skill whenever the user uploads a zip, .pptx, or .pdf exported from Claude Design (or mentions "Design" export, an AI-generated deck, or a generated slide deck/PDF) AND reports it looking broken, wrong, cut off, garbled, or different from the original when opened, printed, or converted to PDF — even if they don't use the word "repair" or name the specific defect. Also trigger for general "my exported PDF/deck is broken, help fix it" requests when the file was clearly produced by an AI design/deck tool rather than hand-authored. Produces both a repaired, still-editable .pptx and a clean PDF, plus a report of exactly what was wrong and what changed.
日本語の概要は準備中です。原文の説明を表示しています。
Use before starting a product, feature, MVP, agent, automation, or integration build to identify the main pre-build risk and choose the smallest validation step. Trigger when the user asks whether to build, scope, validate, prioritize, or sanity-check an idea before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Compose a premium, animated landing page section by section in Next.js + Tailwind + Motion (Framer Motion) — built on a real design system, with editorial copy and motion that feels human-crafted, not template-generated. Use when building or rebuilding a landing page, marketing site, or hero/feature/pricing/CTA sections that need to look production-ready and bespoke from day one.
日本語の概要は準備中です。原文の説明を表示しています。
PRD（プロダクト要件定義書）の作成、機能仕様の策定、受け入れ基準の定義を行うスキル。 「PRDを書いて」「機能仕様を作って」「要件定義して」等のリクエストで発動。
API reference: MapKit for SwiftUI. Map view, Marker, Annotation, camera positions, map features.
日本語の概要は準備中です。原文の説明を表示しています。
API reference: SwiftUI. Query for views, layouts, navigation, @State/@Binding/@Observable, view modifiers, NavigationStack, iOS 26+ features.
日本語の概要は準備中です。原文の説明を表示しています。