tmoody1973

Radio show preparation — generates station-voiced track context, talk breaks, social copy, and interview prep from a pasted setlist

Trace sample chains across records — identify original sources, who sampled whom, and production lineage

Comprehensive artist research — discography, influences, collaborations, market presence, biographical context

Geographic and temporal music scene analysis — map artists, labels, venues, and movements within a city or era

Vinyl record identification and market valuation — pressing details, matrix numbers, price comparison across markets

AI-powered music research with 92+ tools across 17 sources — MusicBrainz, Bandcamp, Discogs, Genius, Last.fm, Wikipedia, and more. Influence tracing, track verification, playlist building, and publishing.

Apply the Boy Scout Rule to existing code -- leave every file cleaner than you found it. Use this skill when the user is working in an existing codebase and asks to clean up code, improve existing files, apply the Boy Scout Rule, tidy up a module, or says things like "clean this up while you're in there," "this file needs some love," "improve this code," or "make this better." Performs incremental cleanup without changing behavior.

Comprehensive clean code review, refactoring, and code quality analysis skill. Use this skill whenever the user asks to review code, refactor code, improve code quality, audit code for best practices, find code smells, clean up messy code, apply clean code principles, enforce coding standards, or evaluate code readability. Also trigger when the user says things like "make this cleaner," "this code is a mess," "review my code," "refactor this," "code quality check," or "apply clean code patterns." This skill provides the full Clean Code Handbook reference with detailed examples and patterns for writing maintainable, scalable code.

Scaffold a clean project structure organized by concern. Use this skill when the user asks to set up a new project, organize a messy codebase, create a project structure, restructure files, or says things like "set up the project," "organize this code," "create a clean folder structure," or "scaffold this project." Guides users through creating a well-organized codebase following Clean Code Pattern 7 (Clean Project Structure).

This skill should be used when creating or configuring CI/CD pipeline files for automated testing, building, and deployment. Use this for generating GitHub Actions workflows, GitLab CI configs, CircleCI configs, or other CI/CD platform configurations. Ideal for setting up automated pipelines for Node.js/Next.js applications, including linting, testing, building, and deploying to platforms like Vercel, Netlify, or AWS.

Structured PR creation and CodeRabbit review workflow for Tarik's projects (Hakivo, Crate CLI, StoryForge, Extended Play, Radio Milwaukee tools). Use this skill when the user wants to open a pull request, create a feature branch, review PR status, respond to CodeRabbit comments, manage branch cleanup, or follow a professional git workflow. Trigger for any mention of PR, pull request, branch, CodeRabbit, code review, merging, or git workflow.

Pipeline for halftone paper-collage and stop-motion-graphic ads. Decodes a reference image into a field-editable JSON spec, generates cut-out elements directly on the Gemini image API (nano-banana line), then assembles them into build-from-empty stop motion with code: a bundled Python compositor by default, or OpenMontage's HyperFrames (HTML + GSAP) or Remotion runtimes. No paid video model needed; the assembly is deterministic. Trigger whenever the user pastes a reference to decode, replicate, or make "similar"; asks for a halftone, paper-cut, paper-collage, editorial-collage, or stop-motion-graphic look; wants a still or product turned into an animated ad or motion graphic; or says "analyze this", "break this down", "animate this", "make a collage ad", or "assemble it in". Also trigger for guided creation: "director mode", "guide me", "interview me", or a vague ask like "make me something cool for my brand". Use even when the user never says "collage" or "stop motion" but the visual is clearly this look.

Use when starting or building tracked work in Linear — e.g. "build RAD-42", "start the next Linear issue", "turn this into a Linear issue", or "create a Linear project for X / plan this milestone in Linear". Creates a project, fans it into spec'd issues (Intent / Acceptance / Verification) assigned to that project, builds each to its acceptance criteria, runs a verification gate against real data, and writes results back to the issue. Requires the Linear MCP server (linear-server).

Brainstorm, evaluate, and blueprint award-winning hackathon projects using a bumwad-coding (architecture-phase) methodology with mandatory data/API feasibility scouting. Use whenever the user mentions a hackathon, hackathon ideas, hackathon prep, sponsor tech challenges, demo day projects, prize categories, or wants to pressure-test a hackathon concept — even if they don't say "brainstorm." Pushes past generic ideas toward projects judges remember and that actually ship.