Automation & AI Agent Support
Glyx is building a layered automation story — from static discoverability to active tool calling — so that AI coding assistants can scaffold, configure, and extend Glyx apps on your behalf.
What exists today
glyx create scaffolding
glyx create <name> --template <template> generates a complete project in seconds. Templates: blank, notes, dashboard, settings. See CLI reference.
glyx generate plugin
Scaffolds a JS plugin file and prints the glyx.config.ts snippet to register it. See JS Plugins.
#[glyx_plugin] and #[glyx_command] macros
Rust proc-macros that generate the GlyxExtension impl from an annotated impl block. Native extension authors write async Rust functions and get JS-callable backend.* commands with zero boilerplate. See Native Extensions.
llms.txt and llms-full.txt
Machine-readable Glyx documentation for LLMs and AI crawlers.
/llms.txt(opens in a new tab) — framework summary, primitives, API surface table, capability reference, CLI commands, and links. Follows the llms.txt convention (opens in a new tab)./llms-full.txt(opens in a new tab) — full API reference in a single file: every native API with signatures, completeglyx.config.tsshape, plugin patterns, testing, and common error explanations. For LLMs that need a single-pass offline read.
Any AI coding assistant that encounters a Glyx project can index the framework from these files without relying on training data.
Claude Code skills
Every project scaffolded by glyx create includes .claude/SKILLS.md — Glyx-specific Claude Code (opens in a new tab) skills that let an AI agent work with your project without being briefed from scratch:
| Skill | What it does |
|---|---|
/add-capability | Adds a capability to glyx.config.ts and explains the implications |
/scaffold-component | Creates a component file wired to the design system |
/scaffold-plugin | Creates a JS plugin file and registers it in the config |
/explain-error | Explains a Glyx runtime error and suggests a fix |
The Glyx framework repo also has a contributor-level .claude/SKILLS.md with /add-binding, /add-capability-gate, /add-snapshot-stub, and /run-tests.
Skills use Claude Code's own file-editing tools — no server process required.
What's coming
@glyx-dev/mcp — MCP server
An MCP (Model Context Protocol) (opens in a new tab) server that exposes Glyx operations as callable tools for AI agents. Add it once to Claude Desktop, Cursor, Windsurf, or any MCP-compatible host:
{
"mcpServers": {
"glyx": { "command": "bunx", "args": ["@glyx-dev/mcp"] }
}
}Planned tools:
| Tool | Description |
|---|---|
glyx_get_docs | Returns the full API reference for a capability, component, or hook |
glyx_list_capabilities | Lists all capabilities with descriptions and the APIs they unlock |
glyx_create_project | Scaffolds a new project via glyx create |
glyx_read_config | Reads and parses the current project's glyx.config.ts |
glyx_add_capability | Adds or updates a capability in glyx.config.ts |
glyx_scaffold_component | Creates a boilerplate component file in src/components/ |
glyx_scaffold_plugin | Creates a plugin file and prints the registration snippet |
glyx_get_docs will work offline using a bundled docs snapshot, with a live fetch from glyx.dev when online.
Skills work without any server — Claude Code reads the SKILLS.md and uses its built-in file tools. The MCP server adds on top of that with callable tools that work across any MCP-compatible AI host, not just Claude Code.