Results for “try-on”

Build throwaway code that answers exactly one design question — a tiny terminal app to feel out logic/state models, or several radically different UI variants switchable on one route. Use when the user wants to "prototype", "mock up", "sketch", "try a few versions", "see what it'd look like", "feel out this state machine", or is stuck choosing between designs they can only judge by seeing or driving them. Also used by the whiteboard skill for napkin-type tickets.

Throwaway experiments to validate an idea before build.

Runs throwaway experiments to validate feasibility, compare approaches, and surface unknowns before committing to a real build.

Throwaway experiments to validate an idea before build.

Throwaway experiments to validate an idea before build.

Runs throwaway experiments to validate feasibility before building, producing a verdict with evidence.

Internal harness probe for the OI-3 readability-guidance spike. Use only when explicitly told to invoke spike-probe. Verifies that a freshly-created project skill renders into a subagent's context via the Skill tool.

Write effective unit tests with best practices for any project. Use when writing tests, creating test cases, improving test coverage, increasing confidence before release, or when the user mentions testing. Mutation score / assertion theater → test-mutation.

Test-Driven Development (TDD)

Verify that a change really works before you claim completion

Use when implementing any feature or bugfix, before writing implementation code.

Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

Runs a relentless interview that sharpens a plan or design. Use when the user wants to be grilled on an idea, pressure-test a plan, or refine a design through questioning.

Builds a throwaway prototype to answer a design question, either as a terminal app for logic exploration or as multiple UI variations switchable from one route.

This skill should be used when the user asks to "run example" or "test example skill".

Applies practical test-first and regression testing to behavior changes, bug fixes, state transitions, and public contracts.

Close the PDCA loop on this session's diff. Headed playwright-cli, fix as you go. Use when "test my changes", "PDCA this". Pixel diffs → test-visual-regression. Story CRUD → test-qa. Monkey / guest vs logged-in → test-exploratory.

Verify code changes work by running them. Proves through execution, not just inspection.

Plan soak test planner operations. Auto-activating skill for Performance Testing. Triggers on: soak test planner, soak test planner Part of the Performance Testing skill category. Use when writing or running tests. Trigger with phrases like "soak test planner", "soak planner", "soak".

Prove a feature works by delegating verification to an independent sub-agent that drives the real app, then open a pull request with the proof.

基于证据优先的仓库执行工作流，适用于ECC。当用户需要运行命令、检查仓库、调试CI失败或推送带有精确执行和验证证明的窄修复时使用。

Recognize when you're in a runaway loop and stop yourself. Use when the same tool call has repeated 3× with the same args, when the same error class has fired 3× in a turn, when you've been told the same correction twice, when "let me try one more variation" is the third small variation, or when a refinement loop is orbiting rather than converging. The right move on a trip is to switch from action to inquiry — read events.jsonl, list assumptions, look for contradictions, ask the human, file a chainlink — not to retry harder.

Approach an app, tool, codebase, website, or product as a genuine first-time user with zero insider context — try it out using only the information provided, get confused where a real newcomer would, and surface the "obvious" questions that people who built or use the thing daily can no longer see. Use this whenever the user wants a first-time-user test, a fresh perspective, a naive walkthrough, a cold read of their README/onboarding/docs/UI, or says things like "pretend you've never seen this", "would a new user get this?", "test my app like a beginner", "what would confuse someone new?", or "give me fresh eyes on this". Also use it when someone wants to find gaps in onboarding, docs, or first-run experience — even if they don't say "fresh eyes" explicitly.