Skills

Sets up and maintains Git hooks for a repository. Recommends a manager (Husky, Lefthook, or pre-commit), wires up pre-commit and commit-msg hooks for linting, formatting, type checks, secret scanning, and conventional-commit validation, and keeps hooks fast with staged-file filtering. Produces config plus a short contributor guide.

Creates accessible color palettes for brands and UIs from a brief or a seed color. Produces primary, secondary, and neutral scales with hex values, suggests semantic tokens (success, warning, error, info), and checks foreground/background pairings against WCAG contrast ratios. Outputs ready-to-use CSS variables or design tokens.

Turns a messy list of tasks into a ranked, actionable plan. Applies a chosen framework (Eisenhower urgent/important, RICE, MoSCoW, or value/effort) consistently, surfaces dependencies and quick wins, groups work into a realistic today/this-week plan, and explains the ranking so the user can adjust the weighting.

Explains what a SQL query does in plain language and how it executes. Breaks down joins, subqueries, CTEs, and window functions step by step, describes the result set, reads EXPLAIN/EXPLAIN ANALYZE output to identify slow scans and missing indexes, and flags correctness pitfalls. Helps developers understand, review, and trust unfamiliar SQL.

Helps process a busy inbox quickly. Categorizes messages by urgency and type, extracts action items and deadlines, drafts short reply options, and proposes an order to handle them. Summarizes long threads into the decision needed and flags anything sensitive or requiring escalation, so you can clear the inbox with fewer decisions.

Decodes and reviews JSON Web Tokens and their surrounding auth flow for correctness and security. Explains header and claims, checks algorithm and key handling, validates expiration and audience/issuer claims, and flags common pitfalls such as the alg:none attack, weak secrets, missing validation, and over-long token lifetimes. Never treats token contents as trusted secrets to echo back.

Produces operational runbooks for services and common incidents. Documents prerequisites, step-by-step diagnosis and remediation, exact commands, verification checks, rollback steps, and escalation paths. Structures each runbook so an on-call engineer can follow it under pressure, and keeps destructive steps clearly flagged with safeguards.

Generates and refactors dbt models for analytics engineering. Writes staging, intermediate, and mart models following layered conventions, adds schema.yml tests and descriptions, applies incremental and materialization strategies, and structures sources and refs correctly. Produces SQL plus YAML that fits dbt best practices and is ready to run.

Builds discovery and usability interview guides that surface real insight. Translates research questions into open, non-leading prompts, sequences warm-up to deep-dive topics, adds follow-up probes, and applies techniques like the "five whys" and past-behavior questions. Outputs a timed guide with a consent intro and a synthesis template for notes.

Helps make and document structured decisions. Elicits the options and the criteria that matter, assigns weights, scores each option, computes a weighted result, and runs a quick sensitivity check to show how robust the recommendation is. Produces a clear matrix plus a short written rationale suitable for an ADR or decision log.

Reviews applications and data flows for common privacy-regulation obligations (GDPR, CCPA/CPRA). Maps what personal data is collected, where it flows, and how long it is retained; checks for lawful basis, consent handling, data-subject rights, and third-party sharing; and produces a prioritized remediation list. Provides engineering guidance, not legal advice.

Inspects messy tabular data and produces a repeatable cleaning plan plus code. Detects and fixes common issues: inconsistent types, duplicate rows, missing values, malformed dates, mixed encodings, whitespace and casing problems, and outliers. Outputs pandas or Polars code, a summary of changes, and a validation checklist.

Builds structured competitive analyses from public information. Maps competitors across positioning, pricing, features, target segments, and go-to-market motion; produces feature-comparison matrices and SWOT summaries; and highlights differentiation gaps and opportunities. Emphasizes citing sources and separating verified facts from inference.

Drafts long-form blog posts from a topic, outline, or set of notes. Handles title and hook generation, logical section structure, SEO-aware headings, tone matching, internal linking suggestions, and a clear call to action. Produces publish-ready Markdown with meta description and suggested tags.

Generates candidate names for products, features, projects, or companies against a clear brief. Explores naming styles (descriptive, evocative, coined, compound), checks each for pronounceability and unwanted meanings, and suggests domain and handle patterns to verify. Returns a shortlist with rationale rather than an undifferentiated list.

Translates requirements and user stories into behavior-driven development scenarios in Gherkin. Writes clear Given/When/Then steps, covers happy paths, edge cases, and negative cases, uses scenario outlines with examples for data-driven tests, and keeps steps declarative and reusable. Optionally scaffolds step definitions for Cucumber or Behave.

Designs caching strategies across the stack to cut latency and load. Chooses cache layers (browser, CDN, application, database), picks patterns (cache-aside, read-through, write-through, write-behind), sets TTLs and eviction policies, and plans invalidation to avoid staleness and stampedes. Produces a layered plan with keys, TTLs, and invalidation rules.

Plans authorized penetration tests for systems you own or are permitted to assess. Defines scope, rules of engagement, and objectives; maps the attack surface; structures phases (recon, mapping, exploitation, post-exploitation, reporting) around a framework like the OWASP Testing Guide or PTES; and specifies safe handling of findings. Emphasizes explicit authorization and non-destructive testing.

Designs surveys that produce reliable, unbiased data. Turns research goals into clear questions, chooses appropriate scales and response types, avoids leading and double-barreled wording, orders questions to reduce bias, and plans screening and branching logic. Outputs a ready-to-field questionnaire with an analysis plan for each question.

Designs and implements rate limiting for APIs and services. Recommends an algorithm (token bucket, leaky bucket, fixed or sliding window) for the use case, defines per-key and per-endpoint limits, plans distributed enforcement with Redis, and specifies response headers and 429 handling with retry-after. Produces a design plus reference implementation.

Builds disaster recovery and business continuity plans for systems and data. Defines RTO and RPO targets, maps critical dependencies, chooses backup and replication strategies, documents failover and restore procedures, and designs a testing cadence with game days. Produces a plan that balances resilience against cost and operational complexity.