mikersays

by mikersays

Spin up a swarm of expert subagents to build an interactive zero-to-hero course site on any topic — progressive modules, worked examples, exercises with solutions, checkpoints, a capstone, and progress tracking — shipped to docs/ and deployed on GitHub Pages

by mikersays

Generate a self-contained HTML slide deck from a topic — single file, dark theme, keyboard nav

by mikersays

Generate an interactive SVG diagram (architecture, sequence, flowchart, ER) from a description

by mikersays

Build or publish a static site on GitHub Pages — saves the site to docs/ and enables Pages from the docs/ folder on the default branch

by mikersays

Audit session context and persist what matters for the next agent — decisions, dead ends, insights, and in-flight work

by mikersays

Per-issue bug/feature/incident tracker that lives in docs/issues/ — one file per ticket with symptom, repro, root cause, fix, and verification. Includes a branch-on-start workflow and a hard rule to align with the user before implementing.

by mikersays

Maintenance skills for the mikersays-plugins marketplace

by mikersays

Build a multi-page PhD-level GitHub Pages site on any topic — research, free-licensed photography, a distinctive topic-tuned design, and shipped via parallel expert subagents

by mikersays

Author, index, and validate Open Knowledge Format (OKF v0.2) bundles — markdown concepts with YAML frontmatter for provenance, trust, lifecycle, and attested computations — so humans and agents share one vendor-neutral knowledge corpus

by mikersays

Lightweight markdown-based tracker for bugs, features, chores, and todos that lives in docs/plan/ inside your repo

by mikersays

Create a GitHub PR for the current branch with auto-generated title, summary, and test plan

by mikersays

Generate a self-contained interactive HTML Gantt chart from a markdown roadmap file

by mikersays

Stage, commit, and push all changes in one step, with auto-generated message if none given

by mikersays

Rewrite any text to maximally overuse every known AI-writing tell — em-dashes, rule of three, "not X but Y", and more — /slop

by mikersays

Review and rewrite documentation in place using either Google's Technical Writing guidelines or strict Simplified Technical English (ASD-STE100), chosen per document