文件

Transform rough ideas into clear, engaging writing using Gary Provost's rhythm and structure principles. Use when the user needs help writing emails, tweets, scripts, sales copy, articles, or any content where readability, flow, and digestibility matter. Ideal for entrepreneurs and content creators who want to turn ideas into professional writing without sounding robotic or over-polished. Apply when the user asks for help writing, editing for clarity, improving pacing, or making content more engaging.

Identify friction points, bottlenecks, bugs, and technical debt. Use for audits, debugging sessions, when something feels wrong, or before major work to surface hidden issues. This is the second system in the 5-system framework.

Create or update project issues following the Epic specification format with Behaviors (Rules + Examples), Technical Specifications (Action/Hook/Component/Service), and task lists. Use when user asks to create/update an issue, document requirements, or write specifications for a new feature.

This skill provides access to a project's recorded technical decisions and architectural patterns. Use this skill to understand established patterns, validate proposals against decisions, and cite decisions when reviewing code or specifications. Works with any project that maintains a decisions registry.

Testing patterns for Composable Svelte. Use when writing tests, using TestStore, mocking dependencies, or testing reducers and effects. Covers the send/receive pattern, mock implementations, testing composition strategies, and testing best practices.

箇条書きコンテンツを技術記事に仕上げる際に使用する。自然な文体とスタイルで執筆するためのガイドライン。

Generate OpenAPI 3.x specification files (YAML) with endpoints, schemas, authentication, and examples for REST API documentation. Triggers on "create OpenAPI spec", "generate API documentation", "swagger spec for", "REST API schema".

Edit writing to adopt Paul Graham's exceptionally clear style for research and long-form content - concrete language, varied sentence rhythm, accessible formality, specific evidence. Use when user wants to rewrite content in PG's style or asks to "make this clearer" or "simplify research writing."

Write clean, consistent code following naming conventions, formatting standards, and DRY principles across all files. When writing or editing any code in any programming language (TypeScript, JavaScript, Python, etc.). When creating functions, variables, classes, or modules. When refactoring code to improve readability or reduce duplication. When implementing small, focused functions or removing dead code. When ensuring consistent indentation, naming patterns, and code structure. This skill applies universally to all code files regardless of their specific purpose.

Enhance writing quality by fixing grammar, improving sentence structure, maintaining consistent style, and strengthening prose. Use when editing chapters, improving readability, or polishing final drafts.

Convert experiment results to Markdown research notes and optionally update research state with evidence

This skill should be used when the user asks to "create a README", "write a README", "generate a README", "improve my README", "make my README better", "README best practices", or mentions needing project documentation. Provides guidance for creating excellent READMEs following patterns from awesome-readme.

NVIDIA API documentation for integrating NVIDIA services. Use for NVIDIA NIM (NVIDIA Inference Microservices), LLM APIs, visual models, multimodal APIs, retrieval APIs, healthcare APIs, and CUDA-X microservices integration.

Ansible automation and configuration management patterns. Use when writing Ansible playbooks, roles, or automating infrastructure configuration and deployment tasks.

Generate initial project planning documents (PVS, ADR, Tech Spec, Roadmap) from a project concept description. Use when starting a new project, when docs/planning/ contains placeholder files, or when user requests project planning document generation.

Create and manage database migrations following best practices for schema evolution and data integrity. When creating or modifying database migration files (migrations/*, *.migration.ts, migrate.ts). When working on schema changes, data migrations, or database version control. When implementing reversible migrations with up/down methods, managing indexes on large tables, or handling zero-downtime deployments. When writing migration scripts that alter database structure, add or remove tables, modify columns, or transform data.

Enforce strict TDD workflow for all development tasks. Use when implementing new features, fixing bugs, or refactoring code. Ensures comprehensive test coverage (unit, integration, e2e) before writing implementation code. Activates automatically for all coding tasks unless explicitly authorized to skip testing.

Create Architecture Decision Records for significant technical decisions. Use after making architectural choices, when documenting why a technology was selected, or when solutions-architect needs to record a decision.

Create, improve, and debug professional LuaLaTeX documents using KOMA-Script + the moderndoc package (and the legacy modern-doc shim). Use for: generating new documents from a goal, improving typography/layout, producing PDF/A-4-friendly output, setting up minted/biblatex/tabularray/tikz, converting Mermaid → TikZ, and debugging compilation logs.

Testing guidelines for Bun/TypeScript projects using bun:test framework. Use when writing tests, creating test files, debugging test failures, setting up mocks, or reviewing test code. Triggers on *.test.ts files, test-related questions, mocking patterns, and coverage discussions.