tmoody1973
- 7 skills
- 0 followers
- 8 hours ago last updated
- ▌ Paper Film · tmoody1973 bundleTurn a short story into a handmade paper-cut stop-motion film with narration, music, and burned-in captions. Five-question interview, then beat-by-beat Higgsfield MiniMax H3 clips chained by last frame, ElevenLabs narration, a Seed Audio music bed, stitched with ffmpeg. Use when the user says make a paper-cut film, stop-motion story, paper theater video, or animate this story as paper cutouts. Shows cost and waits for yes before spending anything.
- ▌ Boy Scout Cleanup · tmoody1973Make 3 to 5 small, local, behavior-preserving improvements to existing code. Use when the user asks to tidy a file, clean up code while working nearby, remove local clutter, or make a module easier to read. Do not use for a read-only review, public API changes, file moves, broad rewrites, or feature work.
- ▌ Clean Code Review · tmoody1973 bundlePerform a read-only, evidence-based code quality review focused on correctness, clarity, maintainability, tests, security, and framework conventions. Use when the user asks to review code, audit code quality, find code smells, assess maintainability, or asks whether code is ready for another developer. Do not edit files; use boy-scout-cleanup for small safe edits or /refactor for structural changes.
- ▌ Developer Handoff · tmoody1973 bundleCreate or update a concise developer handoff for an existing product by documenting setup, architecture, user flows, data, integrations, environment variables, testing, deployment, decisions, known issues, and next steps. Use when a vibe coder wants to give a project to a developer, onboard an engineer, prepare technical due diligence, or make a repository easier for someone else to understand.
- ▌ Clean Code Scaffold · tmoody1973Create or propose a project structure that follows the detected language and framework conventions. Use when the user asks to start a project, scaffold an application, organize a new feature, or restructure a messy repository. Inspect the stack before proposing directories and get confirmation before moving existing files.
- ▌ Prod Readiness Coach · tmoody1973 bundleScans repository controls and scripts, not user journeys: access control on request handlers, CI/CD pipeline, structured logging, error tracking, secrets management, CLAUDE.md/AGENTS.md, resilience and runbooks, multi-surface deployment and coordinated rollback risk, irreversible migrations, test coverage, and dependency security. Runs a deterministic script, then produces two plain-English documents: a beginner-friendly audit explainer and a phase-gated Claude Code fix brief. Detects the repo's stack (frameworks, deploy platforms, runtimes) and loads matching stack-specific reference material so advice reflects real platform gotchas instead of generic checklist language. Repository-level checks run on any language; stack-specific checks are strongest on Node and Next.js, good on Python, and report what they could not check elsewhere. Use when a user asks to audit, check, or review a repo for production readiness, best practices, or launch-blockers, or asks to turn code-quality/DevOps findings into something
- ▌ Product Readiness Review · tmoody1973 bundleJudges user journeys and product behavior, not repository controls: whether a real person can finish the core flows, what happens when they do the wrong thing, and whether the product is ready for users, production, technical due diligence, or developer handoff. A read-only, evidence-based assessment that reads code and docs and reasons about the product as a working system. Use when the user asks whether a product is production-ready, wants a product audit, wants to improve more than code style, or asks what must be fixed before launch or handoff. For broad production-readiness requests, run prod-readiness-coach first for the repository-controls scan, then this review for product judgment.