Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

bodish-coder

@bodish-coder source repo

20 published skills

  1. ▌
    Screenshot Loop · bodish-coder
    Use when the user says "screenshots", "check the screenshots", "I dropped new screenshots", "test screenshots", "look at the latest run", or gives a screenshot directory path — test screenshots dropped in a project's screenshot folder that need acting on and then clearing. NOT for taking screenshots (use a browser/app skill for that) and NOT for permanent design assets — everything in that folder is treated as disposable.
    0
    installs
  2. ▌
    Brainstorm Build Mid · bodish-coder
    Use when the user wants straight Opus quality for both the thinking and the code — an all-Opus plan then build, run autonomously with no stop in between, no Fable creative ideation, no Sonnet cost-tiering and no ceremony (no session record, no handoff checkpoint). For a Fable-led creative design plus the full ceremony use brainstorm-build-prime; to offload the simple / mechanical parts to Sonnet use brainstorm-build-lite. NOT for tiny one-line edits (just do them) or pure design/no-build work.
    0
    installs
  3. ▌
    Brainstorm Build Lite · bodish-coder
    The lightest "brainstorm then build". Use when the user wants a quick, cost-aware build that offloads the simpler or mechanical parts to a cheaper model and doesn't need Fable's creative brainstorm — "just design and build it, cheap where it can be". For a straight all-Opus plan→build (no Sonnet offload) use brainstorm-build-mid; for a Fable-led creative design plus the full ceremony use brainstorm-build-prime. NOT for tiny one-line edits (just do them) or pure design/no-build work.
    0
    installs
  4. ▌
    Brainstorm Build Prime · bodish-coder bundle
    Use when the user wants top-tier "brainstorm then build" — a deep-tier model doing creative design thinking, a build-tier model implementing, with full ceremony (design written to disk, handoff before checkpoints, session .md record, rework) so the work survives context loss. Runs on Claude Code, Cursor, Codex, Antigravity, Pi and Prime Agent. For all-Opus without ceremony use brainstorm-build-mid; for Sonnet offload use brainstorm-build-lite. NOT for tiny one-line edits or pure design/no-build work.
    0
    installs
  5. ▌
    Func UI · bodish-coder
    Use when an EXISTING UI-only / mockup / prototype frontend needs to become a real, working system — the user says their app is "just a UI", "only a mockup / shell", "not functional", "fake / hardcoded data", "no backend", "the buttons don't do anything / just clear", or asks to "make it real / functional", "wire it up", "connect the frontend to a backend / API / database", "make the buttons actually save", "turn this prototype into a working app". Ends at a confirmed plan; does not build. NOT for Figma-to-UI, design / UX / a11y review, visual or styling bugs, debugging a feature that already works, a brand-new app with no existing mockup, or backend-only fixes.
    0
    installs
  6. ▌
    Handoff · bodish-coder bundle
    Use when the user asks to "hand off", "write a handoff", "create a handoff doc", "document where we are", "prepare for the next session/person", or wants a continuity/checkpoint summary of the current session — an in-depth, verified session-handoff document (a Markdown file) so a different person or AI can continue the work with zero loss of context, plan, or intent.
    0
    installs
  7. ▌
    A11Y Proof · bodish-coder bundle
    Use when accessibility is the subject: an a11y or WCAG audit of existing code, a VPAT or compliance question, or a reported bug — "can't tab to it", "focus ring invisible", "screen reader reads nothing", "the toast never announces", "fails contrast", "no reduced-motion", "tap target too small", "the error is only red". Also for wiring axe, pa11y or Lighthouse into tests or CI. NOT for designing or building an interface — a11y inside a design task is design-arwen's ship gate.
    0
    installs
  8. ▌
    Live Build · bodish-coder
    Use when the user says "let me see it", "show me while you work", "don't make me wait", "live preview", "run it while you build", "stream the build", or whenever a change is about to be made to a project that has a runnable surface — JS/web dev server, Rust, C++, Python, Go, Electron, mobile or a plain CLI. Armed as standard by grayskull-power. NOT for taking screenshots (screenshot-loop) and NOT a substitute for tests — it is exposure, not verification.
    0
    installs
  9. ▌
    Merge Prep · bodish-coder
    Use when the user wants to "prep a branch for merge", "clean up a branch before merging", "make sure only the real changes get merged", "strip stale/old parts", or is about to run merge-agent and wants the branch normalized first. Everything happens ON THE BRANCH ITSELF — never a side branch, never a history rewrite, never a force-push, never the base. NOT for the actual merge (use merge-agent) or for non-git tasks.
    0
    installs
  10. ▌
    Spec Trace · bodish-coder bundle
    Use when what a feature must do exists only in conversation — a spoken brief, a chat thread, a ticket body, a handover — and the work outlives the session: a contract ending, someone else picking it up, a spec a later pass must re-check against the code. Also on requests for spec-driven development, spec-kit, specify/plan/tasks artifacts, or a traceability matrix. NOT for requirements already carrying stable identifiers, and not for a one-off edit.
    0
    installs
  11. ▌
    Merge Agent · bodish-coder
    Use when the user wants to combine/consolidate several GitHub branches into one integration branch, merge a feature branch into a base (main/develop), or reconcile divergent branches that touched the same code — and wants conflicts handled intelligently rather than by hand. The merge direction (`<source>` INTO `<destination>`) is confirmed before anything is touched; the base branch is never touched directly and nothing is pushed without explicit approval. NOT for a single trivial fast-forward, or non-git tasks.
    0
    installs
  12. ▌
    Skill Smith · bodish-coder bundle
    Use when writing a new agent skill, editing an existing one, or diagnosing a skill agents don't load or don't follow — a SKILL.md, a slash command, a reference file, or an always-on file (CLAUDE.md, AGENTS.md, GEMINI.md). Also when the user says "write a skill", "make this a skill", "skillify this", "my skill isn't triggering", "the agent ignored the skill", "improve this skill", or asks why a rule keeps getting rationalized away. NOT for using a skill (just invoke it) or installing/enabling skills on disk.
    0
    installs
  13. ▌
    Deploy Niyoj · bodish-coder bundle
    Use when the user says "niyoj", "set up niyoj deploy", "deploy without CI", "manual deploy", "no github actions deploy", "one-button deploy from my laptop", when converting a project off `.github/workflows/deploy.yml`, or when a NiYoj deploy failed and needs diagnosing. The target is a single-VPS app (Docker Compose + nginx + maintenance gate + Let's Encrypt) deployed over SSH from the NiYoj desktop app, with no CI runner. NOT for CI-triggered deploys (use `deploy-wizard`) or managed-PaaS targets.
    0
    installs
  14. ▌
    Design Arwen · bodish-coder bundle
    Use whenever the user wants to build, redesign, improve or critique a UI/UX, native or web: a web page/app/component, an iOS or Android screen, a React Native app, a dashboard, landing page, form, data table, settings screen, multi-step flow, onboarding, empty state, or design system; or asks to make something "more unique / bolder / quieter / more polished / less generic / more memorable / less AI-made", pick fonts/colors/layout/motion, fix visual hierarchy, spacing, contrast, a11y or UI performance, write UX copy and error states, or share one design language across native and web. NOT for backend-only or non-UI tasks; `impeccable` covers craft with no aesthetic direction to forge, gstack the headless-browser review of a finished page.
    0
    installs
  15. ▌
    Deploy Wizard · bodish-coder
    Use when the user says "prep the deployment", "set up deploy", "deployment wizard", "get this ready to ship to my server", "scaffold the deploy", or is about to stand up a new app on a Linux VPS with the standard single-VPS pattern (Docker Compose + nginx + GitHub Actions, one-push deploy, maintenance gate, TLS via Let's Encrypt). NOT for non-VPS / managed-PaaS deploys, or for the actual server administration.
    0
    installs
  16. ▌
    Handoff Watch · bodish-coder bundle
    Use when the user asks to "monitor usage limits", "auto handoff before I run out", "warn me at 92%", "save the session before the limit", "hand off automatically", or wants to install, configure or debug the usage watcher. Installs hooks — the monitoring is done by those hooks, not the model, and the handoff document itself comes from the handoff skill. NOT for reporting current usage (use /usage) and NOT for context-compaction tuning.
    0
    installs
  17. ▌
    Ticket Master · bodish-coder bundle
    Use when the user reports a bug or asks for a feature, says "log this", "what's pending", "ticket", "B3", "F12", "A4", "next ticket number", "mark it done", "block it", "defer it", "cancel it", "list tickets", "list tickets status", "ultracode", "work the board", "use a workflow", "fan out agents", mentions TICKETS.md, or when starting work and you need to know what's already open. Also before closing a session to sync statuses. NOT an issue tracker replacement and NOT for syncing to real Jira/GitHub Issues.
    0
    installs
  18. ▌
    Handoff Resume · bodish-coder
    Use when the user says "execute the handoff", "run the handoff", "work through the handoffs", "pick up the pending tasks", "resume from the handoff doc(s)", "do the next tasks in the handout", "process docs/handoffs", or wants a repeatable pass — safe to re-run or /loop — that picks up where a handoff left off. The execution counterpart to handoff, which writes the doc. NOT for writing a handoff (use handoff), and not for arbitrary tasks that live outside a handoff document.
    0
    installs
  19. ▌
    Sherlock Codes · bodish-coder
    Use when the user says "sherlock", "audit the app", "review everything", "find what's broken", "full code review", "what's wrong with this codebase", "check the whole thing", "sherlock #482", wants a full-application forensic audit for the defects nobody filed, or is before a release/handover. Can also be pointed at a single GitHub PR. Merging and conflict resolution are handed to `skillator:merge-agent`. NOT a security-only scan (use /security-review), and for a quick pass over the working diff `/code-review` is cheaper.
    0
    installs
  20. ▌
    Grayskull Power · bodish-coder bundle
    Use when the user says "dev mode", "activate the programming skills", "turn on the skillator workflow", "use our skills", "by the power of grayskull", "grayskull", "check screenshot", "set up for coding", or starts real development work in a repo with no skillator skill active. The single entry point that routes each request to the right skillator skill; it does not do the work itself. NOT for enabling/disabling skills on disk.
    0
    installs