nessar
bb8d09dda4
- Created SKILL.md and SKILL-MECHANICS.md for writing agent skills. - Added openai.yaml for agent interface configuration. - Introduced AGENTS.md for agent skills overview. - Established CONTEXT.md for personal leave planning terminology. - Documented ordered heuristic optimization in ADRs. - Defined personal client-side planner limitations in ADRs. - Created domain documentation for engineering skills. - Added issue tracker guidelines for GitLab. - Mapped triage labels for issue tracking. - Initialized skills-lock.json to manage skill dependencies.
33 lines
1.9 KiB
Markdown
33 lines
1.9 KiB
Markdown
# RESOURCES.md Format
|
|
|
|
`RESOURCES.md` is the curated set of trusted sources for this topic. Knowledge for explainers should be drawn from here, not from parametric guesses. Wisdom comes from the communities listed here.
|
|
|
|
## Structure
|
|
|
|
```md
|
|
# {Topic} Resources
|
|
|
|
## Knowledge
|
|
|
|
- [Book: _The Science and Practice of Strength Training_ — Zatsiorsky & Kraemer](https://example.com)
|
|
Foundational text on programming and adaptation. Use for: anything to do with periodisation, recovery, intensity zones.
|
|
- [Article: "How Much Should I Train?" — Greg Nuckols (Stronger By Science)](https://example.com)
|
|
Evidence-based review of volume landmarks. Use for: weekly set targets per muscle group.
|
|
|
|
## Wisdom (Communities)
|
|
|
|
- [r/weightroom](https://reddit.com/r/weightroom)
|
|
High-signal subreddit, moderated against bro-science. Use for: programme critique, plateau troubleshooting.
|
|
- Local: Tuesday strength class at {gym name}
|
|
Use for: real-time coaching feedback on lifts.
|
|
```
|
|
|
|
## Rules
|
|
|
|
- **High-trust only.** Prefer primary sources, recognised experts, peer-reviewed work, and communities with strong moderation. If a resource is marketing dressed as education, leave it out.
|
|
- **Annotate every entry.** A bare link is useless in three months. Add one line: what it covers and when to reach for it.
|
|
- **Group by Knowledge / Wisdom.** Mirrors the philosophy in [SKILL.md](./SKILL.md). It is fine for a resource to appear in only one group.
|
|
- **Surface gaps explicitly.** If no good resource exists for an area the mission needs, write a `## Gaps` section listing what is missing. This drives future search.
|
|
- **Prune ruthlessly.** A resource that turned out to be wrong, shallow, or off-mission should be removed, not buried. Better five sharp sources than thirty mediocre ones.
|
|
- **Record community preferences.** If the user has opted out of joining communities, note it here so future sessions don't keep proposing them.
|