Technical Writing

Emerging technologies (prompt engineering, AI agents, red teaming) and leadership roles (product manager, engineering manager, DevRel, UX design, technical writing).

エンタープライズ Azure 環境構築スキル。AVM 活用、VM アプリ初期化、App Service/AKS/Container Apps へのアプリデプロイ、サービス間設定連携、CI/CD 生成をサポート。Hub-Spoke, AKS, AI Foundry 等の複合アーキテクチャに対応。Bicep MCP と Microsoft Learn Docs MCP で最新スキーマを取得。

Create repository context bundles and code maps. Use to share codebase context, generate documentation, and understand project structure.

Use for Phase 10 of Course OS - generating the complete production package including handoff documentation, platform-specific exports, quality audits, and launch checklists. Triggers on "/course-production", "generate package", "export course", "production handoff", or after completing Phase 9.

Evaluate a headline using copywriting domain expertise

Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes

Generate and optimize PRDs, Implementation Plans, and Progress Tracking documents optimized as AI artifacts for development agents. Use when creating new feature plans, breaking down long planning docs (>800 lines), or setting up progress tracking. Supports: 1) Create PRD from feature request, 2) Create Implementation Plan from PRD with phase breakdown and subagent assignments, 3) Optimize existing plans by breaking into phase-specific files, 4) Create progress tracking with task assignments. Example: "Create a PRD for user authentication feature" or "Break down the sidebar-polish implementation plan into phase files" or "Create progress tracking for data-layer-fixes PRD".

Expert guidance on writing in Chamath Palihapitiya's communication style across 5 formats (Annual Letters, Customer Briefs, Emails, Policy Ideas Briefs, Learn with Me Presentations). Use when helping with any writing task, document creation, editing, reviewing communications, or answering questions about how to write something. Includes 10 universal principles, format-specific playbooks, internal team email guidance, templates, decision frameworks, and quality control checklists. MODULAR ARCHITECTURE: Optimized for LLM consumption with selective context loading (core + format).

typescript expert with self-populating documentation

Provides guidance on spec-driven, test-driven, iterative development methodology. Activated when user asks about MVP-first development, iterative workflows, TDD cycles, specification writing, or how to structure feature development.

Enforces online documentation research before any technical implementation. Use when implementing features to ensure code follows current best practices by researching official documentation first.

Create the deliverable (code, documentation, tests, content) following the user's standards and best practices. Use after validation passes to actually build the work product.

Automated build, deploy, and documentation workflow for backend and combined (frontend+Theia) services to GKE. Use when starting a new build, deploying code changes to production GKE, or need consistent deployment documentation.

Human writing standards to eliminate AI-generated text patterns. This skill should be used for any copywriting, marketing content, documentation, or professional writing to ensure output reads as genuinely human. Covers banned vocabulary, punctuation discipline, sentence variety, and tone guidelines.

This skill should be used when the user asks "how to use MorphLLM", "set up MorphLLM MCP", "configure Morph", "get started with MorphLLM", or needs initial guidance on using MorphLLM MCP tools and understanding available capabilities.

Nix conditional patterns: mkIf, optionals, optionalString, mkMerge. Use when writing conditional configuration, avoiding if-then-else, or combining multiple conditional blocks.

Guide for writing Rust code covering ownership, borrowing, lifetimes, error handling, async programming, and Rust best practices

Hierarchical machine-readable documentation - root CLAUDE.md with module index, per-module CLAUDE.md for significant modules

Automates development of TogetherOS Rewards module features. Use when building reward types, implementing validation, creating UI components, writing tests, or updating Rewards documentation. Handles end-to-end implementation from entity models through API handlers to frontend components.

Guides writing bundler tests using itBundled/expectBundled in test/bundler/. Use when creating or modifying bundler, transpiler, or code transformation tests.