owainlewis

Make one focused code change: understand the task, make the smallest complete change, test it, verify it, and report.

Review a code change for correctness, security, broken contracts, robustness, and real tests.

Fetch GitHub PR review feedback, judge each comment, implement valid fixes, verify, and optionally reply.

Write a lightweight technical design document for ambiguous or consequential architecture decisions before implementation.

Improve the shape of existing code without changing behavior.

Write an implementation spec to docs/<feature-slug>/spec.md and pause for human review. Use when the user says "write a spec", "spec this out", "technical design", "design doc", or when a task has decisions, invariants, or contracts that should be reviewed before code is written.

Verify browser-rendered work in a real browser. Use for HTML, UI, visual docs, presentations, local apps, and browser-facing changes.

Break a spec, brief, issue tracker item, or user request into a portable task list that can be reviewed, copied into an issue tracker, or delegated independently.

Create camera-readable Markdown teaching documents for courses, YouTube videos, workshops, and companion docs. Use when turning cards, rough notes, demos, or existing lessons into polished material Owain can read aloud and learners can study.

Write compact, reusable teaching cards that make one idea click. Use when turning rough expertise, lesson sections, YouTube ideas, demos, or course material into clear teachable units.

Format Markdown for iA Writer. Minimal, prose-first, almost no bold or italic.

Turn a vague, messy, or multi-part user ask into a clean, self-contained prompt that a fresh agent could execute without further questions. Interview the user one question at a time — walking down the decision tree, branching on each answer — until the prompt is tight, then output the final prompt as the deliverable. Trigger eagerly: any voice-dictated input, filler-heavy prose, underspecified references ("the thing", "that script"), multi-part requests, or any plan the user wants stress-tested. The skill itself can be skipped for trivial one-line requests where producing a prompt artifact would be pure ceremony — but once invoked, always produce the prompt, even if execution looks trivial.

Create a beautiful HTML explanation of a repo, spec, PR, architecture, or concept so a smart beginner can understand and retell it.

Rewrite text to remove AI tells. Use when editing or reviewing writing that sounds like a chatbot wrote it. Detects and replaces inflated significance, rule-of-three, em dash overuse, AI vocabulary, condescending openers, reader-lecturing, signposting, and other tells.

Write a short implementation plan or a longer execution plan before coding. Use when starting new work, when a ticket needs clearer boundaries, when a change spans multiple files or interfaces, or when a multi-hour task needs a living plan.

Review code changes for bugs, security issues, performance problems, and style violations. Use when asked to review code, a PR, or recent changes.

Research video ideas for a topic and add them to the Airtable content pipeline.