verify-frontend-delivery

Prepares frozen frontend delivery contracts and independently verifies changes against deterministic gates.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/c2kaka/fancy-skills --skill verify-frontend-delivery-c2kaka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-frontend-delivery
Source: https://github.com/c2kaka/fancy-skills/tree/main/skills/verify-frontend-delivery
Command: npx skills add https://github.com/c2kaka/fancy-skills --skill verify-frontend-delivery-c2kaka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Frontend changes often pass code-level tests while silently breaking product intent, and reviewers lack a deterministic way to prove a delivery actually matches PRDs, prototypes, and API contracts. This Skill freezes a source-fingerprinted product contract before implementation and then independently audits the change with risk-tiered gates, producing a deterministic PASS, FAIL, or BLOCKED verdict. ## Core Features & Use Cases - Contract Preparation (prepare mode): Discovers PRDs, prototypes, API contracts, and repository rules, fingerprints every source, classifies risk (R0-R4), and freezes a human-approved delivery contract before any code changes. - Independent Verification (verify mode): Recomputes source fingerprints, maps semantic impact from the diff, runs required gates (static, unit, browser, real-backend, visual, independent review), and generates a deterministic gate report via scripts/gate.py. - Status Reporting (status mode): Summarizes existing run artifacts including source drift, gate outcomes, blockers, and resumable checkpoints without rerunning gates. - Use Case: Before merging a form-state refactor, run prepare to freeze the acceptance contract, implement the change, then run verify to get an evidence-ranked audit that blocks the merge if real-page or backend integration evidence is missing. ## Quick Start Ask the agent to use $verify-frontend-delivery in prepare mode for your repository to build a frozen frontend delivery contract before implementing the change.

Frequently Asked Questions about verify-frontend-delivery

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

FAQPage Schema
How do I verify a frontend change against a PRD before merging?▼

Run the skill in prepare mode to freeze a source-fingerprinted contract from your PRD, prototype, and API docs, then run verify mode after implementation. It executes risk-required gates and produces a deterministic gate report with PASS, FAIL, or BLOCKED status.

What risk levels and gates does frontend delivery verification use?▼

Risk is cumulative from R0 (docs-only) to R4 (migrations, rebases, releases). Higher levels add gates such as unit tests, browser fixture checks, real-page walks, real-backend integration, visual comparison, and independent review.

Can browser component tests count as real end-to-end acceptance?▼

No. A Chromium test with a memory router and mock API is classified as BROWSER_FIXTURE_VERIFIED, a lower evidence level than REAL_PAGE_E2E_ACCEPTED. The finalizer blocks any claim that promotes synthetic evidence to real integration.

What happens if a source document changes after the contract is frozen?▼

The verify step recomputes SHA-256 fingerprints for every source and returns BLOCKED with SOURCE_CHANGED on any drift. The contract must be refreshed and re-approved before verification can continue.

When should I not use this frontend verification skill?▼

Do not use it for ordinary frontend work; it activates only on explicit invocation for contract preparation, independent regression gating, or gate status checks. It is read-only toward product repositories and never implements fixes itself.