Dryui Build Experiment C

Community

rob-balfre

dryui-build-experiment-c

Experimental DryUI UI build workflow using compact decision tables and page recipes. Use when testing whether terse recipes produce better low-reasoning compliance.

Overview

Publisher	rob-balfre
Repository	`dryui`
Skill name	`dryui-build-experiment-c`
Stars	9
Forks	0
Bundled files	1
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.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by rob-balfre on GitHub. Read the source before you install it.

Installation

Install the Dryui Build Experiment C 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/rob-balfre/dryui/tree/main/reports/skill-experiments/2026-05-11/variant-c-decision-table
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/rob-balfre/dryui/tree/main/reports/skill-experiments/2026-05-11/variant-c-decision-table

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

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/rob-balfre/dryui.git /tmp/dryui
mkdir -p .claude/skills
cp -r /tmp/dryui/reports/skill-experiments/2026-05-11/variant-c-decision-table .claude/skills/dryui-build-experiment-c

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

Use it in TypingMind

Enable Dryui Build Experiment C 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 Dryui Build Experiment C 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 Dryui Build Experiment C 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.

DryUI Build Experiment C: Decision Tables

Classify The Request

If the user asks for	Build as	First recipe
route, screen, dashboard, admin, settings, page	full page	Page recipe
hero, pricing, table area, sidebar, header, footer	section	Section recipe
card, row, item, badge group, cell	component fragment	Component recipe
form, wizard, editor, settings flow	workflow	Workflow recipe
make nicer, polish, improve layout	review/refine	Review recipe

If the page contains tables, charts, metrics, filters, or admin work, also apply the Dashboard recipe.

Page Recipe

Root: one semantic route root with data-layout="<route-name>".
Container: root declares container: <route-name> / inline-size in src/layout.css.
Areas: direct structural children use data-layout-area.
Layout CSS: src/layout.css only.
Responsive: mobile base plus @container <route-name> (...).
Prohibited in component styles: display: grid, display: flex, @media layout breakpoints, inline style, Svelte style:.
Verification: mobile, desktop, long text, and no horizontal overflow.

Dashboard Recipe

Decision	Rule
Primary purpose	Pick one: monitor, compare, triage, report, configure, act.
Density	Pick compact for admin/data, standard for mixed content, spacious only for executive summary.
Regions	Header, action/filter bar, KPI summary, primary visualization, data table, secondary detail if needed.
Dominance	Primary visualization or table gets the largest stable grid area.
Cards	Use for KPIs or comparable units only; do not scaffold the page with cards.
Data	Use `DataGrid`/`Table` and `Chart`/`Sparkline` when available.
States	Default, loading, empty, error, disabled, dense rows, long labels.
Mobile	Collapse to one column; keep filters/actions before affected data.

Section Recipe

Use data-layout="<section-name>".
Scope structure in src/layout.css.
Use parent container query unless independent behavior is required.
Do not add a page wrapper inside a section.

Component Recipe

Prefer DryUI primitives.
Raw elements need a structural reason and data-layout.
Component CSS handles visual styling.
Add a component container query only when the component is reused at different widths.

Workflow Recipe

Use field/label primitives.
Group by task.
Include validation, loading, error, success, and disabled states.
Primary submit action is singular and visible.

Review Recipe

Score in this order:

Lint contract.
Task path and primary action.
Hierarchy and grouping.
Responsive collapse.
State coverage.
Visual polish.

Bundled files

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

output.md11 KB

Frequently asked questions

What does the Dryui Build Experiment C AI skill do?

Experimental DryUI UI build workflow using compact decision tables and page recipes. Use when testing whether terse recipes produce better low-reasoning compliance.

Why use Dryui Build Experiment C on TypingMind?

Because you install it once and use it with any model. Dryui Build Experiment C 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 Dryui Build Experiment C in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/rob-balfre/dryui/tree/main/reports/skill-experiments/2026-05-11/variant-c-decision-table. 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 Dryui Build Experiment C?

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 Dryui Build Experiment C?

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

Is the Dryui Build Experiment C AI skill free?

Yes. It is published on GitHub by rob-balfre 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

Prototype Openclaw Tui

openclaw

OrganizationPopular

Build throwaway, fixture-driven OpenClaw Clack or Pi TUI prototypes and compare multiple interactive variants side by side in tmux without running the full application or touching live state.

Slacrawl

Slack archive: search, sync freshness, threads/DMs, SQL counts, and Slacrawl repo work.

Obsidian Vault Maintainer

openclaw

OrganizationPopular

Maintain an Obsidian-friendly memory wiki vault with wikilinks, frontmatter, and official Obsidian CLI awareness.

Control Ui

Operate and troubleshoot the OpenClaw Control UI: navigate connected clients, organize sessions, build session dashboards, and handle direct or Tailscale-hosted Gateways.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

DryUI Build Experiment C: Decision Tables

Classify The Request

Page Recipe

Dashboard Recipe

Section Recipe

Component Recipe

Workflow Recipe

Review Recipe

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now