// System You are a senior PM. Direct, declarative. No hedging. No exclamation marks. Past tense for shipped work, present for what's blocking. // Prompt Summarize {{ project }} for {{ audience | execs }}. Structure: · Shipped this week (3 bullets, verbs first) · Blocked on (1 line per blocker, name owner) · Next week's bet ({{ horizon | one week }}) · Risk to call out (only if material) Tone: {{ ref: voice_guide }}.
Starter pack · 18 prompts · ~14 kB JSON
Skip the blank library. Start with 18 prompts that already work.
Most prompt managers hand you an empty database and a tutorial. Prompt Organizer ships with 18 prompts the author actually reuses on weekly work - writing, code review, research synthesis, doc rewrites, and agent briefs. They're seeded on first launch and yours to edit, fork, or delete the moment they hit your browser.
Loads in about 1 second on first open. No account, no fetch.
- Bundled with the app
- 0 network calls to load
- Editable JSON you own
Why these eighteen
Boring on purpose. Picked for repeat use, not novelty.
Most starter packs are dazzling and useless: clever one-shots that you never reach for. These eighteen are the opposite - mundane workflows you'll trigger this week, structured tightly enough that you stop retyping them.
Five categories. The 18 prompts in detail.
The pack avoids novelty. Every prompt is something the author uses on actual work - the recurring, high-leverage chores that benefit from being saved once and called dozens of times. Below: the sample prompt expanded, plus the full eighteen.
// System You are a senior application security engineer. Be specific. Cite line numbers and file paths. No CVSS theatre. Real exploit chains only. // Prompt Scan {{ diff }} for these classes: · Auth bypass and missing authorization · Output encoding gaps (XSS, template injection) · SQL/NoSQL/command injection · Secret handling and logging leaks · Race conditions in {{ component | the diff }} Output one finding per line: [severity] file:line - what an attacker does Reference standard: {{ ref: secure_coding_v2 }}
- Writing (4 prompts).Weekly status update, exec-voice rewrite, customer-email reply, internal memo to one decision-maker.
- Code review (4 prompts).Security pass on a diff, performance pass, readability pass, public-API review for a library change.
- Research synthesis (3 prompts).Reconcile five sources into one timeline, extract the single disagreement across two papers, build a counter-argument scaffold.
- Doc rewrites (4 prompts).Clarity pass at reading age 14, tone shift to declarative, structure pass for skimmers, glossary extraction from a long doc.
- Agent briefs (3 prompts).Brief a coding agent with scope and constraints, brief a research agent with a stop condition, brief a writing agent with style references.
Seed automatically. Re-import any time.
The pack ships inside the app bundle, so the first time you open Prompt Organizer it's already there. No network call, no opt-in checkbox. If you cleared the library, started a fresh browser profile, or want to compare your edits against the original, you can re-import the same JSON file by hand.
The pack is also a plain file in the repo. Fork it, edit titles or bodies in your editor, change variable defaults, and import your version. It's a starter - not a contract.
- Automatic on first launch.Open the app for the first time and the pack is loaded. No checkbox, no setup.
- Re-import via the import page.Drop the JSON file in. Merges by ID, so your edits survive; new prompts are added.
- Download and customize.Grab the file, edit it in your editor, then import. Schema is documented and human-readable.
// 14 kB, schema v3, sha256:c91e...4a08 { "schemaVersion": 3, "name": "Prompt Organizer Starter Pack", "prompts": [ { "id": "sp_001", "title": "Weekly status update - exec voice", "category": "writing", "system": "You are a senior PM...", "body": "Summarize {{ project }} for...", "variables": ["project", "audience", "horizon"], "refs": ["voice_guide"] }, { "id": "sp_002", "title": "Code review - security pass", "category": "code-review", "system": "You are a senior application...", "body": "Scan {{ diff }} for these classes...", "variables": ["diff", "component"], "refs": ["secure_coding_v2"] }, // ... 16 more, total 18 prompts ] }
Open the app, or grab the JSON and edit it first.
Either path ends in the same place: 18 prompts in your local library, ready to call, edit, or delete. Nothing waits on a server.
It's a file. You own it.
The starter pack lands in your browser the moment the app loads. Nothing leaves. Edit a prompt and the change is in IndexedDB on your machine, not on a server. Export the library and you have a JSON file you could email to yourself in five years.