typeui-fundamentals SKILL.md skillA

typeui-fundamentals from bergside/typeui is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add bergside/typeui/typeui-fundamentals@git:20260615.6a4ad36

Pins git:20260615.6a4ad36 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
bergside/typeui
Path
skills/fundamentals/SKILL.md
Versions recorded
3
Latest version
git:20260615.6a4ad36, committed Jun 15, 2026
First version recorded
May 19, 2026
Size
3,476 bytes
Repository stars
2,262
License
a license file GitHub does not identify

Universal UI/UX design principles covering visual hierarchy, interaction laws, typography foundations, and WCAG accessibility requirements. Use when making design decisions not covered by a specific design system, validating principle compliance, or resolving conflicts between aesthetics and accessibility. Design-system-agnostic and applies to every surface.

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 Fundamentals — Agent Instructions

Universal design principles that define **why** patterns work, **how** to apply them correctly, and **what** accessibility requirements are non-negotiable. These are timeless, design-system-agnostic foundations that apply to every surface regardless of vertical or workflow phase.

## Load order

Read these files **after** loading the design system (`SKILL.md` / `DESIGN.md` + token modules). The design system tells you *what* token to use; these files explain *why* that decision is correct and *how* to avoid common principle violations.

## Module index

| File | Purpose |
|---|---|
| [ui-principles.md](ui-principles.md) | Universal visual design principles — hierarchy, layout rhythm, typography placement, color theory, depth & layering, interaction design, responsive adaptation, component behavior |
| [spacing-principles.md](spacing-principles.md) | Spacing-specific principles — 4-point grid, proximity grouping, inner vs outer gaps, vertical and horizontal rhythm, heading→paragraph spacing, section and component spacing tiers |
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lf4etsa6yuaz2r7p/af01b69d592b2294093b94c376617836961b28a0ba21d9c080241c189422b32e.json

Then /plugin install typeui-fundamentals@markdownregistry-lf4etsa6yuaz2r7p in Claude Code. It installs git:20260615.6a4ad36, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add bergside/typeui/typeui-fundamentals@sha256:af01b69d592b2294

The line at the top of this page pins the label git:20260615.6a4ad36, 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 badge

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

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

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in bergside/typeui/typeui-fundamentals since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of typeui-fundamentals from somewhere else? Ask it: where did my typeui-fundamentals come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 3 versions of this file, between May 19, 2026 and Jun 15, 2026, about one every 14 days. Its first recorded version is graded B and its latest A.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260615.6a4ad36 latest2026-06-15 6a4ad36 3,476 BA view · diff
git:20260519.c972abb2026-05-19 c972abb 3,239 BA view · diff
git:20260519.364799c2026-05-19 364799c 2,879 BB view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

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 (3476 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

bergside/typeui · 2,262 stars · license a license file GitHub does not identify · pushed 2026-10-22 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_lf4etsa6yuaz2r7p
GET https://markdownregistry.com/api/v1/resolve?ref=bergside/typeui/typeui-fundamentals
GET https://markdownregistry.com/api/v1/blob/af01b69d592b2294093b94c376617836961b28a0ba21d9c080241c189422b32e

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.

More from bergside/typeui

DESIGN.md DESIGN.md file
bergside/typeui · DESIGN.md
git:20260403.6277a40 · audit A · 2,262 stars
typeui SKILL.md skill
bergside/typeui · plugins/grok/typeui/skills/typeui/SKILL.md · Use TypeUI with Grok to access project design skills, brand kits, UI prompts, and layout variations through the TypeUI…
git:20260626.6976535 · audit A · 2,262 stars
typeui SKILL.md skill
bergside/typeui · plugins/hermes/typeui/typeui_hermes/skills/typeui/SKILL.md · Use TypeUI with Hermes Agent to access project design skills, brand kits, UI prompts, and layout variations through the…
git:20260702.9f313da · audit A · 2,262 stars
typeui SKILL.md skill
bergside/typeui · plugins/openclaw/typeui/skills/typeui/SKILL.md · Use TypeUI with OpenClaw to access project design skills, brand kits, UI prompts, and layout variations through the…
git:20260630.17afb5d · audit A · 2,262 stars

Every file in bergside/typeui

Browse by kind, by grade A, or by owner.