2,338 件 ・ 関連度順
概要と使いどころ
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
日本語の概要は準備中です。原文の説明を表示しています。
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "plan how our narrative lands on every surface", "write per-surface message-match specs", or "brief each creative builder from the canon"; maps the narrative-registry canon onto every flagship surface (homepage, pricing, store listing, sales deck, social bio, docs, email) as a per-surface message-match spec — what claim, pillar, proof, and objection reframe each surface must carry — and cuts a handoff brief to each discipline's creative builder (content-writer, ad-creative-builder, email-creative-builder, social-creative-builder, message-house-builder), so the same story lands consistently everywhere. Not for writing the finished surface copy — use each discipline creative builder; not for the tier-scoped launch asset manifest — use launch-asset-packager; not for scoring cross-surface consistency — use narrative-quality-auditor; not for claim adjudication — use offer-claims-registry. 叙事落地/逐面消息一致/创意交接简报/画布传导
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "map what our surfaces say today", "inventory our current messaging", or "find the gap between what we say and what we mean"; produces the narrative baseline — a surface-by-surface inventory of what every owned touchpoint (homepage, pricing, docs, decks, social bios, email footers) claims RIGHT NOW, each line labeled Measured / User-provided / Estimated, plus a per-surface gap read vs the intended message and the drift-baseline snapshot the Evaluate phase measures future drift against. Not for authoring the canon — use message-system-architect; not for scoring the surfaces or running the vetoes — use narrative-quality-auditor. 现状叙事盘点/各触点口径/意图差距/漂移基线
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.
日本語の概要は準備中です。原文の説明を表示しています。
Developer marketing and developer relations for B2B SaaS with technical audiences. Use this skill when the buyer or user is a developer: documentation as a marketing surface, quickstarts and time-to-first-call, SDKs and sample apps, developer community and DevRel programs, open-source strategy, and technical content that survives engineer scrutiny. Also triggers on: developer marketing, DevRel, developer relations, developer experience, DX, docs, documentation, quickstart, SDK, API marketing, open source strategy, developer community, technical content, dev audience, hacker news, engineering blog.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure architecture docs define RPO/RTO, failover paths, data consistency, and DR drillability.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure requirement docs define scope, terminology, acceptance criteria, edge cases, and non-functional requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Checks design/ADR docs for consistency and missing decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure design docs explicitly capture risks, assumptions, and open questions with owners, deadlines, and mitigation plans.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure architecture docs capture availability targets, failover strategy, capacity headroom, and resilience trade-offs for critical services.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure architecture/design docs state traffic assumptions, performance budgets, resource limits, and cost risks for critical paths.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure architecture docs define bounded contexts, ownership, and a consistent ubiquitous language to prevent domain drift and coupling.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure architecture/design docs define clear boundaries, ownership, dependency direction, and change impact to avoid tight coupling.
日本語の概要は準備中です。原文の説明を表示しています。
microCMSの公式開発者ドキュメント(document.microcms.io)を取得し、API仕様・制限・認証・クエリ・管理画面の操作手順を出典付きで確認する。最新の仕様確認や公式資料・コード例の参照が必要な場合に使用する。プロジェクトの設計・実装・改善はmicrocms-guide、Next.js固有の実装はmicrocms-nextjsを優先し、必要な仕様確認をこのSkillで補う。
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
日本語の概要は準備中です。原文の説明を表示しています。
Generate AI agent skills from TypeScript documentation
日本語の概要は準備中です。原文の説明を表示しています。
MCP server documentation conventions for high-quality generated skills. Use when writing tool descriptions, `_meta` annotations, or input schemas for MCP extraction.
日本語の概要は準備中です。原文の説明を表示しています。
Documentation conventions for generating high-quality AI agent skills from TypeScript source. Use when preparing a library for skill generation, auditing JSDoc quality, fixing audit warnings, writing @useWhen/@avoidWhen/@never tags, or asking about documentation conventions for skills.
日本語の概要は準備中です。原文の説明を表示しています。
Check task processing statistics to see how much data and how many docs are moving. Use when checking throughput, diagnosing a stalled task, verifying data movement, or reporting on task activity. Use when user says "is data flowing", "how much data", "check throughput", "how many documents", "task not processing", "data not arriving", "stats", "bytes processed", "stalled capture", "no data in destination", "data volume", "task report", "usage report", or "how much data did we process".
日本語の概要は準備中です。原文の説明を表示しています。
How to migrate the tdmcp Claude Desktop bundle from legacy .dxt to .mcpb (MCP Bundle) and keep it building — covers the manifest schema (verify against the installed packer, never hardcode), the build-dxt.mjs packer/zip-fallback flow, the npm scripts, and the full .dxt→.mcpb reference sweep across docs and scripts. Use when packaging or migrating the tdmcp desktop bundle.
日本語の概要は準備中です。原文の説明を表示しています。
Write operator-facing and public documentation plans for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for runbooks, rehearsal checklists, show-day checklists, EN/PT docs updates, demo scripts, safety wording, and follow-up documentation revisions.
日本語の概要は準備中です。原文の説明を表示しています。
Marp形式プレゼンテーションの専門レビュー・評価・改善スキル。 10軸スコアリング（100点満点）で品質を定量評価し、具体的な改善コード付きで提案する。 Use when the user asks to: - Review, evaluate, or critique a Marp presentation / プレゼンをレビュー / 評価 / 添削 - Improve, polish, or upgrade existing slides / スライドを改善 / ブラッシュアップ - Check slide quality, score slides, or audit a deck / スライドの品質チェック / 採点 - "このプレゼンどう？" "スライドを見てほしい" "プレゼン資料のフィードバック" Reads .md files with Marp frontmatter, scores across 10 dimensions, and outputs a detailed review report with concrete before/after code improvements. Works as a companion to the marp-slides skill (generation → review → improvement cycle).