Technical Writing

Use when finishing any task. Final checklist before marking complete. Ensures nothing forgotten, all tests pass, documentation updated.

Interactive Archon integration for knowledge base and project management via REST API. On first use, asks for Archon host URL. Use when searching documentation, managing projects/tasks, or querying indexed knowledge. Provides RAG-powered semantic search, website crawling, document upload, hierarchical project/task management, and document versioning. Always try Archon first for external documentation and knowledge retrieval before using other sources.

Work Log - Confluence 작업 문서화

Deploy GitHub repositories to remote servers via SSH. Claude reads the README, understands build/start instructions, and executes deployment commands over SSH. Supports rollback on failure.

Generates PR descriptions, commit messages, release notes, and manages branch strategies, changelog automation, and git hooks. Use when creating pull requests, writing commits, preparing releases, managing branches, or automating changelogs.

Create, modify, and maintain Vue 3 components with TypeScript and SCSS. Use when building Vue components, modifying .vue files, defining component props/emits, styling with SCSS, or documenting component APIs. Handles component architecture, type safety, styling patterns, and documentation.

Unit testing patterns with xUnit, Moq, and FluentAssertions including AAA pattern, naming conventions, mocking, and edge case coverage. Use when writing or reviewing unit tests.

Creates comprehensive GitHub project documentation including README, CONTRIBUTING, CODE_OF_CONDUCT, CHANGELOG, architecture docs, and API documentation. Analyzes codebase to generate accurate, well-styled documentation with modern GitHub aesthetics. Use when setting up a new project, improving existing documentation, or generating missing docs.

Manage multilingual content for JSON messages and MDX files. Use when adding new UI strings, translating blog posts, creating multilingual pages, or updating content across locales (pt-BR, es, ja, fr).

Table-driven tests, mocking strategies, and comprehensive testing patterns. Use when writing tests.

Creates feature specifications capturing requirements and acceptance criteria. Use when writing specs, documenting features, or defining requirements.

Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context. Use this when design is complete and you need detailed implementation tasks for engineers with zero codebase context

Best practices AutoHotkey v2. Use when writing AHK v2 scripts - covers global variable declarations, SetTimer usage, event handlers, and GUI positioning.

Fetch Kit (ConvertKit) newsletter broadcasts for writing context. Use when asked to download newsletters, get past email content for style reference, or fetch broadcasts for analysis.

ALWAYS invoke this skill BEFORE writing or modifying ANY Rust code (.rs files) even for simple Hello World programs. Enforces Microsoft-style Rust development discipline and requires consulting the appropriate guideline files before any coding activity. This skill is MANDATORY for all Rust development.

Use when developing BigQuery Dataform transformations, SQLX files, source declarations, or troubleshooting pipelines - enforces TDD workflow (tests first), ALWAYS use ${ref()} never hardcoded table paths, comprehensive columns:{} documentation, safety practices (--schema-suffix dev, --dry-run), proper ref() syntax, .sqlx for new declarations, no schema config in operations/tests, and architecture patterns that prevent technical debt under time pressure

This skill automatically detects when CLAUDE.md files need updates based on codebase analysis. It identifies new patterns, code violations, stale documentation, and anti-patterns, then proposes specific markdown diffs showing exactly what CLAUDE.md sections should be added, modified, or removed. When codebase architecture changes, new patterns emerge, or documented practices diverge from actual code, this skill analyzes the robo-trader project structure and generates actionable recommendations with confidence scores. Should be invoked after major feature completions, during code reviews, or as periodic maintenance scans.

Use when implementing any feature or bugfix, before writing implementation code

Use when creating, auditing, or optimizing web content for search engines - routes to specialized sub-skills for content writing, keyword strategy, meta optimization, structure, authority building, snippet optimization, content planning, freshness updates, and cannibalization detection

Storybook CSF3 story authoring methodology for UI component catalogs.Prioritizes visual showcase patterns over exhaustive argTypes enumeration.Reference for creating scannable, maintainable component documentation.