qf

Audit frontend projects for Tailwind compliance, component patterns, and accessibility issues.

6|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/skillsets-cc/main --skill qf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qf
Source: https://github.com/skillsets-cc/main/tree/main/skillsets/%40supercollectible/Valence/content/.claude/skills/qf
Command: npx skills add https://github.com/skillsets-cc/main --skill qf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend QA audits to identify Tailwind compliance, component usage patterns, and accessibility gaps across frontend codebases, helping teams raise code quality and consistency.

Core Features & Use Cases

  • Tailwind compliance checks across styles and utilities.
  • Migration guidance for tests_[module] standardization and test relocation.
  • Resource cleanup and security/accessibility checks to reduce risk and regressions.

Quick Start

Provide the path to the frontend project you want audited, and the agent will begin the QA pass against the codebase.

Frequently Asked Questions about qf

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

FAQPage Schema
How do I audit my Tailwind codebase for accessibility and pattern compliance?

You can audit Tailwind compliance and accessibility by pointing the agent to your project path, which scans for component pattern inconsistencies, security risks, and resource cleanup needs across the frontend codebase.

What does a frontend QA audit check for during pre-release reviews?

A frontend QA audit checks for Tailwind utility compliance, component pattern consistency, and accessibility gaps, while enforcing test relocation and resource cleanup to reduce pre-release regression risks.

Can I use this QA audit for ongoing sprints in modern frontend frameworks?

Yes, this QA audit is designed for ongoing QA sprints on codebases using Tailwind and modern frontend frameworks, continuously enforcing pattern consistency, security checks, and resource cleanup.

How do I migrate tests to the tests_[module] standardization format?

You can migrate tests to the tests_[module] standard by following the audit's migration guidance, which enforces test relocation and standardization to ensure pattern consistency across your frontend project.

What is the best way to enforce Tailwind compliance and security checks together?

The best way to enforce Tailwind and security compliance is running a unified frontend QA audit that identifies utility issues, executes surface resource cleanup, and validates accessibility patterns simultaneously.