技術寫作

Expert writing for technical content, social media, and developer documentation. Use when asked to write tweets, LinkedIn posts, blog posts, READMEs, commit messages, feature announcements, or any written content. Optimized to avoid AI detection patterns.

Tracks package.json dependencies and identifies undocumented, outdated, or misaligned tools. Compares installed packages against documented versions in docs/infrastructure/, detects unused dependencies, and flags version mismatches. Use when user requests "check dependencies", "audit package.json", "find undocumented packages", or mentions dependency alignment.

Write WYSIWID-style design docs (Concepts + Synchronizations) for go-lcpd, keeping terminology consistent with code.

CRITICAL: PostgreSQL MCP Server SQL limitations and correct patterns. This skill MUST be consulted before writing any SQL for the CRM database. Documents what works and what DOES NOT work with mcp__postgresql__ tools.

GitHub Actionsセルフホストランナーの設計、セットアップ、セキュリティ管理を行うスキル。インストールから運用、トラブルシューティングまでの完全なライフサイクル管理を提供する。Anchors:• GitHub Actions Documentation / 適用: セルフホストランナー公式仕様 / 目的: 正確なAPI使用と設定• CIS Benchmark for Linux / 適用: ランナーホストのセキュリティ / 目的: セキュリティ強化• The Pragmatic Programmer / 適用: 実践的改善 / 目的: 段階的な実装と継続的改善Trigger:Use when setting up self-hosted runners, configuring runner labels, implementing security measures, troubleshooting runner issues, or optimizing runner performance.self-hosted, runner, GitHub Actions, ephemeral, labels, security, setup, configuration

Master declarative, no-code data dashboards with Lumen YAML specifications. Use this skill when building standard data exploration dashboards, connecting multiple data sources (files, databases, APIs), creating interactive filters and cross-filtering, designing responsive layouts with indicators and charts, or enabling rapid dashboard prototyping without writing code.

Developer reporting skill for work documentation and communication. Use when writing journals, devlogs, status updates (22A/22B), progress reports, or documenting development work. Generates reports from git history or manual input.

TypeScript expertise for React/Next.js development. Use when writing React components with strict typing, fixing TypeScript errors, handling generic components, or working with TanStack Query types. Focuses on common pitfalls and advanced patterns.

Enforce mature commit hygiene and documentation standards for long-lived projects. Trigger this skill automatically in ANY project before ANY commit creation, whether prompted by human, agent, or another skill; always do this, to ensure changesets are clean, tests pass, commit messages are terse and insightful, and all committed content is timeless rather than dependent on circumstantial context to cohere or be useful. Targets senior/staff engineer standards - no cruft, no debug statements, no transient language, no obvious comments. Maintains README accuracy and prevents documentation bloat.

Write and optimize instructions for Claude Code (skills, slash commands, memory files, CLAUDE.md). **ALWAYS use before creating or modifying any CLAUDE.md file, SKILL.md file, command file, or instruction documentation.** Triggers when writing skill descriptions, optimizing prompts for clarity/token efficiency, or when user mentions "write a skill", "create a command", "optimize instructions", or "improve this prompt".

Meta-skill (Phase 0) for bootstrapping new repositories withworkflow system. Interactive callable tool that copies skills,documentation, and standards from source repository.Use when: Starting a new project that needs the workflow systemTriggers: "initialize new repository", "bootstrap workflow","replicate workflow system"

Use when implementing any feature or bugfix, before writing implementation code. Execute strict Red-Green-Refactor TDD cycle following industry testing standards. Write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first.

Comprehensive guide for Terraform code style, formatting, and best practices based on HashiCorp's official standards and Azure Verified Modules (AVM) requirements. Use when writing or reviewing Terraform configurations, formatting code, organizing files and modules, establishing team conventions, managing version control, ensuring code quality and consistency across infrastructure projects, or developing Azure Verified Modules.

This skill empowers Claude to build AutoML pipelines using the automl-pipeline-builder plugin. It is triggered when the user requests the creation of an automated machine learning pipeline, specifies the use of AutoML techniques, or asks for assistance in automating the machine learning model building process. The skill analyzes the context, generates code for the ML task, includes data validation and error handling, provides performance metrics, and saves artifacts with documentation. Use this skill when the user explicitly asks to "build automl pipeline", "create automated ml pipeline", or needs help with "automating machine learning workflows".

Write compelling copy using proven frameworks. Use when: (1) Creating headlines, ads, or CTAs, (2) Writing sales pages or emails, (3) Positioning products, (4) Validating copy quality.

Use this skill when modifying or creating architecture documentation.

AWS development with CDK best practices, serverless patterns, cost optimization, and event-driven architecture. Use when deploying to AWS, writing Lambda functions, configuring API Gateway, working with DynamoDB, S3, or any AWS service.

運用ランブックの作成・保守スキル。本番システムの障害対応、トラブルシューティング手順、リカバリーワークフロー、運用知識の共有を標準化し、信頼性の高いシステム運用を実現する。Anchors:• Site Reliability Engineering (Google) / 適用: ランブックパターン、ポストモーテム / 目的: 運用の卓越性と信頼性• The Practice of System and Network Administration (Limoncelli) / 適用: 手順書標準化 / 目的: 再現可能な運用• Incident Management for Operations (Mogull) / 適用: インシデント対応 / 目的: 効果的な危機対応Trigger:Use when creating runbooks, documenting incident procedures, standardizing operational workflows,building troubleshooting guides, establishing recovery procedures, improving on-call readiness.runbook, incident response, troubleshooting, recovery procedures, operational documentation, on-call playbook

MUST be loaded when setting up, installing, migrating, reviewing, auditing, or checking CLAUDE.md files in projects. Covers installing the promode CLAUDE.md into new projects, migrating existing CLAUDE.md content to READMEs (progressive disclosure), and auditing projects for conformance. Invoke PROACTIVELY when user mentions CLAUDE.md, project setup, agent configuration, or code meta files.

Build and maintain effective CLAUDE.md files that improve Claude Code efficiency. Use when creating a new CLAUDE.md file, auditing/improving an existing one, setting up progressive disclosure with agent documentation, or optimizing context window usage for Claude Code projects.