← ClaudeAtlas

agent-developing-agentslisted

AI agent development standards including frontmatter structure, naming conventions, tool access patterns, model selection, and reference documentation structure
wahidyankf/ose-primer · ★ 3 · AI & Automation · score 74
Install: claude install-skill wahidyankf/ose-primer
# Developing AI Agents Comprehensive guidance for creating AI agents following repository conventions. ## Core Requirements - Frontmatter: name, description, tools, model, color, skills - Name must match filename exactly - Non-empty skills field required ## File Operations in .claude/ and .opencode/ Directories Use the normal `Write` / `Edit` tools to create and modify files under `.claude/` and `.opencode/`. Both paths are pre-authorized in `.claude/settings.json` (`Write(.claude/**)`, `Edit(.claude/**)`, `Write(.opencode/**)`, `Edit(.opencode/**)`), so no approval prompts fire. `Bash` heredoc and `sed` remain appropriate for bulk mechanical substitutions across many files, but there is no restriction on direct edits. This applies to: - `.claude/agents/*.md` — agent definitions - `.claude/skills/*/SKILL.md` — skill files - `.claude/skills/*/reference/*.md` — skill reference modules - `.opencode/agents/*.md` — OpenCode agent mirrors - `.opencode/skills/*/SKILL.md` — Nx/OpenCode-native skill files (not mirrored from `.claude/skills/`; OpenCode reads `.claude/skills/` natively) After editing `.claude/` sources, run `npm run generate:bindings` so the `.opencode/` mirrors stay aligned. The pre-commit hook validates both formats. Those regenerated mirrors are part of your change: they belong on your touched-file ledger and MUST land in the **same commit** as the `.claude/` source that produced them, never a follow-up sync commit. Verify with `npm run validate:sync`; never