Neural archive

Prompt Library

supabase://prompts

354
prompts
38
images
58
folders
6
categories
Make one

Describe what you want, the brain builds it from your library.

brain . your library
Find one
Search your library

Browse and copy prompts you have already saved.

354 prompts . 38 images . 58 folders

Prompts

12
Fable5.2 Opus5.5Goal: a step-by-step plan for [your goal]. Don't build it yet. Context: [what you have, what you want at the end, your limits: budget, deadline, what's off-limits] If you need more context, ask me questions. Once done, we need to take Fable’s work and ask Opus to do it (because it’s much cheaper). So simply follow up with this prompt, still on Fable: Write a brief so a new chat on Claude Opus 5.5 can take over this work. It won't see this chat or your thinking. Write it for a smart reader who saw none of this. Plain words. Copy the exact names, numbers, dates, links and file names from this chat. Only the final version of anything we changed. Add nothing we didn't say. Use these parts: 1. Goal: one sentence, then "Done when:" with the checks I'd use. 2. Next step: the first thing Opus should do. Pick one it can do without me. 3. Decided: each final decision, with its reason in a few words. Then what we rejected, and why. 4. Facts: everything the work depends on. 5. Done here: what we already finished, so it isn't redone. 6. Ask me first: what needs my OK, and why. 7. Open: only what we left undecided. No new questions. 8. Checklist: every step left, as boxes to tick. 9. For Opus: copy these lines as they are. - Before you act, open every file and connected app that could matter, including ones this brief doesn't name, and use what you find. - Work through the checklist and tick each box as you go. Don't end with a summary that announces the next step: take it. Don't offer to continue: continue. - Stop only for what's under "Ask me first", or when you need a 11/14/26, 11:09 AM Gmail - Prompt 5.2. https://mail.google.com/mail/u/0/?ik=2551b954ac&view=pt&search=all&permthid=thread-f%3A1881721708637361670&simpl=msg-f%3A1881721708637361670 5/18 decision only I can make. - Don't reopen what's under "Decided". If something you find contradicts it, tell me. - End with a short recap: what you did, and what's next. Make it as short as it can be while complete. Give me the brief in one block I can copy. Now open a new chat on Opus 5.5 (Medium or High, I prefer High). Attach what Fable answered. And simply prompt it: Take it from there. U se fable 5.2 (high) as the agent orchestrator you’re the conductor. you do the thinking: the plan, the architecture, the strategy. split the job into tasks. give each one to its own Opus 5.5 worker. nudge every worker until its task is done. while they work, sit idle. don’t do their work for them. when a worker reports back, check it, then give out the next task. handle anything that doesn’t need me. only stop when you need a decision from me. I want to [goal] /agents use opus 5.5 (medium) as subagentsAiFable5.2 Worflows## Rewrite vague rules as clear instructions **Old:** Never change my prices. **New:** Ask me before you change a price: my clients have signed quotes. **Old:** Go. **New:** Yes, rewrite the 3 welcome emails. Leave the invoice template alone. ## Instructions - Finish the whole job before you stop. Don't offer to continue: continue. - Ask me before you delete anything. - This onboarding is yours: how it's built is your call, and you'll keep building on it. - End with a recap for someone who saw none of the work: key points first, plain words.AiFrontend Change Browser Verification## verify-frontend-change Verify any UI change end-to-end before declaring it done. # Verifying frontend changes Never report a UI change as complete based on a successful edit alone. Verify it the way a human reviewer would: 1. Start the dev server and open the edited page in the browser. 2. Interact with the change directly. For a new control (button, input, toggle): click it, confirm the expected state change, and screenshot before/after. 3. Check the browser console: zero new errors or warnings. 4. Run a performance trace and audit Core Web Vitals. If any step fails, fix the issue and rerun from step 1 — do not hand back partially verified work.AiGetting Started## SITUATIONAL CONTEXT I'm working on [the larger task] for [who it's for]. They need [what the output enables]. With that in mind: [your actual request]. ## MID-TASK CHECK-INS Pause the work every [time interval]. Give me a mini update so I can ensure we are on the right track. If you need anything from me, let me know so I can steer us in the right direction. ## TOKEN EFFICIENCY: THE 10-80-10 SYSTEM **Planning (10%)** Use your strongest model to define the structure, approach, success criteria, and constraints of your project upfront. **Execution (80%)** Hand the actual grunt work to a cheaper model. This is where most tokens get burned, and it's overkill to pay top prices for it. **Review (10%)** Bring your strongest model back to check the finished output against the original plan. ## LOOPS - `/goal`: Perfect for tackling single tasks (think: research, simple tasks with a single outcome). - `/loop`: How to run on a schedule or for deep, complex tasks. ``` /loop [your prompt] --interval 30m --expires 8h ``` Combine loop engineering with the 10-80-10 system: your strongest model architects the loop, a cheaper model executes it, and the strongest model steps back in only when the loop closes or when something needs review. - `/schedule` ### Six Parts of Every Loop 1. **Trigger**: What starts the loop. Usually `/schedule` or `/loop`. 2. **Execution Layer**: Where the actual work happens (no manual intervention needed here). 3. **The Verifier**: A checkpoint that confirms the agent is on track. 4. **Stop Rules**: Every loop needs a success condition and a failure condition. ``` Max 20 attempts. If all tests pass, report TASK_COMPLETE and stop. If unresolved after 3 retries, report TASK_FAILED and stop. ``` 5. **Memory**: A markdown progress file logging what's been done. 6. **Skills (CLAUDE.md)**: Saved instructions that freeze project context so the agent doesn't relearn it every run. ### Putting It All Together ``` /loop [verifiable end state], only touching [scope], stop after [X] iterations, use [skill] for verification, and keep a memory file of all your work. ``` ## VERIFICATION Make stop rules explicit in your instructions, not implicit: ``` You have a maximum of 20 attempts. If all tests pass, report "TASK_COMPLETE" and stop. If you encounter an error you cannot resolve after 3 retries, report "TASK_FAILED: [reason]" and stop. ``` Example: ``` /loop all tests in the auth module pass and coverage is above 80% ``` ## FINAL Optimal loop structure: ``` TRIGGER → every 15min / on PR comment / on CI failure DOER → the agent works the task CHECKER → separate model grades the output STOP → all tests green, or 10 iterations, or $5 spent MEMORY → progress.md updated each run SKILLS → CLAUDE.md read on every session start ``` Example: ``` /loop [verifiable end state/time], only touching [scope], stop after [X] constraints, use [X] Skills, use verifier agents for [x] checkpoint, and keep a memory file of all your work. ``` Full example: **CLAUDE.md (set once):** - Research style: comprehensive, cited, no fluff - Output format: markdown with clear headers - Never create files outside /research - Preferred sources: primary sources, reputable publications, official data - Max budget per session: $3 **Skill (set once):** ``` /skill verify-research: before marking any section complete, confirm every major claim has a source, every section has at least 3 supporting data points, and there are no obvious gaps. Never hand back thin research. ``` **The loop:** ``` /loop every 30 minutes, only touching /research/brief.md, stop after 10 iterations or if the same search query appears 3 times in a row without new information surfacing, use the verify-research skill after each section is drafted, use a verifier agent to check source quality and coverage completeness at the halfway point and before final submission, and keep a memory file at /research/progress.md that logs what sections are done, what sources have been used, and what angles still need coverage — read it at the start of every run and update it at the end. Topic: [your topic here] ``` Every principle in one place. The loop runs on a timer, stays scoped to one file, stops itself on stall or budget, uses a saved skill as the quality gate, spins up a separate verifier at two checkpoints, and keeps a persistent memory file so each run picks up exactly where the last one stopped.AiLoop2/goal get the homepage Lighthouse score to 90 or above, stop after 5 triesAiLoop4## Triggered by An event or schedule, with no human in real time. ## Stop criteria Each task exits when its goal is met. The routine itself runs until you turn it off. ## Best used for Recurring streams of well-defined work: bug reports, issue triage, migrations, dependency upgrades, etc. ## Managed usage by Routing routines to smaller, faster models and using the most capable model for judgment calls.AiMulti Agent Coordination"I'm working on [your project] for [who it's for]. Request: break this task into parallel workstreams and launch a subagent for each one — [list the workstreams, e.g. research, drafting, fact-checking, formatting]. Each subagent should work independently with a fresh context window. Output format: once all subagents complete their work, consolidate everything into one finished deliverable and flag any conflicts or overlaps between what each subagent produced. Constraints: don't let subagents duplicate work, and check in with me only if two subagents produce contradictory results."AiOvernight Research Loop"/loop every 30 minutes, only touching /research/brief.md, stop after 10 iterations or if the same search query appears 3 times in a row without new information surfacing, use a verify-research skill after each section is drafted to confirm every major claim has a source and every section has at least 3 supporting data points, use a verifier agent to check source quality and coverage completeness at the halfway point and before final submission, and keep a memory file at /research/progress.md that logs what sections are done, what sources have been used, and what angles still need coverage. Topic: [your research topic]" Before running this,   set up two things: CLAUDE . md : Including your research rules, session budget, and overall scope. The verify-research skill : Confirms every claim is sourced and every section has enough supporting data before it's marked complete.AiPersonal Os Dashboard"I'm working on a personal OS dashboard for myself. I want a single web app that pulls together my calendar, tasks, and daily priorities into one clean view. Request: build a personal dashboard web app with a calendar view, a task list with priority tags, and a notes section, using a clean minimal dark UI. Output format: a fully functioning web app with all three sections on one page. Constraints: don't add any features beyond these three sections, keep the file structure simple, and pause only if you hit a decision that changes the scope."AiPrompting Loops## Prompt Templates ### Task Framing "I'm working on [the larger task] for [who it's for]. They need [what the output enables]. With that in mind: [your actual request]." ### Mid-Task Check-Ins "Pause the work every [time interval] - give me a mini update so I can ensure we are on the right track. If you need anything from me, let me know so I can steer us in the right direction." ## Token Efficiency: The 10-80-10 System ### Planning (10%) Use your top-tier model to define the structure, approach, success criteria, and constraints of your project upfront. ### Execution (80%) Hand the actual grunt work to a cheaper model. This is where most tokens get burned, and it's overkill to pay top-tier prices for it. ### Review (10%) Bring your top-tier model back to check the finished output against the original plan. ## Loops ### /goal Perfect for tackling single tasks (think: research, simple tasks with a single outcome). ``` /goal get the homepage Lighthouse score to 90 or above, stop after 5 tries. ``` ### /loop How to run on a schedule or for deep, complex tasks. ``` /loop [your prompt] --interval 30m --expires 8h ``` Combine loop engineering with the 10-80-10 system: the top-tier model architects the loop, a cheaper model executes it, and the top-tier model steps back in only when the loop closes or when something needs review. ``` /loop 5m check my PR, address review comments, and fix failing CI ``` ### /schedule `/loop` runs on your computer, so if you turn it off, it stops. You can move the loop to the cloud by creating a routine with `/schedule`. ``` /schedule every hour: check the project-feedback channel for bug reports. /goal: don't stop until every report found this run is triaged, actioned, and responded to. When fixing a bug, use a workflow to explore three solutions in parallel worktrees and have a judge adversarially review them. ``` ## The Six Parts of Every Loop 1. **Trigger:** What starts the loop. Usually `/schedule` or `/loop`. 2. **Execution Layer:** Where the actual work happens (no manual intervention needed here). 3. **The Verifier:** A checkpoint that confirms the agent is on track. 4. **Stop Rules:** Every loop needs a success condition and a failure condition. > "Max 20 attempts. If all tests pass, report TASK_COMPLETE and stop. If unresolved after 3 retries, report TASK_FAILED and stop." 5. **Memory:** A markdown progress file logging what's been done. 6. **Skills (CLAUDE.md):** Saved instructions that freeze project context so the agent doesn't relearn it every run. ## Putting It All Together ``` /loop [verifiable end state], only touching [scope], stop after [X] iterations, use [skill] for verification, and keep a memory file of all your work. ``` ## Verification Make stop rules explicit in your instructions, not implicit: > You have a maximum of 20 attempts. If all tests pass, report "TASK_COMPLETE" and stop. If you encounter an error you cannot resolve after 3 retries, report "TASK_FAILED: [reason]" and stop. Example: ``` /loop all tests in the auth module pass and coverage is above 80% ``` ## Final: Optimal Loop Structure ``` TRIGGER → every 15min / on PR comment / on CI failure DOER → the agent works the task CHECKER → separate model grades the output STOP → all tests green, or 10 iterations, or $5 spent MEMORY → progress.md updated each run SKILLS → CLAUDE.md read on every session start ``` Example: ``` /loop [verifiable end state/time], only touching [scope], stop after [X] constraints, use [X] Skills, use verifier agents for [x] checkpoint, and keep a memory file of all your work. ``` ### Full Example **CLAUDE.md (set once):** - Research style: comprehensive, cited, no fluff - Output format: markdown with clear headers - Never create files outside `/research` - Preferred sources: primary sources, reputable publications, official data - Max budget per session: $3 **Skill (set once):** ``` /skill verify-research: before marking any section complete, confirm every major claim has a source, every section has at least 3 supporting data points, and there are no obvious gaps. Never hand back thin research. ``` **The loop:** ``` /loop every 30 minutes, only touching /research/brief.md, stop after 10 iterations or if the same search query appears 3 times in a row without new information surfacing, use the verify-research skill after each section is drafted, use a verifier agent to check source quality and coverage completeness at the halfway point and before final submission, and keep a memory file at /research/progress.md that logs what sections are done, what sources have been used, and what angles still need coverage — read it at the start of every run and update it at the end. Topic: [your topic here] ``` Every principle in one place: the loop runs on a timer, stays scoped to one file, stops itself on stall or budget, uses a saved skill as the quality gate, spins up a separate verifier at two checkpoints, and keeps a persistent memory file so each run picks up exactly where the last one stopped.AiTime-Based Loop Reference# Time-based Loop (`/loop` and `/schedule`) - **Triggered by:** A specified time interval. - **Stop criteria:** You cancel it, or the work completes (the PR merges, the queue is empty). - **Best used for:** Recurring work, or interfacing with external environments / systems. - **Managed usage by:** Setting longer intervals or reacting based on events rather than time. </think>AiTurn-Based Agent Loop## Turn-based loops Your prompt → Gather context → Take action → Verify the work → Response Exits when the model judges the task complete — or the effort budget runs out.Ai
AiImported version

Fable5.2 Opus5.5

/Users/fabien/Desktop/AI/PROMPTS/-ai/-fable5/-fable5.2-opus5.5.odt

Folder-ai/-fable5
Versions0
Imported2026-11-16
StatusActive
Goal: a step-by-step plan for [your goal]. Don't build it yet.

 Context: [what you have, what you want at the end, your limits:

 budget, deadline, what's off-limits]

 If you need more context, ask me questions.

 Once done, we need to take Fable’s work and ask Opus to do it (because it’s

 much cheaper). So simply follow up with this prompt, still on Fable:

 Write a brief so a new chat on Claude Opus 5.5 can take over this

 work. It won't see this chat or your thinking.

 Write it for a smart reader who saw none of this. Plain words.

 Copy the exact names, numbers, dates, links and file names from

 this chat. Only the final version of anything we changed. Add

 nothing we didn't say.

 Use these parts:

 1. Goal: one sentence, then "Done when:" with the checks I'd use.

 2. Next step: the first thing Opus should do. Pick one it can do

 without me.

 3. Decided: each final decision, with its reason in a few words.

 Then what we rejected, and why.

 4. Facts: everything the work depends on.

 5. Done here: what we already finished, so it isn't redone.

 6. Ask me first: what needs my OK, and why.

 7. Open: only what we left undecided. No new questions.

 8. Checklist: every step left, as boxes to tick.

 9. For Opus: copy these lines as they are.

 - Before you act, open every file and connected app that could

 matter, including ones this brief doesn't name, and use what you

 find.

 - Work through the checklist and tick each box as you go. Don't

 end with a summary that announces the next step: take it. Don't

 offer to continue: continue.

 - Stop only for what's under "Ask me first", or when you need a

 11/14/26, 11:09 AM Gmail - Prompt 5.2.

 https://mail.google.com/mail/u/0/?ik=2551b954ac&view=pt&search=all&permthid=thread-f%3A1881721708637361670&simpl=msg-f%3A1881721708637361670 5/18 decision only I can make.

 - Don't reopen what's under "Decided". If something you find

 contradicts it, tell me.

 - End with a short recap: what you did, and what's next.

 Make it as short as it can be while complete. Give me the brief

 in one block I can copy.

 Now open a new chat on Opus 5.5 (Medium or High, I prefer High). Attach

 what Fable answered. And simply prompt it:

 Take it from there.

U se fable 5.2 (high) as the agent orchestrator

 you’re the conductor. you do the thinking: the plan, the

 architecture, the strategy.

 split the job into tasks. give each one to its own Opus 5.5

 worker. nudge every worker until its task is done. while they

 work, sit idle. don’t do their work for them. when a worker

 reports back, check it, then give out the next task. handle

 anything that doesn’t need me. only stop when you need a decision

 from me.

 I want to [goal]

 /agents use opus 5.5 (medium) as subagents
Combine some
Fuse from your library

Find the closest matches, pick a few, and fuse them into one prompt.

search . match . fuse
Search finds the best-matching prompts, then Fuse weaves your selection into one.
Build a loop

Dump an outcome. Get a copy-paste autonomous loop for any LLM or harness.

brain . loop library
Does this job have a finish line?
Auto: the brain picks goal vs loop for you.