ux-architect

Creates CSS design systems, responsive layouts, component architectures, and accessible HTML/CSS foundations for web projects. Generates design token files, grid frameworks, theme toggle systems (light/dark/system), and developer handoff documentation. Use when the user asks about CSS architecture, design systems, responsive layouts, component naming conventions, frontend structure, layout frameworks, theme switching, or needs a scalable CSS foundation before implementation begins.

Quality

84%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, highly actionable skill with excellent workflow clarity and concrete, executable code throughout. Its main weakness is that it inlines substantial implementation code that could be better organized via progressive disclosure into referenced files, which also impacts conciseness. The checkpoints and validation steps are well-designed and appropriately placed for a multi-step architecture workflow.

Suggestions

Move the full CSS design system, layout framework, and theme toggle code into referenced template files (e.g., `templates/design-system.css`, `templates/theme-manager.js`) and keep only concise summaries or key snippets in SKILL.md.

Trim the inline code examples to show only the essential patterns (e.g., 2-3 representative tokens per category) rather than complete token sets, since the full templates are already referenced in `ai/agents/architect.md`.

Dimension	Reasoning	Score
Conciseness	The skill is fairly detailed and includes substantial executable CSS/JS code that earns its place, but some sections are verbose — e.g., the full theme toggle implementation and layout utilities could be referenced from a separate file rather than inlined. The inline code is useful but pushes the token budget given that a reference to `ai/agents/architect.md` already exists.	2 / 3
Actionability	Highly actionable with fully executable CSS, HTML, and JavaScript code throughout. Commands for reading project files are concrete, token definitions are copy-paste ready, and the theme manager class is complete and functional.	3 / 3
Workflow Clarity	Clear 5-step sequential workflow with explicit checkpoints after each step (confirm brand values, browser render check, responsive verification, theme persistence test, developer handoff review). Includes validation feedback loops — e.g., 'confirm before proceeding' gates between steps.	3 / 3
Progressive Disclosure	References `ai/agents/architect.md` for full templates and additional patterns, which is good. However, a significant amount of code (design tokens, layout framework, full theme toggle implementation) is inlined that could be split into referenced files, making the SKILL.md quite long. The balance between overview and detail leans too far toward inline detail.	2 / 3
	Total	10 / 12 Passed

Description

92%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly articulates specific capabilities, includes a comprehensive 'Use when' clause with natural trigger terms, and covers both the 'what' and 'when' dimensions well. The main weakness is a slight risk of overlap with general frontend/web development skills, though the focus on CSS architecture and design system foundations provides reasonable distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: creating CSS design systems, responsive layouts, component architectures, accessible HTML/CSS foundations, design token files, grid frameworks, theme toggle systems, and developer handoff documentation.	3 / 3
Completeness	Clearly answers both 'what' (creates CSS design systems, generates design token files, grid frameworks, theme toggle systems, etc.) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'CSS architecture', 'design systems', 'responsive layouts', 'component naming conventions', 'frontend structure', 'layout frameworks', 'theme switching', 'light/dark/system', 'design tokens', 'grid frameworks'. These are terms developers naturally use.	3 / 3
Distinctiveness Conflict Risk	While it carves out a niche around CSS architecture and design systems specifically, terms like 'responsive layouts', 'frontend structure', and 'accessible HTML/CSS' could overlap with general frontend development or web development skills. The focus on pre-implementation CSS foundations helps distinguish it, but some overlap risk remains.	2 / 3
	Total	11 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: OpenRoster-ai/awesome-agents
Commit: 010799b

Reviewed: 3 months ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.