Labsco
github logo

remember-interactive-programming

✓ Official★ 36,200

by github · part of github/awesome-copilot

Micro-prompt that reinforces interactive programming workflows with live REPL access. Designed for Clojure with Copilot integration via Backseat Driver, but adaptable to any system with a live REPL Reminds the agent to use the REPL as the source of truth for exploration and system modification Encourages clear communication about evaluated code and preference for structural editing tools over text replacement Includes guidance on maintaining a todo list during interactive development sessions

🔥🔥✓ VerifiedFreeQuick setup
#automation#git
🧩 One of 7 skills in the github/awesome-copilot package — works on its own, and pairs well with its siblings.

Micro-prompt that reinforces interactive programming workflows with live REPL access. Designed for Clojure with Copilot integration via Backseat Driver, but adaptable to any system with a live REPL Reminds the agent to use the REPL as the source of truth for exploration and system modification Encourages clear communication about evaluated code and preference for structural editing tools over text replacement Includes guidance on maintaining a todo list during interactive development sessions

Inspect the full instructions your agent will receiveExpand

This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.

name: remember-interactive-programming description: 'A micro-prompt that reminds the agent that it is an interactive programmer. Works great in Clojure when Copilot has access to the REPL (probably via Backseat Driver). Will work with any system that has a live REPL that the agent can use. Adapt the prompt with any specific reminders in your workflow and/or workspace.'

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.