Loading...
Loading...
Found 2 Skills
Triggers when a user asks to prototype a decision, compare visible or behavioral options in throwaway pages, keep prototyping through a consultant, grilling, or wayfinder session, or says /prototyping. It builds one loopback session that grows step by step and also handles a one-off "prototype this" request. Not for durable standalone HTML artifacts, polished product demos, browser QA, or integrating selected prototype code into an application.
Aggressively produce self-contained HTML artifacts instead of Markdown for substantial agent outputs. Use when the user asks for a doc, plan, spec, report, review, PR description, explainer, summary, comparison, research artifact, dashboard, diagram, flowchart, timeline, deck, slides, prototype, design reference, component sheet, editor, prompt tuner, config editor, triage board, or any human-facing deliverable that benefits from layout, visual hierarchy, navigation, diagrams, interactivity, or sharing. Default to this skill even when the user does not explicitly request HTML; stay in plain chat only for very short replies, code-only snippets, terminal commands, or explicit non-HTML requests.