Explore skills

マルチクラウド基盤（ランディングゾーン）設計用スキル。AWS / Azure / GCP を対象に、ベンダー中立の canonical model、ベンダー別マッピング、実装仕様、IaC スケルトンを生成する。組織構造、ID、ネットワーク、ポリシー、ログ、課金、セキュリティガードレールをカバーする。クラウド基盤設計、ランディングゾーンアーキテクチャ、組織構造、アカウント/サブスクリプション/プロジェクト階層、ID フェデレーション、ネットワーク分離、ポリシー適用、監査/ログ集約、課金境界、セキュリティガードレールに関する要求で使用すること。1 クラウドのみの言及でも発動する。AWS Organizations/SCP、Azure Management Groups/Policy、GCP Org Policy に関する質問も基盤設計の文脈であればトリガーする。

共有プラットフォーム設計用スキル。AWS / Azure / GCP を対象に、ベンダー中立の canonical model、ベンダー別マッピング、サービスカタログ、実装仕様、IaC スケルトンを生成する。共有ランタイム（Kubernetes）、オブザーバビリティ、CI/CD デリバリーパイプライン、アーティファクト管理、シークレット/証明書管理、プラットフォーム所有モデル、テナントオンボーディングをカバーする。共有プラットフォームレイヤー、内部開発者プラットフォーム、プラットフォームエンジニアリング、共有サービスカタログ、共通インフラサービスの設計やレビューに使用すること。1 クラウドのみの言及でも発動する。EKS/AKS/GKE 共有クラスタ、集中監視、共有 CI/CD、プラットフォームチームの責務に関するトピックでもトリガーする。

Generate properly formatted Markdown from unstructured notes, scratch text, transcripts, or rough drafts. Use when the user wants content rewritten into cleaner Markdown without inventing new information.

Apply when producing any markdown artifact for someone else (or future-you) to read — READMEs, analysis documents, Confluence pages, status reports, troubleshooting write-ups, skill content, conversation summaries, ticket descriptions, post-mortems, snapshots of system state, or any document that contains concrete current-state values. Defines the "snapshot + reproducer" rule (every static value m

Read, analyze, create, edit, repair, format, or validate spreadsheet files such as .xlsx, .xlsm, .csv, and .tsv. Use when the user provides a spreadsheet file, asks for native Excel output, needs formulas/pivots/financial-model formatting, or needs format-preserving edits. Do not use for ordinary Markdown tables or quick tabular prose unless spreadsheet file output is required.

Model product UI actions from user intent questions after a meaningful outcome, completion, created resource, imported data, uploaded file, synced integration, report, deployment, automation, review state, handoff, or workflow milestone. Use when deciding which actions to show, hide, group, name, prioritize, defer, or place across outcome, item, selection, continuation, navigation, recovery, and a

Convert Pencil `.pen` design files and named Pencil node IDs into production frontend code. Use when asked to implement, migrate, reproduce, or refine a Pencil/Figma-like visual design in code, especially for responsive artboards, glassmorphism, typography matching, background image layers, design tokens, or visual fidelity debugging against Pencil node IDs.

Final visual polish for an existing UI without redesigning it. Use after structure is clear, when asked to improve spacing, alignment, text hierarchy, readability, shadows, highlights, effects, action placement, or overall production feel. For screen structure, layer naming, code handoff, preview scenes, or animation planning, use pencil-ui-structure first.

Run multiple skills on the same task in parallel and compare outputs side by side. A creative pitch room -- give it a brief, and it finds skills (local + trusted community repos) to work on it independently, then presents all outputs for comparison. Use when asked to "skill battle", "compare skills", "run multiple skills", "pitch room", "get different takes", "split test this", "give me options",

Quick-reference card for shakespeare mode — all intensity levels, commands, and activation phrases. One-shot display, not a persistent mode. Use when the user types /shakespeare-help or asks "what shakespeare commands are there".

Framework based on April Dunford''s "Obviously Awesome" and "Sales Pitch". Use this skill whenever the user is discussing how to describe, frame, differentiate, sell, or talk about their product — even if they do not explicitly say "positioning," "pitch," or "messaging." Triggers include: (1) defining or evaluating product positioning using the five-component framework, (2) translating positioning

Framework based on April Dunford''s "Sales Pitch". Use this skill whenever the user is discussing sales conversations, pitch decks, demos, buyer messaging, or stalled deals — even if they do not explicitly say "sales pitch," "positioning," or "Dunford." Triggers include: (1) structuring a B2B sales conversation that builds buyer confidence rather than pushing features, (2) developing a pitch narra