Skip to content
Back to skills

Ztx3 Component System

ASecurity

Component Architecture & Design System — select, implement, audit and test component system for production Codex frontend work, with responsive and accessibility checks.

  • 14 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
developmenttypescriptgoreactfrontend

Works with

  • mcp

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add Realjustawall/Perfect-AI --skill ztx3-component-system --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ztx3 Component System?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ztx3 Component System
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/realjustawall-ztx3-component-system/badge)](https://www.skillsdirectory.com/skills/realjustawall-ztx3-component-system)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ztx3-component-system
description: "Component Architecture & Design System — select, implement, audit and test component system for production Codex frontend work, with responsive and accessibility checks."
---

# Component Architecture & Design System

Implement headless state/behavior, semantic accessible markup and visual skin separately. Build React/TypeScript contracts, Storybook states, automated interaction tests, RTL, responsive containers and token inheritance. Choose Radix/shadcn/Ark/Headless only per ecosystem compatibility, never mix redundant primitives without a plan.

## Workflow

1. Record explicit project requirements, business goal, content and accepted test budget.
2. Read `references/HANDBOOK.md` and pick precise technique Skill files, not the entire catalog.
3. Implement smallest meaningful working baseline, then add incremental enhancements.
4. Measure or inspect result with real devices and produce fallback.
5. Report verified/untested results. No MCP, no destructive overwrites.

## Core obligations

Define a typed component contract; implement semantic state transitions and storybook fixtures; map variants to design tokens.

Test keyboard focus/Escape, loading/error/empty and RTL using automated and manual cases.

## References

- `references/HANDBOOK.md` — full architecture and 12 deep techniques.
- Refer to `ztx3-<technique>` Skill for focused implementation and acceptance.

Files in this skill

  • SKILL.md1.4 KB
  • references/HANDBOOK.md6.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.