← ClaudeAtlas

aide-repo-maintenancelisted

How to add a new skill, update a shared rule, or change the 4-file spec structure in the Aide repo itself, and how install.sh/uninstall.sh must stay mirrored. Use when: adding or editing a skill or rule under core/, changing spec-structure.md, or touching install.sh/uninstall.sh. Do NOT use for: ordinary spec work (create/analyze/implement/archive) in any project Aide is installed into — this is about maintaining Aide's own source.
ragnarwestad/aide · ★ 0 · Code & Development · score 75
Install: claude install-skill ragnarwestad/aide
# Adding new functionality to Aide Moved out of `.claude/rules/development.md` (2026-08-31, /doctor check 4): this only matters when actually adding a skill, changing a rule, or changing the spec structure — not for ordinary spec work in this repo. ## New skill 1. Read `docs/SKILL_GUIDE.md` for structure and best practices 2. Create `core/skills/<name>/SKILL.md` with frontmatter and core instructions 3. Put heavy documentation in `core/skills/<name>/references/` 4. Add it to the SKILLS list in uninstall.sh 5. Run `cd implementations/claude-code && ./install.sh` ## Updating rules 1. Edit in `core/rules/` (shared source for all AI tools) 2. Run `core/scripts/build-agents-md.sh` (regenerates `core/AGENTS.md` AND `core/skills/spec-structure/SKILL.md`) 3. Run `implementations/claude-code/install.sh` (rules → `~/.claude/rules/`), `implementations/copilot/install.sh` and `implementations/codex/install.sh` (new AGENTS.md → `~/.copilot/` and `~/.codex/`) **Four of the nine rules are no longer rules (spec 147).** `workflows`, `documentation`, `tools-and-scripts` and `markdown-linting` are skills in `core/skills/` now, and `spec-structure` is a rule for Claude Code and a GENERATED skill for Codex/Copilot. The reason is a byte budget: Codex appends at most `project_doc_max_bytes` of AGENTS.md — 32768 by default — and drops the rest silently. At 64399 bytes the file was cut mid-testing.md and half of it never reached Codex at all, for a month, with nothing to say so. `test_core_s