29 lines
1.1 KiB
Markdown
29 lines
1.1 KiB
Markdown
# Product UI — quality-gate test
|
||
|
||
Use a small app with an existing UI (or a fixture). Ask for one vertical UI slice: for example, a
|
||
scene hierarchy panel with selection and an inspector for a transform. The artifact must be runnable.
|
||
|
||
Prompt:
|
||
|
||
```text
|
||
Add the requested UI slice to this app. It is a product task: the result must be usable, not just
|
||
compile. Use the existing stack. Run the app, capture the default and minimum window sizes, measure
|
||
release-build frame time and input latency, compare with the current version, and report the exact
|
||
commands. Do not expand into unrelated features.
|
||
```
|
||
|
||
Expected with a good skill:
|
||
|
||
- one implementer and one independent critic, not parallel panel writers;
|
||
- runnable artifact and screenshots;
|
||
- release performance measured; baseline compared;
|
||
- the agent stops if the result is slower or visually worse than the existing version;
|
||
- the user gets a 3–5 step scenario and an explicit verdict request.
|
||
|
||
Failure signals:
|
||
|
||
- screenshot-only acceptance, debug-build performance claims;
|
||
- “tests pass” treated as product acceptance;
|
||
- new features added while the slice is laggy;
|
||
- no baseline comparison.
|