Technical Writing
5624 skills in Documentation > Technical Writing
svelte-expert
Expert Svelte/SvelteKit development assistant for building components, utilities, and applications. Use when creating Svelte components, SvelteKit applications, implementing reactive patterns, handling state management, working with stores, transitions, animations, or any Svelte/SvelteKit development task. Includes comprehensive documentation access, code validation with svelte-autofixer, and playground link generation.
ros2-patterns
ROS 2 node templates and message types for robotics development. Use when creating ROS 2 nodes, understanding message types, or writing publisher/subscriber patterns.
ant-design-knowledge-base
Provides comprehensive answers about Ant Design components, documentation, and semantic descriptions using local knowledge base files. Use when asked about Ant Design, React UI components, design system, component semantics, or specific component usage.
revision-framework
Apply 3-column revision method (problem/diagnosis/fix), detect weak phrasing, check clarity, enforce house-rulebook style. Use when revising drafts, improving prose quality, or when user asks to edit or refine writing.
google-workspace
Google Workspace 통합 스킬. Docs, Sheets, Drive, Gmail, Calendar API 연동. OAuth 2.0 인증, 서비스 계정 설정, 데이터 읽기/쓰기 자동화 지원.
auto-commit
Automatically commits changes using conventional commits format (feat:, fix:, docs:, chore:, refactor:, test:, style:). Use after completing bug fixes, feature implementations, or documentation updates. Triggered automatically via Stop hook.
writing-guide
7년차 시니어 백엔드 개발자 이력서/경력기술서 작성 가이드입니다. STAR+I 기법, 정량화 방식, 시니어 톤 표현을 제공합니다.
markdowntown-cli
Repo workflow for markdowntown-cli development and scans.
subject-line-optimizer
Improve newsletter open rates through better subject lines. Use when:(1) Writing subject lines for tacosdedatos editions, (2) Analyzing why an editionhad low open rates, (3) A/B testing subject line variants, (4) Reviewing subjectlines before sending. Produces 5-10 variants with recommendations.
global-validation
Implement comprehensive validation using Zod schemas for type-safe validation on both client and server, with server-side validation as the security boundary (never trust client input). Use this skill when validating user inputs, creating API endpoints that accept data, implementing forms, defining data schemas, validating file uploads, creating validation middleware, implementing Firestore security rules or Supabase RLS, or writing validation rules for any user-provided data. Apply when working on API route handlers, form components with React Hook Form, validation middleware, Zod schema definitions (schemas/*.ts, validation/*.ts), Firestore security rules (firestore.rules), Supabase RLS policies, or any code that accepts external input. This skill ensures server-side validation always (client-side is for UX only), Zod for schema validation with TypeScript type inference (z.infer<typeof schema>), validation middleware factory for Express/Bun APIs, React Hook Form + zodResolver for forms, user-friendly error
c99-code-review
Review C99 code for compliance with HBF's strict coding standards including compiler warnings, Linux kernel style, and licensing constraints. Use when reviewing or writing C code in this project.
docs-release-notes
docsca が summary.md を作り、必要なグローバル文書を更新する手順。
ln-100-documents-pipeline
Top orchestrator for complete doc system. Delegates to ln-110 coordinator (project docs via 5 L3 workers) + ln-120-150 workers. Phase 4: global cleanup. Idempotent.
web-content-summarizer
Fetch and summarize web content for any research task - documentation, design inspiration, competitor analysis, tutorials, API docs. Use when you need to understand web pages, extract key information, research patterns, or gather context for development work.
unity-testing
This skill should be used when the user asks about "tests", "unit tests", "EditMode tests", "PlayMode tests", "Test Runner", "test coverage", "NUnit", "Assert", "test fixtures", "writing tests", "running tests", or discusses Unity testing patterns and practices.
software-product-manager
Expert software product manager who works directly with stakeholders to understand their needs and create comprehensive product specifications. Use when users need help designing software, defining requirements, creating PRDs, writing user stories, or developing functional specifications. Guides product management aspects of software development, asks clarifying questions, uncovers unstated preferences and assumptions, determines happy paths and error handling, and creates documentation understandable to both stakeholders and engineers.
programming
Write, debug, review and explain source code following object-oriented best practices, DDD principles, and comprehensive testing standards. Use when writing new code, refactoring, debugging, code review, or explaining programming concepts.
notebooks-front-end
Use when editing docs/index.html, creating charts with Plot, adding SQL cells, loading data with FileAttachment, or building visualizations. Triggers on any editing of docs/index.html, Observable notebooks, or front-end visualization work.
go-maintainable-code
Write clean, maintainable Go code following Clean Architecture, dependency injection, and ChecklistApplication patterns. Use when writing new Go code, refactoring, or implementing features.
testing-patterns
Test infrastructure patterns - PGlite for in-memory PostgreSQL, Redis/S3 mocks, TestSetup factory, Vitest. Use when writing tests or adding test infrastructure.