LSST SQuaRE
Official@lsst-sqre · LSST HQ, Tucson AZ
Rubin Observatory Science Quality and Reliability Engineering team
Agent Skills by LSST SQuaRE
Showing 14 vetted skills indexed across 1 GitHub repositories.
lsst-sqrefile-factory
Scaffold React components, hooks, contexts, and Next.js pages with CSS Modules and tests.
lsst-sqregithub-issues
Synchronize GitHub issues with local .issues directory plans using gh CLI workflows.
lsst-sqretesting-infrastructure
Configure Vitest, React Testing Library, and MSW mocks for monorepo CI testing.
lsst-sqredocker-version-validation
Validate Dockerfile Node.js, pnpm, and turbo versions against package.json constraints.
lsst-sqretimes-square-integration
Integrate Times Square notebook execution with SSE updates and mock API endpoints.
lsst-sqresquared-package
Integrate the squared package into TypeScript React/Next.js apps without a build step.
lsst-sqrewcag-contrast-checker
Compute WCAG contrast ratios and AA/AAA compliance for CSS colors.
lsst-sqreturborepo-workflow
Resolve Turborepo build orchestration and remote caching in monorepos.
lsst-sqreplatform-api-integration
Integrate Rubin Science Platform APIs from OpenAPI specifications with TypeScript and SWR hooks.
lsst-sqredata-fetching-patterns
Standardize SWR-based API data fetching with typed fetchers and custom hooks.
lsst-sqreappconfig-system
Load and validate runtime configuration for SquareOne apps with AppConfig.
lsst-sqredesign-system
Reference Rubin Observatory design system CSS variables and design tokens.
lsst-sqremigrate-styled-components-to-css-modules
Migrate React components from styled-components to CSS Modules with design tokens.
lsst-sqrecomponent-creation
Create React components with TypeScript, CSS Modules, Storybook, and vitest tests.
Frequently Asked Questions About LSST SQuaRE
FAQPage SchemaWhat specific tasks does LSST SQuaRE enable for frontend engineers?▼
Engineers can standardize React component creation, implement WCAG color contrast compliance, and manage runtime configuration for complex web applications. These patterns ensure consistency across Rubin Observatory interfaces by utilizing shared design tokens and structured scaffolding for components, hooks, and pages.
Which technical personas benefit from these engineering patterns?▼
Frontend developers, UI engineers, and platform architects working within the Rubin Observatory ecosystem benefit most. These patterns are designed for teams managing monorepos who require strict adherence to design systems, accessibility standards, and reliable data fetching from scientific platform endpoints.
What are the primary dependencies for implementing these patterns?▼
Implementation requires a TypeScript-based React environment, typically utilizing Next.js, Turborepo for monorepo management, and SWR for data fetching. Projects must also integrate the Rubin Observatory design system tokens and follow the established CSS Modules migration path for styling components.