guidance-promoter
Skill4 starsChanged 6 months agoMITView on GitHub
Use when user corrections, repeated AI failures, or session-state conclusions should be promoted into stable AI development guidance.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agent-feed.mdcCursor rule
- concept-reviewSkill
- design-reviewSkill
- docxSkill
- engineering-planningSkill
- frontend-designSkill
- guidance-promoterSkill
- project-architectureSkill
- project-developmentSkill
- project-fixSkill
- project-reviewSkill
- skill-creatorSkill
- skill-maintainerSkill
- specialist-routerSkill
- xlsxSkill
- concept-reviewSkill
- design-reviewSkill
- docxSkill
- engineering-planningSkill
- frontend-designSkill
- project-architectureSkill
- project-developmentSkill
- project-fixSkill
- project-reviewSkill
- skill-creatorSkill
- skill-maintainerSkill
- specialist-routerSkill
- xlsxSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 9 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill to turn user corrections and repeated AI development failures into stable project guidance.
- Distinctive: line 14
Use this skill when:
- Distinctive: line 27
Check existing rules, project/domain indexes, skills, README, and session-state before creating a new asset.
- Very specific: line 36
If the target is .agents/skills/, use .agents/skills/skill-maintainer/SKILL.md.
- Very specific: line 37
If the target is .agents/project/ or .agents/domain/, update the corresponding README recall index with owned boundary, read trigger, and …
- Very specific: line 38
If the change is still session-local, update .agents/session-state/<session_id>.json instead of stable docs.
- Distinctive: line 39
Run the relevant design review and verification gates before final handoff.
- Distinctive: line 43
Do not promote a one-off preference into reusable rules.
- Distinctive: line 44
Do not put project-specific facts into generic Agent Feed rules.
- Very specific: line 45
Do not put reusable AI workflow gates into .agents/project/ or .agents/domain/.
- Distinctive: line 46
Do not silently write durable guidance when the user only asked for read-only analysis.
- Distinctive: line 47
Do not preserve a user correction as transcript text.
- Very specific: line 48
When the correction reveals an external/custom skill gap, route through .agents/skills/specialist-router/SKILL.md or …
- Distinctive: line 52
When proposing or applying a promotion, report:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Guidance Promoter
Use this skill to turn user corrections and repeated AI development failures into stable project guidance.
Required Use
Use this skill when:
- The user corrects how the AI should work in this repository.
- The user says a rule, workflow, or conclusion should be remembered.
- A repeated failure appears across multiple turns.
- Session-state carry-forwards become stable enough to promote.
- The user asks to improve
.agents, AGENTS, rules, skills, or development protocol docs.
Workflow
- Identify what the user corrected, requested to remember, or showed through repeated failure.
- State the AI failure, missing source-of-truth, unclear trigger, or workflow gap it reveals.
- Decide whether the conclusion is durable guidance or only session-local state.
- Check existing rules, project/domain indexes, skills, README, and session-state before creating a new asset.
- Choose the owning asset:
.agents/rules/: reusable invariant, gate, or protocol constraint..agents/project/: repository-specific engineering constraint, source layout, verification, release, security, dependency, or delivery boundary..agents/domain/: stable project concepts, contracts, business rules, source-of-truth ownership, or durable domain facts..agents/skills/: repeatable task method with clear triggers and workflow steps..agents/session-state/<session_id>.json: active handoff fact that is useful now but not stable enough to promote.README.mdordocs/: user-facing capability, setup, command, or protocol explanation.
- Propose the target asset and exact change. Ask for confirmation when
.agents/rules/decision-gates.mdsays the change affects future development results, source-of-truth ownership, public behavior, protocol rules, verification, release, or product scope. - If the target is
.agents/skills/, use.agents/skills/skill-maintainer/SKILL.md. - If the target is
.agents/project/or.agents/domain/, update the corresponding README recall index with owned boundary, read trigger, and evidence expectation. - If the change is still session-local, update
.agents/session-state/<session_id>.jsoninstead of stable docs. - Run the relevant design review and verification gates before final handoff.
Guardrails
- Do not promote a one-off preference into reusable rules.
- Do not put project-specific facts into generic Agent Feed rules.
- Do not put reusable AI workflow gates into
.agents/project/or.agents/domain/. - Do not silently write durable guidance when the user only asked for read-only analysis.
- Do not preserve a user correction as transcript text; extract the repeatable rule, trigger, or source-of-truth boundary.
- When the correction reveals an external/custom skill gap, route through
.agents/skills/specialist-router/SKILL.mdor.agents/skills/skill-maintainer/SKILL.mdinstead of making the external skill authoritative.
Output
When proposing or applying a promotion, report:
- User feedback or repeated failure.
- Stable conclusion.
- Target asset.
- Why that asset owns it.
- Index or mirror updates required.
- Verification command.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

