Install
Use the Helios MCP tools to select a component, read its props and dependencies, and retrieve its source. Source examples run the same export shown in Preview.
MCP setupWhat’s inside
Download agent instructionsWhat’s included
Project instructions
helios-ui-agent-instructions.mdReusable guidance for inspecting source, composing shared exports and checking behavior.
Component source
react/sources.jsonThe editable TSX, CSS and supporting source included in the local package.
Typed props
react/canonical-registry.jsonActual public prop types generated from the React implementation.
Semantic tokens
foundation-tokens.jsonPreviously resolved Helios foundations and their values.
Implementation APIs
MCP component metadataUse get_component to inspect fixture props and callback APIs before integrating.
Where it goes per client
Review the downloaded guidance and add the relevant parts to your project’s own agent instructions. These examples are project files; this page does not install or change any global skill.
Keep project guidance in CLAUDE.md at the application root. Connect the source tools separately through MCP.
Add the reviewed guidance as a project rule in Cursor’s Rules settings. Scope it to the application that consumes Helios UI.
For GitHub Copilot project instructions, merge the reviewed guidance into .github/copilot-instructions.md. Preserve the project’s existing instructions.
Merge the reviewed guidance into the target application’s AGENTS.md. Keep its existing build, test and authorization rules.
Attach the Markdown as project context using your client’s supported instruction mechanism. Configure MCP separately to retrieve current implementation files.
Instructions and MCP serve different roles
The downloadable Markdown records implementation guidance. It does not install a global skill or an MCP server. Add the reviewed guidance to the target project’s own agent instructions if appropriate. MCP supplies versioned source, props, dependency and token data from this checkout.
Updating
Re-download and review the instruction file when the library changes. Keep project-specific authorization and backend rules in that project. This website does not change your agent configuration or grant permission to edit Figma, enable a provider, or deploy an application.