Documentation

Track, prioritize, and pay down technical debt systematically in ANY project. Use when quantifying debt, prioritizing fixes, or convincing management to invest in improvements.

This skill should be used when the user asks about "snapshot.md", "constraints.md", "decisions.md", "debt.md", ".ctx/", "living context", "documentation freshness", "stale docs", "ADR", "architecture decision", "technical debt", "system context", "co-located documentation", "context health", "validation", or needs help managing co-located documentation that stays synchronized with code.

Production-grade Go CLI patterns, automated release workflows with Release Please, versioned docs, and coverage enforcement for DevSecOps build pipelines.

Generates clear commit messages from jj diffs. Use when writing commit messages or reviewing staged changes.

Execute Sprint 1 tasks for FASA optimization and trade analytics. This skill should be used when the user requests execution of any Sprint 1 task (Tasks 1.1-1.4, 11-13, 2.1-2.4, 3.1-3.2), including cap space parsing, Sleeper integration, FASA target marts, FA acquisition history, roster depth analysis, enhanced FASA targets, notebooks, valuation models, trade analysis, automation workflows, or documentation. Each task is atomic, standalone, and designed for independent execution with built-in validation. Current focus: Phase 2 FASA Intelligence (Tasks 11-13, 1.4).

Generate detailed technical design documents including architecture, APIs, database schemas, and implementation specifications

Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes.

Use when building a production-ready REST API from requirements through deployment.Orchestrates 8-12 specialist agents across 5 phases using Test-Driven Development methodology.Covers planning, architecture, TDD implementation, comprehensive testing, documentation, andblue-green deployment over a 2-week timeline with emphasis on quality and reliability.

Comprehensive checklist for releasing OSS projects. Covers security (CSP, PII, secrets), legal compliance (licenses, API terms, trademarks), privacy (GDPR, telemetry opt-out), and documentation. Use when preparing to open source a project, adding telemetry/error monitoring, auditing dependencies, or creating privacy policies.

Use when the user asks to "refactor shell script", "fix bash style", "apply Google style guide to shell", "review shell script style", "format bash script", or when writing, reviewing, or refactoring shell/bash scripts. Provides Google Shell Style Guide rules for formatting, quoting, naming, control flow, and common anti-patterns.

Use when generating PDFs from markdown with Pandoc - covers differences from Python-Markdown, blank line rules, fix scripts for labels/anchors/metadata, and visual testing workflow

Swift code style conventions for clean, readable code. Use when writing Swift code to ensure consistent formatting, naming, organization, and idiomatic patterns.

Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.

Use to validate process documentation. Apply TDD to skill writing: RED (run without skill, document failures) → GREEN (write skill) → REFACTOR (close loopholes). Test under pressure: time constraints, sunk cost, exhaustion, authority.

Generate professional slide decks and presentations using Formula Botanica brand guidelines - green botanical theme with Roboto Light/Thin fonts, leaf logo motifs, and clean layouts for finance processes, team presentations, and internal documentation.

This skill should be used when the user asks to "update spec", "update plan", "create derive artifacts", "check progress", "session continuity", "derive documents", or needs guidance on managing the persistent documentation artifacts used by the DERIVE workflow. Provides templates and guidance for each artifact type.

Design phase with validation gates. Annotates PRD, creates story outlines, builds execution plan (via execution-plan-creation skill), validates artifacts via reviewer. NO HITL in this phase - single HITL happens after all docs complete.

Write consistent, maintainable CSS following the project's methodology (Tailwind utility classes) while minimizing custom CSS and adhering to design system tokens. Use this skill when writing or editing CSS files, Tailwind classes in React components (.tsx, .jsx files), when implementing design system colors/spacing/typography, when using Tailwind utility classes, when deciding between framework utilities vs. custom CSS, when optimizing CSS for production with tree-shaking, when configuring Tailwind theme extensions, or when maintaining design consistency across the application.

Token-efficient library API documentation fetcher using Context7 MCP with 77% token savings.Fetches code examples, API references, and usage patterns for published libraries (React,Next.js, Prisma, etc). Use when users ask "how do I use X library", need code examples,want API syntax, or are learning a framework's official API. Triggers: "Show me React hooks","Prisma query syntax", "Next.js routing API". NOT for exploring repo internals/source code(use researching-with-deepwiki) or local files.

Keep the backend REST API and the shared OpenAPI spec in sync. Use when adding/changing endpoints so the contract in the shared repo stays accurate.