verification

Infer end-to-end user stories and verify boundaries across UI, API, data, and environment.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/masermediagroup-stack/CursorSkills --skill verification-masermediagroup-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/masermediagroup-stack/CursorSkills/tree/main/skills-bundle/plugins-vercel/eb3b6f19e9ca59b23c88d7cc8dfe609388be0fc7/skills/verification
Command: npx skills add https://github.com/masermediagroup-stack/CursorSkills --skill verification-masermediagroup-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates end-to-end verification by inferring the complete user story and validating every boundary from browser UI to API, data, and environment signals.

Core Features & Use Cases

  • Infers the full user journey across UI, API, data layer, and configuration to provide a comprehensive verification plan.
  • Verifies critical boundaries such as UI rendering, client-to-server requests, API handling, data retrieval, and response correctness, including environment variable and middleware considerations.
  • Use Case: When a developer asks "is this feature really working end-to-end?" this Skill produces a verified flow report with actionable findings.

Quick Start

Describe the end-to-end verification scenario from dev server start to UI response and generate a structured verification plan.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I verify end-to-end user flow from browser UI to API and data sources?

End-to-end flow verification infers the complete user journey and validates every boundary from browser UI to API requests, data retrieval, and environment configuration to detect failures across the full stack.

What is end-to-end flow verification in a development workflow?

End-to-end flow verification is a process that infers the full user story across UI, API, data layers, and configuration, producing a comprehensive verification plan to validate critical boundaries and report actionable findings.

How do I check if a feature is really working across UI and server boundaries?

To check if a feature works across boundaries, validate UI rendering, client-to-server requests, API handling, data retrieval, and response correctness, including environment variables and middleware considerations.

Do I need access to project files and runtime logs to verify full-flow boundaries?

Yes, verifying full-flow boundaries requires access to project files, runtime logs, environment variables, and server prompts to validate the complete development workflow and detect configuration failures.

What's the best way to generate a verification plan for a dev server flow?

The best way to generate a verification plan is to describe the end-to-end scenario from dev server start to UI response, which infers the journey and outputs a structured plan with actionable findings.

Why does my feature seem broken when UI rendering and API handling work independently?

Features break when boundaries between UI rendering and API handling fail, requiring full-flow checks across data sources, environment variables, and middleware to detect hidden integration failures.