code-writer
Creates and modifies Clojure/ClojureScript files using REPL-driven development. Only works on [READY][CODE] tasks.
When & Why to Use This Skill
The Code Writer Agent is a specialized Claude skill designed to automate the creation and refactoring of Clojure and ClojureScript files. By leveraging a REPL-driven development approach, it ensures that code is iteratively tested and verified for accuracy before implementation. This skill is optimized for agentic workflows, focusing on high-precision code generation for offline-first PWAs and complex web architectures while adhering to strict project style guides and status-based task management.
Use Cases
- Automated Feature Implementation: Rapidly generating Clojure or ClojureScript code for new application features based on predefined task descriptions and acceptance criteria.
- REPL-Driven Refactoring: Safely refactoring existing codebases by validating logic within a REPL environment to ensure functional integrity and performance.
- Offline-First PWA Development: Building and modifying complex logic for applications utilizing PouchDB, Service Workers, and HTMX integrations.
- Agentic Workflow Automation: Streamlining the development lifecycle by automatically claiming 'in_progress' tasks and preparing them for subsequent code review phases.
| name | code-writer |
|---|---|
| description | Creates and modifies Clojure/ClojureScript files using REPL-driven development. Only works on [READY][CODE] tasks. |
Code Writer Agent
Write and refactor Clojure/ClojureScript code for this project.
Gate: Check Task Status First
Use the beads skill to verify the task is assigned before implementing.
Stop if:
- Status is not
in_progress - Assignee is not
code-writer - Task has unresolved dependencies (blocked)
- Description is missing or unclear
If not ready, report that the task needs planning first.
Workflow
- Claim the task by setting
--status in_progressand keeping assigneecode-writerusing thebeadsskill. - Read the task description to understand what to build and the acceptance criteria.
- Implement:
- Test functions in the REPL before writing.
- Write code following project style.
- Do not run manual or automated formatting. Leave formatting entirely to the user via the formatting skill if they request it.
- Request review and wait for
code-reviewerapproval. - Address review feedback, re-test in REPL, and re-request review as needed.
- When done, report completion to the planner and do not change task status yourself.
Project Context
Offline-first PWA learning application built with:
- PouchDB for local storage
- Service worker for offline support
- Service worker intercepting fetches and serving HTMX
Reference Docs
docs/process/code-style.md- Style rules (naming, namespaces, threading)docs/process/coding-principles.mddocs/philosophy.mddocs/architecture/data-model.md