Start with a prompt
Copy the text below into your coding agent, then replace the final line with your task. Your agent needs a web-fetch or HTTP tool. Reading the site needs no login, API key, or client connection. The prompt directs your agent to review and install the current skill, or update the one already in your repository, before implementing your task. No executable installer is needed to read the docs or save the skill. Normal app dependency setup still applies; follow your repository's package manager, lockfile, and approval rules.
Use CoreAI for my UI task. First check https://microsoft.github.io/coreai-design-system/version.json, then fetch and review https://microsoft.github.io/coreai-design-system/source/package/SKILL.md. Install it at .github/skills/coreai-ds-fluentui-react/SKILL.md, or update the existing CoreAI skill to the latest published version, before implementing. Preserve repository-specific rules, do not downgrade newer local guidance, and ask before resolving conflicts. Follow the updated skill, read only relevant Markdown pages from https://microsoft.github.io/coreai-design-system/llms.txt, and check my installed package versions. Use @coreai-ds/react-components; templates are copy-and-adapt source. Report retrieval or write failures; do not invent APIs.
My task: [describe the UI you want to build or change]
What the agent reads
The documentation index lists page purposes and current package versions. The small version manifest identifies the shared docs/skill version and the documented package version independently. Each human page has a Markdown counterpart with the same guidance, API summaries, and complete example source. For example, the Button page is available as Markdown.
The agent workflow explains targeted retrieval, version checks, templates, and validation. The machine-readable index adds exact paths, source links, API members, and provenance.
Keep the repository skill current
The agent skill is the persistent entry point for CoreAI tasks. Its description and metadata carry its docs/skill version and the documented package version. Before each task it checks whether newer published guidance is available; an older npm package may contain an older skill.
Review the skill before saving it. The starter prompt authorizes that skill's installation or update, not changes to unrelated repository instructions. Preserve local rules and adapters; ask before resolving conflicts or when the client requires approval. If fetching or saving fails, the agent must report it and ask how to proceed instead of silently skipping setup.
Privacy and limitations
These are public, read-only static files. Fetching a page does not require sending your source code, prompts, or credentials to this site. Your agent provider and HTTP client have their own data policies.
The site hosts only the current docs/skill release and its documented package version. Agents must compare that package version with your installed packages, report unavailable pages, and test adapted code in your app. The skill is guidance, not an enforcement mechanism or a guarantee of correctness.