itseffi/productize/productize-acceptance-criteria-for-ui
Claude Code and agent skill by itseffi/productize
- community
Checking that the SKILL.md file is still in the repository.
Acceptance criteria for UI. Use when the user needs a product workflow for technical related to acceptance criteria for ui. Trigger terms: quality-assurance, ui, acceptance-criteria, responsive-design, technical.
Install
npx vskill@latest install itseffi/productize/productize-acceptance-criteria-for-uiSKILL.md
The same SKILL.md was published earlier as itseffi/productize/productize-acceptance-criteria-for-ui.
Acceptance criteria for UI
Productize Preamble
Before producing the artifact, implementation step, or code change, classify the work:
- User/persona: founder, product leader, AI PM, AI builder, stakeholder, or mixed/unknown.
- Product stage: idea, validation, PMF search, growth, scale, pivot, or unknown.
- Artifact mode: strategy memo, PRD, research plan, positioning, experiment, deck, roadmap, execution brief, diagnostic, or decision record.
- Artifact format: Markdown for short, repo-native, diff-sensitive artifacts; self-contained HTML for long, visual, shareable, interactive, or explicitly requested artifacts.
- Evidence standard: what is known, assumed, missing, and risky.
- Decision mode: recommend, ask for a blocking input, or proceed with explicit assumptions.
Operating rules:
- Do not produce generic product strategy filler. Tie every recommendation to the user's context, evidence, stage, and decision pressure.
- Separate facts from assumptions. Convert high-risk assumptions into tests, research prompts, or instrumentation.
- Search existing context, attached docs, repo files, or prior Productize artifacts before inventing new structure when those sources are available.
- Ask only for inputs that materially change the output. If the next step is obvious, proceed and state assumptions.
- If another Productize skill is a better fit, name it and explain the routing in one sentence before continuing.
- Enforce the output contract for this skill. Produce the artifact, implementation step, verification evidence, or code change; do not stop at a meta-explanation of the method.
- End with the concrete next action, decision owner, validation step, metric, or artifact handoff when applicable.
- Use the user's saved Productize preferences when available, but do not let stale preferences override explicit instructions in the current request.
- If you must ask a blocking question, use this compact format:
AskUserQuestion: <one question> Why it matters: <decision it changes>. - Record completion status for durable work as
completed,blocked,deferred, orneeds-reviewwhen runtime hooks are available.
Artifact format policy:
- Default to Markdown for short notes, repo-native documentation, changelog fragments, or artifacts where clean source diffs matter.
- Use a self-contained HTML file when the user asks for HTML, the artifact is likely to exceed about 100 lines, the reader needs diagrams/tables/comparisons/screenshots, the artifact is meant to be shared, or interaction/export controls would help the user stay in the loop.
- Route by product job first, then choose the format. Do not create a generic HTML workflow when a Productize playbook, gate, or routed skill owns the work.
- HTML artifacts must be local-first and portable: one file, embedded CSS/JS, no remote dependencies unless explicitly requested, readable without a dev server, responsive, accessible, and easy to skim.
- Prefer semantic sections, tables, SVG diagrams, annotated code blocks, status chips, collapsible detail, and copy/export buttons when they improve review speed. Avoid decorative complexity that hides the decision.
- For implementation work with ambiguities, use
$implementation-noteswhen the user asks for a running notes file, especiallyimplementation-notes.htmlorimplementation-notes.md.
Runtime hooks, if available:
- Use
productize-workflow start "<user request>"at the beginning of durable product work; it restores context, routes the request, records the session, and returns the required artifact contract. - Use
productize-workflow complete --id <id> --status completed|blocked|deferred|needs-review --artifact-type <type> --summary <summary>before ending durable product work; it records the artifact, saves context, and logs completion status. - Use
productize-update-check --strictat the start of maintenance, setup, release, or generated-output work. - Use
productize-configto read or write user/team preferences such as persona, artifact mode, evidence threshold, or update-check policy. - Use
productize-session-logto record important workflow decisions. - Use
productize-artifact-logwhen a durable artifact is produced. - Use
productize-context-restorebefore restarting long-running product work from scratch. - Use
productize-context-saveafter producing a durable strategy, research, spec, or stakeholder artifact. - Use
productize-registry-searchorproductize-skill-routerwhen routing is ambiguous. - Use
productize-completion-statusto log whether the workflow completed, blocked, deferred, or needs review.
Telemetry standard:
- Keep telemetry local by default in
.productize/orPRODUCTIZE_STATE_DIR. - Log artifact type, routing decision, evidence gaps, and completion status; do not log secrets or private customer data unless the user explicitly asks for it.
Current skill metadata:
- Skill:
acceptance-criteria-for-ui - Lifecycle: Design
- Category: Design
- Primary artifact: Acceptance criteria for UI UX/design review with findings, constraints, fixes, and acceptance checks
Use this skill to run the Productize prompt contract for Acceptance criteria for UI.
Instructions
- Treat every
{{PLACEHOLDER}}in the contract as an input to collect, infer, or mark as missing. - If missing information blocks useful work, ask only for the blocking inputs. If work can proceed, state assumptions explicitly.
- Follow the contract's
GOAL,CONSTRAINTS,FORMAT, andFAILUREclauses exactly. - Preserve the required output schema unless the user explicitly asks for a different artifact.
- Keep claims grounded in the provided inputs and disclose gaps.
Prompt Contract
INPUTS <provided_inputs>
- [No explicit variables declared; use provided context.]
</provided_inputs>
GOAL Produce a high-quality deliverable for: Acceptance criteria for UI. Success metric:
- Completes all required tasks and decision logic from the prompt instructions.
- Output is specific, evidence-based, and actionable.
- Output follows the required structure exactly.
CONSTRAINTS
- Use only provided inputs and clearly state assumptions when information is missing.
- Do not skip required analysis steps, sections, or validation logic.
- Keep recommendations/outputs grounded in the input context; avoid generic filler.
- Produce a testable UI acceptance-criteria and QA validation checklist for the provided UI context.
- Cover at minimum:
- Visual testing (default/state/responsive checks).
- Functional testing (primary action, loading, error handling, edge cases).
- Accessibility testing (keyboard, screen reader, contrast, ARIA/semantic checks).
- Browser/device compatibility.
- Pass/fail summary with issues, tester, and date.
- Keep checks specific and verifiable (observable behavior, measurable thresholds, concrete expected results).
- Use a checklist style suitable for QA execution.
FORMAT Return exactly this structure:
<qa_validation>
QA Validation Checklist
Visual Testing
- [ ] [check]
- [ ] [check]
Functional Testing
- [ ] [check]
- [ ] [check]
Accessibility Testing
- [ ] [check]
- [ ] [check]
Browser Compatibility
- [ ] Chrome (latest): [result]
- [ ] Safari (latest): [result]
- [ ] Firefox (latest): [result]
- [ ] Edge (latest): [result]
- [ ] Safari iOS: [result]
- [ ] Chrome Android: [result]
Pass/Fail
Overall Result: [PASS or FAIL] Issues Found: [list deviations or "None"] Tester: [name] Date: [date] </qa_validation>
FAILURE
<qa_validation>schema is missing, malformed, or materially incomplete.- Checklist items are vague/non-testable (no clear expected behavior or measurable criteria).
- Any critical section (Visual, Functional, Accessibility, Browser Compatibility, Pass/Fail) is missing.
- Claims are generic or not grounded in provided inputs.
- Assumptions are used but not explicitly stated.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/productize-acceptance-criteria-for-ui/SKILL.md
Popularity
- 7-day trend score
- 5
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/itseffi/productize/productize-acceptance-criteria-for-ui)