ajenchen
Community@ajenchen
ajenchen provides design-system governance, multi-dimensional component auditing, and Storybook delivery skills for world-class UI quality enforcement.
Agent Skills by ajenchen
Showing 25 vetted skills indexed across 1 GitHub repositories.
ajenchendeep-audit-cross-codex
Runs two isolated full-coverage audits against one inventory and reconciles disagreements with evidence.
ajenchenensure-canonical
Plans multi-layer enforcement pipelines for design system rules from trigger phrases.
ajenchenscan-similar-bugs
Scans a design system codebase for recurring bug anti-patterns after fix commits.
ajenchencanonical-reviewer
Review governance changes in isolated read-only contexts with canonical evidence and mutation detection.
ajenchenpropose-options
Validates proposed options against a seven-question governance checklist before presenting them to users.
ajenchendesign-system-audit
Audits a design system codebase across dozens of quality dimensions and remediates findings.
ajenchenindependent-review
Obtains a read-only cross-provider second opinion on product-consumer changes with evidence-bound review records.
ajenchengovernance-status
Runs deterministic repository checks to report governance health and adapter drift status.
ajenchenproduct-ui-audit
Audits consumer UI code against design system usage rules across seven dimensions.
ajenchengovernance-health
Scans Git-owned governance telemetry to detect dead hooks, hot rules, and pending corrections.
ajenchennew-component
Guides creation of design-system components through a six-phase workflow with checkpoints.
ajenchenstory-auto-compile-migrate
Migrate design system components to auto-compile structure with componentMeta exports and spec frontmatter.
ajenchenprototype
Builds UI prototypes as Storybook explorations through a six-phase benchmark and evaluation workflow.
ajenchenvisual-audit
Audits design-system component screenshots against a 13-item pixel-level geometry checklist.
ajenchenperformance-audit
Audits React components for re-renders, memoization gaps, and bundle size impact.
ajenchendelivery-handoff
Generate Storybook handoff pages with UI flow diagrams, component inventories, and per-screen specs.
ajenchencomponent-quality-gate
Validates design-system components against a 35-item spec, code, stories, and ship checklist before merge.
ajenchencode-quality-audit
Audits TypeScript and TSX code for any usage, dead exports, oversized files, long functions, and circular dependencies.
ajenchencodify-principle
Generates five-layer governance artifacts from new design principle text.
ajenchenbug-fix-rhythm
Orchestrates batch-end verification rhythm for multi-fix sessions with parallel tool calls.
ajenchenux-audit
Audits keyboard navigation, focus management, ARIA correctness, and animation timing in UI components.
ajenchencodex-collab
Coordinates independent peer review of primary analysis with evidence verification and synthesis.
ajenchenknowledge-prune
Detects and retires duplicate, stale, and contradictory governance rules across instructions, specs, skills, hooks, and memory files.
ajenchenstory-writing
Guides writing Storybook stories for design-system components with canonical structure and quality rules.
Frequently Asked Questions About ajenchen
FAQPage SchemaWhat tasks can I accomplish with ajenchen's skills?▼
You can audit design systems and product UI across code, visual, UX, and performance dimensions, create new components through a 6-phase disciplined pipeline, write Storybook stories, migrate components to Story Auto-Compile, run governance health checks, and produce final delivery handoff documentation.
Who are these skills designed for?▼
Design-system maintainers, front-end engineers, and UX engineers working in a component library (packages/design-system) who need enforced quality gates, canonical governance, and evidence-based peer review before shipping components or product UI.
How are the skills invoked in practice?▼
Each skill is invoked via a slash command such as /design-system-audit, /component-quality-gate, /visual-audit, or /prototype, and several auto-invoke on trigger phrases (e.g. 確保/ensure/never bypass) or chain from parent audits like /design-system-audit --deep.
What prerequisites or inputs do the audits require?▼
Visual audits require a user-provided screenshot and refuse to guess; governance skills read Git-owned telemetry and user-corrections.jsonl state; component audits expect a design-system repository with specs, tokens, stories, and canonical governance surfaces already in place.
How do the skills handle governance and rule changes?▼
Skills like codify-principle, codify-corrections, knowledge-prune, and ensure-canonical convert principles and user corrections into SSOT canonical text, hooks, audit dimensions, and memory entries under a shared authority classifier, stopping only for genuine product/UI/UX SSOT tradeoffs.