mvdmakesthings
- 13 skills
- 0 followers
- 1 week ago last updated
- ▌ Human Voice Writer · mvdmakesthings bundleWrite prose that sounds authentically human rather than AI-generated. Use this skill whenever writing long-form content, emails, articles, reports, documentation, blog posts, creative writing, social media copy, proposals, memos, or any text where sounding like a real person matters. Triggers on requests like "write this naturally," "make it sound human," "don't sound like AI," "write like a real person," or any writing task where the user has indicated they want authentic, non-robotic prose. Also use when editing existing text to remove AI-sounding patterns.
- ▌ Storyteller Guidance · mvdmakesthings bundleHelp the user craft presentations, pitches, talks, demos, launch announcements, all-hands updates, sales decks, fundraising pitches, conference talks, memos, narratives, blog posts, founder updates, internal announcements, layoff communications, post-mortems, kickoffs, town halls, and any other communication intended to persuade, inspire, inform, or move an audience. Use this skill whenever the user is preparing to present, pitch, announce, launch, kick off, give a talk, write a memo, share news, or otherwise tell a story to other humans — even when they don't use the word "story." It walks a structured diagnostic and applies tactics from a 54-card storytelling system (Concept, Explore, Character, Function, Structure, Style, Organise) plus seven recipes that combine tactics for common goals.
- ▌ Skill Reflect · mvdmakesthings bundleCapture a friction log immediately after finishing a skill session — what was improvised, what the user corrected, what edge cases the skill missed, and what changes would help. Writes a structured session log to ~/.claude/skill-sessions/<plugin>/sessions/<skill-name>/ so it can be read by the evolver from the skills repo later. Works in any project, not just the skills repo. Use whenever you've just finished running a skill and want to capture what happened while the session is fresh. Triggers on "/skill-reflect", "reflect on this session", "log this session", "write a session log", "capture skill friction", or any phrase asking to record what happened during a skill run.
- ▌ Plan Design · mvdmakesthings bundleDesign planning entry point — reads DESIGN.md, CONTEXT.md, and ADRs plus a Linear issue, identifies all UI surfaces that need design, lets you choose which to work through, then for each surface conducts an alignment interview, generates three layout-archetype mockups via OpenAI image generation, lets you pick one, produces an HTML/CSS implementation, and attaches it to the Linear issue. Use when starting design work on any feature, when you need visual options before committing to layout, or any time you want a Linear ticket to carry its own design artifacts.
- ▌ Grill With Docs · mvdmakesthings bundleGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
- ▌ To Prd · mvdmakesthingsTurn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
- ▌ Plan QA · mvdmakesthingsTest-planning entry point — reads a Linear issue and its acceptance criteria (plus the repo's test conventions if available), then drafts a comprehensive, layer-aware test plan — per-AC scenarios (happy path, edge, negative) each tagged with a test layer and an expected result, the auth roles / fixtures / data setup needed, the visual states to verify, and the regression watch areas. Shows you the draft for approval, then attaches it to the ticket as <issue-id>-test-plan.md so the qa skill can execute against it later. Use this skill whenever you are refining or grooming a ticket, planning QA before implementation, or whenever someone says "/plan-qa", "plan the QA", "write a test plan", "what should we test for this ticket", "QA plan", "test strategy for this issue", or "how do we verify this" — even if they don't say the words "plan-qa".
- ▌ To Issues · mvdmakesthingsBreak a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
- ▌ Skill Improve · mvdmakesthings bundleRead accumulated session logs for a skill, synthesize numbered improvement proposals with rationale and session evidence, collect conversational HITL approval, apply accepted changes to the SKILL.md, bump the patch version, and write a changelog entry. Use when you have enough session logs and are ready to improve a skill. Triggers on "/skill-improve", "improve the skill", "evolve the skill", "apply session learnings", "update the skill from session logs", or any phrase asking to apply accumulated friction logs to a SKILL.md.
- ▌ Track · mvdmakesthingsConsole-native billable hours tracker. Routes /track:start, /track:stop, /track:pause, /track:resume, /track:status, /track:report to a bash dispatcher that maintains a git-versioned JSONL ledger under ~/.time-tracker/. Use whenever the user invokes one of those slash commands. The skill itself does no time arithmetic, file I/O, or git work — the dispatcher does all of that. The skill's job is to construct the correct Bash invocation — for /track:start, /track:stop, /track:pause, and /track:resume, split optional --at/--ago flags from the positional client name (start). For /track:stop the user's note must be piped through stdin rather than passed as an argument (so shell metacharacters in the note cannot be interpreted). /track:pause and /track:resume take no positional args.
- ▌ Pir · mvdmakesthingsGenerate a post-incident report (PIR) from the current session and write it to docs/pir/. Use this skill whenever the user types "/pir", "write a PIR", "write up what happened", "document this incident", "post-incident report", "post-mortem", or "incident retrospective". Use it proactively whenever a debugging session, production outage, failed deployment, data migration incident, or any problem-solving session is winding down — even if the user doesn't explicitly say "PIR". The output is a structured markdown document capturing the timeline, root cause, impact, resolution, and lessons learned.
- ▌ Dba · mvdmakesthings bundlePostgres-first DBA workflows — run a full database health audit, design and implement schema (tables, constraints, RLS, indexes, migrations + tests), clean up unused indexes / bloat / dead tuples, diagnose and fix slow queries, and investigate live database incidents (high CPU, lock storms, error spikes, connection exhaustion). Use whenever the user says "audit the database", "DB health check", "design a schema", "model this table", "add a table for X", "clean up indexes", "database bloat", "why is this query slow", "optimize this query", "explain analyze this", "investigate the database", "the DB is on fire", "high CPU on Postgres", "connection pool exhausted", or types "/dba" — even when they don't say the word "DBA" or name a specific workflow. Discovers each project's migration, test, and deploy conventions at runtime rather than assuming them.
- ▌ QA · mvdmakesthings bundleSoftware QA skill — validates that current code changes satisfy the linked Linear issue. Fetches the issue, reads acceptance criteria, executes the ticket's attached test plan when one exists (produced by /plan-qa), runs every test layer it finds, and uses Playwright to visually verify the UI against any design attachments on the ticket. Use whenever the user wants to QA a feature, verify a fix, check that code matches a ticket's acceptance criteria, run a pre-merge review, or confirm the UI looks right against a design. Trigger on — "/qa", "run QA", "QA this", "verify the feature", "does this match the ticket", "check AC", "acceptance criteria check", "visual QA", "playwright verify", "does this pass QA".