Technical Writing

Documentation pattern for translating brand platforms into modular experience systems.

Style and formatting rules for API/SDK documentation, samples, and tutorials.

Template for packaging financial products with pricing, underwriting, and compliance details.

Use when planning or drafting search-optimized content that balances keyword intent with GTM messaging.

Tone, diction, and phrasebook system for consistent writing + localization.

Designs integration and E2E tests with mock boundaries. Use when: writing E2E tests, integration tests, or reviewing test quality.

Turn the idea for a feature into a fully-formed PRD/design/specification and implementation-plan. Use when you have a spec or requirements that needs implementation. Use in pre-implementation (idea-to-design) stages to make sure you understand the spec/requirements and ensure you have a correct implementation plan before writing actual code.

Guides PRD, ADR, Design Doc, and Work Plan creation. Use when: planning features, writing specs, or creating technical documents.

After implementing a new feature or fixing a bug, make sure to document the changes. Use after finishing the implementation phase for a feature or a bug-fix

Applies coding standards for clean, maintainable code. Use when: writing functions, handling errors, refactoring, or reviewing code style.

Applies TDD process, test quality criteria, and mock guidelines. Use when: writing unit tests, using mocks, or reviewing test quality.

Python development best practices including PEP 8 style guidelines, type hints, docstring conventions, and common patterns. Use when writing or modifying Python code.

Guidelines describing how to test the code. Use whenever writing new or updating existing code, for example after implementing a new feature or fixing a bug.

Editing mode for clarity and semantic density; use for prompts, docs, specs, emails, and naming.

This skill should be used when creating comprehensive ontological documentation for software systems, including extracting domain concepts, modeling semantic relationships, and generating visual representations of system architectures and business domains.

Query and manage Oak AI squad tasks and sprints in Notion. Use when checking current sprint, finding tasks by status, updating task information, or understanding team priorities and workload.

Testing commands and patterns for Oak AI project including running Jest unit tests, E2E tests with Playwright, coverage reports, and filtering tests. Use when writing tests, running test suites, or debugging test failures.

Oak AI project TypeScript coding conventions including naming patterns (kebab-case files, PascalCase components, camelCase functions), component structure, error handling with cause, state management patterns, and tRPC implementation. Use when writing, reviewing, or refactoring code.

Document solved problems for knowledge persistence

Retrieval-augmented generation (RAG) skill for the D&D 5e System Reference Document (SRD). Use when answering questions about D&D 5e core rules, spells, combat, equipment, conditions, monsters, and other SRD content. This skill provides agentic search-based access to the SRD split into page-range markdown files.