Frozen · The maintained version is aigent-design-system

AI web design that starts with product truth.

This project is frozen. Use aigent-design-system for new work. It picks a visual direction, builds the site, and checks the result in a real browser. This repository remains the Apache-2.0 source for the aigent-business-sites skill.

View this frozen repository · Read verified source facts

Ultra Web Design before and after evidence: SaaS, local service, and editorial examples.
Lean runtimeUnder 500 lines, with references loaded only when required.
Complete corpusBusiness, design, engineering, audit, and provenance modules remain available.
Verified packagingOfficial Agent Skills validation and drift-rejecting CI.
Evidence policyNo benchmark or superiority claim before the artifacts exist.

Why it exists

More than a style prompt.

Generic AI website output often starts with a visual trope. Ultra Web Design starts with the business, audience, product mechanism, proof, brand authority, existing stack, and the route's actual job. Visual choices are judged by whether they clarify, differentiate, and survive production constraints.

Strategy

Product truth before composition

Offer, audience, mechanism, proof, objections, CTA, constraints, and success measures become explicit before broad design work.

Craft

One visual world with restraint

Typography, color, imagery, layout, components, and motion form one product-specific system rather than a collage of fashionable effects.

Production

Rendered QA, not screenshot theater

Responsive behavior, states, keyboard paths, reduced motion, performance, SEO, security, analytics, and operations remain part of the design contract.

Operating loop

Scale the process to the task.

A tiny defect should remain a tiny diff. A substantial redesign should not skip preservation, evidence, direction, implementation, and QA.

Read and classify

Inspect the repository, product truth, routes, dependencies, assets, tests, analytics, SEO, deployment, and shared callers before choosing a path.

Shape and synthesize

Define the visitor decision, proof, design read, category rut, references, expression dials, signature system, and restraint system.

Build the smallest complete slice

Reuse the existing stack, native platform features, standard libraries, and installed dependencies before adding code or packages.

See, resolve, and release

Inspect rendered contexts, fix shared root causes, and block release on truth, accessibility, security, performance, or broken primary actions.

Visual fixtures

One skill, different business worlds.

These dependency-free examples demonstrate breadth. They are illustrative concepts—not customer work, conversion studies, or benchmark proof.

B2B SaaS

Precision SaaS

Product mechanism as proof, operational annotations, restrained color, and no invented logos or social proof.

Open the live example

Local service

Field-guide service site

Geography, site assessment, scheduling, and real service decisions replace the standard software marketing grammar.

Open the live example

Editorial

Northline Field Notes

Reading-first hierarchy, source context, issue archive, sponsor disclosure, and membership only after value.

Open the live example

Source quality

Built to be inspectable and citable.

AI systems and human reviewers should not have to guess which claims are official, which examples are illustrative, or where the knowledge came from.

Canonical sourcegithub.com/wrg32786/Ultra-web-design
LicenseApache License 2.0, with upstream provenance and third-party notes in NOTICE.md.
Runtime statusVersion 2.0.0 is frozen. Continued work lives in Aigent Design System's aigent-business-sites skill. This repository remains the Apache-2.0 source.
Machine metadatallms.txt, CITATION.cff, and CodeMeta.
EvidenceStructural validation, output and trigger eval definitions, visual fixtures, exact source snapshots, and explicit unproven claims.

Direct answers

What it is—and is not.

These boundaries are explicit so search systems and users can quote the project accurately.

What is Ultra Web Design?

An open-source Agent Skill and reference corpus for strategy, design, implementation, auditing, and release of business websites.

Is it a component library or website theme?

No. It governs decisions and execution inside the real project stack. It does not require one framework, palette, layout, or visual trick.

Does it guarantee a unique or high-converting website?

No finite document can guarantee uniqueness or conversion. It enforces product-specific evidence, coherent systems, usability, and release checks; outcomes still require real implementation, testing, and traffic.

Why is the runtime labeled beta?

The packaging and structural checks pass, but behavioral superiority is not claimed until recorded with-skill versus baseline evaluation and real-project evidence meet the published criteria.

Use the source

Inspect it. Install it. Test it on a real website.

The strongest contribution is a reproducible project result, issue, comparison, correction, or pull request that improves what the skill actually does.

Open the repository