test

Name: test
Author: owainlewis

238stars46forks

How to install test?

owainlewis/blueprint/test

$npx -y skills add owainlewis/blueprint --skill test

Installs into the current project.

Summary

Tests a code change against its acceptance criteria using focused automated checks and real-browser verification for browser-facing work. Use when the user asks to test, verify, validate, QA, check acceptance criteria, browser-test, or prove a diff, branch, PR, URL, or user flow

Files · 1

View on GitHub

SKILL.md

1	# Test
2
3	## Workflow
4
5	1. Read the task, acceptance criteria, changed code, existing tests, and repository instructions.
6	2. Map every acceptance criterion and important failure path to proof. Add or update focused tests when proof is missing.
7	3. Run the narrowest relevant checks, then wider checks when shared behavior or interfaces changed.
8	4. For browser-rendered behavior, start the documented app and verify the main flow and important failure states in a real browser. Check desktop and mobile layout when relevant, keyboard use, console errors, and failed requests. Capture evidence. Source inspection is not browser proof.
9	5. Report each criterion as pass, fail, or unverified with the command, browser flow, or evidence that supports it.
10
11	## Boundaries
12
13	- Do not weaken assertions to make a change pass.
14	- Do not fix unrelated failures.
15	- If required browser tooling is unavailable, report the check as blocked unless the user explicitly accepts a manual exception.

People who liked this also viewed

6 picks

Type

test

238stars46forks

View on GitHub

How to install test?

owainlewis/blueprint/test

$npx -y skills add owainlewis/blueprint --skill test

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Test
2
3	## Workflow
4
5	1. Read the task, acceptance criteria, changed code, existing tests, and repository instructions.
6	2. Map every acceptance criterion and important failure path to proof. Add or update focused tests when proof is missing.
7	3. Run the narrowest relevant checks, then wider checks when shared behavior or interfaces changed.
8	4. For browser-rendered behavior, start the documented app and verify the main flow and important failure states in a real browser. Check desktop and mobile layout when relevant, keyboard use, console errors, and failed requests. Capture evidence. Source inspection is not browser proof.
9	5. Report each criterion as pass, fail, or unverified with the command, browser flow, or evidence that supports it.
10
11	## Boundaries
12
13	- Do not weaken assertions to make a change pass.
14	- Do not fix unrelated failures.
15	- If required browser tooling is unavailable, report the check as blocked unless the user explicitly accepts a manual exception.

People who liked this also viewed

6 picks

Type