Component States

Organization

KyaniteLabs

component-states

State matrix for interactive UI. Use when building or reviewing buttons, links, inputs, tabs, toggles, menus, cards, or controls that need hover, focus, active, disabled, loading, selected, error, keyboard, or ARIA states.

Overview

Publisher	KyaniteLabs
Repository	`tastecheck`
Skill name	`component-states`
Stars	10
Forks	7
Bundled files	4
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
4 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by KyaniteLabs on GitHub. Read the source before you install it.

Installation

Install the Component States AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/KyaniteLabs/tastecheck/tree/main/skills/component-states
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/KyaniteLabs/tastecheck.git /tmp/tastecheck
mkdir -p .claude/skills
cp -r /tmp/tastecheck/skills/component-states .claude/skills/component-states

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Component States in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Component States on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Component States is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Component States

An interactive control is a lifecycle, not a resting style. Map applicable states to semantics, visible treatment, and recovery.

Decision order and evidence

Name role, interaction model, owner, and applicable states.
Give each state ARIA/DOM mapping, visible non-color treatment, trigger, and recovery.
Test keyboard, focus-visible, contrast, reduced motion, and async completion.

Report one evidence row per state; n/a needs a subject-absence reason. Hand field validation to form-ux, emptiness to empty-states, and missing tokens back as gaps, never fallbacks.

Async/destructive controls

Name one semantic owner; visual states only present its lifecycle.

State / event	Guard and observable contract
`ready` / invoke	Click, Enter, Space, and script use one route; accepted work creates a request key.
`confirming`	Use only for irreversible/broad/cascading work; name consequence, move focus in, restore invoker on cancel.
`submitting`	Create key before dispatch; reject duplicates; expose disabled/busy and working label.
matching completion	Only matching key settles work; stale results cannot clear busy, alter target, or move focus.
success / failure	Record data first; confirm locally and choose focus, or retain context with nearby error/retry/cancel.

Test real and stale/failed completion. If success empties a region, hand it to empty-states.

State matrix

Account for these states where applicable:

State	Trigger	Must communicate	CSS
Default	rest	"this is here / interactive"	base styles
Hover	pointer over	"you can interact" (pointer devices only)	`:hover`
Focus	keyboard tab / programmatic	"this is where you are" (keyboard)	`:focus-visible`
Active / pressed	during click/tap	"your action registered"	`:active`
Disabled	not available	"not available, and why"	`:disabled` / `[aria-disabled]`
Loading	async in progress	"working, wait"	a `data-loading` / `aria-busy` class
Selected / current	chosen / active page	"this is the active one"	`[aria-selected]`/`[aria-current]`
Error / invalid	failed validation	"something's wrong here"	`[aria-invalid]`

The first five baseline any control; add selected and error where applicable.

Non-negotiables

Never ship default-only: applicable states need semantics and non-color signals.
Never remove a focus outline without an equally visible replacement; hover is not focus.
Explain unavailability; a silent disabled submit is a form-ux failure.
Async controls prevent duplicate dispatch, expose busy state, and preserve contrast (≥3:1 UI, ≥4.5:1 text); feedback is fast and reduced-motion-safe.

Implementation starter

Read assets/states-starter.css for tokenized CSS/reduced-motion details. A missing token is a gap, never a fallback hex; add the request guard before styling async work.

State by component

Button/link: default, hover, focus-visible, active, disabled/loading as applicable; toggles use aria-pressed; links retain non-color/visited cues.
Toggle / switch: use role="switch" (not role="checkbox") with aria-checked; Space toggles, Tab moves focus. Example: <button role="switch" aria-checked="true">Notifications</button>. Screen readers announce "switch, on/off" instead of "checkbox, checked."
Fields: focus, disabled, filled/readonly, error, selected/open/checked states; style a correctly labelled focusable input (form-ux owns validation).
Navigation/list/menu: current/selected uses aria-current/aria-selected; pointer and keyboard focus are equally legible.
Overlays: model open/closed and entry/exit; prefer native Popover/<dialog>; toasts use role="status"; hover-only content remains focus-reachable.

Reference files

references/states.md — state semantics, pitfalls, ARIA pairings.
references/decision-records.md — novel-case ADR rules.

Self-check (per interactive element)

For each applicable state, confirm visible focus, semantics, non-color contrast, and reduced-motion behavior. For async/destructive work confirm owner, guard, justified confirmation, duplicate prevention, recovery, and final focus; exercise real and stale/ failed completion separately. Do not collapse controls into one checkmark.

How to deliver

Deliver applicable matrix and lifecycle evidence. Pair with form-ux, empty-states, micro-motion, a11y-pass, and color-system at their boundaries.

Contract (generated)

Canonical detail: contract.json.

Route: A control has interaction states missing or inconsistent with its semantics. (+1 in contract.json); avoid: The request is only about form copy or validation timing. (+1 in contract.json)
Exclude: Do not invent page-level empty states or validation policy. (+2 in contract.json)
Stop / handoff: Stop when the component semantics or interactive states cannot be identified. (+2 in contract.json); receives [design-system-interview, empty-states, improve-existing-website, responsive-layout, spacing-system, tasteroll, theming] -> sends [form-ux, empty-states, a11y-pass, micro-motion, tastecheck-pass]
Output: component lifecycle contract and implementation guidance
Evidence: table_with_evidence with status, reason, remediation, evidence, provenance.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Component States AI skill do?

Why use Component States on TypingMind?

Because you install it once and use it with any model. Component States is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Component States in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/KyaniteLabs/tastecheck/tree/main/skills/component-states. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Component States?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Component States?

As many as you like. As long as a model supports skills, you can use Component States with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Component States AI skill free?

Yes. It is published on GitHub by KyaniteLabs under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Canvas

openclaw

OrganizationPopular

Present hosted widget documents on a connected macOS panel and control panel visibility or navigation.

Diagram Maker

Create SVG/HTML or Excalidraw diagrams for concepts, architecture, flows, and whiteboards.

Grill With Docs

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Grill Me

A relentless interview to sharpen a plan or design.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Component States

Decision order and evidence

Async/destructive controls

State matrix

Non-negotiables

Implementation starter

State by component

Reference files

Self-check (per interactive element)

How to deliver

Contract (generated)

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now