文件
文件工具和技術寫作技能
6825 skills in this category
Subcategories
doc-formatter
Format documentation with emojis, status bars, and versioning matrix. Use when creating or updating README files, documentation, specs, or any markdown files.
planning-docs
企画・設計・アイデア出し・ブレインストーミング・要件定義など、プロジェクトの企画フェーズに関する会話をしているときに自動発動。会話の内容を自動的にdocs/ディレクトリにタイムスタンプ付きドキュメントとして保存する。
api-docs-generator
Generate API documentation in OpenAPI/Swagger, Markdown, or Postman Collection formats. Use when documenting REST APIs, GraphQL schemas, or creating client code examples.
writing-documentation
Creates technical documentation including READMEs, API references, user guides, architecture docs, ADRs, and runbooks. Use for requests to create, write, generate, or draft documentation. Trigger phrases include "document this", "write docs", "create readme", "API reference", "user guide", "architecture docs", "ADR", "runbook". For updating existing READMEs, use updating-readme instead.
test-writing
TDD(テスト駆動開発)に基づいたテストコード作成スキル。Red-Green-Refactorサイクルを実践し、t-wadaのベストプラクティスに従ってテストファーストで高品質なテストを作成します。Backend(Go test)とFrontend(Jest)の両方に対応。
zenn-markdown
This skill should be used when the user asks about "Zenn記法", "Zenn Markdown", "メッセージブロック", "アコーディオン", "埋め込み", "Zenn特有の記法", or mentions writing Zenn articles with specific formatting needs. Provides comprehensive knowledge of Zenn-specific Markdown syntax and best practices.
pal-analyze
Comprehensive code analysis for architecture, performance, security, and quality using PAL MCP. Use when reviewing codebases, assessing technical decisions, or planning improvements. Triggers on analysis requests, architecture reviews, or code quality assessments.
project-linking
Use when session starts with CLAUDE.local.md containing Vault project field - automatically loads vault index, enables dual-location routing (vault + local docs), style adaptation, and cross-location linking with GitHub URLs for Obsidian project documentation
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
obsidian-content-curator
Curate and improve content quality across Obsidian vault. Use when identifying stub notes, finding duplicate content, detecting outdated information, or improving overall documentation quality. Works with Korean and English content.
tech-ecosystem-analyzer
This skill should be used when users request comprehensive analysis of technology ecosystems, comparing multiple libraries/frameworks/tools with quantitative metrics from GitHub and web research. Trigger words include "ecosystem analysis", "compare libraries", "analyze React/Vue/Python ecosystem", "trending libraries", "technology stack comparison", or requests to evaluate multiple technical tools with data-driven insights.
task-manager
Manage project tasks, status, and dependencies using the Task Documentation System.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
backend-queries
Write efficient and secure database queries using parameterized statements, preventing SQL injection, and optimizing performance through proper indexing and eager loading. Use this skill when writing database queries, ORM query methods, SQL statements, or repository pattern implementations. Use this skill when optimizing query performance, preventing N+1 query problems, implementing transactions for data consistency, or adding query timeouts and caching strategies. Use this skill when working with SELECT statements, JOIN operations, WHERE clauses, or any code that interacts with the database to fetch or manipulate data. Use this skill when working with files in repositories/, queries/, services/, or data access layers that contain database query logic.
human-docs
Creates human-friendly documentation from AI context documentation. Transforms detailed AI documentation in ai/ folder into digestible summaries, quick starts, and visual diagrams in docs/ folder. Use when users need to quickly understand complex systems or when AI documentation is too detailed for human consumption. Specializes in Mermaid diagrams, executive summaries, and quick reference guides.
report-generator
Generates professional markdown comparison report with tables, executive summary, and verdict by use case. Use when user asks to 'generate report', 'create comparison report', 'synthesize comparison', 'write comparison', or when orchestrator has completed all data collection. Creates structured report with specs tables, pros/cons, pricing analysis, and actionable recommendations.
netgraph-dsl
NetGraph scenario DSL for defining network topologies, traffic demands, failure policies, and analysis workflows in YAML. Use when: creating or editing .yaml/.yml network scenarios, defining nodes/links/groups, writing adjacency rules, configuring selectors or blueprints, setting up traffic matrices or failure policies, debugging DSL syntax or validation errors, or asking about NetGraph scenario structure.
golang-dev-guidelines
Use this skill when planning, researching, writing, reviewing, refactoring, or testing Go code (including creating unit tests, test files, and mocks). It provides comprehensive Go development guidelines including proverbs, SOLID principles, and testing standards. Apply these guidelines to ensure code quality, maintainability, and consistency in any Go project.
global-commenting
Write minimal, evergreen code comments that explain complex logic without documenting obvious behavior or temporary changes. Use this skill when adding comments to PHP files, TypeScript/JavaScript files, or any code files, when documenting complex algorithms or business logic, when adding PHPDoc blocks or JSDoc comments, when writing self-documenting code with clear naming, or when reviewing existing comments for relevance and necessity. Focus on keeping code self-explanatory through clear structure and naming rather than relying heavily on comments.
bats-testing-patterns
Comprehensive guide for writing shell script tests using Bats (Bash Automated Testing System). Use when writing or improving tests for Bash/shell scripts, creating test fixtures, mocking commands, or setting up CI/CD for shell script testing. Includes patterns for assertions, setup/teardown, mocking, fixtures, and integration with GitHub Actions.