Design skills

Use when asked to explain or teach a subsystem, module, pattern, or change in progressive layers from purpose to code depth. Not for design rationale: use why. Not for source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when the user asks to restore service from a known failure with a prescribed recovery operation. Not for design-time failure definition or open-ended debugging.

The English summary is being prepared. Showing the original description.

Use when asked to build, run, or triage a coverage-guided C/C++ fuzz campaign on the libFuzzer or AFL++ engine. Not for harness design: use fuzz-harness-writing.

The English summary is being prepared. Showing the original description.

Use when planning an end-to-end fuzzing program for a project: engine and target selection, corpus management, and CI or nightly wiring. Not for harness design: use fuzz-harness-writing. Not for engine operation or triage: use libfuzzer. Not for sanitizer flag reference: use sanitizers.

The English summary is being prepared. Showing the original description.

Use when a user builds or styles a web frontend or asks to make it not look AI-generated. Not for component-level UI work without the token system: use frontend-ui-engineering.

The English summary is being prepared. Showing the original description.

Use when asked to design, write, review, refactor, lint, or performance-diagnose Lean 4 proofs, libraries, or tactics. Not for non-Lean code or changes outside source, API, proof, or linter scope.

The English summary is being prepared. Showing the original description.

Use when asked to build spring, easing, gesture, and choreographed animations with correct physics and reduced-motion support. Not for auditing existing motion or finding animation opportunities.

The English summary is being prepared. Showing the original description.

Use when asked to prototype one design question through a cheap logic or UI experiment, including button-driven state-model checks. Not for polished artifacts: use polished-web-prototype.

The English summary is being prepared. Showing the original description.

Use when a human invokes this skill to build a webhook UI that wakes a bot. Not for unpreviewed or unapproved credential, host, Tailscale, deployment, remote, paid, or irreversible changes.

The English summary is being prepared. Showing the original description.

Use when starting UI work, defining palettes or tokens, fixing AI-generic UI, or persisting a design system to DESIGN.md (modes: implement, persist). Not for live URLs: use web-design-review.

The English summary is being prepared. Showing the original description.

Use when /design-variants generates distinct design directions and a gallery for selection. Not for one polished artifact: use polished-web-prototype. Not for token-system picking: use design.

The English summary is being prepared. Showing the original description.

Use when the user runs /web-design-review with a URL to visually audit and fix a live UI. Not for design direction: use design. Not for variant galleries: use design-variants.

The English summary is being prepared. Showing the original description.

Use when writing, editing, cleaning, or refactoring Tailwind classes, components, or configuration. Not for read-only audits of Tailwind code, or general CSS without Tailwind.

The English summary is being prepared. Showing the original description.

Use when asked to build or modify production-quality components, layouts, state, and pages with WCAG 2.1 AA and real content. Not for token-system design: use frontend-design-deslop.

The English summary is being prepared. Showing the original description.

Use when deciding what an interface should do before UI is built or audited: consequences, action scope, reachable states, naming, and accessibility. Not for visual implementation: use prototype.

The English summary is being prepared. Showing the original description.

Use when directing, building, or auditing React/Next.js Tailwind UI: visual direction, responsive/dark-mode retrofits, UX audits. Not for typography or motion: use typography-audit or ui-animation.

The English summary is being prepared. Showing the original description.

Use when creative work is requested with no approved design, or a raw idea or repository must be developed into an approved design document. Not for work with an approved design in context.

The English summary is being prepared. Showing the original description.

Use when a protocol, concurrent algorithm, or design needs a model-checked TLA+ or Alloy spec, or a TLC or Apalache trace needs reading. Not for choosing when to model: use validation-first-driven.

The English summary is being prepared. Showing the original description.

Use when asked to design a module interface, seam, or testable boundary. Not for UI direction picking: use design. No source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when asked to run /ios-build-fix to fix a failing iOS build, regenerate an Xcode project from project.yml, or correct UI behavior. Not for a clean rebuild: use ios-build-cleanup.

The English summary is being prepared. Showing the original description.

Use when invoked to apply an invariant-first, fail-fast, special-case-eliminating baseline. Not for domain models in types: use type-driven. Not for design-by-contract: use contract-driven.

The English summary is being prepared. Showing the original description.

Use when asked to design or change a public API, route, CLI flag, or module boundary. Not for remote, credential, publish, deploy, or irreversible changes.

The English summary is being prepared. Showing the original description.

Record one authorized non-remediation terminal outcome in Proto UI's autonomous-maintenance state. Use after a supported no-finding result, an independently rejected finding, or a blocked mission whose terminal evidence is complete.

The English summary is being prepared. Showing the original description.

Select at most one eligible Proto UI work item and return a read-only proposal without changing GitHub or repository state. Use after pui-orient when requested contribution work is not yet bounded, or when a user asks what ready task fits the current capability and permission envelope. Do not post a claim, assign anyone, decide readiness, or invent work.

The English summary is being prepared. Showing the original description.