# Neo

> Neo is a source-owned liquid-glass component system. Standards-based Web source is canonical; React is a maintained adapter. Use the catalog to discover components and each component manifest to retrieve files and requirements.

## Start here

- [Component catalog](https://neo.voorhees.dev/neo/catalog.json): Machine-readable component index, target support, and manifest URLs.
- [Neo MCP server](https://mcp.neo.voorhees.dev/mcp): Streamable HTTP tools: `list_components`, `get_component`, and `get_foundations`, backed by the evolving Neo catalog.
- [System overview](https://neo.voorhees.dev/docs/overview.md): Design principles, architecture, themes, and component inventory.
- [Agent adoption guide](https://neo.voorhees.dev/docs/agent-usage.md): How an agent should select, copy, adapt, and verify Neo source.
- [Interactive setup](https://neo.voorhees.dev/#components): Install the Neo skill, connect MCP, or copy a small Web/React starter from Install Neo.

## Reusable workflow

- [Neo skill](https://neo.voorhees.dev/skill/neo/SKILL.md): Optional Agent Skills-compatible workflow for repeated Neo adoption.
- [Neo skill package](https://neo.voorhees.dev/skill/neo-skill.zip): Complete project-installable skill directory, including MCP dependency metadata.
- [Target reference](https://neo.voorhees.dev/skill/neo/references/targets.md): Web canonical source and adapter selection rules.

## Notes

- `AGENTS.md` is project-local guidance. Neo provides a template, but it is not an installer or distribution format.
- Neo does not require a shadcn registry. A registry adapter can be added later for shadcn consumers without changing the canonical source model.
- The component catalog currently contains 40 source-backed components across surfaces, controls, navigation, overlays, feedback, data visualization, data display, and utilities.