Skills

Turns a script, concept, or product idea into a shot-by-shot storyboard. Breaks the narrative into scenes and panels with framing, camera movement, action, and dialogue notes, and generates image-model prompts for each panel so teams can visualize a video, ad, or explainer before production.

Designs and implements real-time services using WebSockets and Server-Sent Events. Covers connection lifecycle, heartbeats, reconnection with backoff, room/channel fan-out, backpressure, authentication on upgrade, and horizontal scaling with a pub/sub backplane. Produces production patterns for chat, live dashboards, collaborative editing, and streaming updates.

Turns merged pull requests, commits, and issue references into clear, audience-appropriate release notes. Groups changes into features, fixes, and breaking changes, translates technical detail into user-facing value, and produces both a concise highlights section and a complete changelog.

Adds production-grade observability to a codebase by instrumenting it with structured logs, metrics, and distributed traces. Recommends span boundaries, cardinality-safe labels, and OpenTelemetry conventions, then generates the wiring code and dashboards needed to make a service debuggable in production.

Defines data contracts between producers and consumers to prevent breaking changes in pipelines. Covers schema definitions, semantic types, freshness and quality SLAs, ownership, versioning, and backward/forward compatibility rules. Generates contract specs (e.g., ODCS-style) and CI checks that fail builds when a producer violates the contract.

Modernizes legacy codebases incrementally and safely. Establishes characterization tests to lock in current behavior, then applies the strangler-fig pattern, dependency updates, and idiomatic refactors in small verifiable steps, producing a migration plan that avoids big-bang rewrites.

Designs chaos engineering experiments to validate system resilience. Defines steady-state hypotheses, blast-radius limits, fault injections (latency, errors, instance/zone loss, resource exhaustion), abort conditions, and observability checks. Produces a safe, incremental experiment plan and success criteria for game days and automated chaos.

Advises on how to evolve APIs without breaking clients. Compares versioning strategies (URI, header, media-type), classifies changes as breaking or non-breaking, and produces deprecation timelines, migration guides, and compatibility shims so teams can ship changes safely.

Models complex application logic as explicit finite state machines and statecharts. Identifies states, events, guards, and side effects; prevents impossible states; and generates implementations (e.g., XState-style) with diagrams. Ideal for wizards, checkout flows, connection lifecycles, and any feature where implicit boolean flags cause bugs.

Scans code, configuration, and git history for leaked credentials such as API keys, tokens, private keys, and connection strings. Classifies findings by severity and false-positive likelihood, and provides safe remediation steps including rotation, history scrubbing, and pre-commit prevention.

Writes reusable, well-structured Terraform modules with clean input/output interfaces, sensible defaults, validation rules, and examples. Covers module composition, variable typing and validation, remote state and backends, provider version pinning, and testing with terraform validate/plan and tools like Terratest. Emphasizes least-privilege IAM and safe defaults.

Develops a distinctive, consistent brand voice and tone system. Defines voice attributes, do/don't guidance, vocabulary and grammar rules, tone shifts by context (marketing, support, errors), and worked before/after examples. Produces a practical style guide teams and AI assistants can apply across every touchpoint.

Analyzes LLM usage and reduces inference cost without sacrificing quality. Covers prompt compression, context trimming, caching (prompt and semantic), model routing by task difficulty, batching, structured output to cut retries, and token accounting. Produces a concrete plan with estimated savings and quality guardrails.

Helps design and implement features for machine learning models from raw tabular, time-series, or text data. Suggests transformations, encodings, aggregations, and leakage-safe splits, explains the rationale, and generates reproducible feature pipeline code with validation.

Designs evaluation harnesses for LLM applications, covering dataset construction, task-specific metrics, LLM-as-judge rubrics with bias controls, and regression gates. Helps teams measure quality, catch regressions across model or prompt changes, and report results with confidence intervals rather than vibes.

Turns reliability goals into concrete SLIs, SLOs, and error budgets. Helps choose the right service level indicators, set realistic targets from historical data, compute burn rates, and design multi-window multi-burn-rate alerting so teams get paged before the budget is exhausted.