dirien/yet-another-agent-harness / .claude/skills/agent-rules
agent-rules
FlaggedUse when creating or updating AGENTS.md files, .github/copilot-instructions.md, or other AI agent rule files, onboarding AI agents to a project, standardizing agent documentation, or when anyone mentions AGENTS.md, agent rules, project onboarding, or codebase documentation for AI agents.
assets/scoped/documentation.md
View on GitHub<!-- Managed by agent: keep sections and order; edit content, not structure. Last updated: {{TIMESTAMP}} -->
# AGENTS.md — {{SCOPE_NAME}}
<!-- AGENTS-GENERATED:START overview -->
## Overview
{{SCOPE_DESCRIPTION}}
<!-- AGENTS-GENERATED:END overview -->
<!-- AGENTS-GENERATED:START filemap -->
## Key Files
{{SCOPE_FILE_MAP}}
<!-- AGENTS-GENERATED:END filemap -->
<!-- AGENTS-GENERATED:START golden-samples -->
## Golden Samples (follow these patterns)
{{SCOPE_GOLDEN_SAMPLES}}
<!-- AGENTS-GENERATED:END golden-samples -->
<!-- AGENTS-GENERATED:START setup -->
## Setup & environment
- Documentation may use a static site generator (check for config files)
- Preview locally before committing major changes
- Check for broken links and formatting issues
<!-- AGENTS-GENERATED:END setup -->
<!-- AGENTS-GENERATED:START commands -->
## Building docs
- Preview: check for `npm run docs`, `make docs`, or similar
- Build: check for documentation build commands in root
- Serve locally to verify rendering
<!-- AGENTS-GENERATED:END commands -->
<!-- AGENTS-GENERATED:START structure -->
## Documentation structure
- `README.md` - Entry point, project overview
- `getting-started/` - Installation and quick start guides
- `guides/` - How-to guides and tutorials
- `reference/` - API documentation, configuration reference
- `architecture/` - Design documents, ADRs
- `contributing/` - Contribution guidelines
<!-- AGENTS-GENERATED:END structure -->
<!-- AGENTS-GENERATED:START code-style -->
## Code style & conventions
- Use clear, concise language
- Include code examples for technical concepts
- Keep line length reasonable (~80-120 chars for readability)
- Use consistent heading hierarchy (H1 for page title, H2 for sections)
- Add alt text to images for accessibility
- Use relative links for internal references
- Keep code examples up-to-date with actual codebase
<!-- AGENTS-GENERATED:END code-style -->
<!-- AGENTS-GENERATED:START markdown -->
## Markdown best practices
- Use fenced code blocks with language hints: ```python
- Use tables for structured data comparison
- Use admonitions for warnings/notes (if supported)
- Keep paragraphs focused on one idea
- Use bullet points for lists, numbered lists for sequences
<!-- AGENTS-GENERATED:END markdown -->
<!-- AGENTS-GENERATED:START security -->
## Security & safety
- Never include secrets, API keys, or credentials in examples
- Use placeholder values: `your-api-key`, `example.com`
- Review screenshots for sensitive information
- Avoid documenting security vulnerabilities in detail
<!-- AGENTS-GENERATED:END security -->
<!-- AGENTS-GENERATED:START checklist -->
## PR/commit checklist
- [ ] Documentation matches current code behavior
- [ ] Code examples are tested and work
- [ ] Links are valid (no 404s)
- [ ] Images have alt text
- [ ] Spelling and grammar checked
- [ ] Formatting renders correctly
<!-- AGENTS-GENERATED:END checklist -->
<!-- AGENTS-GENERATED:START examples -->
## Patterns to Follow
> **Prefer looking at real code in this repo over generic examples.**
> See **Golden Samples** section above for files that demonstrate correct patterns.
<!-- AGENTS-GENERATED:END examples -->
<!-- AGENTS-GENERATED:START help -->
## When stuck
- Check existing documentation for patterns
- Review the style guide (if one exists)
- Preview changes locally before committing
- Check root AGENTS.md for project conventions
<!-- AGENTS-GENERATED:END help -->
## House Rules (project-specific)
<!-- This section is NOT auto-generated - add your project-specific rules here -->
{{HOUSE_RULES}}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |