dm1681
- 6 skills
- 0 followers
- 19 hours ago last updated
- ▌ Ponytail · dm1681 bundleForces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
- ▌ Wow Addon Dev · dm1681 bundleBuild, debug, package, and publish World of Warcraft retail addons - TOC manifests, the event and widget model, SavedVariables, taint and secure templates, the Midnight-era "secret value" restrictions on combat data, Ace3 and the library ecosystem, and BigWigs-packager CI. Use when writing or reviewing Lua for a WoW addon, editing a .toc file, working under Interface/AddOns, debugging taint or "action blocked" errors, judging whether an addon idea is still possible on modern retail, or publishing to CurseForge, Wago, or WoWInterface.
- ▌ Viz Driven Dev · dm1681Hypothesis-first visualization workflow for feature development - build the plot, overlay, rendered artifact, or video that would show the feature's effect before implementing it, then regenerate the same artifact from real output to confirm or refute the hypothesis. Use when building or changing a feature whose effect can be seen or watched - signals over time, overlays on media, spatial or sequential behavior, state evolution, or any before/after comparison.
- ▌ Semantic Pr Review · dm1681 bundlePull and explain a GitHub pull request as a source-referenced hierarchy and interactive semantic flowchart with complete execution branches, DTO-labeled handoffs, source-excerpt hover cards, and code-linked details. Use when a user wants to understand a PR, trace its architectural layers, compare execution strategies, inspect boundary or ownership shifts, or receive a standalone interactive walkthrough instead of a flat diff summary.
- ▌ Cloudflare Artifacts · dm1681 bundlePublish files or static browser artifacts to the user's Cloudflare artifact library and return verified public URLs and Markdown links. Use when sharing an artifact through Cloudflare, making a report or visualization accessible without a VPN, or attaching a hosted artifact link to a GitHub issue.
- ▌ Olympus Report Progress · dm1681 bundleReport an agent session's Repository Checkout and append a Session Update to the Olympus Project for the repository you are working in. Use when the user says "report progress to Olympus", "log this to Olympus", "append a session update", when finishing or pausing work in a repository that has an Olympus Project, or when a GitHub issue carries an `Olympus-Task:` marker and the session must leave a record of what happened.