clojurescript

Guide ClojureScript development in the Seon pod runtime environment.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/seantempesta/seon --skill clojurescript
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clojurescript
Source: https://github.com/seantempesta/seon/tree/main/seon-skills/clojurescript
Command: npx skills add https://github.com/seantempesta/seon --skill clojurescript

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves ambiguity and runtime errors when developing or debugging ClojureScript within the Seon pod environment, specifically addressing the complexities of self-host compilation and asynchronous execution.

Core Features & Use Cases

  • Async/Await Management: Provides clear guidance on using native JS async/await patterns in the pod, replacing legacy core.async approaches.
  • Self-Host Debugging: Offers critical insights into the differences between shadow-cljs builds and agent-eval'd forms to prevent common runtime surprises.
  • Use Case: When an agent encounters a malli instrumentation error or a Promise leakage during code evaluation, this Skill provides the necessary semantic context to refactor the code for the pod's specific execution model.

Quick Start

Ask the clojurescript skill to explain how to properly wrap an asynchronous function to avoid Promise leakage in the agent evaluation path.

Frequently Asked Questions about clojurescript

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent Promise leakage when evaluating asynchronous ClojureScript functions?

To prevent Promise leakage in ClojureScript asynchronous functions, you must properly wrap native JS async/await patterns to align with the agent evaluation path, replacing legacy core.async approaches to ensure correct execution state management.

Why does my self-hosted ClojureScript build behave differently from agent-eval'd forms?

Self-hosted ClojureScript builds behave differently from agent-eval'd forms due to distinct execution contexts. Understanding these semantic differences is critical to prevent unexpected runtime surprises and malli instrumentation errors during Node.js process evaluation.

How do I handle malli instrumentation errors during ClojureScript code evaluation?

Handling malli instrumentation errors during ClojureScript code evaluation requires applying the correct semantic context for the pod's specific execution model, refactoring the code to resolve conflicts between shadow-cljs builds and native asynchronous operations.

Can I use native JavaScript async/await instead of core.async in a ClojureScript Node.js runtime?

Yes, you can use native JavaScript async/await instead of core.async in a ClojureScript Node.js runtime. This approach provides clear execution guidance for the pod environment, ensuring correct instrumentation and state management for long-running processes.

What are the limitations of using shadow-cljs builds for long-running ClojureScript processes?

The limitations of using shadow-cljs builds for long-running ClojureScript processes involve potential runtime surprises from agent-eval differences and Promise leakage, requiring specific semantic guidance to maintain correct state and instrumentation.