add-resource-path-conventionlisted

# Resource Path Convention <!-- uses: - command: /add.wiki --> Commands and skills in `framwork/.codeadd/` are the source of truth. After build, they are placed in provider-specific directories (`.claude/commands/`, `.agents/skills/`, `.gemini/commands/`, etc.). Hardcoded `.codeadd/commands/` or `.codeadd/skills/` paths break because these directories do not exist in the installed project. Use build-time variables to reference resources. ## When to Use - Writing a command that references another command (e.g., add.plan-to-ready naming add.done) - Writing a command or skill that references a skill file - Reviewing existing commands/skills for broken path references - Creating new commands via `/add.make` ## When NOT to Use - Referencing scripts (`.codeadd/scripts/*.sh` is always correct — fixed path) - Referencing project files outside the framework (`docs/`, `src/`, etc.) - Writing code in `build.js` or `cli/` (these operate on the build/install pipeline, not agent runtime) ## Variables Build-time variables are available. `build.js` replaces them with the correct provider path during build. ### `{{cmd:NAME}}` Resolves to the full path of a command file for the target provider. ``` {{cmd:add.plan}} # Claude → .claude/commands/add.plan.md # Gemini → .gemini/commands/add.plan.toml ``` ### `{{skill:NAME/FILE}}` Resolves to the full path of a skill file. Use `SKILL.md` for the main file, or any sub-file name. ``` {{skill:add-backend-development/SKILL.md}} # Claude