preview

Seed a real session via the dev API and open its URL in a browser.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/danielkhigay/gaz --skill preview-danielkhigay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preview
Source: https://github.com/danielkhigay/gaz/tree/main/.claude/skills/preview
Command: npx skills add https://github.com/danielkhigay/gaz --skill preview-danielkhigay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Instantly open and preview any session page state in a browser by seeding a real dev session and navigating to it, enabling rapid UI testing without manual voting.

Core Features & Use Cases

  • Seed real sessions in development to reproduce specific voting workflows and UI states.
  • Open targeted pages for states such as round_1, round_1_5, round_2, locked, and tabled with a single command.
  • Authenticate when needed and clean up seeded sessions to keep the dev database tidy.

Quick Start

Seed a session for the target state and open its session URL in the browser to begin previewing.

Frequently Asked Questions about preview

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

FAQPage Schema
How do I preview a specific session page state in a browser during development?

You can preview a specific session state by seeding a real dev session via the dev API endpoint and navigating to the generated session URL, enabling rapid UI testing for states like round_1, locked, or tabled without manual voting.

What is session seeding for QA testing and how does it work?

Session seeding for QA testing creates a real development session with a predefined state using the dev seed endpoint. It instantly reproduces specific voting workflows and UI states, bypassing the need to manually cast votes to reach a desired page condition.

Do I need running backend and frontend servers to preview seeded sessions?

Yes, previewing seeded sessions requires both running backend and frontend servers. The backend hosts the dev seed endpoint to create the session state, while the frontend server renders the actual UI page you navigate to for visual QA verification.

What voting workflow UI states can I reproduce for testing?

You can reproduce voting workflow UI states including round_1, round_1_5, round_2, locked, and tabled. Seeding these states allows developers to test interface rendering and behavior across the voting lifecycle instantly without triggering the natural voting progression.

Can I authenticate and clean up dev sessions after previewing UI states?

Yes, the session preview workflow supports optional login authentication when needed and cleans up seeded sessions after use. This ensures the development database remains tidy and does not accumulate test data during QA workflows.

What is the best way to test locked or tabled session UI without manual voting?

The best way to test locked or tabled session UI without manual voting is using a dev seed endpoint to create a session with the target state. This approach skips the standard voting progression and opens the specific UI page directly.