Coding & Dev Tools

Use to distil a CX dashboard into the three numbers a board or exec actually needs — volume/demand health, quality/outcome, and cost/efficiency — with commentary that drives decisions instead of forty tiles nobody acts on. Trigger for "board pack", "exec summary for support", "what should leadership see", "too many metrics on the dashboard", "three KPIs for the board", quarterly business review CX section, or when a leadership deck is mostly charts with no story.

Use to recover a day in real time when volume, handle time or availability diverge from plan — reforecasting decisions, break moves, overtime, callbacks and skill flex without burning tomorrow. Trigger for "intraday management", "real-time reforecast", "we are underwater at 11am", move breaks or lunches, call people back in, flex agents between queues, ride out the spike, or when the WFM plan is wrong before close of business.

Use to export CSAT or satisfaction survey responses from a support platform into one canonical shape. Trigger for "export our CSAT data", "pull satisfaction ratings", "get survey responses out of Zendesk/Freshdesk/Gorgias/HubSpot", joining CSAT to tickets, or when a conversation export left the csat field null.

Use to analyse the help-centre funnel from search through article view to contact, find actionable drop-off, and align KB content to contact drivers. Trigger for "self-service funnel", "contact after viewing an article", "why doesn't the help centre deflect", KB deflection rate, search-to-contact conversion, or article effectiveness.

Use to monitor support conversations for conduct risk — pressure, mis-selling, unfair outcomes, obstruction and misleading statements — as distinct from whether the answer matched policy. Trigger for "monitor for mis-selling", "conduct risk in our support conversations", "are agents pressuring customers", "customers being obstructed from cancelling", conduct surveillance, or a conduct finding raised by second line.

Use to compare BPO sites, vendors or partner teams fairly, adjusting for the work mix each is given before concluding anything about performance. Trigger for "compare our BPO sites", "which vendor is performing best", "site A scores lower than site B", outsourcer QBR packs, partner MI reporting, or setting contractual quality targets with a vendor.

Use to staff and schedule QA reviewers for sustainable throughput without grading quality collapsing — fatigue, drift, and false precision from treating reviewers like production agents. Trigger for "how many QA reviewers do we need", reviewer capacity planning, grader fatigue, throughput per reviewer, calibration after long shifts, or scores drifting over the course of a day.

Use to review how call recordings are notified, stored, accessed, redacted and deleted, including the parts that differ from text conversations. Trigger for "review our call recording practices", "do we need to tell customers we're recording", "who can listen to our calls", recording retention, card details spoken on a call, or a request for a customer's own recording.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

Spotify: play, search, queue, manage playlists and devices.

Author a Hermes color theme that skins every surface.

Skills system architecture — progressive disclosure, frontmatter, platform filtering, self-editing

Manage your Radarr (movies) and Sonarr (TV series) media library from the terminal. Search and browse movies/series, add new content, check calendars, view queue and download history, inspect quality profiles, and trigger searches. Use when the user mentions Radarr, Sonarr, the *arr stack, adding a movie or series, checking the library, finding something to watch, what's in the queue, download history, upcoming releases, media server setup, or movie/TV automation.

Forces investigation of file dependencies before editing code to prevent cascade failures.

EPUB file format expert — read, write, and edit EPUB2/EPUB3 ebooks. Extract text, metadata, structure, and knowledge from EPUB files for enrichment or memory. Create valid EPUBs from scratch. Validate against the EPUB specification. Use when the user mentions epub, ebook, EPUB file, ebook format, read epub, write epub, create ebook, extract from epub, epub to text, or ebook structure.

HeartMuLa: Suno-like song generation from lyrics + tags.

Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

Teach and guide GitHub workflows. Explains concepts, recommends approaches, and references specialist GitHub skills for execution.

Create or analyze settings, scenes, world operations, and image direction in the literary cyberpunk mode of William Gibson's Sprawl fiction: dense, accreted urban systems; uneven high technology; corporate power; mediated culture; and human-scale survival inside global networks. Use for Gibson-informed creative work, setting design, or visual briefs, not for generic neon cyberpunk, faithful continuation of named canon, or imitation of Gibson's prose.

Query, search, and download public datasets from the City of Raleigh Open Data portal. Use this whenever someone wants to explore city data — crime reports, food inspections, building permits, bike lanes, parks, zoning, traffic, budgets, or any of 200+ public datasets.

Keeps code readable. File size limits, function length caps, nesting depth rules. Written for non-coders who need to understand what the AI wrote.

Manage your Lidarr music library from the terminal. Search and browse artists and albums, add new artists, check calendars, view queue and download history, inspect quality and metadata profiles, and trigger searches. Use when the user mentions Lidarr, music management, adding an artist, searching for music, checking the music library, upcoming album releases, or download queue.

Generate project ideas via creative constraints.

Interact with Atlassian Jira from the terminal: search issues, view details, create issues, add comments, list projects, and transition status. Use when the user mentions Jira, a ticket key (e.g. PROJ-123), or asks about issues, bugs, tasks, projects, or sprint work.

Distinguish Hermes skills from regular GitHub repos and know how to install each correctly.

Write, review, and maintain architecture decision records with clear context, alternatives, consequences, and lifecycle governance. Use when a consequential technical decision must remain understandable.

Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "technical debt prevention", "prototype vs tracer bullet", or "code ownership". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.

Bootstrap Team-Wiki directory with SCHEMA.md, index.md, log.md, and folder READMEs

Query your Jellyfin media server from the terminal — recently added movies and episodes, search across your library, browse libraries, and check server info and stats. Use when the user asks about Jellyfin, media server, movies, TV shows, recently added content, or their media library.

Manage your Prowlarr indexer hub from the terminal. List and inspect indexers, view query/grab statistics, check health, manage connected *arr applications and download clients, browse search history, and test indexer connectivity. Use when the user mentions Prowlarr, indexers, indexer management, testing indexers, search history, or the indexer hub.

Design the small details -- triggers, rules, feedback, loops and modes -- that separate good products from great ones. Use when the user mentions "microinteraction", "button feedback", "loading state", "toggle design", "animation detail", "interaction polish", "state transitions", or "input feedback". Also trigger when designing form validation responses, progress indicators, confirmation dialogs, or any UI element where the user expects immediate feedback. Covers trigger design, state rules, feedback mechanisms, and progressive loops. For overall UI polish, see refactoring-ui. For affordance design, see design-everyday-things.

Team-Wiki Ingest

Systematic exploratory QA testing of web applications — find bugs, capture evidence, and generate structured reports

Yuanbao (元宝) groups: @mention users, query info/members.

Classify tasks by complexity and route heavy isolated coding work to Codex CLI with the correct current command syntax.

Author/validate/export Google's DESIGN.md token spec files.