cre8-a2ui

Generate vanilla HTML and Web Components markup using cre8-* custom elements.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/tmorrowdev/tmorrow_ai --skill cre8-a2ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cre8-a2ui
Source: https://github.com/tmorrowdev/tmorrow_ai/tree/main/cre8/skills/cre8-a2ui
Command: npx skills add https://github.com/tmorrowdev/tmorrow_ai --skill cre8-a2ui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

CRE8 UI generation often fails when the right components, imports, and layout conventions aren’t followed, producing broken or unstyled pages.

Core Features & Use Cases

  • Web Components-first UI schema: Produces vanilla JS/HTML UI markup using CRE8 cre8- custom elements for consistent styling and structure.
  • Correct dependency ordering: Ensures required CRE8 design tokens and the CRE8 Web Components module are loaded so components render with proper --cre8-* CSS variables.
  • Use-case-aligned component selection: Maps common React equivalents to their Web Component counterparts (e.g., buttons, forms, layout, feedback, data).
  • Mandatory validation and testing workflow: Requires pre-generation UI validation and post-generation visual/DevTools verification to catch rendering and console issues early.

Quick Start

Use the cre8-a2ui skill to generate a static CRE8 design-system landing page using cre8-* elements for a vanilla HTML project.

Frequently Asked Questions about cre8-a2ui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate CRE8 web components for a vanilla HTML project?

To generate CRE8 web components for vanilla HTML, the Skill outputs markup using `cre8-*` custom elements. It ensures correct dependency ordering by loading CRE8 design tokens before the web components module so components render with proper `--cre8-*` CSS variables.

Why does my CRE8 UI generation produce broken or unstyled pages?

Broken or unstyled CRE8 UI generation typically happens when required design tokens and the web components module are loaded incorrectly. This Skill enforces correct dependency ordering and applies pre-validation plus post-generation visual and DevTools testing to catch rendering issues.

Can I use CRE8 web components for static landing pages and non-React integrations?

Yes, CRE8 web components work for static landing pages and non-React UI integrations. The Skill generates vanilla HTML and Web Components markup using `cre8-*` custom elements, mapping common React equivalents to their Web Component counterparts for layout, form, navigation, and feedback patterns.

What's the best way to map React components to CRE8 web components?

The best way to map React components to CRE8 web components is using the Skill's use-case-aligned component selection. It maps common React equivalents for buttons, forms, layout, feedback, and data to their corresponding `cre8-*` Web Component counterparts following the CRE8Element schema.

Do I need to load CRE8 design tokens before using cre8 web components?

Yes, you must load CRE8 design tokens before the CRE8 web components module. This Skill requires correct dependency ordering to ensure components render with proper `--cre8-*` CSS variables, preventing unstyled output and visual rendering errors.

What validation steps are required after generating CRE8 component markup?

After generating CRE8 component markup, the Skill requires post-generation visual and DevTools verification to catch rendering and console issues. It also mandates pre-generation UI validation to ensure the `cre8-*` elements follow the CRE8Element schema correctly.