mirror of
https://github.com/onestardao/WFGY.git
synced 2026-05-01 21:11:11 +00:00
121 lines
3.1 KiB
Markdown
121 lines
3.1 KiB
Markdown
<!--
|
|
AI_NOTE_START
|
|
|
|
Document role:
|
|
This file explains what belongs in the community prompts folder.
|
|
|
|
How to use this file:
|
|
1. Read this page before adding any prompt-based repair or routing asset.
|
|
2. Use this page to decide whether your contribution is really a prompt contribution.
|
|
3. Use this page together with:
|
|
- [Community Fix Lab](../README.md)
|
|
- [Contribution Checklist](../../templates/contribution-checklist.md)
|
|
- [Prompt Template](../../templates/prompt-template.md)
|
|
|
|
What this file is:
|
|
- A folder-level guide for prompt packs
|
|
- A scope filter for route-aware prompt contributions
|
|
- A lightweight quality guide for reusable prompt assets
|
|
|
|
What this file is not:
|
|
- Not a random prompt dump
|
|
- Not a leaderboard for prompt tricks
|
|
- Not a replacement for atlas routing logic
|
|
|
|
Reading discipline for AI:
|
|
- Prompt assets here should remain subordinate to atlas routing.
|
|
- Do not treat community prompts as official frozen repair grammar.
|
|
|
|
AI_NOTE_END
|
|
-->
|
|
|
|
# Community Prompts
|
|
|
|
## Prompt packs, routing prompts, and repair-oriented prompt assets
|
|
|
|
This folder is for community-contributed prompts that help apply the atlas in practical workflows.
|
|
|
|
Typical contributions here include:
|
|
|
|
- route-first prompts
|
|
- repair-preview prompts
|
|
- boundary teaching prompts
|
|
- prompt comparisons between wrong-route and right-route behavior
|
|
- prompts that demonstrate atlas-first, WFGY-second workflow
|
|
|
|
---
|
|
|
|
## 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
|
|
|
|
---
|
|
|
|
## Suggested prompt contribution pattern
|
|
|
|
A useful contribution usually includes:
|
|
|
|
1. what case or family it targets
|
|
2. what the prompt is trying to improve
|
|
3. the prompt text
|
|
4. how to use it
|
|
5. expected result
|
|
6. known limits
|
|
|
|
That is enough to make a prompt pack usable.
|
|
|
|
---
|
|
|
|
## Suggested naming style
|
|
|
|
Examples:
|
|
|
|
- `f1-regrounding-prompt-pack-v1.md`
|
|
- `f5-trace-first-prompt-pack-v1.md`
|
|
- `f7-container-tightening-prompt-pack-v1.md`
|
|
|
|
Use names that reveal both the family and the action.
|
|
|
|
---
|
|
|
|
## Before contributing
|
|
|
|
Please read:
|
|
|
|
- [Community Fix Lab](../README.md)
|
|
- [Contribution Checklist](../../templates/contribution-checklist.md)
|
|
- [Prompt Template](../../templates/prompt-template.md)
|
|
- [Family Fix Surface v1](../../official/family-fix-surface-v1.md)
|
|
- [Atlas to WFGY Bridge v1](../../official/atlas-to-wfgy-bridge-v1.md)
|
|
|
|
---
|
|
|
|
## One-line status
|
|
|
|
**This folder holds community prompt assets that help turn atlas routing into repeatable prompt-based repair workflows.**
|