Technical Writing

Writing controller handler functions

BANKSY spatial transcriptomics analysis tool - complete documentation with precise file name-based categorization

Expert knowledge for UX Layer modeling in Documentation Robotics

Automatically check documentation-code consistency after implementation. Verifies README.md and docs/*.md match actual code.

Design and build reusable, composable UI components following the single responsibility principle with clear prop interfaces and proper state management. Use this skill when creating or modifying React components, Vue components, Svelte components, web components, or any modular UI building blocks. Use this skill when implementing component composition patterns, defining component props and interfaces, managing local component state, or creating component documentation. Use this skill when working with component files in components/, widgets/, views/, or pages/ directories. Use this skill when refactoring large components into smaller composable pieces, establishing component naming conventions, or designing component APIs for reusability across different contexts.

Use when creating or updating tickets. Covers ticket writing best practices, what to include, and what to avoid.

Use when encountering errors, investigating library APIs, troubleshooting issues, or needing up-to-date documentation. Prioritizes Context7 and WebSearch over outdated training data.

Perform comprehensive code audits on repositories or directories. Use when asked to audit code, review a codebase, analyze code quality, find bugs, check for security issues, review architecture, check SOLID/DRY compliance, or generate a code audit report. Produces well-formatted markdown reports with prioritized recommendations.

Type-safe database access with Prisma ORM for Node.js and TypeScript. Use when designing schemas, writing queries, running migrations, or optimizing database operations. Triggers on Prisma, database, ORM, migration, or SQL questions.

This skill should be used when the user requests learning materials for algorithm or data structure patterns (e.g., "Create learning material for sliding window pattern"). It automatically generates structured markdown documents in the _learning/ folder and updates the main README.md with links to the new materials.

This skill should be used when the user asks to "write a spec", "create a specification", "define acceptance criteria", "break down a feature", "write user stories", or needs guidance on structuring feature requirements. Provides patterns for effective spec writing and task decomposition.

Process and analyze PDF documents including text extraction, table extraction, chart analysis, and visual content understanding. Use when working with PDFs, extracting structured data, generating summaries, or converting PDFs to other formats (markdown, JSON, CSV).

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).

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.