agent-skills
AGENTS.md3 starsChanged 8 days agoMITView on GitHub
docs/architecture/, quickstart.md and current product decisions own self-contained Skill use and maintenance truth. Author semantic composition diagrams as .puml under docs/architecture/diagrams/ and regenerate tracked .svg projections with bash scripts/render-diagrams.sh; do not edit generated SVG by hand. Reader-facing decision maps use .dot sources under docs/architecture/diagrams/decisions/ and SVG projections under docs/architecture/generated/decisions/; render them with bash scripts/render-decision-diagrams.sh. Decision Guidance maps each diagram to its owning Skill or method. These maps explain conditional choices, not a required agent workflow or executable acceptance contract; do…
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- analyze-projectSkill
- api-contract-strategySkill
- architecture-patternsSkill
- close-changeSkill
- design-changeSkill
- development-standardsSkill
- docker-multiarch-buildSkill
- error-patternsSkill
- go-guidelinesSkill
- herdr-implementSkill
- implement-changeSkill
- logging-standardsSkill
- lua-guidelinesSkill
- organize-docsSkill
- output-stylesSkill
- plan-changeSkill
- powershell-guidelinesSkill
- python-guidelinesSkill
- review-changeSkill
- review-designSkill
- review-implementationSkill
- review-planSkill
- routeros-scripting-guidelinesSkill
- runtime-diagnosisSkill
- security-guardrailsSkill
- shell-guidelinesSkill
- skill-authoringSkill
- skill-minerSkill
- skills-routingSkill
- smart-commitSkill
- sops-age-guardrailsSkill
- sync-truthSkill
- testing-strategySkill
The file
Files
Product Documentation
docs/architecture/, quickstart.md and current product decisions own self-contained Skill use and maintenance truth. Author semantic composition diagrams as .puml under docs/architecture/diagrams/ and regenerate tracked .svg projections with bash scripts/render-diagrams.sh; do not edit generated SVG by hand.
Reader-facing decision maps use .dot sources under docs/architecture/diagrams/decisions/ and SVG projections under docs/architecture/generated/decisions/; render them with bash scripts/render-decision-diagrams.sh. Decision Guidance maps each diagram to its owning Skill or method. These maps explain conditional choices, not a required agent workflow or executable acceptance contract; do not make their labels or edges CI assertions.
Shared boundaries and all new designs/plans belong to $AGENT_ARCHITECTURE_DIR/docs/; use its plans/skills/ and evaluations/skills/ domains for this product. Historical originals live in its archived/agent-skills/ tree. Product checks must not require these external records or local docs/plans files.
Default search here covers product truth. Honor the architecture owner's search boundary when reading stage artifacts, using explicit paths and rg --no-ignore. Git tracking and search exclusion are distinct. Preserve product rationale, exceptions and compatibility obligations; do not copy the shared architecture explanation back into this tree.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

