Working prompts, per area
The core idea. Pick an area — auth, database, UI — and it reads
every request you ever made in it, then produces one prompt
covering the objective, your stack, the concrete requirements,
your conventions, a
Do not list mined from your corrections, and a
definition of done.
Save it to .github/prompts/ and it becomes a
/ command in chat. Save it to
.github/instructions/ and it applies automatically.
Grouped by topic
Prompts are classified into areas — UI, API, data, auth,
security, infra, testing, performance and more. Not happy with
the taxonomy? Describe a different one and it regroups.
Ask your own history
"What did I keep getting wrong about auth?" Answers are grounded
in the prompts your filters select, and cite them.
Correction patterns
Where the assistant repeatedly fails you, clustered into failure
modes, each with a copy-ready rule that prevents it.
Prompt quality
Specificity, context and actionability scored per prompt, with a
monthly trend and the share of turns that carried no information
at all. Computed locally.
Repeated questions
Near-duplicate asks across sessions and months. Each cluster is
an instruction file you have not written yet.
Paste hygiene
Finds the prompts that are mostly pasted terminal output, tells
you what they cost, and what to do instead.
Project specs & decision log
Reconstructs what each project is from the questions you asked
while building it, and recovers the architecture decisions you
made in chat — including the ones you later reversed.
Global instructions
The rules that hold everywhere, distilled into a
copilot-instructions.md that improves every future
session whether you remember this tool or not.