console-ux SKILL.md skillA

console-ux from mikeheid/overture is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add mikeheid/overture/console-ux@git:20261020.f2abddc

Pins git:20261020.f2abddc in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: mikeheid/overture
Path: plugin/skills/console-ux/SKILL.md
Versions recorded: 8
Latest version: git:20261020.f2abddc, committed Oct 20, 2026
First version recorded: Oct 11, 2026
Size: 17,281 bytes
Repository stars: 5
License: MIT

Use when the owner console asks for a UX component - a visual request on a UX item (one whose section has a lane-ui or lane-ux segment). Designs and codes the component as a world-class UX designer and component engineer - accessible, psychologically sound, on-trend without being faddish - as ONE self-contained HTML document that works with no JavaScript, checks it with tools/ux_check.py, posts it with `agent.py visual`, and lands it by PR. Called by console-process for UX visual requests…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Design and build a UX component

You are two people at once:

- **The UX lead.** You know the great design systems, the laws of UX and
  WCAG 2.2 by heart. You know which trends will last and which are fads.
- **The component engineer.** You write semantic HTML and modern CSS that
  work with no script at all, and add a small, careful script only when the
  owner has allowed one.

What you post appears on the item, like any HTML visual, inside a sandboxed
frame beside earlier versions. When the owner **saves** a version (a
`ux-save`), you land it as `components/<item>.md` by pull request (step 7).
*(Planned, UX-VIEW.md step 2: the UX View modal the owner saves from.)*

Set up `KIT`, `STATE` and `A` as in the console-process skill: from the
user's registry only, and stop if this project is not registered there.

Your references:

- [references/checklist.md](references/checklist.md): the gate every
  version passes. **Read it every time.**
- [references/patterns.md](references/patterns.md): how the best design
  systems build each component, and the no-JavaScript recipe for each.
  Read **only the section for this component** and the platform table.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add mikeheid/overture/console-ux@sha256:dd3eb76c2b998329

The line at the top of this page pins the label git:20261020.f2abddc, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_higwcb77rtuhvv2t.svg)](https://markdownregistry.com/a/art_higwcb77rtuhvv2t)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 8 versions of this file, between Oct 11, 2026 and Oct 20, 2026, about one every day.

version	committed	commit	size	audit
git:20261020.f2abddc latest	2026-10-20	f2abddc	17,281 B	A	view · diff
git:20261019.b1f9dd6	2026-10-19	b1f9dd6	17,078 B	A	view · diff
git:20261011.c45190c	2026-10-11	c45190c	16,464 B	A	view · diff
git:20261011.4ee2ee4	2026-10-11	4ee2ee4	15,480 B	A	view · diff
git:20261011.b123dce	2026-10-11	b123dce	15,358 B	A	view · diff
git:20261011.7a28a9c	2026-10-11	7a28a9c	12,739 B	A	view · diff
git:20261011.d7c4731	2026-10-11	d7c4731	12,659 B	A	view · diff
git:20261011.80c85ef	2026-10-11	80c85ef	12,358 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (17281 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

mikeheid/overture · 5 stars · license MIT · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_higwcb77rtuhvv2t
GET https://markdownregistry.com/api/v1/resolve?ref=mikeheid/overture/console-ux
GET https://markdownregistry.com/api/v1/blob/dd3eb76c2b998329a646e784dda46dc98d55e270105329bbe6af067bee86f5b0

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.