← all publishers

popmechanic

@popmechanic source repo

19 published skills

  1. Deploy 2 · popmechanic
    Deploy Julian to an exe.xyz VM (new instance or update existing)
    0
    installs
  2. Loom · popmechanic bundle
    Build server-based web applications where Claude Code CLI (`claude -p`) is the backend runtime — a Node/Express server spawns Claude processes to power a custom browser interface with streaming output.
    0
    installs
  3. Loom Local · popmechanic bundle
    Build local web applications where Claude Code CLI (`claude -p`) is the runtime, using Bun (`Bun.serve()`) as a thin server that streams results to a browser. No auth, no deployment — the machine's existing Claude Code login is inherited.
    0
    installs
  4. Loom Desktop · popmechanic bundle
    Build native desktop applications where Claude Code CLI (`claude -p`) is the runtime, using ElectroBun (Bun + system webview) with typed RPC — no HTTP server, no auth.
    0
    installs
  5. Sing · popmechanic
    Use when Julian should sing — a melody, a sung phrase, a signature motif, a canon or harmony with himself, or when Marcus asks for a song. Also use when composing any sung klattsch passage (note pitches, syllable groups, melisma).
    0
    installs
  6. Speak · popmechanic bundle
    Use when Julian should say something aloud in his chosen synthesized voice — a greeting, a moment that wants audio, a line Marcus asks to hear, or any occasion where sound serves better than text. Also use when composing or rendering any spoken klattsch utterance as Julian.
    0
    installs
  7. Deploy · popmechanic
    Deploy Julian to an exe.xyz VM (new instance or update existing)
    0
    installs
  8. Ultralearn · popmechanic bundle
    Use when the operator wants to learn from real ultrapowers runs — harvest runs across projects, read them through five lenses, accumulate a redaction-guarded observation ledger, and distill human-gated improvement proposals. Two verbs - "ultralearn" (sense) and "ultralearn distill" (propose).
    0
    installs
  9. Ultrawrite · popmechanic bundle
    Use when writing ANY implementation plan — this plugin's owned authoring skill. Elicits the operator's claim, shapes the decomposition into signed contracts, runs the proof gate, and emits a claims-v1 plan that /ultrapowers compiles into waves. Replaces the marker-layering skill and the external writing-plans dependency for plan bodies.
    0
    installs
  10. Ultradocket · popmechanic bundle
    Use when the operator has a backlog rather than a single idea — triage open issues into a ranked docket, sweep the accepted queue into engine-tagged plans, and drain that queue through an autonomous build. Optional; the single-feature superpowers flow is unchanged when not summoned.
    0
    installs
  11. Ultrapowers · popmechanic bundle
    Use when the user runs "/ultrapowers <plan-path>", asks to "execute this plan", "go ultra", or wants an approved plan built autonomously in parallel waves — on the exe.dev fleet, never on this machine. Also use when the user runs "/ultrapowers setup", asks whether they have a fleet yet, or asks to build one.
    0
    installs
  12. Riff · popmechanic bundle
    Self-contained parallel generator — invoke directly, do not decompose. Generates 3-10 app variations in parallel for comparing ideas. Use when user says "explore options", "give me variations", "riff on this", "brainstorm approaches", or wants to see multiple interpretations of a concept.
    0
    installs
  13. Test · popmechanic bundle
    Self-contained test automation — invoke directly, do not decompose. End-to-end integration test that assembles a fixture, deploys to Cloudflare (with auto-provisioned Connect), and presents a live URL for browser verification. Use when testing the plugin, running E2E tests, verifying deployment works, or checking that templates assemble correctly.
    0
    installs
  14. Vibes · popmechanic bundle
    Self-contained app generator — invoke this skill directly, do not decompose into sub-steps. Generates React web apps with TinyBase reactive data store. Use when creating new web applications, adding components, or working with real-time data. Ideal for quick prototypes and single-page apps that need real-time data sync.
    0
    installs
  15. Design · popmechanic
    Self-contained design transformer — invoke directly, do not decompose. Transforms a design reference HTML file into a Vibes app. Use when user provides a design.html, mockup, or static prototype to match exactly.
    0
    installs
  16. Launch · popmechanic bundle
    Self-contained SaaS pipeline — invoke directly, do not decompose. Generates a Vibes app, adds auth + billing, and deploys live. Uses Agent Teams to parallelize for maximum speed. Use when the user wants to build and ship a complete SaaS product in one step, or says "launch", "ship it", "build and deploy".
    0
    installs
  17. Factory · popmechanic bundle
    Self-contained SaaS pipeline — invoke directly, do not decompose. Generates a factory app with landing page, Stripe subscription checkout, Vibe Token economics, and deploys to Cloudflare Workers. Use when the user wants to monetize an app, add billing, create token-backed revenue sharing, or turn an app into a business.
    0
    installs
  18. Cloudflare · popmechanic
    Self-contained deploy automation — invoke directly, do not decompose. Deploys a Vibes app to Cloudflare Workers via the Deploy API. Use when deploying, publishing, going live, pushing to production, or hosting on the edge.
    0
    installs
  19. Vibes Brainstorm · popmechanic
    Lightweight requirements gathering before app generation. Asks non-technical multiple-choice questions to understand user intent, then produces a brief for the generate prompt.
    0
    installs