← ClaudeAtlas

add-global-mode-targetlisted

Use when adding global mode support for one existing agentsmesh target from a target-structure/global-path doc. Covers contract extraction from docs, descriptor.global layout wiring, generator/import/reference-rewrite touchpoints, strict tests, docs updates, and final verification for one target at a time.
sampleXbro/agentsmesh · ★ 15 · AI & Automation · score 73
Install: claude install-skill sampleXbro/agentsmesh
## Purpose # Add Global Mode Target Use this skill when the task is to add global mode support for one existing target after you have a target-specific document that describes the native global file paths and behavior. Read `./references/global-mode-target-checklist.md` before editing code. Treat it as the minimum implementation and QA checklist. ## When To Use - The target already exists in `src/targets/<target>/` - You have a target doc with native global paths or global behavior - The repository-wide global-mode foundation already exists (`init|install|generate|import|diff|lint|watch|check|merge|matrix --global`) - The work is scoped to one target at a time ## Do Not Use This Skill For - Adding a brand-new target from scratch - Defining the shared global-mode architecture for the first time - Guessing a target's global behavior without a concrete doc or official source Use `add-agent-target` for new targets. Use this skill only for the per-target global-mode pass. ## Non-Negotiable Rules ### MUST - Start from the target doc and verify it against the live target implementation. - Treat current code as the source of truth for project-mode behavior; preserve it unless the target doc requires a change. - Write failing tests first for every new global-mode behavior. - Keep the change target-scoped. Do not scatter new target-specific branches through shared code if descriptor metadata can carry the behavior. - Add or update `descriptor.global` and keep project/global