qf

Audit frontend code against frontend_styleguide.md for Tailwind, accessibility, and security.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/madebymlai/feldspar --skill qf-madebymlai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qf
Source: https://github.com/madebymlai/feldspar/tree/main/.claude/skills/qf
Command: npx skills add https://github.com/madebymlai/feldspar --skill qf-madebymlai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits frontend code against a formal style guide to ensure consistent UI, accessibility, and security practices, while migrating tests to standardized patterns.

Core Features & Use Cases

  • Validates Tailwind usage against the style guide.
  • Checks component patterns, resource cleanup, and accessibility conformance.
  • Migrates legacy tests to tests_[module] for maintainable test structure.

Quick Start

Run the frontend QA audit against the target project using the frontend_styleguide.md baseline to generate the remediation report.

Frequently Asked Questions about qf

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

FAQPage Schema
How do I automate frontend QA audits for styleguide compliance?

Frontend QA audits validate Tailwind usage, component patterns, accessibility, and security against a formal style guide. This automated process scales from single files to entire projects, providing deterministic remediation guidance for consistent UI.

Can I check Tailwind usage and accessibility conformance across an entire project?

Yes, frontend QA audits scale from single files to entire frontend projects. The automated task orchestration checks Tailwind usage, accessibility conformance, and resource cleanup against the defined frontend_styleguide.md baseline.

How do I migrate legacy tests to a standardized module pattern?

Migrate legacy tests by moving them from standard __tests__ directories to a tests_[module] structure. This automated migration ensures a maintainable test structure while simultaneously running styleguide compliance checks.

What is included in a frontend styleguide compliance audit?

A frontend styleguide compliance audit includes validating Tailwind usage, checking component patterns, verifying accessibility conformance, ensuring resource cleanup, and migrating legacy tests to standardized patterns for maintainable structure.

Does the frontend QA audit require specific dependencies or components?

The frontend QA audit requires no external dependencies or components. It uses automated task orchestration like TaskCreate and TeamCreate to validate code against the frontend_styleguide.md baseline without additional setup.

When should I use an automated style guide audit instead of manual code review?

Use an automated style guide audit when scaling frontend QA from single files to entire projects. It provides deterministic remediation guidance for Tailwind usage, accessibility, and security that manual reviews might miss at scale.