Update to Fullstack Dev Kit

{
  "description": "Create or update end-to-end tests for a user-facing flow that changed, using whatever e2e framework the repo already uses. Use after implementing a user story that alters UI behavior, routing, forms, or API-driven views.",
  "included_files": [],
  "name": "e2e-generate",
  "skill_md_contents": "---\nname: e2e-generate\ndescription: Create or update end-to-end tests for a user-facing flow that changed, using whatever e2e framework the repo already uses. Use after implementing a user story that alters UI behavior, routing, forms, or API-driven views.\n---\n\n# E2E Test Generation\n\nWhen a user story changes user-facing behavior **and the project already does e2e**, an existing e2e test must be updated or a new one created before the story is done. This skill is framework-agnostic — it uses whatever e2e stack the consuming repo already has, and **never introduces a new one unprompted**.\n\n**Adaptive gate** (see `instructions/testing-standards.md`): if the repo has **no e2e setup**, this is a *recommendation*, not a blocker — report \"no e2e setup; recommend adding one\" (and offer to, if the user wants), and do not scaffold a framework. Only treat missing e2e as a hard failure when `gates.e2e` is `required` in `.claude/dev-kit.json`.\n\n## Process\n\n1. **Identify the affected flow(s)** from the story's acceptance criteria and the diff: which pages, routes, forms, and roles are involved.\n2. **Discover the project's e2e framework and conventions first** — before writing anything. If `.claude/dev-kit.json` names a stack, `instructions/stacks/<id>.md` lists the frameworks common for it as a starting hint. Then look for the config and test tree of whatever the repo actually uses (e.g. `playwright.config.*` + `e2e/`, `cypress.config.*` + `cypress/`, a Selenium/WebDriver test project, `*.feature` files for Cucumber, etc.) and reuse its existing page objects, fixtures, helpers, and app/API seeding or stubbing. Follow them exactly; do not introduce a new pattern or framework when one exists. If the repo has no e2e setup at all, say so and propose one that fits the stack instead of scaffolding silently.\n3. **Prefer updating an existing test** for the flow over creating a parallel one.\n4. **Write the scenarios.** Every generated suite must cover realistic edge cases, not just the happy path:\n   - Empty states\n   - API failures and timeouts\n   - Validation errors\n   - Role/permission differences where applicable\n   - Navigation and back-flow behavior where applicable\n5. **Run the tests** with the project's e2e command (check the consuming repo's CLAUDE.md; e.g. `npx playwright test <file>`, `npx cypress run`, or the repo's WebDriver test command). Related e2e tests must pass before PR creation.\n\n## Quality rules\n\n- Page Object Model: new pages get a page object; interactions go through it, not raw selectors in the test body.\n- Stable selectors: prefer test ids / accessible roles over CSS chains.\n- No sleeps: use the framework's waiting primitives.\n- Keep test names descriptive of the user behavior, not the implementation.\n- Preserve existing test names when updating a file.\n\n## Output\n\nReport which flows are covered, which test files were added/updated, the run result, and any flow you could not cover (with the reason) — never silently skip a flow.\n"
}