skills.rest
MohammedHTahir
MohammedHTahirCOMMUNITY
Explore all skills by this author →
GitHub

verification

Verify end-to-end application flows across browser, API, data, and response rendering.

Updated May 16, 2026
Search Tags:#data flow#verification#environment variables#end-to-end testing#API routes#runtime logs#full-stack debugging
One-click install
npx skills add https://github.com/MohammedHTahir/vibe-coding-platform --skill verification-mohammedhtahir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/MohammedHTahir/vibe-coding-platform/tree/main/.kiro/vercel-plugin/skills/verification
Command: npx skills add https://github.com/MohammedHTahir/vibe-coding-platform --skill verification-mohammedhtahir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification helps you stop guessing when an AI-built feature “almost works” by validating the complete user story across browser, server, data, and rendered responses.

Core Features & Use Cases

  • End-to-end story inference: infers the feature boundaries (UI entry point → API route → data source → response rendering) before running checks.
  • Evidence-first diagnostics: gathers baseline signals from the browser, dev server output, runtime logs, and environment configuration to locate the failing boundary quickly.
  • Data-flow boundary verification: checks the end-to-end flow for common breaks such as wrong HTTP methods, mismatched request/response shapes, missing awaits, env var gaps, import mismatches, and missing error boundaries.

Quick Start

Ask the agent to verify the flow and confirm whether the feature works end-to-end after starting the dev server.

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 application flows when a feature almost works but behaves inconsistently across layers?▼

To verify end-to-end application flows, you infer the complete user story from UI entry point to API route and data source, then collect evidence from console, server logs, and environment variables to locate the failing boundary.

How do I trace data flow boundaries to find missing awaits or mismatched request and response shapes?▼

Tracing data flow boundaries involves checking the end-to-end flow for common breaks like wrong HTTP methods, mismatched request or response shapes, missing awaits, import mismatches, and missing error boundaries.

Can I use runtime logs and environment variables to diagnose why my API routes are returning inconsistent responses?▼

Yes, diagnosing inconsistent API responses requires gathering runtime logs and environment values to pinpoint data-flow breaks, stopping at the first broken boundary and reporting a status with concrete evidence.

Why does my full-stack feature fail end-to-end testing despite no obvious errors in the browser console?▼

Full-stack features fail end-to-end testing when breaks exist beyond the browser console, such as environment variable gaps, import mismatches, or missing error boundaries between the server and data source.

Related Skills

Explore More Software Engineering Skills→
cute-baobaocute-baobao

add-setting-env

Merge server-side environment variables into user settings at runtime.

Community
Intermediate
rauell1rauell1
3

verification

Verify end-to-end user flows across browser, server, API, and data layers.

Community
Advanced
miptah21miptah21
2

webapp-testing

Automates deterministic browser-based testing of local web applications with Python and Playwright.

Community
Intermediate
DarkMonkDevDarkMonkDev
1

test-environment

Run unit, integration, and end-to-end tests in isolated containers.

Community
Advanced