技術寫作

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

Maintain and update architecture documentation in docs/architecture/. Uses tool-based inspection first, falling back to CLI only when needed.

Use when saving notes to Obsidian vault, creating documentation, capturing knowledge, or logging any information. This skill determines the correct PARA location and applies the appropriate template from the vault.

Maintain living documentation with single source of truth approach, journal reconciliation, and worklog.db integration

Use this skill when starting a new project or adding SynthesisFlow to an existing project. Scaffolds the directory structure (docs/specs, docs/changes) and configuration files needed for the spec-driven development workflow.

QA engineer and test automation specialist with deep expertise in Flutter testing. Use for designing test strategies, writing unit/widget/integration tests, improving test coverage, and ensuring code reliability.

Convierte archivos Markdown a DOCX con formato profesional usando pandoc. Incluye portada con título, tabla de contenidos, cabeceras y estilos corporativos. Usar cuando se necesite generar documentos Word desde Markdown, exportar documentación, o crear informes en formato .docx.

Эксперт по копирайтингу. Используй для написания продающих текстов, заголовков, landing pages и conversion copy.

Create, update, and review code-map and spec documents for features. Use this skill to document code execution flows, trace function calls, and maintain architectural documentation in docs/2-current/.

Find and add authoritative source links for all facts, citations, and references in markdown documents

Generates high-quality documentation for code, including inline comments, function docstrings, and README files. It ensures consistency in tone, format, and detail level.

This skill should be used proactively before writing any Scala code for the first time in a session. It ensures all Scala code adheres to project-specific coding standards, formatting rules, naming conventions, and architectural patterns defined in the comprehensive style guide. Trigger this skill when about to write Scala classes, traits, objects, or modify existing Scala files.

Orchestrator agent that coordinates all BarqNet specialized agents (backend, integration, client, documentation, audit, testing) to execute complete end-to-end workflows. Plans multi-agent deployments, manages task dependencies, tracks progress across all platforms, and ensures comprehensive completion. Use for complex multi-component tasks, full-stack features, or production deployments.