zeta-design-audit

Audit Vue.js frontend code for brutalist design system compliance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/russiankendricklamar/zetaterminal --skill zeta-design-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zeta-design-audit
Source: https://github.com/russiankendricklamar/zetaterminal/tree/main/.claude/skills/zeta-design-audit
Command: npx skills add https://github.com/russiankendricklamar/zetaterminal --skill zeta-design-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious process of manually checking Vue pages and components for adherence to the Zeta Terminal's brutalist design system, catching common violations before they reach production.

Core Features & Use Cases

  • Automated Design Checks: Scans code for hardcoded colors, incorrect typography, forbidden patterns (like excessive border-radius or gradients), and layout class violations.
  • Component Pattern Validation: Verifies the use of modern Vue patterns (<script setup>), correct API call helpers, and appropriate loading/error states.
  • Use Case: Before merging a new feature branch, run this audit on the new components to ensure they align with the established brutalist aesthetic and technical standards, preventing design drift.

Quick Start

Run the zeta-design-audit skill on the file '/src/components/NewFeatureCard.vue' to check for design violations.

Frequently Asked Questions about zeta-design-audit

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

FAQPage Schema
How do I automate a Vue.js design system compliance audit for brutalist UI components?

A Vue.js design system compliance audit scans component code to identify hardcoded colors, typography violations, forbidden CSS patterns, and layout class deviations from brutalist design standards. It catches common violations before they reach production.

What brutalist design violations should I check for in Vue.js frontend code?

Brutalist design violations in Vue.js frontend code include hardcoded colors, incorrect typography, excessive border-radius, gradients, and layout class violations. A design audit checks for these forbidden CSS patterns and component implementation deviations.

Can I use a design audit skill to validate modern Vue patterns like script setup in my components?

Yes, a design audit skill validates modern Vue patterns by verifying the use of `<script setup>`, correct API call helpers, and appropriate loading and error states. It ensures components align with modern Vue development practices and technical standards.

How do I prevent design drift in a Vue.js application before merging new features?

To prevent design drift in a Vue.js application, run a design compliance audit on new feature branch components before merging. This verifies alignment with the established brutalist aesthetic and technical standards, catching deviations early.

Does this design audit tool work with Vue.js component files like NewFeatureCard.vue?

Yes, this design audit tool works directly with Vue.js component files. You can run the audit on a specific file path like '/src/components/NewFeatureCard.vue' to scan for design system violations and ensure brutalist compliance.

What are the limitations of automating brutalist design system checks for Vue.js?

Automating brutalist design system checks for Vue.js is limited to identifying predefined code-level violations like hardcoded colors, forbidden CSS patterns, and incorrect component patterns. It cannot assess subjective visual aesthetics or runtime rendering behavior.