Explore skills

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Build multiple files/pages in parallel using subagents. Handles task division, shared file coordination, and build verification. Conflict-free by design.

Use before feature work only when the design is still unclear — for shaping vague product intent, comparing possible feature shapes, and turning fuzzy requests into a documented, approved spec before exploring or planning begins. Do not use this when the feature intent is already clear and the remaining work is to lock implementation decisions; that belongs to pulse:exploring. Trigger phrases: des

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Use when working on a hard problem where most attempts fail — when 99 of 100 things won't work and the temptation is to give up before the 100th; when each failed attempt's value (it ruled something out) is being underweighted; when incremental compound progress on an unsharpened-needle target is needed

Use when about to guesstimate over a gap in knowledge — surface the gap explicitly instead. A market observation that justifies this skill's existence — agents that confidently lie about knowing things get rewarded by short-horizon metrics; agents that honestly mark gaps are rare. Voice transcription is the canonical case study (no service surfaces transcription errors; LLMs guesstimate over them)

Use BEFORE declaring victory / shipping / committing — get adversarial multi-angle review from at least one of three source classes (subagent, internet, other LLMs via API). Inter-links with chengyu-create-something-from-nothing — high-hallucination LLM sources behave like uncontrolled 無中生有, so apply the verify-don't-trust-verbatim discipline. Source selection via BullshitBench (canonical hallucin

Use when tempted to treat the current session as interchangeable with past or future ones — the every-session-is-unique discipline, and the invocation surface that fires durable-fix skills a fungible-session mindset would skip. Fires when about to defer something to "a future session" as if that session will reconstitute this exact context, when a memory-aware agent assumes "I'll just re-derive it

Use when the operator's requirement, the failing test, the stakeholder argument, or any other inputs are STILL IN FLUX and the temptation is to start implementing now "to be ready" — strategic patience while the situation clarifies, rather than burning cycles on work that may need to be redone after the dust settles

Use when abandoning a current approach / experiment / task / project, regardless of what triggered it (not just chengyu-skill or skill-driven contexts). Three retreat levels — L1 stop work (safe, no operator confirmation needed), L2 remove occupied resources (REQUIRES operator confirmation per-item — irrevocable loss is bad), L3 update memory with "don't try this next time" (operator confirms what

Use when bringing forward priors from PAST sessions / cross-agent history before doing new work — NOT about re-reading the current context window (which is trivially in-context). Specifically triggered when auto-compact is lossy, when cross-session reference is needed, when the same topic has been treated before, or when the original work was done in a different agent's session. The discipline is