TypeUI (OpenClaw Skill)
Injects project design skills, brand kits, UI prompts, and layout variation guidance from the TypeUI MCP server so AI agents produce better, on-brand interfaces.
Same as above, the OpenClaw platform adaptation, also connecting to the remote MCP server.
What does this skill do, and when should you use it?
TypeUI is an AI-first design platform by Bergside LLC, and this skill wires it into OpenClaw agents. Once installed, the agent can call the TypeUI remote MCP server when building, redesigning, or refining UI, pulling in project design skills, brand kits (project name, logo, typography, brand color tokens), UI prompt libraries, and layout variation guidance. The skill's core job is to steer the agent to apply TypeUI context before choosing colors, type, spacing, component tone, or page composition. Brand kit values are treated strictly as brand parameters, while the design skill governs UI style, component behavior, visual hierarchy, spacing, and interaction patterns. The remote MCP server lives at https://mcp.typeui.sh.
Instructs the agent to prefer TypeUI MCP tools when available; ask which TypeUI project or design skill to use when the request is ambiguous; apply brand kit values (logo, project name, typography, brand colors) as brand parameters only; treat the design skill as the source for UI style, component behavior, visual hierarchy, spacing, and interaction patterns; and install the remote MCP server via OpenClaw commands when tools are missing.
- A developer on OpenClaw wants the agent to generate a landing page grounded in their existing TypeUI project context
- A designer wants three pricing section variations generated at once to compare before implementation
- A team needs the agent to automatically apply brand colors, typography, and component tone when redesigning a dashboard
- A frontend engineer wants to pull the project's TypeUI design context before making UI changes for consistency
What are this skill's strengths and limitations?
- Clean separation of concerns: brand kits supply only brand parameters; the design skill governs style and interaction
- Remote MCP server works out of the box with a single OpenClaw command
- Prompt libraries and layout variation guidance encourage exploring multiple options before implementation
- Skill file is MIT licensed and explicitly open source
- Hard dependency on the hosted TypeUI service (https://mcp.typeui.sh); offline or outage renders the skill largely inert
- README marks the repo license as NOASSERTION, which conflicts with the SKILL.md MIT claim — verify before commercial use
- Real-world quality depends on TypeUI project configuration on the platform side; the source provides no benchmarks or test evidence
- Written for OpenClaw specifically; other agent platforms need their own MCP setup rather than this skill file
How do you install this skill?
The plugin package installs the TypeUI remote MCP server (https://mcp.typeui.sh). If TypeUI tools are not available in the current OpenClaw session, run: openclaw typeui install-mcp then openclaw mcp login typeui. Agents can also call typeui_install_mcp to write the MCP server entry. The broader repo can be installed with npx skills add (an exact install command for this specific skill name is not documented in the source).
How do you use this skill?
After the MCP server is connected, trigger it with plain-language prompts such as: "Use my TypeUI project and build a landing page", "Generate three pricing section variations with TypeUI", "Redesign this dashboard using my TypeUI design skill", or "Pull the TypeUI context for this project before changing the UI". If the request doesn't specify a project, the skill asks which TypeUI project or design skill to use first.