Create, audit, or standardize CueLABS product design systems and their implementation contracts. Use for Figma variables, tokens, component libraries, screen states, prototype flows, accessibility and motion specifications, design documentation, visual QA, or cross-product design parity.
Audit, bootstrap, standardize, or verify a CueLABS repository. Use for repository structure, service naming, community-health files, project manifests, shared templates, cross-repository parity, or adoption of the CueLABS engineering standard. Route web, Flutter, design, CI, packaging, and deployment work to the…
Build, audit, or standardize CueLABS mobile applications. Use for Flutter architecture, Riverpod, routing, repositories, TESTMODE fakes, flavors, Firebase authentication, design tokens, golden tests, mobile CI, device behavior, or web-to-mobile product parity.
Build, audit, or standardize CueLABS web applications and marketing sites. Use for Next.js and React architecture, design tokens, component libraries, TESTMODE, mock APIs, routes, accessibility, performance, SEO, marketing navigation and footer parity, or Figma-to-web implementation.
Design or redesign a product's backend system the CueLABS way and publish it as a document plus an interactive diagram page. Use when asked for a system design, architecture, service breakdown, or architecture diagram from a PRD, an existing repository, or a plain description; to decide how many services a product…
★not rated 2 14d agoA136 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: