Results for “rule”

Trigger: clean architecture, hexagonal architecture, domain model, state machine, boundary decoupling. Scope: Software modular design, dependency boundaries, architectural layering. Boundary: Excludes frontend aesthetic styling.

Configure and use UnoCSS, an instant atomic CSS engine with presets, rules, shortcuts, and integrations for Vite and Nuxt.

A comprehensive form component for data collection, validation, and submission in Naive UI. Provides flexible layout options, built-in validation rules, and seamless integration with various input components.

Scaffolds a new Remotion video project, guides React markup design with video layout rules, and starts the Remotion Studio preview server.

Configure and use UnoCSS, an instant atomic CSS engine that is a superset of Tailwind CSS, including rules, shortcuts, presets, and integrations.

Build a single renderable HyperFrames composition using HTML with data-* timing attributes, clips, tracks, sub-compositions, variables, and deterministic rendering rules.

Applies a battle-tested bilingual web-design system with typography, responsive rules, and performance patterns for Yuval Avidani's projects.

Organizes 70+ React and Next.js performance optimization rules across 8 priority categories for use when writing, reviewing, or refactoring code.

Anti-pattern detector and design rules for AI coding agents. Catches the specific mistakes AI makes when generating UI: gray text on color, nested cards, broken buttons, missing states. Use before shipping any frontend.

Provides a foundational motion system for React/Next.js apps using motion/react, including tokens, spring presets, accessibility enforcement, SSR safety, and performance rules.

Optimize React and Next.js applications with 70 performance rules across 8 categories, prioritized by impact for automated refactoring and code generation.

Optimizes React and Next.js performance with 69 prioritized rules covering waterfalls, bundle size, server-side rendering, and re-rendering patterns.

Provides atomic motion rules, multi-phase scene blueprints, scene transitions, motion-design techniques, and runtime adapters (GSAP, Lottie, Three.js, Anime.js, CSS, WAAPI, TypeGPU) for composing animations with HyperFrames.

Generates premium React/Next.js frontend code with deterministic typography, calibrated color palettes, and motion physics, enforcing anti-cliché design rules and performance guardrails.

Create and manage Ethereum wallets, including EOAs, smart contract wallets, Safe multisig, EIP-7702, and account abstraction, with AI agent key safety rules and transaction approval thresholds.

Reference for producing Adobe Document Authoring (DA) and Edge Delivery Services (EDS) compatible content, covering HTML generation, media uploads, admin API usage, and silent-failure rules.

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.

Use to audit whether customer support is reachable for people with access needs — channels, hours, authentication barriers, CAPTCHA, voice-only paths, and alternate formats. Trigger for "support accessibility audit", "can customers with disabilities reach us", CAPTCHA on contact form, voice-only support, alternate format requests, or accessibility checklist for CX.

Optimizes React and Next.js performance with 70+ rules across 8 priority categories, covering waterfalls, bundle size, server-side, client fetching, re-renders, rendering, JS micro-perf, and advanced patterns. Use when writing, reviewing, or refactoring React/Next.js code.

React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.

Use this skill when the user asks about passenger-carrying CMVs — buses, motorcoaches, charter operations, school buses, limousines, shuttle services. Covers different HOS rules (10-hour driving / 15-hour on-duty / no 34-restart), Class C CDL with P endorsement, S endorsement for school bus, FMCSA Hours-of-Service for passenger vehicles, $5M insurance minimum, BMC-32 filing, accessibility requirements, and how passenger ops differ from property. Cite 49 CFR 395.5 + 387.33.

Use to decide which support channels to offer, add, or retire, and to audit channel mix against accessibility obligations and cost to serve. Trigger for "should we add chat", "which channels should we offer", channel strategy, cost to serve by channel, accessibility requirements for support, opening a new contact route, or retiring phone or email.

Cascade PCB components, add lumped elements, export Touchstone, and bridge to eye diagram or antenna array workflows. TRIGGER: user asks to cascade or connect multiple RF PCB components, add lumped R/L/C, export S-parameters to Touchstone, or combine PCB elements into a circuit. Invoke BEFORE writing pcbcascade or circuit code — cascade rules and port matching are non-obvious. SKIP: designing individual components (use the specific matlab-design-pcb-* skill), EM analysis of a single component (use matlab-analyze-em), material/stackup setup only (use matlab-manage-pcb-material), optimization (use matlab-optimize-pcb-design).

Complete shadcn/ui component management for adding, searching, fixing, styling, and composing UI in any React project. Use this skill whenever the user mentions shadcn, shadcn/ui, adding UI components, building forms or dashboards with Radix, working with component registries (@shadcn, @magicui, @tailark), or any task involving npx shadcn CLI commands. Also trigger when the user asks to fix styling issues, build a settings page, dashboard, or modal flow in a project that uses shadcn/ui — even if they don't say "shadcn" explicitly. This skill manages the full component lifecycle: search, add, view, diff, smart-merge upstream updates, and enforce critical rules for forms, composition, styling, and icons.

Audits an EXISTING UI/codebase for generic AI patterns and applies targeted craft fixes — layout, interactivity, content, iconography, and code quality — without discarding the project's own identity. Use when a UI looks flat, generic, or "AI-slop" and there is code to improve, not build from scratch. Triggers on: "improve the design", "looks generic", "not polished enough", "redesign this", "elevate the UI", "it looks boring", "make it better looking", "apply taste", "design review". Works with any CSS framework. For designing a NEW project's identity from a brief, use `taste-skill` instead — this skill only upgrades what's already built. Source: github.com/Leonxlnx/taste-skill (redesign-skill), restored to the full checklist + the project-identity rule the earlier port had dropped.