design▌

Templates and guidelines for writing company-standard internal communications across multiple formats. \n \n Covers seven communication types: 3P updates, company newsletters, FAQ responses, status reports, leadership updates, project updates, and incident reports \n Each format has a dedicated guideline file in the examples/ directory with specific instructions for tone, structure, and content \n Helps maintain consistency across internal communications by enforcing company-preferred formats an

Audit UI code against Web Interface Guidelines with live rule fetching. \n \n Fetches the latest guidelines from a remote source before each review, ensuring compliance checks stay current \n Accepts file paths or patterns as arguments; prompts for input if none provided \n Outputs findings in concise file:line format for quick scanning and remediation \n Covers accessibility, design patterns, and best practices as defined in the fetched ruleset \n

Production-ready React UI components with TailwindCSS, Radix UI, and shadcn/ui. \n \n Three-layer architecture combining Tailwind utilities, Radix primitives, and shadcn/ui components for accessible, customizable interfaces \n Comprehensive review and audit capabilities covering accessibility (WCAG AA/AAA), performance, responsive design, and design system consistency \n Design token system with three-tier structure (primitive, semantic, component) using OKLCH color space and CSS variables for t

Create visually-driven design artifacts from philosophical aesthetic movements, expressed as pristine PDF or PNG artworks. \n \n Generates custom design philosophies (aesthetic movements articulated through form, space, color, and composition) as markdown foundations \n Expresses philosophies visually through museum-quality single or multi-page PDF/PNG compositions with minimal, integrated text \n Embeds subtle conceptual references invisibly into abstract compositions, rewarding deeper viewing

Establish design tokens, spacing systems, and color palettes for cohesive, accessible visual designs. \n \n Provides modular typography scale, 8-point spacing grid, semantic color tokens, and iconography system with CSS variable templates \n Includes WCAG contrast requirements (4.5:1 for body text, 3:1 for UI), dark mode implementation patterns, and font-pairing guidelines \n Covers responsive typography with clamp() , color accessibility checking, and vertical rhythm techniques for visual consi

Modern framework patterns for building reusable, maintainable UI components across React, Vue, and Svelte. \n \n Covers three composition strategies: compound components, render props, and slots, with framework-specific examples and use cases \n Compares five CSS-in-JS solutions (Tailwind, CSS Modules, styled-components, Emotion, Vanilla Extract) with guidance on when to use each \n Includes component API design principles, accessibility best practices, and patterns for controlled/uncontrolled c

Microinteractions, motion design, and state transitions that enhance UI polish and user feedback. \n \n Covers timing guidelines (100ms to 500ms+), easing functions, and purposeful motion principles for feedback, orientation, and focus \n Includes patterns for loading states, skeleton screens, progress indicators, toggles, page transitions, ripple effects, and swipe gestures \n Provides CSS keyframe animations and transition examples alongside Framer Motion implementations for React \n Built-in

Cross-platform mobile apps with React Native styling, navigation, and performant Reanimated animations. \n \n Covers StyleSheet patterns, dynamic styling, Flexbox layouts, and platform-specific designs for iOS and Android \n Includes React Navigation 6+ setup for stack and tab navigators with type-safe route definitions \n Provides Reanimated 3 fundamentals including shared values, animated styles, and Gesture Handler integration for drag interactions \n Features best practices for performance (

本 Skills 提供了一套工业级标准的 UI 设计规范，用于 Pencil MCP 设计工作。

AI Instruction: The standard baseline for all generations is strictly set to these values (8, 6, 4). Do not ask the user to edit this file. Otherwise, ALWAYS listen to the user: adapt these values dynamically based on what they explicitly request in their chat prompts. Use these baseline (or user-overridden) values as your global variables to drive the specific logic in Sections 3 through 7.