DevOps

Establish clarity before starting work. Use when beginning any significant task, when input is vague or stream-of-consciousness, or when requirements seem unclear. Handles messy voice input efficiently. This is the first system in the 5-system framework.

Install Kyverno, create validation policies, and understand audit vs enforce modes for Kubernetes admission control.

This skill should be used when the user asks to "write a law review article", "draft a legal paper", "edit legal writing", "review my legal article", "write for a journal", "format footnotes", or needs guidance on academic legal writing. Based on Volokh's "Academic Legal Writing" with law-review-specific structure and evidence handling.

Generate FAQ sections with proper FAQPage schema markup for therapy pages. Creates 10-12 therapy-specific questions, 50-100 word answers, and valid JSON-LD schema. Optimized for Google rich snippets (health websites still eligible). Includes CRPO-compliant language and Ontario-specific content. Use when user says "add FAQ", "FAQ schema", "improve rich snippets", or when creating/updating therapy pages.

This skill should be used when the user asks about "DNS performance", "zone settings", "DNS analytics", "domain configuration", "DNS report", "zone list", "DNS troubleshooting", "DNSSEC", "DNS latency", or needs to monitor and optimize Cloudflare DNS.

Guide for creating effective skills that extend agent capabilities with specialized knowledge, workflows, or tool integrations. Use this skill when the user asks to; (1) create a new skill, (2) make a skill, (3) build a skill, (4) set up a skill, (5) initialize a skill, (6) scaffold a skill, (7) update or modify an existing skill, (8) validate a skill, (9) learn about skill structure, (10) understand how skills work, or (11) get guidance on skill design patterns. Trigger on phrases like "create a skill", "new skill", "make a skill", "skill for X", "how do I create a skill", or "help me build a skill".

Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking. Language-agnostic principles with TypeScript/Jest and Python/pytest examples.

Generate rich visualizations for fractal horn design. Use when rendering 3D geometry,creating acoustic plots, animating simulations, building dashboards, or producingpublication-quality figures. Central visualization hub for all SFH-OS agents.

COO 社交媒体运营技能，使用 Playwright MCP 实现小红书、抖音、微信公众号、视频号的自动化运营

Expert guide for Omarchy Linux system management. Use when user asks about Omarchy commands, updates, migrations, configuration, or how Omarchy works. Inspects the local Omarchy installation at ~/.local/share/omarchy to provide accurate answers.

Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.

Provides ruthless prioritization framework for product decisions. Use when advising what to build next, challenging feature ideas, evaluating new features against Impact vs Effort matrix, applying stage-based rules (pre-launch, post-launch, growth), or keeping roadmaps focused by filtering feature creep. Enforces retention-first mindset and validates features against real user needs versus imaginary requirements.

Writes a professional launch press release with headline, dateline, summary, quotes, specs, pricing, availability, and media info.

Use when someone has never heard of animation principles, needs the simplest explanation possible, or is a complete newcomer to animation

Docusaurus build health validation and deployment safety for Claude Skills showcase. Pre-commit MDX validation (Liquid syntax, angle brackets, prop mismatches), pre-build link checking, post-build health reports. Activate on 'build errors', 'commit hooks', 'deployment safety', 'site health', 'MDX validation'. NOT for general DevOps (use deployment-engineer), Kubernetes/cloud infrastructure (use kubernetes-architect), runtime monitoring (use observability-engineer), or non-Docusaurus projects.

Fix import statements across the codebase to use correct module paths, resolve circular dependencies, and align with clean architecture layer boundaries.

Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.

生成多环境配置清单和dotenv模板文件，确保dev/test/staging/prod环境配置完整。当需要创建环境配置、生成.env.example模板、文档化测试框架setup、映射CI环境变量时使用。解决dotenv经常被忽视的痛点。

Expert cloud architecture including AWS, GCP, Azure design patterns, cost optimization, and multi-cloud strategies

Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.