PEZ

Write effective Joyride scripts and source files in ClojureScript. Covers VS Code API interop, async/promise handling, data-oriented functional design, REPL-driven development, disposable lifecycle, Flares (WebViews), and extension API access. Use when: writing or editing .cljs files for Joyride, automating VS Code, building interactive tools with the VS Code API, creating Flare WebViews, fixing or debugging Joyride scripts, troubleshooting async/promise issues, working with joyride.core or promesa.core, or doing REPL-driven ClojureScript development in VS Code. REPL: use joyride_evaluate_code, not the Backseat Driver clojure_evaluate_code — the Joyride REPL is a separate runtime.

Write idiomatic Babashka (bb) scripts and modules. Covers babashka.fs, babashka.process, babashka.cli, babashka.http-client, and built-in namespaces. Use when: writing bb scripts, creating or modifying a task, choosing between shell and process, replacing shell commands with Babashka built-ins, REPL-driven development, or editing .clj files in directories with bb.edn or scripts/ folders.

Write idiomatic bb.edn tasks: thin wrappers delegating to scripts/*.clj modules. Supports project-level bb and global bbg tasks. Use when: creating or modifying a bb/bbg task, editing bb.edn or scripts/*.clj files, structuring task modules, adding CLI argument parsing, resource lifecycle management, or agent-friendly output patterns.

**BROWSER TAMPERING SKILL** — Live tamper with web pages and write userscripts using Epupp (ClojureScript/Scittle in the browser). USE FOR: REPL-driven page inspection and modification, userscript development with manifests, DOM querying and mutation, injecting UI with Replicant/Reagent, async data fetching, troubleshooting Epupp connections. DO NOT USE FOR: Node.js or JVM ClojureScript, npm package usage, server-side scripting. INVOKES: clojure_evaluate_code, clojure_list_sessions, clojure_repl_output_log (Backseat Driver REPL tools), file system tools (read/write userscripts).

Organize and manage Joyride User scripts and source files — the global Joyride directory that applies across all VS Code workspaces. Covers directory structure (scripts/ vs src/), user_activate.cljs, deps.edn and package.json for dependencies, keybinding setup, clojure-lsp configuration, and classpath resolution. Use when: creating or editing files in the Joyride User directory, setting up user activation, adding global keybindings for Joyride functions, configuring user-level dependencies, or organizing user-scoped scripts and source.

Set up and manage Joyride workspace automation in the .joyride/ directory of a project. Covers workspace_activate.cljs, project-local scripts and source, workspace deps.edn and package.json, clojure-lsp configuration, and classpath precedence over user-level code. Use when: creating or editing files in a workspace .joyride/ directory, setting up workspace activation, adding project-specific Joyride automation, configuring workspace-level dependencies, or deciding between workspace and user scope.

**EDITING SKILL** — Create, edit, and style presentation slides for the next-slide system (VS Code markdown preview + CSS + EDN config). USE FOR: creating new slides, editing existing slides, adding slides to a deck, styling slide layouts, extending presentation CSS, choosing slide patterns, fixing slide layout issues. DO NOT USE FOR: slide navigation/runtime (that is next_slide.cljs), audio/narration generation, general markdown editing unrelated to presentations. INVOKES: file system tools (read/write slides, CSS, slides.edn), search tools (discover workspace image paths and existing slide patterns).

Babashka scripting conventions for the Epupp project. Use when: writing or modifying bb.edn tasks, scripts in scripts/, build or test automation, choosing between bb and npx/npm/shell/Python, using babashka.fs, babashka.process, or babashka.http-client, or running any bb command in this repo. Prefer bb tasks over direct npm/npx; keep bb.edn minimal and put code in scripts/tasks.clj. IMPORTANT: Also load when planning automation or build pipeline changes.

Epupp architecture, development patterns, and system contracts. Use when: writing or modifying Epupp source code, implementing features, fixing bugs, debugging extension behavior, working with Uniflow actions or effects, understanding message flows, injection or connection lifecycle, testing strategy, build pipeline, reviewing Epupp PRs, planning implementations, running tests or builds, REPL-driven development, or any coding task in the Epupp workspace. Contains architecture overview, Uniflow contracts, source file map, testing patterns, delegation, and development principles. References hold deep state contracts and temporal sequences. IMPORTANT: Also load when PLANNING Epupp changes, not only at implementation time.

Epupp-specific Squint source conventions for src/**. Use when: editing Squint/ClojureScript in src/, testing pure functions via squint-nrepl, debugging Squint-to-Scittle message interop, avoiding direct .mjs edits, or rewriting legacy JS interop to Clojure style. For universal Squint semantics (keywords, data structures, async, compilation model) load the universal Squint skill separately. IMPORTANT: Also load when planning changes to src/** Squint code.

Reagami UI library patterns for Epupp Squint components. Use when: writing or modifying Reagami components, hiccup UI in popup.cljs or panel.cljs, event handlers with Uniflow dispatch, :on-render lifecycle hooks, list rendering with keys, or comparing Reagami to Reagent. Covers component patterns, class shorthand, and Epupp-specific examples. IMPORTANT: Also load when planning UI changes that use Reagami.

Epupp design context, principles, and visual foundation. Use when: working on popup or panel UI, styling popup or panel, choosing colors or spacing, making layout decisions, reviewing visual consistency, working with CSS or hiccup components, creating or modifying UI elements, editing popup.cljs or panel.cljs, or when any design skill (impeccable, polish, critique, layout, etc.) needs Epupp project context. Provides brand palette, typography, spacing tokens, and design principles.

Page buddy live-tamper architecture and development. USE FOR: modifying page_buddy.cljs or page_buddy_sprites.cljs, adding behaviors/animations/effects, refactoring state management, debugging physics or FSM logic. IMPORTANT: Also load when PLANNING page buddy changes. Enforces Uniflow invariants adapted for Epupp/SCI without Replicant.