技術寫作

Expert guidance for writing TypeScript code following modern best practices, targeting TypeScript 5.x and ES2022. Use this skill when writing, reviewing, or refactoring TypeScript code in any .ts or .tsx file. Provides comprehensive guidelines on type system usage, architecture patterns, security, testing, and performance.

Follow the project's Python-based tech stack using uv, FastMCP, Claude Agent SDK, Pydantic v2, SQLite with SQLModel, and pytest with ruff. Use this skill when writing Python code for the MCP Task Aggregator. When using FastMCP to create MCP servers or tools. When working with Claude Agent SDK for AI agents. When defining Pydantic models or using pydantic-settings for configuration. When writing SQLModel queries or database operations. When using loguru for logging. When integrating with Jira (jira-python), GitHub (pygithub), or Linear (linear-sdk). When running pytest tests or ruff linting. When configuring GitHub Actions CI/CD.

Write copy that converts. Use when writing landing pages, emails, sales copy, headlines, CTAs, social posts, or any persuasive content. Triggers on: make this convert, write copy for X, help me sell X, punch this up, write a landing page, write sales copy. Produces internet-native copy that sounds like a smart friend explaining something while quietly deploying every persuasion principle in the book. Includes complete reference material from Schwartz, Hopkins, Ogilvy, Halbert, Caples, Sugarman, and Collier.

Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.

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.

Generate and validate tech stack documentation. Use when starting a new project, documenting technology choices, or when user asks to create/update tech stack documentation. Includes structural validation and LLM-as-Judge content review.

Ensures CLAUDE.md, README.md, and CHANGELOG.md are updated before git push operations

Lookup up-to-date library docs via Context7 MCP (resolve-library-id / get-library-docs).

Use when looking up information from the latest Docusaurus documentation at https://docusaurus.io/docs

Create and maintain GitHub Pages documentation for administrative guides, ubiquitous language definitions, and domain-driven design artifacts. Use when writing or updating documentation for admin procedures, domain terminology, DDD concepts, or user guides that will be published to GitHub Pages.

Three-pass critical reading framework for systematic document analysis. Supports tech blogs, retrospectives, technical documentation, personal writing, and academic papers. Primary focus on Third Pass critical analysis, context validation, and actionable reconstruction. Use when analyzing complex documents, performing critical reading, extracting actionable insights, or conducting deep analysis. Triggers include Third Pass, 비판적 분석, critique, 깊이 읽기, 심층 분석.

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.

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.

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

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.