Documentation

Create or update a feature spec under `docs/Features/` using `docs/templates/Feature-Template.md`: business rules, user flows, system behaviour, Mermaid diagram(s), verification plan, and Definition of Done. Use before implementing a non-trivial feature or when behaviour changes; keep the spec executable (test flows + traceability to tests).

Framework for capturing documentation requirements, scoring priority, and assigning owners.

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

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

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 diagnosing crawl/index issues, performance regressions, or structured data gaps.

Create or update an ADR (Architecture Decision Record) under `docs/ADR/` using `docs/templates/ADR-Template.md`: context, decision, alternatives, consequences, rollout, and verification. Use when changing architecture, boundaries, dependencies, data model, or cross-cutting patterns; ensure it is self-contained, has a Mermaid diagram, and defines testable invariants.

Deep architectural analysis using Gemini's codebase_investigator tool. Trigger when user needs architecture overview ("analyze this codebase", "map dependencies"), onboarding to unfamiliar code, understanding legacy systems, or identifying technical debt.

Use when producing research-heavy whitepapers or technical guides that require structured argumentation and data.

Use when crafting scripts, storyboards, and messaging for video content.

Use for structured technical SEO audits, incident response, and validation.

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

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.

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.

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