For the complete documentation index, see llms.txt. Markdown variants are available by appending .md to any URL or sending an Accept: text/markdown header. An agent skill is available at /.well-known/agent-skills/site-skill.md.
FrakmentFrakment

Agents

What an AI agent sees when it builds with Frakment. Real MCP tool calls, real responses, no hand-waving.

Frakment ships an MCP server and an agent skill. Agents can compose, install, and use the registry without a human in the loop.

The workflow

Agent calls compose with a scenario name

MCP returns the components that fit that UI pattern.

Agent calls get_install_command with the primary component

MCP returns the npx command that installs it and pulls its registryDependencies.

User runs one command

The rest lands automatically. No manual dependency resolution, no guessing slugs.

Chat UI

Prompt: "Build a chat interface with auto-scroll"

The agent calls compose:

json
{
  "tool": "compose",
  "arguments": { "scenario": "chat" }
}

MCP responds:

# chat
Chat interface with auto-scroll and animated turns
 
Components: bubble, message, message-scroller, avatar, message-animated
 
Install: npx frakment@latest add message-animated

The agent calls get_install_command:

json
{
  "tool": "get_install_command",
  "arguments": { "name": "message-animated" }
}

MCP responds:

$ npx frakment@latest add message-animated

That single command pulls bubble, message-scroller, and the AI engine via registryDependencies.

Agent timeline

Prompt: "Build an agent timeline with reasoning steps"

The agent calls compose:

json
{
  "tool": "compose",
  "arguments": { "scenario": "agent-timeline" }
}

MCP responds:

# agent-timeline
Agent reasoning timeline with status and command output
 
Components: trace, code-block, chain-of-thought, pulse
 
Install: npx frakment@latest add trace code-block

The agent calls get_install_command:

json
{
  "tool": "get_install_command",
  "arguments": { "name": "trace" }
}

MCP responds:

$ npx frakment@latest add trace code-block

trace pulls code-block as a registry dependency. Add chain-of-thought and pulse separately.

Login form

Prompt: "Build an accessible login form"

The agent calls compose:

json
{
  "tool": "compose",
  "arguments": { "scenario": "login-form" }
}

MCP responds:

# login-form
Accessible login form with remember-me toggle
 
Components: field, label, input, button, checkbox
 
Install: npx frakment@latest add field

The agent calls get_install_command:

json
{
  "tool": "get_install_command",
  "arguments": { "name": "field" }
}

MCP responds:

$ npx frakment@latest add field

field pulls label and separator. Add input, button, and checkbox separately.

All scenarios

ScenarioWhat you getEntry
chatChat UI with auto-scroll, avatar, and animated turnsmessage-animated
agent-timelineReasoning timeline with status, pulse, and command outputterminal
login-formAccessible form with field, label, input, button, and checkboxfield
settings-panelSettings view with toggles, grouped options, and separatorstoggle-group
search-inputSearch field with inline button and loading stateinput-group
status-dashboardService health overview with daily timeline and badgespulse

Call list_scenarios with no input to get the current set. The tool is the source of truth so the list stays current.

Connect your agent

See MCP server for the stdio config and the full tool list. See Skills for the load-on-demand skill that teaches agents when to use the registry.