ui-engineering

Codify and enforce shared UI engineering standards for TypeScript projects.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/ajelinek/skills-stash --skill ui-engineering-ajelinek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-engineering
Source: https://github.com/ajelinek/skills-stash/tree/main/ui-engineering
Command: npx skills add https://github.com/ajelinek/skills-stash --skill ui-engineering-ajelinek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill codifies shared front-end standards to ensure consistent, accessible UI components across React, Solid, and Astro codebases.

Core Features & Use Cases

  • Establish foundation components and semantic HTML rules to prevent duplication and drift.
  • Define CSS token usage, theming, and accessibility practices that apply across frameworks.
  • Support design and engineering teams in onboarding and auditing projects for UI consistency.

Quick Start

Invoke this skill to lay down the core UI engineering standards for a new front-end initiative.

Frequently Asked Questions about ui-engineering

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

FAQPage Schema
How do I enforce shared UI engineering standards across React, Solid, and Astro?

To enforce shared UI engineering standards across React, Solid, and Astro, codify semantic HTML rules, CSS token usage, and accessibility practices to prevent component drift and duplication. This ensures consistent foundation components at build time.

What is the best way to maintain consistent CSS theming tokens across multiple TypeScript frameworks?

Maintaining consistent CSS theming tokens across TypeScript frameworks requires codifying shared token definitions and theming architecture. Applying these standards across React, Solid, and Astro guides foundation components and prevents style drift.

How do I set up accessibility practices for foundation components in a multi-framework TypeScript project?

Setting up accessibility practices for foundation components involves enforcing semantic HTML rules and shared testing guidelines. Codifying these standards ensures accessible UI components across React, Solid, and Astro codebases.

Can I audit my front-end project for UI consistency and accessibility compliance?

You can audit front-end projects for UI consistency by applying codified engineering standards. Checking semantic HTML, CSS architecture, and theming practices supports design and engineering teams in onboarding and auditing projects.

When do I need to codify shared front-end standards for a new TypeScript initiative?

You need to codify shared front-end standards when starting a new TypeScript initiative to prevent duplication and drift. Establishing foundation components and CSS token usage early ensures consistent, accessible UI components across frameworks.

Why does UI component duplication occur across React and Solid codebases?

UI component duplication occurs across React and Solid codebases when shared front-end standards are not codified. Without enforced semantic HTML rules, CSS token usage, and accessibility practices, foundation components drift apart over time.