Open-source engineering standards for CueLABS — a skill coding agents use to bootstrap new repos and standardize existing ones (structure, OSS hygiene, deploy conventions).
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.
2 1mo agoA63 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: