frontend▌

$22

Structured guidance for database selection, schema design, and query optimization decisions. \n \n Covers six core areas: database selection (PostgreSQL, Neon, Turso, SQLite), ORM choice (Drizzle, Prisma, Kysely), schema normalization, indexing strategy, query optimization, and safe migrations \n Emphasizes context-driven decision-making rather than defaulting to PostgreSQL; includes a checklist for schema design prerequisites \n Highlights common anti-patterns: unnecessary PostgreSQL adoption,

Framework-driven guidance for writing specs and design documents from seven product leaders. \n \n Determine fidelity level upfront: low-fi sketches for alignment, high-fi specs for implementation details \n Favor prototypes over static documentation; test the feel with real software rather than screenshots \n Use fat marker sketches and breadboarding to avoid getting stuck on UI details like colors or spacing \n Recognize that temporary design shortcuts often become permanent product decisions;

React library for building composable AI chat interfaces with streaming support and flexible runtime adapters. \n \n Layered architecture with UI primitives (ThreadPrimitive, MessagePrimitive, ComposerPrimitive), context hooks, runtime layer, and pluggable backend adapters \n Supports multiple runtime options: Vercel AI SDK, LangGraph, external state stores (Redux/Zustand), AG-UI protocol, A2A protocol, or custom APIs \n Core packages include @assistant-ui/react for primitives, @assistant-ui/rea

Framework-based guidance for building and scaling design systems from product leaders at Figma and Airbnb. \n \n Covers four core principles: separating conceptual design from production output, leveraging design systems for organizational scaling, creating self-teaching assets, and evolving beyond flat design toward dimensional interfaces \n Provides assessment questions to determine scope (component library, tokens, documentation), adoption strategy, and success metrics \n Flags common pitfall

Design system toolkit for generating tokens, documenting components, and enabling design-dev handoff. \n \n Generates complete design tokens (colors, typography, spacing, shadows, animations) from a single brand color in multiple formats (JSON, CSS, SCSS) \n Includes three style presets (modern, classic, playful) and an 8pt spacing grid system with responsive breakpoints \n Covers component architecture, accessibility compliance, and developer handoff documentation for maintaining visual consist

Duit enables backend-driven UI in Flutter applications. The server controls both data and layout via JSON, allowing UI updates without app releases.

Vue 3 components and composables in JavaScript with comprehensive JSDoc type coverage, no TypeScript required. \n \n Builds with <script setup> and .mjs modules using @typedef , @param , and @returns JSDoc annotations for full type safety without a TypeScript compiler \n Covers component architecture (props, emits, slots), custom composables, Pinia state management, and Vue Router configuration entirely in vanilla JavaScript \n Includes ESLint JSDoc plugin verification to ensure all public

Utility-first CSS framework for rapid UI development with responsive design and dark mode support. \n \n Provides single-purpose utility classes for layout, spacing, typography, colors, and effects without writing custom CSS \n Includes mobile-first responsive breakpoints (sm, md, lg, xl, 2xl) and built-in dark mode with class or media strategy \n Supports framework integration with React, Next.js, Vue, Svelte, and others; includes official plugins for forms, typography, and aspect ratios \n Off

Search and extract HTTP traffic, audit findings, and security data from Burp Suite project files via CLI. \n \n Queries proxy history, site map, and audit items using regex patterns on request/response headers and bodies \n Requires Burp Suite Professional and the burpsuite-project-file-parser extension; delegates parsing to Burp's Java runtime \n Enforces sub-component filters (headers, bodies) instead of full dumps to prevent gigabyte-scale data retrieval; mandatory truncation of body content