skills.rest
KyaniteLabs
KyaniteLabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

tastecheck-pass

Aggregate specialist self-checks and browser evidence into a SHIP or HOLD release decision.

3|3|Updated Jun 5, 2026
Search Tags:#quality assurance#accessibility#frontend#design system#audit#release gate
One-click install
npx skills add https://github.com/KyaniteLabs/tastecheck --skill tastecheck-pass
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tastecheck-pass
Source: https://github.com/KyaniteLabs/tastecheck/tree/main/skills/tastecheck-pass
Command: npx skills add https://github.com/KyaniteLabs/tastecheck --skill tastecheck-pass

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill solves the problem of subjective or incomplete frontend quality assurance by enforcing a fail-closed, evidence-based release gate for production-ready artifacts.

Core Features & Use Cases

  • Deterministic Verdicts: Provides a clear SHIP or HOLD decision based on objective evidence rather than assumptions.
  • Actionable Remediation: Converts every failure into a concrete next action with an owner and acceptance rule.
  • Use Case: Use this skill when you need to verify that a new frontend feature meets all design system, accessibility, and performance requirements before merging to production.

Quick Start

Run the tastecheck-pass skill on your current frontend artifact to generate a release brief and evidence ledger.

Frequently Asked Questions about tastecheck-pass

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

FAQPage Schema
What is an evidence-backed frontend release gate?▼

A frontend release gate enforces fail-closed quality assurance by aggregating specialist self-checks and browser-based evidence to produce a deterministic SHIP or HOLD decision before deployment. It requires a defined spec and measurable metrics.

How do I enforce accessibility and design system compliance before merging to production?▼

You enforce accessibility and design system compliance by running a final audit workflow that aggregates browser-based evidence against a defined spec. This fail-closed gate produces a deterministic ship or hold decision with actionable remediation steps for any failures.

Can I use a fail-closed release gate for frontend artifacts without a defined spec?▼

No, a fail-closed release gate for frontend artifacts requires a defined spec and measurable evidence to function. Without these prerequisites, the gate cannot produce a deterministic ship or hold decision for design system, accessibility, and performance metrics.

What's the best way to verify frontend performance metrics before deployment?▼

The best way to verify frontend performance metrics before deployment is to run an evidence-based release gate that aggregates browser-based evidence. This approach converts any performance failures into concrete next actions with assigned owners and acceptance rules.

Why does my frontend release gate return a HOLD decision?▼

Your frontend release gate returns a HOLD decision when browser-based evidence fails to meet your defined spec for design system compliance, accessibility, or performance metrics. Every failure triggers actionable remediation with a concrete next action, owner, and acceptance rule.

Related Skills

Explore More Software Engineering Skills→
chenluhanchenluhan

pm-metrics-acceptance

Define measurable acceptance criteria and success metrics for feature handoffs.

Community
Intermediate
issdandavisissdandavis
6

scbe-dry-run-rubix

Verify cross-language SCBE changes and emit SHIP, HOLD, or BLOCK verdicts.

Community
Advanced
labs21-devlabs21-dev
28

frontend-qa

Run browser-based frontend QA across seven layers and return evidence-backed findings.

Official
Advanced
webdevcom01-cellwebdevcom01-cell
3

safe-agent-builder

Scaffold AgentStack agents with deterministic quality gates and input guards.

Community
Advanced