Skip to main content
// ple
// docs / getting started

Productive in five minutes.

Two ways in: terminal-first with zero signup, or account-first with the web editor. Both end at the same library.

0. Fastest start — terminal, no account

$ terminal
npm i -g promptlike
ple save "code review" -m "Review this diff: {{diff}}"
ple get "code review" --var diff="$(git diff)" | claude

That's a working prompt library — plain Markdown files in ~/.promptlike/prompts/, no account involved. When you want sync, version history and the web editor, continue below; your local prompts come along with one explicit ple sync. Full reference: CLI docs.

1. Create your account and first prompt

Sign up with email or Google. On first login you can seed the library with 3 example prompts, useful for poking at versioning before you commit your own material.

In the dashboard, create a prompt inside your project. The editor uses three sections (ROLE, CONTEXT, INSTRUCTION): write markdown, or type / to insert a section. Hit Commitwhen it's worth keeping: every commit is a numbered version.

2. Install the CLI

$ terminal
npm i -g promptlike
ple login          # email + password
ple list           # your library, from the terminal

Signed up with Google? Set a password first in Settings → Account, because the CLI authenticates with email + password. Your session is stored in ~/.config/promptlike/config.json (file mode 0600) and refreshes itself.

3. Use a prompt where you work

$ terminal
ple copy code-review          # copy to clipboard
ple show code-review          # pretty-print in your terminal
ple get code-review | claude -p   # feed it straight to your agent

Names resolve fuzzily: full UUID, an 8+ character id prefix, or a unique title fragment all work. Ambiguous name? The CLI prints the candidates instead of guessing.

Where to go next

Made an edit you regret? Versioning, diff & rollback. Reusing the same prompt with different inputs? {{variables}}. Not sure which phrasing performs better? Loop.