Skip to content
Back to skills

Fashion Handoff Contracts

ASecurity

Produces and validates SkyyRose structured HTML, JSON, and evidence handoffs with stable IDs, schema parity, provenance, and candidate-bound proof.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 11, 2026
testingperformance

Security analysis

A100/100

Scanned September 11, 2026

npx -y skills add SkyyRoseLLC/DevSkyy --skill fashion-handoff-contracts --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fashion Handoff Contracts?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Fashion Handoff Contracts
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/skyyrosellc-fashion-handoff-contracts/badge)](https://www.skillsdirectory.com/skills/skyyrosellc-fashion-handoff-contracts)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: fashion-handoff-contracts
description: Produces and validates SkyyRose structured HTML, JSON, and evidence handoffs with stable IDs, schema parity, provenance, and candidate-bound proof.
---

# Fashion Handoff Contracts

Use whenever a role returns a page plan, visual artifact, feature scaffold,
commerce contract, or release evidence.

## Contract

Every handoff contains `preview.html`, `contract.json`, and `evidence.json`.
HTML and JSON share stable page/section/component/feature/state IDs. Evidence
records candidate, source, screenshot/trace, command, hash, reviewer, timestamp,
status, and unresolved gaps. Product facts and imagery reference SOT authority.

## Procedure

1. Select the relevant schema from `brain/schemas/` and load route, commerce,
   motion, and acceptance contracts.
2. Render SkyyRose tokens, fonts, provenance, CTA states, responsive notes, and
   explicit loading/error/unavailable behavior.
3. Validate JSON and schema; compare extracted HTML IDs to JSON IDs; check links,
   assets, and source freshness.
4. Attach fresh candidate-bound browser/image evidence. Keep `UNKNOWN`,
   `BLOCKED`, and `EXPERIMENT` explicit.

## Verification

Mixed candidate hashes, missing rights/source records, fabricated imagery,
unreadable previews, and self-certified claims fail. Missing browser,
accessibility, commerce, or performance artifacts remain `UNVERIFIED`.

## Boundaries

This skill validates handoffs; it does not approve, publish, or waive gates.

## End-to-end execution

Run `fashion-e2e-task-execution` with this skill. A handoff task requires
`preview.html`, `contract.json`, `evidence.json`, schema/ID parity, source and
candidate hashes, plus independent validation. A mismatch is recorded at first
observation and blocks a release claim.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.