medcore-e2e-spec

Scaffold a Playwright E2E spec for a MedCore dashboard route with matching assertions.

2|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Globussoft-Technologies/medcore --skill medcore-e2e-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: medcore-e2e-spec
Source: https://github.com/Globussoft-Technologies/medcore/tree/main/.claude/skills/medcore-e2e-spec
Command: npx skills add https://github.com/Globussoft-Technologies/medcore --skill medcore-e2e-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the friction and inconsistency of adding end-to-end UI coverage for MedCore dashboard routes by providing a route-aware Playwright spec scaffold that matches the repository’s fixtures/helpers conventions.

Core Features & Use Cases

  • Scaffold a new Playwright E2E spec for a specific MedCore dashboard route (including route slug → e2e/<route-slug>.spec.ts naming).
  • Write correct assertions by route archetype, handling redirect-bounce, universal-access, and admin-gate placeholder pages without brittle assumptions.
  • Maintain coverage hygiene by updating docs/E2E_COVERAGE_BACKLOG.md with an automated closure annotation and verifying via playwright test --list.

Quick Start

Ask the AI to write an e2e for /dashboard/<route> and include any specific flows, roles, or edge cases you want exercised.

Frequently Asked Questions about medcore-e2e-spec

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

FAQPage Schema
How do I scaffold a Playwright E2E test for a specific dashboard route?

To scaffold a Playwright E2E test for a dashboard route, request a spec for the specific path. The tool generates an `e2e/<route>.spec.ts` file with assertions matching the route's page archetype and existing fixture contracts.

How do I write Playwright assertions for admin-gate or redirect-bounce pages?

Writing Playwright assertions for admin-gate or redirect-bounce pages requires matching the route archetype. The scaffold generates correct assertions for these placeholder pages without brittle assumptions, ensuring reliable test coverage.

What is the best way to close an E2E coverage backlog item in Playwright?

Closing an E2E coverage backlog item involves generating a route spec and verifying its discoverability. The tool updates `docs/E2E_COVERAGE_BACKLOG.md` with a closure annotation and confirms the test appears via `playwright test --list`.

Can I use existing fixtures and helpers when generating a Playwright spec?

You can use existing fixtures and helpers when generating a Playwright spec. The scaffold ensures assertions match the repository's established fixtures and helpers contract, maintaining consistency across your test suite.

How do I verify a newly scaffolded Playwright spec is discoverable?

Verifying a newly scaffolded Playwright spec is discoverable requires listing tests. The tool confirms your new `e2e/<route>.spec.ts` file is properly recognized by running and validating the output of `playwright test --list`.