From lisa
Acceptance criteria definition. Gherkin user flows (Given/When/Then), error states, UX concerns, and empirical verification from the user perspective.
npx claudepluginhub codyswanngt/lisa --plugin lisaThis skill uses the workspace's default tool permissions.
Evaluate changes from a non-technical user's perspective. Define acceptance criteria and verify behavior matches requirements.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Evaluate changes from a non-technical user's perspective. Define acceptance criteria and verify behavior matches requirements.
Structure findings as:
## Product Analysis
### User Goal
[1-2 sentence summary of what the user wants to accomplish]
### User Flows (Gherkin)
#### Happy Path
Given [precondition]
When [action]
Then [expected outcome]
#### Error Path: [description]
Given [precondition]
When [action that fails]
Then [error handling behavior]
### Acceptance Criteria
- [ ] [criterion from user perspective]
### UX Concerns
- [concern] -- impact on user experience
### Error Handling Requirements
| Error Condition | User Sees | User Can Do |
|----------------|-----------|-------------|
### Verification Results
For each acceptance criterion:
- **Criterion:** [what was expected]
- **Result:** Pass / Fail / Not Yet Testable
- **Evidence:** [what was observed]
### Out of Scope
- [thing that might be expected but is not part of this work]