Technical Writing

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

Use when the user has a document (PDF, markdown, book notes, research paper, methodology guide) containing theoretical knowledge or frameworks and wants to convert it into an actionable, reusable skill. Invoke when the user mentions "create a skill from this document", "turn this into a skill", "extract a skill from this file", or when analyzing documents with methodologies, frameworks, processes, or systematic approaches that could be made actionable for future use.

Regel 07: Testing. Use when writing tests, reviewing test coverage, or setting up testing.

Prefer modern CLI tools for better performance: rg (ripgrep) instead of grep for text searching, fd instead of find for file discovery, bat instead of cat for viewing files, sd instead of sed for text replacement, eza instead of ls for directory listing, dust instead of du, procs instead of ps. Use when writing bash scripts, optimizing command chains, working with file searches, or replacing grep/find/cat in workflows. These tools are faster, respect .gitignore, and have better output formatting.

MANDATORY - INVOKE BEFORE writing ANY test code (def test_*, class Test*). Prevents brittle tests. Read this skill first, then write tests.

Generate Architecture Decision Records (ADRs) to document significant architectural decisions. Use when making important technical decisions that need documentation.

React Testing Strategy. Use when writing tests, reviewing test coverage, or setting up testing.

Sync architecture documentation with main branch changes. This skill should be used when the user wants to update docs/guide/architecture.md to reflect changes made on the main branch. It compares origin/docs/arch against local main, analyzes new commits, and updates the architecture document.

Library documentation via Context7. Use for API references, code examples, framework docs.

PM framework for writing product specs from insights. Use when translating analysis into actionable feature requirements.

Write integration and unit tests for this codebase. Generate test files following repo patterns. Use when adding tests, improving coverage, writing test cases, or creating test suites.

Vercel Platform and API Documentation

Convert markdown documents to professional, retro LaTeX-style PDFs with academic formatting, clickable TOC, and proper citations.

. Use when writing tests, reviewing test coverage, or setting up testing.

Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps. Invoke when user mentions abstraction levels, making concepts concrete, or explaining at different depths.

Comprehensive PR review that synthesizes security, performance, correctness, style, and documentation findings with actionable fixes.

Create weekly software meeting agenda in the wiki repo.

Documentation lifecycle skill for API, code, and system guides with continuous validation.

Estrategia de Testes React. Use when writing tests, reviewing test coverage, or setting up testing.

Estrategia de Testing React. Use when writing tests, reviewing test coverage, or setting up testing.