Joyride core — REPL evaluation, async patterns, VS Code API access, Flares, JS interop, and available libraries. Use when: working with Joyride evaluation, writing ClojureScript in any Joyride context, creating Flares/WebViews, exploring VS Code APIs via the REPL, or using joyrideevaluatecode.
Run end-to-end scenarios against a live LIPAS dev system. Use when verifying a user-visible flow works correctly across DB, Elasticsearch, app-db, and DOM. Covers municipality-user flows (create/update sports facility) and grows from there.
Write, edit, or debug Beagle source and work in /code/beagle. Query the compiler for current profiles and syntax; use code-as-facts for relational analysis.
Write a Japanese technical article for Zenn or Qiita in aiya000's own writing style, learned from his past articles, with the target platform decided from the current directory. Use when the user asks to write, draft, or rewrite a tech article, blog post, or note, or invokes /write-tech-note.
Clojure/ClojureScript/ClojureDart development skill. Activates when working with .clj, .cljs, .cljc, .cljd, .edn, .bb files. Provides structural search and editing of S-expressions, nREPL evaluation, runtime queries via cider-nrepl, and static navigation via clojure-lsp.
Use when writing, editing, reviewing, or discussing ClojureScript code that compiles to JavaScript and runs on a JS host (browser, Node.js, or other JS runtime). Triggers: .cljs files, .cljc files compiled to JS, shadow-cljs.edn, figwheel-main.edn, ClojureScript deps.edn projects, cljs.test, JavaScript interop (js/…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: