| .. | ||
| colab-template.md | ||
| contribution-checklist.md | ||
| fix-recipe-template.md | ||
| json-template.json | ||
| prompt-template.md | ||
| README.md | ||
Templates Hub 🧩
Problem Map 3.0 Troubleshooting Atlas
Reusable templates for community fix contributions
This folder contains the reusable templates for the community fixes layer.
Its job is simple:
help contributors submit clearer, smaller, more reviewable fix assets
These templates are here to reduce chaos and make it easier to grow the fix ecosystem.
What this folder is for
Use this folder when you want to create a new community contribution such as:
- a fix recipe
- a prompt pack
- a Colab notebook
- a JSON fixture
- a workflow example
- a reproduction pack
If you are not sure where to start, start here.
Recommended reading order
Before using a template, read:
Then choose the right template below.
Available templates
1. Contribution Checklist
Use this first.
This file helps you check whether your contribution is:
- clear
- scoped
- routed
- usable
- honest about limits
2. Fix Recipe Template
Use this when your contribution is mainly a repair recipe.
Good for:
- first repair move writeups
- small runnable fix notes
- workflow repair guides
- practical repair instructions
3. Prompt Template
Use this when your contribution is mainly prompt-based.
Good for:
- system prompts
- user prompts
- routing prompts
- repair-first prompts
- trace-exposure prompts
4. Colab Template
Use this when your contribution is mainly notebook-based.
Good for:
- Colab demos
- repair notebooks
- before / after notebook comparisons
- benchmark rerun notebooks
5. JSON Template
Use this when your contribution needs structured machine-readable data.
Good for:
- fixtures
- baseline inputs
- expected outputs
- evaluation packs
- demo configs
Which template should I use
Use this quick guide.
If your main asset is text guidance
Use:
If your main asset is a prompt
Use:
If your main asset is a notebook
Use:
If your main asset is structured data
Use:
If your contribution mixes several asset types, choose the main one first, then attach the others as supporting files.
Minimum good contribution rule
A good contribution usually has:
- routing context
- one clear problem
- one useful artifact
- short usage instructions
- expected result
- one misrepair warning
- honest limitations
That is enough to be useful.
What not to do
Please do not use these templates to submit:
- giant vague idea dumps
- unstructured logs
- random files with no routing context
- prompt collections with no explanation
- notebooks with no before / after logic
- JSON files with no meaning
The goal is structured growth, not file pile-up.
Relationship to official fixes
These templates are for the community layer.
Official fix documents live in:
Community assets can be very valuable, but they do not automatically become official atlas guidance.
That distinction should stay clear.
One-line status
This folder contains the reusable templates that help community fix contributions stay structured and reviewable.
Closing note ✨
If the atlas is going to grow through the community, it needs good templates.
That is what this folder is for.