More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    SaaS Design Handoff QA Pack

    1

    Generate structured, traceable SaaS design handoff packs with state matrices, issue registers, and JSON records.

    Free

    1 useSecurity scanned
    SaaS Design Handoff QA Pack

    SaaS Design Handoff QA Pack

    Example session with this skill installed

    Use SaaS Design Handoff QA Pack to prepare a developer handoff for the fictional product Stageboard, reports flow v0.4. Use only this supplied specification. Save the six handoff files to the output directory named in this task, and run the bundled structural checker if available. Do not implement the product.

    Source A — approved desktop reports specification v0.4:

    • A1. Reports page contains FilterBar, ReportTable and ExportButton. Submitting the date filter fetches reports asynchronously. Loading shows "Loading reports"; no matches shows "No reports in this date range" with Clear filters. The result of Clear filters is not defined here.
    • A2. Only admins can export. Non-admins see "Ask an admin to export reports" instead of ExportButton.
    • A3. Starting export asynchronously changes the action to "Preparing" and disables repeat activation while pending. On success, show "Export ready" and a Download CSV link.
    • A4. An export's failure or uncertain-outcome handling is not specified in these pages.

    Source B — approved responsive and component notes v0.4:

    • B1. FilterBar stacks controls below 768 CSS pixels. ReportTable scrolls horizontally below that breakpoint; the column order remains the desktop order. ExportButton appears below FilterBar on small screens.
    • B2. FilterBar, ReportTable and ExportButton are the supplied component names. No token values, other component variants or widths are supplied.

    Source C — product-owner handoff note:

    • C1. Export failure is required but is not designed in v0.4.
    • C2. After an export timeout, completion is unknown. Engineering has not confirmed outcome lookup or whether another export would duplicate work; no Retry action is approved for this case.
    • C3. Search request-failure behavior has not been supplied for this review. Do not treat its absence here as proof of a production defect.

    No screenshots, implementation or runtime test evidence are supplied. This is documentation review, not launch approval. Keep undecided behavior visible.

    • Read your context and instructions
    • Compiled the saas design handoff

    Sample handoff — Stageboard reports flow v0.4

    Abridged from a recorded Codex run on a fictional specification. This reviews documentation, not a live product.

    Handoff status: blocked. Two unresolved P1 issues remain:

    IssuePriorityDecision needed
    I-FAILUREP1Design the explicitly required export-failure state and its safe next action.
    I-TIMEOUTP1Establish unknown-outcome recovery and duplicate-work safety before offering another export.
    I-CLEARP2Define what Clear filters resets and which state it reaches.
    I-FETCH-FAILUREP2Supply reports request-failure behavior; missing evidence is not a confirmed product defect.
    I-RESULTSP2Complete the populated-result transition and preservation behavior.

    Pack produced

    • handoff-summary.md
    • screen-state-matrix.md
    • component-responsive-notes.md
    • issue-register.md
    • acceptance-checks.md
    • handoff.json

    The record links 3 sources, 1 reviewed surface, 9 requirements, 11 state rows, 3 components, 3 responsive rules, 5 decisions, 5 issues and 7 acceptance checks.

    Consistency-check result

    The bundled Python checker ran on handoff.json and returned

    structural validation: pass. It found no structural findings in the generated record.

    That pass does not resolve the design blockers. All seven product acceptance checks are

    not_run; the agent did not inspect or test an implementation. Source truth, semantic completeness, Markdown agreement and live behavior still require review beyond this structural check.

    handoff-summary.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Software handoffs often fail because requirements, visual states, and developer instructions are scattered across screenshots, Slack threads, and half-baked Figma comments. This skill bridges the gap by transforming raw design artifacts into a structured, traceable QA pack. It forces a rigorous audit of screen coverage, state transitions, and responsive rules, ensuring nothing is left to "best guess" implementation.

    What it does

    • Source Traceability catalogs screenshots, specifications, and reports with stable IDs for every claim.
    • State Coverage Audit evaluates loading, empty, error, and recovery states across all supplied surfaces.
    • Conflict Detection flags contradictory requirements or design gaps as explicit issues or decisions.
    • Standardized Handoff Records generates a complete JSON record and Markdown documentation for surfaces and components.
    • Acceptance Check Generation drafts testable checks tied directly to requirements and evidenced states.

    How it works

    1. Define Boundary by identifying the specific user task, surfaces, and source versions to be reviewed.
    2. Build Linked Record to inventory components, responsive rules, and states using a standardized ID system.
    3. Assess Readiness by classifying the handoff status as blocked, review-ready, or open-item pending based on P1-P3 priority.
    4. Export Artifacts including a screen-state matrix, issue register, and a structurally valid handoff.json file.

    Frameworks & tools

    This skill is platform-agnostic but includes a Python 3.10+ validation script for verifying the structural integrity of the handoff.json output against a specific schema contract.

    Why this beats prompting it yourself

    Generic prompts often hallucinate missing states or ignore subtle contradictions in design files. This skill enforces a strict evidence-based methodology that separates "supplied" facts from "proposed" suggestions, preventing developers from building on top of unconfirmed assumptions.

    Use cases

    • Audit Design Handoffs to ensure developers have every state needed for a sprint.
    • Reconcile Requirements when visual mocks and text specs don't align.
    • Generate Test Cases based on design intent rather than post-build exploration.
    • Register Handoff Issues to track blocking UI decisions before coding begins.

    Known limitations

    Does not perform UI implementation, live application inspection, or accessibility certification. Desktop screenshots cannot be used to infer mobile behavior or exact breakpoints.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.

    • Reviews supplied evidence; it does not inspect an unsupplied live product or run product tests.
    • Structural validation checks the JSON record only, not source truth, semantic completeness or Markdown agreement.
    • A passing record can remain blocked by unresolved design decisions.
    • No accessibility certification, implementation guarantee or launch approval.
    • Evaluated in Codex; other hosts, automatic triggering and Agensi ingestion remain unverified.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    Exact
    design
    inputs
    selected
    or
    supplied
    by
    the
    buyer
    User-selected
    output
    directory
    for
    requested
    handoff
    files
    handoff.json
    and
    bundled
    checker
    optional
    validation

    Read only selected inputs. Write only requested deliverables at the selected destination. Shell is optional and restricted by the skill to running its bundled Python checker; the checker itself only reads one JSON file and writes its report to stdout. No browser, network, account, API key or environment-variable access is required.

    Listed24 days ago

    What's inside

    Frequently Asked Questions

    This release is priced Free ($0). The full handoff workflow, output contract and optional structural checker are included; there is no separate paid feature gate in the skill.

    Provide a bounded flow, its screenshots or descriptions, and relevant requirements or design notes. Include source versions and authority where known. Without reviewable input the skill requests evidence instead of inventing a handoff.

    When file output is requested, it creates a handoff summary, screen/state matrix, component/responsive notes, issue register, acceptance checks and handoff.json. By default it can return the pack in your agent conversation.

    It checks JSON structure, required fields, IDs, references, selected evidence-link rules and handoff-status consistency. It does not verify source truth, semantic completeness, Markdown agreement, accessibility or live-product behavior. It reads one selected UTF-8 JSON file up to 2 MiB and prints a report.

    No Figma connection or API key is required. Pasted specifications are sufficient. Python 3.10+ and shell access are optional for the bundled checker; without them the agent reviews against the contract manually and states that automated validation was not run. Screenshots require image understanding; file output requires file-writing capability.

    No. A structurally valid record can still contain unresolved handoff blockers. Generated product checks are not executed tests. The pack is for human review, not launch approval or compliance certification. Evaluation to date is in Codex; other agent hosts remain unverified.

    New in Technical Documentation

    Free