guidelines▌

Opinionated backend architecture standards for Node.js, Express, and TypeScript microservices. \n \n Enforces strict layered architecture (routes → controllers → services → repositories) with zero business logic in routes and mandatory BaseController pattern for all controllers \n Requires Zod validation on all external input, Sentry error tracking on all exceptions, and unifiedConfig as the single source for environment configuration \n Includes Backend Feasibility & Risk Index (BFRI) scor

Rust naming, formatting, and best-practice guidelines covering 50 core rules. \n \n Covers naming conventions (no get_ prefix, iterator patterns, conversion methods), data types (newtypes, slice patterns, pre-allocation), and string handling (prefer bytes for ASCII, use Cow<str> when appropriate) \n Error handling guidance includes ? propagation over try!() , meaningful lifetime names, and lock ordering for concurrency safety \n Includes deprecation mappings (e.g., lazy_static! to OnceLock

Write user-facing copy following Sentry's brand guidelines.

Apply Anthropic's official brand colors, typography, and visual identity to artifacts. \n \n Includes six brand colors (dark, light, mid/light gray, orange, blue, green) with RGB values for precise matching across platforms \n Automatically applies Poppins font to headings (24pt+) and Lora font to body text, with fallback to Arial and Georgia if custom fonts unavailable \n Smart color selection adapts text and accent colors based on background for readability and visual hierarchy \n Works with s

Write user-facing copy following Sentry's brand guidelines.

Project-specific architecture, code patterns, and deployment guidelines for Zenith application. \n \n Next.js 15 frontend with FastAPI backend, Supabase PostgreSQL database, and Claude API integration via structured output \n Includes standardized API response formats, custom React hooks, and Pydantic models for type safety across stack \n Testing requirements: pytest with 80% coverage minimum for backend, React Testing Library for frontend, Playwright for E2E \n Deployment via Google Cloud Run

Smart contract development advisor applying Trail of Bits' security and design guidelines to analyze codebases systematically. \n \n Performs five-phase analysis covering documentation generation, architecture review, upgradeability assessment, implementation quality checks, and dependency evaluation \n Assesses 11 comprehensive areas including function composition, inheritance patterns, event logging, common pitfalls, proxy security, and testing coverage \n Generates plain English system descri

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

Use this skill to design and review Swift APIs that are clear at the point of use, fluent in call sites, and aligned with established Swift naming and labeling conventions. Prioritize readability, explicit intent, and consistency across declarations, call sites, and documentation comments.

Comprehensive guide for modern React development, emphasizing Suspense-based data fetching, lazy loading, proper file organization, and performance optimization.