Technical Writing
5624 skills in Documentation > Technical Writing
doc-writer
Generates and improves documentation
debug-phase
Standard Operating Procedure for /debug phase. Covers error investigation, root cause analysis, systematic debugging, and error documentation.
update-strategy-docs
Update Polymarket bot strategy documentation after code changes. Use after modifying gabagool.py, polymarket.py, or any strategy-related code to ensure STRATEGY_ARCHITECTURE.md and strategy-rules.md accurately reflect the implementation.
test-generator
WHEN: Test code generation, unit/integration/E2E test writing, component/hook/utility testsWHAT: Framework detection + Jest/Vitest/RTL/Playwright templates + Happy Path/Edge/Error case testsWHEN NOT: Coverage analysis → coverage-analyzer, Test quality review → code-reviewer
markitdown-skill
Guide for using Microsoft MarkItDown - a Python utility for converting files to Markdown. Use when converting PDF, Word, PowerPoint, Excel, images, audio, HTML, CSV, JSON, XML, ZIP, YouTube URLs, EPubs, Jupyter notebooks, RSS feeds, or Wikipedia pages to Markdown format. Also use for document processing pipelines, LLM preprocessing, or text extraction tasks.
julien-mcp-notion-internal
Install Notion Internal API MCP. Use when user needs advanced Notion features via internal API.
code-standards
Extract and maintain company-specific coding best practices from PR review comments. Use when the user requests to analyze PR comments from a repository to generate best practices documentation, or when implementing features and needs to reference established coding standards. Triggers include requests like "analyze PR comments and create best practices", "extract coding standards from repo X", or "check if this code follows our best practices".
heyreach-master
Internal resource library for HeyReach integration. Contains shared API client, operation scripts, and reference documentation.
databases
Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.
component-testing-mobile
Jest and React Native Testing Library patterns. Use when writing component tests.
specification
Use when writing or updating spec.md files. Defines requirement format, user story structure, and scenario patterns.
load-testing
Create and manage K6 load tests for REST and GraphQL APIs. Use when creating load tests, writing K6 scripts, testing API performance, debugging load test failures, or setting up performance monitoring. Covers REST endpoints, GraphQL operations, data generation, IRI handling, configuration patterns, and performance troubleshooting.
frontend-css
Write and maintain CSS using consistent methodology, design systems, framework utilities, and minimal custom styles for better performance and maintainability. Use this skill when writing or modifying CSS files, style modules, Tailwind classes, styled-components, CSS-in-JS, or any styling code for UI components. Use this when applying utility classes, maintaining design tokens for colors/spacing/typography, working with CSS frameworks like Tailwind or Bootstrap, avoiding framework style overrides, optimizing CSS for production with purging/tree-shaking, or implementing responsive styling. Use this when working on .css, .scss, .module.css files or when adding className/style attributes to components.
aldoa-e2e-tests
Comprehensive guide for writing Playwright E2E tests in the Aldoa codebase. Use when creating new test files, debugging failing tests, or refactoring existing tests. Covers authentication patterns, helper functions, Semantic UI/React Select interactions, data generation strategies, and common testing scenarios.
task-manager
Automated task lifecycle orchestrator for docs/tasks/ directory - identifies next ready tasks by priority, loads full context from markdown files, guides TDD implementation with Wallaby MCP, runs quality checks, and tracks completion. Use when user says "start next task", "what should I work on", "show ready tasks", or mentions specific task IDs like "start T0001".
technical-book-writer
Comprehensive guide for writing technical books in Markdown format. Use this skill when creating new chapters, managing code examples, reviewing content for technical accuracy and consistency, or organizing book structure (TOC, cross-references). Provides templates, validation scripts, and best practices for technical writing workflows.
bac-presentation-generator
Transforms markdown files into brand-compliant BAC HTML presentations with professional styling, proper typography, and integrated branding. Supports manual browser-based PDF export.
unity-screen-doc
Unity/ゲームクライアントの画面機能ドキュメントを作成。指定された画面のPresenter、ViewModel、UseCaseなどのコードを調査し、プランナー視点でのゲーム体験に焦点を当てた非技術ドキュメントをMarkdown形式で生成します。glow-clientプロジェクト、Unity画面、プランナー向けドキュメント、画面仕様書作成で使用。
code-quality-standards
Use when writing any code - enforces clean architecture with descriptive names, real implementations, no backward compatibility concerns, and no lint suppressions
share-skill
Push a local skill to the Notion skills database. Load when user mentions "share skill", "export skill", "push to notion", "add skill to database", or after creating a new skill with create-skill.