Loading...
Loading...
Found 17 Skills
Laws of UX critique skill. Use when evaluating mockups, screenshots, design specs, prototypes, flows, onboarding, checkout, dashboards, forms, or design-review requests, even when the user does not say UX or name a law. Output the 2-4 most relevant laws with specific application and law-grounded recommendations. Do not use for pure frontend implementation code review, WCAG/accessibility audits, or brand/visual-identity critique unless interaction usability is also in scope.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Use before building anything new or when a plan needs review. Not for bug fixes or small edits.
Analyze construction drawings to extract dimensions, annotations, symbols, and metadata. Support quantity takeoff and design review automation.
Final gate of the Flows app certification flow for external submission. Verifies that flows-app-brief, flows-code-review, and flows-design-review have all been run and are in a passing state (App-Brief.md complete, 0 Must Fix in latest code review, design average ≥ 3.8), then runs `npx @cognite/cli apps submit` to zip the repo and pre-populate the submission form. Use when the user asks to submit a Flows app for certification, run flows-external-app-submit, or finalize an app for external review.
Structure compelling design presentations for stakeholders, reviews, and showcases.
Critique UI/UX designs for clarity, hierarchy, interaction, accessibility, and craft. Use for design reviews, PR feedback on UI changes, evaluating mockups, checking if a component is ship-ready, or when honest feedback is needed on whether something meets a high bar.
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.
Surfaces and assesses hidden assumptions behind decisions, designs, or recurring patterns — use when reviewing a design before committing, reflecting on recurring problems, or questioning why the same kinds of issues keep appearing
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.
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.
Continuously question users about their plan or design. Suitable for scenarios where users want to stress-test their plan before building, or when using any "grill" trigger phrases.