claude-tweaks:stories

Generate and update diff-aware QA story YAMLs from site exploration.

2|Updated Feb 20, 2026

Search Tags:#automation #testing #qa #ui-testing #stories #journeys #diff-aware

Ready to run

npx skills add https://github.com/thomasholknielsen/claude-tweaks --skill claude-tweaks-stories

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: claude-tweaks:stories
Source: https://github.com/thomasholknielsen/claude-tweaks/tree/main/skills/stories
Command: npx skills add https://github.com/thomasholknielsen/claude-tweaks --skill claude-tweaks-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code QA teams struggle to keep stories in sync with evolving UIs; this skill provides a structured workflow to explore a site, derive user journeys, and produce consistent, diff-aware QA stories.

Core Features & Use Cases

Generate structured QA story YAMLs from site exploration and UI flows.
Integrate journey context from docs/journeys to guide coverage and ensure end-to-end validation.
Perform diff-aware updates to refresh existing stories after UI changes, reducing drift.
Enable negative story generation for resilience testing and validate self-verification of stories.
Optionally enrich stories with source-analysis signals when component-level data is available.

Quick Start

Navigate to a target site and run the stories skill to generate or update QA stories for that site.

Frequently Asked Questions about claude-tweaks:stories

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

FAQPage Schema

How do I generate QA stories for UI testing from site exploration?▼

Generate QA stories for UI testing by running the stories skill to explore a target site, derive user journeys, and output structured, diff-aware YAML files with journey context and self-validation.

What is the best way to keep QA stories in sync with evolving web app UIs?▼

Keeping QA stories in sync with evolving UIs is handled through diff-aware updates that refresh existing story YAMLs after UI changes, reducing drift and maintaining consistent journey validation across web apps.

How does diff-aware story maintenance work for automated journey validation?▼

Diff-aware story maintenance works by comparing existing QA story YAMLs against current UI states during site exploration, updating only the changed journey contexts to ensure automated validation remains accurate.

Can I generate negative stories for resilience testing using automated QA workflows?▼

Negative stories for resilience testing can be generated within automated QA workflows, enabling self-verification of stories and validating how user journeys handle unexpected or invalid UI interactions.

Do I need source-analysis data to enrich UI testing story generation?▼

Source-analysis data is optional for enriching UI testing story generation; component-level signals can be integrated to enhance stories, but the core workflow relies on site exploration and journey guides.

What are the limitations of browser-based UI testing story YAMLs?▼

Browser-based UI testing story YAMLs require integration with journey guides for complete coverage and do not automatically capture component-level data without optional source-analysis signals to enrich the stories.