Skills publicadas
Mostrando 12 de 828cm-dockit
Knowledge systematization engine — analyze codebases, generate Personas, JTBD, Process Flows, technical docs, SOP user guides, API references. Output as Markdown or VitePress Premium. SEO-optimized, AI/LLM-readable. One scan = complete knowledge base.
cm-git-worktrees
[Deprecated] worktree management is part of execution. Use `cm-execution` instead.
cm-continuity
Working memory protocol — maintains context across sessions via CONTINUITY.md. Inspired by Loki Mode. Read at turn start, update at turn end. Captures mistakes and learnings to prevent repeating errors.
cm-guardian-runtime
Use when you need to check if a destructive command is blocked or run guardian freeze checks.
cm-skill-chain
Skill Chain Engine — compose skills into automated pipelines. One task triggers multi-skill workflows with progress tracking, auto-detection, and step management.
cm-git-worktrees
[Deprecated] worktree management is part of execution. Use `cm-execution` instead.
cm-skill-index
Progressive Disclosure skill index — efficient skill loading in 3 layers. Layer 1 (index, ~100 tokens) always loaded. Layer 2 (summary, ~300 tokens) loaded on context need. Layer 3 (full SKILL.md) loaded on execution only.
cm-safe-deploy
Use when setting up deployment infrastructure for any project - establishes multi-gate deploy pipeline with test gates, build verification, frontend safety checks, and rollback strategy before code reaches production
cm-skill-mastery
[Deprecated] discovery and meta-skill merged. Use `cm-skill-index` instead.
cm-identity-guard
Verify and lock project identity before ANY git push, Cloudflare deploy, or Supabase operation. Essential when working with multiple GitHub accounts (personal + work), multiple Cloudflare accounts, or multiple Supabase/Neon projects. Prevents wrong-account deploys, cross-project secret leaks, and git history contamination.
cm-secret-shield
[Deprecated] deploy safety merged. Use `cm-safe-deploy` instead.
cm-secret-shield
[Deprecated] deploy safety merged. Use `cm-safe-deploy` instead.