Results for “cover-design”

Designs new software features and multi-component changes for the current repo into implementation-ready BDD specs via autonomous codebase research, then commits the design for review (runs to completion without mid-design questions). Scope covers new features, greenfield design, and multi-component changes. Not for hardware/physical-system design, out-of-repo questions, single-file refactors, or known-root-cause bugs (those go to direct edits or systematic-debugging).

Styles web pages with CSS, covering selectors, flexbox, grid, custom properties, and animations for responsive UI components.

Build accessible React interfaces with Chakra UI, covering theming, responsive styles, color mode, and component composition.

Design and implement SLIs, SLOs, and error budgets for production services. Covers SLI selection, SLO target-setting, error budget calculation, burn-rate alerting, and error budget policy. Use when asked about "SLO", "SLI", "error budget", "reliability targets", "burn rate", "uptime SLA", or when designing alerting for a production service. Do NOT use for: application-level performance optimization — use `web-performance` for frontend.

Guides the design and review of interactive Salesforce Flow screens, covering navigation, validation, component choice, and commit timing to avoid common UX failures.

Use when designing or implementing product-grade web motion like Stripe, Linear, Apple, and Vercel. Covers motion principles, easing/duration defaults, choreography patterns, scroll/hover interactions, performance, accessibility (reduced motion), and implementation guidance.

Creates a clean horizontal-swipe HTML deck for pitches, overviews, or study materials with cover, content pages, progress bar, and keyboard navigation.

HTML-as-medium design for hi-fi prototypes, pitch decks, and motion exports (PPTX/PDF). USE WHEN the user asks for a one-pager, pitch deck, visual deck, capture deck, export deck to PDF or PowerPoint, or HTML visuals from pursuit intel. Builds numbered slide HTML under pursuits/{slug}/05_visuals/ and exports via vendored Node scripts (export_deck_pdf.mjs, export_deck_pptx.mjs). DO NOT USE FOR Word/Excel office docs (use renderers) or proposal prose (use proposal-generator).

Creates editorial-minimalist web prototypes with warm monochrome canvas, serif display and grotesque body typography, hairline borders, and ambient micro-motion.

Design one-off HTML artifacts (landing, deck, prototype).

设计原型专家团入口。用于 Codex CLI 的 $expert-design 调用。 覆盖需求发现、设计系统选择、原型生成、质量审查和导出交付。 触发词：设计原型、UI、UX、设计系统、高保真、HTML 原型、品牌设计、页面设计

Throwaway HTML mockups: 2-3 design variants to compare.

Improve the visual design of a frontend by restyling components one at a time, with approval gates and no functional changes.

Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style), not a decorative one. Encodes the discipline — columns + modules + baseline, grotesque type, flush-left ragged-right, restrained black/white/red — AND the front-end engineering that makes the grid load-bearing: one CSS-variable source of truth, a grid-toggle overlay that lives in the SAME content box as the content, subgrid 'bands' so every element snaps to a column line, an 8px baseline lock, and runtime optical alignment that puts display type's ink (not its box) on the line. Ships a scaffold generator and a Puppeteer harness that proves 0px adherence. Use when: building any editorial, magazine, report, or longform page that must read as rigorously grid-aligned, Swiss, International Typographic Style, or 'Müller-Brockmann'. Triggers: magazine spread, grid system, Swiss design, editorial layout, show the grid, grid overlay toggle, baseline grid, modular grid, 12-column layout, 瑞士网格, 版面网格.

Create award-winning, immersive web experiences with dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation.

Review a built frontend against its chosen direction, catch drift back to generic AI defaults, enforce state coverage, ethical patterns, UX heuristics, and polish, and check contrast with APCA (not the legacy WCAG ratio). Produces specific, prioritized fixes — never vibes-based feedback. Works with pasted screenshots or Playwright MCP automated capture. Load when the user asks to review a UI, audit a design, check if a frontend looks generic or vibecoded, evaluate visual quality or polish, says "review this UI", "is this design good", "audit my frontend", "does this feel like [product]", "design QA", or when frontend-design routes here. Sub-skill of frontend-design.

Design one-off HTML artifacts (landing, deck, prototype).

Expert UI designer specializing in visual design systems, component libraries, and pixel-perfect interface creation. Creates beautiful, consistent, accessible user interfaces that enhance UX and reflect brand identity

Design one-off HTML artifacts (landing, deck, prototype).

Audits the course learn experience for section coverage, sidebar rendering, layout, design token compliance, tenant isolation, accessibility, data flow, and component quality. Use when reviewing course UI code quality or diagnosing learn experience issues. Pass a course slug or "all".

Performs comprehensive exploratory testing on a website using browser automation, covering user journeys, forms, errors, accessibility, responsiveness, performance, and security basics.

Design and review native DTOs in WordPress plugins without better-data, covering immutable data carriers, explicit hydration, strict coercion, WP_Error validation, sensitive-field handling, and layer boundaries.

Audits and enforces web interface standards covering accessibility, performance, UX, and code quality from Vercel Engineering's Web Interface Guidelines. Use this skill when reviewing UI code, checking accessibility compliance, auditing design implementations, running pre-merge frontend checks, or when someone asks to "review my UI", "check accessibility", "check my site", "audit design", or "is this component correct". Apply proactively when writing form elements, interactive components, images, animations, or anything that users directly touch — these guidelines prevent common mistakes before they reach production.

Technical architecture guide for building a multi-purpose consent preference center. Covers per-purpose granularity, easy withdrawal under Article 7(3), version history, audit trails, and IAB Transparency and Consent Framework v2.2 integration. Includes database schema, API design, and UI component specifications.

Use when designing or auditing the evaluation of an ASE (IEEE/ACM Automated Software Engineering) paper, covering real subject systems, fair runnable tool baselines, task-matched effectiveness metrics, ablations that isolate a learned component, oracle and correctness validation, contamination-aware LLM handling, and provenance for mining.

React composition and performance optimization patterns from Vercel. Use when building component libraries, refactoring components with prop proliferation, optimizing React/Next.js performance, or designing scalable component architectures. Covers composition patterns, React 19 APIs, performance optimization across waterfalls, bundle size, server/client rendering, and re-render optimization.

Jest is a comprehensive JavaScript testing framework built by Meta, designed for zero-configuration testing of JavaScript and TypeScript applications. It provides a complete ecosystem for unit testing, integration testing, and snapshot testing with built-in code coverage, mocking capabilities, and parallel test execution. Jest works seamlessly with React, Node.js, Angular, Vue, and virtually any JavaScript project, making it the most widely adopted testing framework in the ecosystem.

Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.