Technical Writing

Manage offline reference material in the `extra/` directory. Use when needing external documentation, library source code, screenshots, PDFs, or API specs. ALWAYS check `extra/` before web searches. HALT and ask the human when required material is missing - do NOT fall back to WebFetch/WebSearch.

Generate conventional commit messages from staged changes by inspecting diffs, picking the correct type/scope, and writing the final text to the prompt-specified file.

Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.

Comprehensive research workflow for feature implementation planning. Use this skill when gathering information about how to implement features, understanding technology choices, researching APIs and libraries, or exploring implementation approaches. Combines web search for general research with Context7 for API documentation, and includes structured questioning to clarify requirements.

Specialist in Rekordbox MIDI Learn integration, including MIDI mapping workflow, CSV file format, Rekordbox function reference, official documentation, and real-world DDJ controller examples. Use when working on Rekordbox MIDI controllers, CSV generation/import/export, function mapping, or debugging Rekordbox MIDI integration.

Automatically convert arXiv papers to well-structured Markdown documentation. Invoke with an arXiv ID to fetch materials (LaTeX source or PDF), convert to Markdown, and generate implementation-ready reference documentation with preserved mathematics and section structure.

Telegram automation assistant using telegram-mcp. Use when users want to:(1) Get a digest of unread Telegram messages(2) Analyze their writing style from channel posts(3) Draft and publish posts to Telegram channels(4) Search and reply to messages across chatsTriggers: "telegram digest", "unread messages", "morning summary","post to channel", "draft telegram post", "analyze writing style","extract style from channel", "telegram workflow"

API documentation, tutorials, guide writing, and developer content strategy.

Use the local Context7 CLI in this repo to search libraries and fetch Context7 context for skills or documentation tasks. Trigger when you need to run `c7 search`/`c7 context`, resolve library IDs, or retrieve text/json outputs from Context7 via the CLI.

Automatically logs every user prompt and AI output to datewise Notion pages. Use this skill to create a comprehensive archive of all AI interactions, track research progress, maintain conversation history, and build a searchable knowledge base. The skill creates one JSON file per day with all interactions and can export them to Notion in a structured format.

Project documentation with MkDocs Material - consistent structure, API auto-generation, GitHub Pages deployment

Updates existing README.md files after code changes. Use for requests to update, check, fix, or add to an existing README. Trigger phrases include "update readme", "check readme", "is the readme current", "add to readme", "fix readme", "readme out of date". Also use after adding dependencies, environment variables, or configuration. For creating new READMEs from scratch, use writing-documentation instead.

Guide for authoring output-styles that transform Claude's behavior and personality. Use when creating, writing, designing, building, reviewing, or improving output-styles, persona modes, or behavior modifications. Helps with style files, keep-coding-instructions decisions, persona design, and choosing between output-styles, agents, and skills. Expert in style best practices.

Coordination documentation synchronization patterns. Covers .coord/ structure management, worktree-based doc PRs, PROJECT-CONTEXT/APP-CONTEXT updates, and documentation placement rules. Use for HO delegation to system-steward for doc updates.

E2E testing skill for Pawel Lipowczan portfolio project (Playwright + React/Vite). Use when user wants to create new E2E tests, debug flaky tests, extend test coverage, verify test completeness for features, or run/interpret test results. Covers navigation, forms, blog, SEO, accessibility (WCAG 2.1 AA), responsiveness. References docs/portfolio/testing/{README.md,TESTING_QUICKSTART.md}. Complements portfolio-code-review skill.

Use repo lab experiments (src/ui/lab) to answer jsgui3 “how should we do this?” questions, then distill the validated result into durable docs + Skills.

Knowledge base for session continuity. Maintains project documentationwith fixed directory structure (.pmc/docs/) and formats for PRDs, SOPs,tickets (T0000N), patterns, decisions, code maps, research, and status.CRITICAL BEHAVIORS:1. LOOKUP FIRST - Before any task, check kb for existing docs (SOPs, patterns, code maps, status) that may guide the work. Don't reinvent what's documented.2. LEARN = DOCUMENT - When user says "learn X", record it in appropriate doc: - Procedure? → 2-sop/ - Problem/solution? → 6-patterns/ (with Status: open|resolved) - Code flow? → 7-code-maps/ - Research/notes? → 8-research/ - Design decision? → 5-decisions/D###-{name}.md - User clarification? → capture in ticket 5-final.md3. CAPTURE INTENT - When user clarifies requirements or expresses preferences, record in ticket's 5-final.md (Revealed Intent section).4. INBOX - Direct user messages → 0-inbox/ for later processing by /pmc:dev or /pmc:plan.Use when: setting up docs structure, creating/managing t

Generates component API documentation with props tables, usage examples, and guidelines. Use when documenting component libraries, creating API references, or building component documentation for designers and developers.

My personal best practices for writing clear and effective code comments.

Use when turning a documentation link or article into spaced-repetition flashcards - fetches and extracts core ideas, compares against existing cards/notes, right-sizes output by source density and existing coverage, updates only incorrect/outdated cards, and creates missing cards with strict citation, slug, and tag rules