← ClaudeAtlas

target-instructions-bootstraplisted

Create the target repository's local AI instruction scaffold during first-use bootstrap. Use from repo-init-scan when `.github/instructions`, runtime adapters such as `AGENTS.md` / `CLAUDE.md`, or the neutral project facts scaffold are missing. Do not use to overwrite existing project-specific rules.
funky-eyes/best-copilot · ★ 10 · AI & Automation · score 79
Install: claude install-skill funky-eyes/best-copilot
# Target Instructions Bootstrap Use this skill during `repo-init-scan` when target-local instruction entrypoints are missing. It may create a neutral `.github/instructions/project.instructions.md` scaffold, but that scaffold is not enough to pass initialization until `repo-init-scan` replaces the neutral markers with bounded repository facts or bounded-scan `unknown` gaps, updates the `## Init Status` record, and writes the root `best-copilot.md` version sentinel after full verification. ## Boundary - Write into the target repository, never into the installed plugin package or plugin cache. - Create missing files only. If a file exists, preserve it and append only a clearly compatible missing section. - Do not copy this plugin repository's instruction files or active workflow state into the target repository. Generate only the neutral target-local scaffold below. - Do not overwrite project-specific rules, language policy, build commands, or existing `AGENTS.md` / `CLAUDE.md`. - Keep generated files short. They are routing and safety scaffolds, not a full manual. - Keep generated files runtime-neutral across Copilot CLI, Claude Code, VS Code Copilot, and Codex. If a runtime-specific command is mentioned, label it as runtime-specific. - Do not generate, require, or assume plugin hooks, local scripts, Python, Node, shell, or other interpreter-based closeout enforcement. The native-ask and closeout gates must be self-contained instruction text because target repositories may n