Loading...
Loading...
Found 37 Skills
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use whenever the user wants to stress-test a plan, get grilled on their design, mentions "grill me", "challenge my thinking", "poke holes in this", "play devil's advocate", "review my approach", "what am I missing", "pressure test", "tell me why this won't work", or asks for feedback on a plan, proposal, architecture decision, or technical design. Even if they're just explaining an idea or asking "does this make sense?", treat it as a signal to invoke this skill and interview them thoroughly. Don't wait for an explicit "grill me" — any request for input on a plan or decision warrants this.
Pencil Design Skill for Team Workflows (Phase 2). Produce design.pen (or declare no UI design) based on requirements and plans, and prepare G2 design review materials.
Walden drafts and maintains feature specs in `.walden/specs/` with EARS requirements, reviewed design, tasks, and executable proofs. Use when the user asks for Walden, a feature spec, requirements, design, an implementation plan, or work governed by an existing Walden spec. First distinguish contract-preserving maintenance from new or changed behavior.
Structure compelling design presentations for stakeholders, reviews, and showcases.
Read a Canva design and return structured, actionable design feedback — visual hierarchy, copy/messaging, layout & spacing, consistency, readability, and accessibility. Read-only; makes no changes to the design. Use when the user asks to "review my design", "give me feedback on this", "critique my deck/poster/flyer", "how can I improve this design", or "what's wrong with this slide".
Run taste-informed design reviews using Observation > Principle > Question. Use when facilitating design critiques, improving feedback quality on a team, or building a shared vocabulary for quality.
Three-phase design review. Chain architect → refiner → critique subagents. Triggers on: 'design review', 'architecture review', '/arc', system design proposals, significant refactoring decisions, new service or module design.
Design QA audit — red flags, severity classification, visual quality scorecard. Use when asked to "QA the design", "check visual quality", "design review before launch", "visual bugs", "design audit", or "does this look right".
Set up the Inflight feedback widget, authenticate with the CLI, and share staging URLs for design review. Use when the user wants to collect design feedback, add Inflight to a project, or share a staging deployment for review.
Grill the user relentlessly about any idea, plan, or design, a round of unblocked decisions at a time, each with a recommended answer, until you both share the same picture. Use when the user wants to stress-test or pressure-test an idea, says "grill me", "grill this plan", "poke holes in this", "interrogate my design", or otherwise asks to interrogate a concept before committing to it, whether a rough idea, a plan file, an architecture, or a PR.
Use when stress-testing a plan, getting grilled on a design, or before writing a PRD.
You MUST use this when work has to be designed before any code is written - a new feature, a change to product or UX behavior, an architecture change, success criteria that are still unclear, or a choice between two materially different approaches - including a spec revision after a document review. A fully specified mechanical refactor, a localized fix whose expected behavior is known, or a config change with a single possible outcome gets no spec; the skill hands it to implement in one sentence. Turns the request into a spec with checkable acceptance criteria behind an explicit approval. Replaces devflow scope-triage.