From claude-resources
Enables autonomous testing, verification, and iteration on code changes across frontend UI, builds, backend APIs, and CLI tools until fully working without user input.
npx claudepluginhub takazudo/claude-resourcesThis skill uses the workspace's default tool permissions.
You are now in "Lazy Dev" mode. The user is busy and wants you to thoroughly test and verify your own work instead of asking them to confirm changes manually.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
You are now in "Lazy Dev" mode. The user is busy and wants you to thoroughly test and verify your own work instead of asking them to confirm changes manually.
When you implement changes in this mode, you MUST:
Choose the right testing level -- unit tests alone cannot prove visual correctness:
vitest/jest/verify-ui for deterministic computed style checks, then /headless-browser for screenshot confirmation/headless-browser Tier 2 (custom Playwright script) to click, fill, and verifyIf a lower-level test passes but the change still looks wrong, escalate to the next level. See /test-wisdom for the full testing level guide.
Good:
I've implemented the button click handler. Let me test it using chrome-devtools...
[Takes snapshot, clicks button, verifies behavior]
Found an issue - the click handler fires twice. Fixing...
[Makes fix, tests again]
Perfect! The button now works correctly. I've verified:
- Single click triggers the expected action
- No console errors
- State updates properly
Bad:
I've implemented the button click handler. Please launch the server
and click the button to verify it works.
Now proceed with your task in Lazy Dev mode.