How do I install the Instui Docs skill?

Run npx skillmds@latest add instructure/instui-docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Instui Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Instui Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Instui Docs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Instui Docs?

instructure (@instructure) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Instui Docs by instructure — Agent Skill

Name: Instui Docs
Author: instructure

Instui Docs

Look up authoritative Instructure UI (InstUI, @instructure/ui-*) documentation — component APIs, props, theme variables, usage examples, and guides — by querying instructure.design's plaintext docs. Use whenever the user asks how to use an InstUI component, which props/prop types exist, how to theme/style it, accessibility/i18n/RTL guidance, or which component fits a need. Prefer this over guessing InstUI APIs from memory.

instructure 82b38f3 2.0 KB Updated Sep 17, 2026

File contents

Instructure UI docs lookup

Instructure UI publishes its full docs as plaintext/markdown. Use it as the source of truth instead of recalling APIs from memory (they change across major versions).

Workflow

Fetch the index: WebFetch https://instructure.design/llms.txt It lists every component and guide with a one-line description and the exact markdown URL for each, grouped into User Guides, Components, Util Components, Contexts, and AI Components. Use it to find the relevant component/guide and its URL.
Fetch the specific page(s) using the URLs from the index. A component page contains examples, size/color/variant options, theme customization, guidelines (Do's/Don'ts/Accessibility), a props table, and install/import instructions. Fetch several in parallel when a question spans multiple components or a component + a guide.

Notes

The online docs track the latest published release. A consuming repo may be pinned to an older major where props/APIs differ — check its installed @instructure/ui* version. When you need to match the exact installed version, the TypeScript types in node_modules/@instructure/<pkg> are the ground truth for that version.
Components can be imported either from their individual package (@instructure/ui-<name>) or from the metapackage (@instructure/ui). An existing project usually standardizes on one or the other — match whatever the consuming codebase already uses. For a greenfield project, recommend the @instructure/ui metapackage.

---name: instui-docsdescription: Look up authoritative Instructure UI (InstUI, @instructure/ui-*) documentation — component APIs, props, theme variables, usage examples, and guides — by querying instructure.design's plaintext docs. Use whenever the user asks how to use an InstUI component, which props/prop types exist, how to theme/style it, accessibility/i18n/RTL guidance, or which component fits a need. Prefer this over guessing InstUI APIs from memory.---# Instructure UI docs lookupInstructure UI publishes its full docs as plaintext/markdown. Use it as the source of truth instead of recalling APIs from memory (they change across major versions).## Workflow1. **Fetch the index:** `WebFetch https://instructure.design/llms.txt` It lists every component and guide with a one-line description and the exact markdown URL for each, grouped into User Guides, Components, Util Components, Contexts, and AI Components. Use it to find the relevant component/guide and its URL.2. **Fetch the specific page(s)** using the URLs from the index. A component page contains examples, size/color/variant options, theme customization, guidelines (Do's/Don'ts/Accessibility), a props table, and install/import instructions. Fetch several in parallel when a question spans multiple components or a component + a guide.## Notes- The online docs track the **latest published release**. A consuming repo may be pinned to an older major where props/APIs differ — check its installed `@instructure/ui*` version. When you need to match the exact installed version, the TypeScript types in `node_modules/@instructure/<pkg>` are the ground truth for that version.- Components can be imported either from their individual package (`@instructure/ui-<name>`) or from the metapackage (`@instructure/ui`). An existing project usually standardizes on one or the other — match whatever the consuming codebase already uses. For a greenfield project, recommend the `@instructure/ui` metapackage.

Frequently asked questions