skills/per-repo-conventions/SKILL.md
Use when starting work in any repository, and again at each work-phase transition (design, coding, debugging, verification, opening a PR). Loads the canonical per-repo-conventions guidance from foundation:docs/PER_REPO_CONVENTIONS.md — the discovery pattern for AGENTS.md, PR templates, CONTRIBUTING.md, and contextual files (PRINCIPLES.md, SMOKE_TESTS.md, KNOWN_ISSUES.md), plus the re-read cadence and verification gradient.
npx skillsauth add microsoft/amplifier-foundation per-repo-conventionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Before writing code, debugging, verifying, or opening a PR in any repository, discover and honor that repo's local conventions. You are a guest — read the house rules before changing the furniture.
Read foundation:docs/PER_REPO_CONVENTIONS.md and follow it. Re-read the
relevant parts at each major shift in what you are doing (design →
implementation, investigation → fix, coding → verification → PR): earlier reads
fall out of context, and each file reads differently through the lens of the
current objective.
That document is the single source of truth. It covers discovery order (repo
root + subdirectory walk, most-specific-wins), the always-loaded files
(AGENTS.md, .github/PULL_REQUEST_TEMPLATE.md, CONTRIBUTING.md,
README.md), the contextual files (PRINCIPLES.md, SMOKE_TESTS.md,
KNOWN_ISSUES.md), when to read and re-read them, the verification gradient,
and author guidance.
tools
Use when creating a new Amplifier module (tool, hook, orchestrator, context, or provider). Covers the mount() contract, protocol compliance validation, placeholder patterns, and the module directory structure. Prevents the common mistake of creating no-op mount() stubs that fail protocol_compliance validation.
tools
Use when creating a new Amplifier module (tool, hook, orchestrator, context, or provider). Covers the mount() contract, protocol compliance validation, placeholder patterns, and the module directory structure. Prevents the common mistake of creating no-op mount() stubs that fail protocol_compliance validation.
testing
Convention for the v3 bundle documentation system: a single bundle.dot + bundle.png per repo, generated by bundle_repo_dot(). Use when generating, validating, or interpreting bundle documentation files. Covers 7-cluster DOT structure, token cost model, color conventions, external reference distinction, freshness tracking via source_hash, generation recipes, and the lifecycle model.
tools
Use when creating a new Amplifier module (tool, hook, orchestrator, context, or provider). Covers the mount() contract, protocol compliance validation, placeholder patterns, and the module directory structure. Prevents the common mistake of creating no-op mount() stubs that fail protocol_compliance validation.