Explore skills

mcl-foundation-design / mcl-shared-platform-design / mcl-product-design が共通で参照するメタスキル。共通メタデータスキーマ、YAML テンプレート、正規化・マッピング・競合解決のルールを提供する。このスキルを直接トリガーする必要はない。他の mcl-* スキルが references/ templates/ schemas/ を参照する際に自動的に利用される。mcl-common の内容を確認・編集したい場合や、共通ルールやテンプレートについて質問がある場合にもこのスキルを参照すること。

Load saved session context from a previous session. Lists available sessions and restores TODOs, context, and pending work.

Save current session progress, TODOs, and context to a local file before ending a session. Enables picking up later with /session-load.

Plan a new feature before writing code. Explores the codebase, creates a structured plan with verification criteria, and only implements after approval.

個別プロダクト/ワークロード設計用スキル。AWS / Azure / GCP を対象に、ベンダー中立のワークロードモデル、ベンダー別サービスマッピング、実装仕様、オブザーバビリティ仕様、コスト最適化ヒント、IaC スケルトンを生成する。コンピュート、データベース、メッセージング、ストレージ、キャッシュ、CDN のサービス選定を、可用性、レイテンシ、データ機密性、トラフィックパターン、整合性、復旧目標、コストポスチャに基づいて行う。特定のアプリケーションワークロード、マイクロサービスアーキテクチャ、プロダクトインフラ、ユースケースごとのクラウドサービス選定の設計やレビューに使用すること。1 クラウドのみの言及でも発動する。EC2/App Service/Cloud Run、RDS/Azure SQL/Cloud SQL、SQS/Service Bus/Pub/Sub などのサービス比較もワー

Turn what we just did into a reusable skill. Captures the current workflow as a new SKILL.md file.

Generates a human-readable architecture document for any codebase. Use when onboarding contributors, presenting to stakeholders, explaining how a system works to non-technical collaborators, or after a major architectural change. Outputs docs/ARCHITECTURE.md with a Mermaid system diagram, plain English narrative, data flow walkthrough, and tech stack rationale. Trigger on: "map the architecture",

Activate when the user wants to reduce token usage, manage context efficiently, or says "be frugal", "save tokens", "token usage", "frugal mode", "reduce context", "don't waste tokens", "context limit", or "token efficient". Reviews current behaviour and enforces minimal-token rules for the rest of the session. Always active via CLAUDE.md — this skill is a mid-session audit and reminder.

Use when about to emit a warning, flag, or alert for a LOW-confidence issue — the alert-fatigue / signal-credibility discipline. False alarms have an asymmetric cost: after repeated low-confidence warnings, the operator stops reading the channel, and the one true warning gets ignored. Fires on choosing a log level (warn vs info vs error), inflating a PR title/commit to "CRITICAL", marking speculat

Use when about to extract maximum present value from a RENEWABLE source in a way that degrades the source itself — the kill-the-source / unsustainable-extraction anti-pattern. Fires when about to max out an API rate limit or quota to ship one task faster (risks the access), flood the operator with low-priority pings (burns attention/trust budget), sacrifice maintainability for one task's throughpu

Run the repo's make targets in dependency order (setup → lint → test → end-to-end) and verify each command's terminal output against its `logs/dev-<ts>-<cmd>.log` archive. Supports a full audit and a fast variant. Use whenever the user wants to validate the toolchain is clean, run lint+test locally before pushing, or reconcile terminal output against the dev-runner log archives — phrasings like "r

PHP 8.x migration guide for WordPress — covers PHP 8.0 through 8.3 features, breaking changes, backward compatibility patterns, dynamic properties fixes, and step-by-step migration strategy for themes, plugins, and custom code.