johnlindquist

Prompt Builder — Development skill for Claude Code

Development community

Terminal prompt builder for composing a prompt before handing it to Pi, Codex.

How to install Prompt Builder

This entry records only its repository, not the path inside it, so there is no exact command to give. Open johnlindquist/prompt-builder and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Prompt Builder does

Terminal prompt builder for composing a prompt before handing it to Pi, Codex,

Alternatives in Development

README

prompt-builder

Terminal prompt builder for composing a prompt before handing it to Pi, Codex, or Claude Code.

`prompt-builder` opens a small Ratatui composer with skill lookup, Codex-like paste handling, optional conversation naming, launch targets (profiles) for multiple Pi, Codex, and Claude Code profiles, and a generic handoff mode for shell workflows.

Install

Requirements:

  • Rust toolchain from rustup; this repo pins Rust 1.95.0.
  • Pi CLI on PATH for the default submission target.
  • Codex and Claude Code CLIs are optional when using those targets.

Private GitHub install:

cargo install --git ssh://git@github.com/johnlindquist/prompt-builder.git --locked

Public HTTPS install, once the repo is public:

cargo install --git https://github.com/johnlindquist/prompt-builder.git --locked

Local development install:

git clone git@github.com:johnlindquist/prompt-builder.git
cd prompt-builder
cargo install --path . --locked

The installed binary is `prompt-builder`. If you want the short local command `p`, add an alias or symlink:

alias p=prompt-builder
ln -sf ~/.cargo/bin/prompt-builder ~/.cargo/bin/p

Safety

By default, submitted prompts launch Pi with its normal interactive behavior:

pi 

Pi does not add a permission-bypass flag; use Pi's own isolation, trust, and extension settings for the safety policy you want. Explicit Codex targets launch with `--dangerously-bypass-approvals-and-sandbox`, and Claude targets launch:

claude --dangerously-skip-permissions -- 

Only use these launchers in directories where you are comfortable letting the selected agent modify files and run commands.

Before launching an agent, inspect what would run:

prompt-builder --dry-run --print-command "hello"
PROMPT_BUILDER_PI_BIN=/bin/echo prompt-builder --submit "hello"

For scripts that should avoid parsing shell-quoted command text, print the raw launch manifest:

prompt-buil