Technical Writing
5624 skills in Documentation > Technical Writing
reading-websites
Use ONLY this skill when user mentions a domain (example.com, site.pl, docs.io), URL (https://...), or asks to read/fetch/check a website or webpage - MANDATORY, replaces WebFetch, crawl4ai, and curl
content-research-writer
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
global-commenting
Write purposeful code comments that explain the "why" behind technical decisions, complex logic, and non-obvious implementations using JSDoc for components and APIs. Use this skill when documenting component props, explaining complex algorithms, noting performance optimizations, documenting workarounds, or adding API documentation. When working on component prop interfaces requiring JSDoc documentation, complex business logic or algorithms, performance optimization rationale, browser compatibility workarounds or hacks, API route documentation with request/response formats, configuration file explanations, Content Collection schema documentation, or regex patterns and what they match.
slash-command-design
Interpretive guidance for designing Claude Code slash commands. Helps you apply official documentation effectively and create high-quality commands. Use when creating or reviewing slash commands.
kiss-principle
Apply the K.I.S.S principle (Keep It Simple, Stupid) to reduce complexity, improve maintainability, and solve problems elegantly. Use when designing systems, writing code, planning solutions, creating documentation, architecting features, or making decisions where simplicity drives quality and efficiency.
prd-writing
プロダクト要求定義書(PRD)を作成するスキル
write-commit-message
Guidelines for writing effective git commit messages using conventional commits style
briefkit-documenter
Create interface-first documentation using BRIEF system v3. Generate BRIEF.md files with inputs/outputs contracts, validate against spec, convert PRDs/specs to BRIEFs, and support multi-surface applications (Web/Mobile/API). Use when creating module documentation, establishing documentation standards, or documenting legacy code.
frontend-designer
Convert UI/UX designs (mockups, wireframes, screenshots) into technical specs, component architectures, and implementation guides. Use for design analysis, design system extraction, component specifications, and frontend documentation.
miden-assembly
Guide for understanding and writing Miden VM assembly (MASM) code. Use when:(1) Reading, analyzing, or explaining MASM code(2) Writing new MASM procedures or programs(3) Debugging MASM execution or stack state(4) Optimizing MASM code for cycle count(5) Working with Miden VM stack machine conceptsCovers instructions, code organization, core library, and common patterns.
web-search
Web research and literature search capabilities for external resources.LOAD THIS SKILL WHEN: User says "搜尋", "search", "找資料", "查詢", "檢索", "web search", "網路搜尋" | needs external documentation | research task | API reference lookup | technology comparison | wants latest information.CAPABILITIES: Technical docs (MDN, GitHub, Stack Overflow), academic papers (PubMed integration), API documentation, real-time web data via fetch_webpage, structured search results.
content-publisher
Handles the publication workflow for AndesRC blog articles. Creates markdown files, triggers builds, submits to Google Search Console, and initiates promotion. Use as the final step in the content pipeline.
create-agent-skills
This skill provides expert guidance for creating, writing, building, and refining Claude Code Skills. It should be used when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best practices.
nuxt-ui
Use when implementing or debugging UI features with Nuxt UI components, designing forms, tables, modals, or any user interface work - fetches current documentation to ensure accurate component APIs
documentation
Project documentation patterns using README.md with visual diagrams. For creating and maintaining product-level documentation that's accessible in-app via CMD-I.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
git-commit
Generate meaningful commit messages from git changes following conventional commits format. Use when user says "commit", "create commit", or needs help writing commit messages.
backend-queries
Write efficient and secure database queries following best practices for SQL injection prevention, N+1 query optimization, and performance for PostgreSQL (Bun.sql, Prisma, Supabase) and Firestore. Use this skill when writing or modifying database queries, implementing data fetching logic, working with ORMs (Prisma, TypeORM, Entity Framework), using Bun.sql native driver, querying Firestore collections, or implementing caching strategies. Apply when working on service files (services/*.ts, repositories/*.ts, *Service.cs), query builder implementations, data access layers, or any code that fetches or manipulates data. This skill ensures parameterized queries to prevent SQL injection (never interpolate user input), eager loading to prevent N+1 problems, selective column fetching (no SELECT *), strategic indexing on WHERE/JOIN/ORDER BY columns, transactions for related operations, query timeouts for performance, caching expensive queries, prepared statements with Bun.sql for repeated queries, and query-driven mod
generating-commit-messages
Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes.
documentation-standards
How user-facing and internal documentation should be written and maintained.