7 KiB
Community Prompts 🧠
Prompt packs, routing prompts, and repair-oriented prompt assets
Quick links:
- Back to Community Fix Lab
- Back to Official Fixes
- Back to Fixes Hub
- Back to Atlas landing page
- Back to AI Eval Evidence
- Back to Atlas Hub
- Open the Flagship Runnable Demo Pack
- Open Templates
- Open Prompt Template
- Get the Atlas Router TXT
If the Community Fix Lab is the broader entry page for community repair assets, this folder is the prompt lane for route-aware workflows, repair guidance, boundary teaching, and compact troubleshooting prompt packs. 🧭
Use this folder when a contribution is mainly about how prompt structure helps apply atlas routing more clearly, not when the contribution is mainly a notebook, JSON fixture, workflow recipe, or official repair rule.
Short version:
official layer gives the repair grammar
this folder helps turn that grammar into repeatable prompt workflows
Quick start 🚀
I want to contribute a prompt asset
Use this path:
- decide whether the asset is really a prompt contribution
- route the case first with the atlas
- keep the prompt scoped to one family, one case, or one boundary cut
- explain what the prompt is trying to improve
- document expected behavior and known limits
I want to browse prompt assets
Use this path:
- open one prompt pack with a clear routing context
- identify the target family or case
- inspect what the prompt is trying to improve
- compare the expected behavior against the route
- check the result note and limitations
Short version:
route first
keep prompts scoped
make the workflow repeatable ✨
Prompts quick map 🗂️
| If your asset is mainly... | Best folder |
|---|---|
| a route-aware prompt asset or repair prompt pack | Prompts |
| a runnable notebook walkthrough | Colab |
| a structured fixture or machine-readable case | JSON |
| a step-by-step repair sequence | Workflows |
| a before / after comparison slice | Benchmark Reruns |
| a portable one-case bundle | Reproduction Packs |
This folder is the right place when the prompt itself is the main reusable teaching or troubleshooting surface.
What belongs here ✅
Good prompt contributions include:
- one prompt pack tied to a known family
- one prompt that improves first repair direction clarity
- one prompt that teaches a difficult boundary cut
- one prompt that compares misrepair and correct repair
- one small prompt workflow with clear expected behavior
A good prompt contribution should be:
- scoped
- explainable
- reproducible when possible
- clearly connected to atlas routing
- honest about what it improves
What does not belong here 🚫
Please do not use this folder for:
- giant prompt collections with no structure
- roleplay prompts unrelated to troubleshooting
- vague prompt ideas with no case framing
- prompts that ignore routing and jump straight to random repair
- prompt packs presented as official atlas rules without review
- prompt tricks with no explanation of when they should be used
A prompt asset should help someone apply atlas routing more clearly, not bypass it.
Suggested prompt contribution pattern 🧩
A useful contribution usually includes:
- what case or family it targets
- what the prompt is trying to improve
- the prompt text
- how to use it
- expected result
- known limits
That is enough to make a prompt pack usable.
Suggested naming style 📌
Examples:
f1-regrounding-prompt-pack-v1.mdf5-trace-first-prompt-pack-v1.mdf7-container-tightening-prompt-pack-v1.md
Use names that reveal both the family and the action.
Keep names readable and compact.
What a good first prompt pack looks like 🌱
A strong first contribution usually looks like this:
- one family
- one case
- one prompt pack
- one expected behavior
- one short explanation of what changed
Small, clear prompt packs are much better than giant messy collections.
Before contributing 📚
Please read:
- Community Fix Lab
- Contribution Checklist
- Prompt Template
- Family Fix Surface v1
- Atlas to WFGY Bridge v1
This helps keep prompt contributions aligned with atlas grammar instead of drifting into random prompt experimentation.
Review standard ✅
A prompt contribution is much more likely to be accepted if it is:
- clearly named
- easy to understand
- easy to reuse
- connected to atlas routing
- explicit about expected behavior
- honest about limitations
Messy prompting is still messy.
Clean scoped prompt packs are more valuable.
Next steps ✨
After this page, most contributors continue with:
If you want the broader product surface:
One-line status 🌍
This folder holds community prompt assets that help turn atlas routing into repeatable prompt-based repair workflows.