documentation-consistency
Skill10 starsChanged 12 days agoMITView on GitHub
Keeps Agent Landing Zone UI developer, user, and operator documentation aligned with shipped behavior. Use for features, configuration keys, security policy, deployment parameters, defaults, UI behavior, or breaking changes.
11 other projects use a version of this, 8 of them edited.
Adopted by
Most recently taken up by
- Azure/agent-app-mcpedited, first seen Nov 8, 2026
- Azure/gpt-rag-mcpedited, first seen Nov 2, 2026
- Azure/agent-app-ingestionedited, first seen Oct 30, 2026
- Azure/gpt-rag-ingestionedited, first seen Oct 30, 2026
- Azure/agent-app-orchestratoredited, first seen Oct 30, 2026
- Azure/gpt-rag-orchestratoredited, first seen Oct 30, 2026
Other versions11 projects use a version of this.
Word for word · 1
- Azure/gpt-rag-ui★ 10100% same
Edited · 8
- Azure/agent-landing-zone★ 1.2k27% same
- Azure/GPT-RAG★ 1.2k27% same
- Azure/agent-app-ingestion★ 18811% same
- Azure/gpt-rag-ingestion★ 18811% same
- Azure/agent-app-orchestrator★ 10721% same
- Azure/gpt-rag-orchestrator★ 10721% same
- Azure/agent-app-mcp★ 2212% same
- Azure/gpt-rag-mcp★ 2212% same
Wrote their own version · 2
- wallstop/unity-helpers★ 176same name
- Azure/bicep-ptn-aiml-landing-zone★ 19same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- architecture-decisionSkill
- component-releaseSkill
- engineering-principlesSkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
All application user, operator, and developer manuals are published from Azure/AI-Landing-Zones, main, docs/agent-landing-zone at
- Distinctive: line 19
Search local and central documentation for the feature, configuration key, endpoint, security requirement, UI term, and previous behavior.
- Distinctive: line 21
Update affected internal engineering guidance and entry-point links locally.
- Distinctive: line 22
Do not add local product manuals or redirect-guide stubs.
- Very specific: line 23
Update affected application manuals in Azure/AI-Landing-Zones on main.
- Distinctive: line 25
Keep the repository README concise and link to canonical documentation instead of duplicating application or platform guidance.
- Distinctive: line 27
Ensure examples match current defaults, supported auth modes, security boundaries, deployment modes, and accessibility behavior.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Landing Zone UI documentation consistency
All application user, operator, and developer manuals are published from
Azure/AI-Landing-Zones, main, docs/agent-landing-zone
at https://azure.github.io/AI-Landing-Zones/agent-landing-zone/.
This repository keeps concise entry-point links, internal contributor rules,
governance, security policies, ADRs, contracts, code comments, source examples,
and release metadata. Keep runtime ownership local. chainlit.md is an
intentional runtime presentation asset even when empty, not a product-manual
destination. Preserve it alongside public/, .chainlit/, and VERSION.
- Identify the developer, user, or operator behavior that changed.
- Search local and central documentation for the feature, configuration key, endpoint, security requirement, UI term, and previous behavior.
- Update affected internal engineering guidance and entry-point links locally. Do not add local product manuals or redirect-guide stubs.
- Update affected application manuals in
Azure/AI-Landing-Zonesonmain. Coordinate that change when the task does not authorize central edits. - Keep the repository README concise and link to canonical documentation instead of duplicating application or platform guidance.
- Ensure examples match current defaults, supported auth modes, security boundaries, deployment modes, and accessibility behavior.
- Report local and central documentation status in the implementation handoff.
A user-visible or operator-visible change is incomplete until documentation is updated or the search demonstrates that no published page is affected.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.