Results for “design-chain”

Expert in designing effective prompts for LLM-powered applications. Masters prompt structure, context management, output formatting, and prompt evaluation. Use when: prompt engineering, system prompt, few-shot, chain of thought, prompt design.

Ark protocol: VTXOs (Virtual Transaction Outputs) batched off-chain with periodic on-chain settlement. ARKADE (Ark Labs) is the first mainnet implementation. ASP (Ark Service Provider) coordinates rounds; users keep unilateral exit. USE WHEN: building Ark integrations, evaluating Ark vs Lightning, designing batched payment flows.

Design, review, and debug Batch Apex contracts, scope sizing, stateful behavior, chaining, and AsyncApexJob monitoring.

Use when designing a Digital Down Converter (DDC) using dsphdl System objects. Triggers on requests involving DDC design, frequency down-conversion for FPGA/ASIC, NCO + mixer + decimation filter chains, fractional/non-integer sample rate conversion, or HDL-optimized receiver front-end signal processing.

Composite skill — design, scaffold, build, and verify a UI in one workflow. Chains ui-ux-pro-max or web-design-guidelines (audit/principles) → shadcn or tailwind-design-system (component scaffold) → impeccable or frontend-design (build) → webapp-testing (verify). Use when the task is "build this page", "design and implement X", or any new UI surface.

Chains architecture review, implementation, and pull request creation to take a story from design through to a convention-compliant PR.

Implements SDD change tasks from specs and design, enforcing workload budgets, supporting chain strategies, and merging apply-progress across batches.

Turn a chosen design direction into a canonical DESIGN.md plus production tokens that don't look vibecoded — state-level colors (8-step neutral ramp, rest/hover/active/ disabled, focus ring), APCA-checked contrast, typography, spacing/radius/motion/elevation, an icon strategy, and component contracts for the core atoms. Emits tokens in the project's stack format (shadcn HSL vars or Tailwind v4 @theme). Load when the user asks to build a design system, generate design tokens, create a DESIGN.md, set up a theme, design a color or type system, pick icons, or when frontend-design routes here. Replaces design-tokens-craft and icon-craft. Sub-skill of frontend-design. Reads DIRECTION.md first.

Validate process decomposition and architecture design quality before execution begins. Load when the setup-evaluator agent fires (automatic for agent-chain tasks), or when user says "evaluate this setup", "check the decomposition", "validate the architecture", "is this plan sound", "review the agent design". Catches structural errors, missing knowledge, unrealistic step ordering, and topology mismatches. Does NOT modify — only evaluates.

Design decentralized exchanges. TRIGGERS - Use when user needs help with dex-design related tasks.

Creates comprehensive design systems with tokens, components, patterns, and documentation

71 套品牌级设计系统知识库，覆盖 AI/LLM、开发工具、生产力、金融科技、电商、媒体、汽车等 8 大类别。 每套系统包含 9 段标准结构：视觉主题、色彩、排版、组件、布局、深度、注意事项、响应式、Agent 指南。 触发词：设计系统、选择风格、品牌风格、设计令牌、DESIGN.md、配色方案

Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues.

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.

Creates and manages design tokens with a three-layer architecture (primitive, semantic, component), generates CSS variables and component specifications, and produces brand-compliant slide presentations with Chart.js integration.

SKILL — Stitch Mastery

Identifies reusable UI patterns, components, and design tokens, then extracts and consolidates them into a design system for systematic reuse.

Provides a design system specification for NVIDIA's marketing pages, including color tokens, typography hierarchy, and component patterns for building engineering-style landing pages.

Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.

Builds and governs design systems with a three-layer token architecture, component specs, and design-to-code handoff, including slide generation.

Establish clear naming conventions for design assets, components, and tokens to make design systems predictable and maintainable.

Generate technical architecture diagrams, pipeline flows, layer/stack diagrams, and system illustrations as standalone HTML files. Uses a dark-mode design system with embedded CSS and inline SVG. Use when the user needs architecture diagrams, system illustrations, flow charts, or technical visualizations.

Onboards brand tokens and generates a 12-token CSS palette for consistent, WCAG-AA-compliant HTML document styling across markdown conversions.

Define and organize design tokens for color, spacing, typography, elevation, and motion with naming conventions and usage guidance.

Design decentralized exchanges. TRIGGERS - Use when user needs help with dex-design related tasks.

Creates and manages design token systems with three-layer architecture, generates CSS variables, validates token usage, and produces brand-compliant slide presentations with Chart.js and contextual decision logic.

Use when a project's visual foundation — typography scale, color palette, spacing — needs establishing as canonical design tokens; the target has no design system yet (the 0→1 case), the A-Team design phase needs tokens for the lofi and the spec's design-system mapping, or a human runs the token flow standalone ("set up the design system", "pick fonts and colors", "define design tokens"). In the A-Team pipeline it is conducted by ateam-design in pipeline mode — no interview; inputs derive from context.md's

System Design

Orchestrator + builder for distinctive, production-grade frontends that don't look AI-generated. Derives stack and design context from product-soul/PRD/specs, then runs the anti-slop chain — explore distinct directions, lock a DESIGN.md system, build from golden examples with mandatory polish + every interactive/empty/loading/error state, then review. Load when the user asks to build a UI, design a frontend, build a landing page or dashboard or web app, beautify or redesign a page, make a UI look premium/playful/editorial, says "build me a frontend", "make this not look AI-generated", "design this interface", "give this real polish", or "frontend design". Routes to design-direction, design-system, design-review.

Rebuild existing site pages with byte-faithful content on a separately-defined donor design system, preserving text, images, and metadata while applying a new visual design.