What is this skill for?

It serves as a micro-prompt that keeps you aware you’re an interactive programmer and guides REPL-based exploration and changes.

Can it work outside Clojure?

Yes. It works with any system that has a live REPL; Clojure is the common case with Backseat Driver, but the principle applies broadly.

How private is the evaluated output?

The human does not see what you evaluate; you should describe evaluations succinctly and avoid exposing sensitive data.

remember-interactive-programming

Scanned

npx machina-cli add skill github/awesome-copilot/remember-interactive-programming --openclaw

Files (1)

SKILL.md

882 B

Remember that you are an interactive programmer with the system itself as your source of truth. You use the REPL to explore the current system and to modify the current system in order to understand what changes need to be made.

Remember that the human does not see what you evaluate with the tool:

If you evaluate a large amount of code: describe in a succinct way what is being evaluated.

When editing files you prefer to use the structural editing tools.

Also remember to tend your todo list.

Source

git clone https://github.com/github/awesome-copilot/blob/main/plugins/clojure-interactive-programming/skills/remember-interactive-programming/SKILL.md

View on GitHub

Overview

This micro-prompt keeps you aware that you are an interactive programmer and should use the REPL to explore and modify the system. It shines in Clojure with access to a REPL (e.g., via Backseat Driver) but works with any live REPL. Adapt the prompt with workflow- and workspace-specific reminders to stay productive.

How This Skill Works

The agent treats the system as the source of truth and uses the REPL to investigate and modify the current state. When evaluating code, it remains concise about what is being evaluated and why. Edits are performed with structural editing tools, and the agent maintains a running todo list to track next actions.

When to Use It

Starting a coding session with a live REPL to explore the current system.
Debugging or prototyping in a Clojure REPL (likely with Backseat Driver).
Exploring unfamiliar codebases or APIs via the REPL to surface behavior and side effects.
Documenting what the REPL evaluates and how results inform changes.
Maintaining and updating your personal todo list within the workflow.

Quick Start

Step 1: Ensure a live REPL is accessible to the agent (e.g., via Backseat Driver in Clojure).
Step 2: Enable the remember-interactive-programming micro-prompt in your workspace and connect it to your workflow.
Step 3: During coding, use structural editing tools for changes, summarize REPL evaluations succinctly, and tend your todo list.

Best Practices

Keep the micro-prompt lightweight and contextually relevant to the current task.
Describe large or complex evaluations succinctly to avoid long, noisy outputs.
Prefer structural editing tools for code changes rather than ad-hoc edits.
Treat the system as the source of truth; verify conclusions with REPL results.
Tend your todo list actively and revisit it before committing changes.

Example Use Cases

In a Clojure REPL, you evaluate a function against live data, observe results, and iteratively refine the function.
You edit code with structural editors to preserve syntax integrity and readability.
You briefly summarize what is being evaluated in the REPL rather than exposing verbose tool outputs.
Backseat Driver provides the REPL context, while you maintain a concise narrative of findings.
You maintain a running todo list and review it before finalizing changes.

Frequently Asked Questions

Add this skill to your agents