Typeui Agent Skill
Use TypeUI with Hermes Agent to access project design skills, brand kits, UI prompts, and layout variations through the TypeUI MCP server when creating or refining user interfaces.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/bergside/typeui --skill typeuiThe instruction itself
5 sections, as written by the authorTypeUI for Hermes Agent
Use this skill when the user wants Hermes Agent to build, redesign, or refine UI with TypeUI context.
What TypeUI Provides
- Project design skills for consistent visual direction.
- Brand kits with project name, logo, typography, and brand color tokens.
- UI prompt libraries for common interface sections and full-product flows.
- Layout variation guidance for producing better options before implementation.
How to Use TypeUI
- Prefer TypeUI MCP tools when they are available in the session.
- Ask the user which TypeUI project or design skill to use if the request does not specify one.
- Apply the selected project context before choosing colors, type, spacing, component tone, or page composition.
- Treat brand kit values as brand parameters only: logo, project name, typography, and brand colors.
- Treat the design skill as the source of UI style, component behavior, visual hierarchy, spacing, and interaction patterns.
MCP Server
This plugin package installs the TypeUI remote MCP server:
https://mcp.typeui.sh
If TypeUI tools are not available in the current Hermes session, install the MCP server with the plugin command:
hermes typeui install-mcp
hermes mcp login typeui
Hermes agents can also call typeui_install_mcp to write the TypeUI MCP server entry.
Prompt Examples
- Use my TypeUI project and build a landing page.
- Generate three pricing section variations with TypeUI.
- Redesign this dashboard using my TypeUI design skill.
- Pull the TypeUI context for this project before changing the UI.
Other skills for the same job
different authors, same section of the catalogue
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How to use it
Take bergside/typeui-typeui from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.