Merge pull request #1600 from ASU/add-copilot-instructions

chore: update copilot instructions

Author: mlsamuelson

.github/copilot-instructions.md

@@ -0,0 +1,96 @@
+# ASU Unity Design System - AI Coding Guide
+
+## Architecture Overview
+
+This is a **Lerna + Yarn Workspaces monorepo** containing ASU's design system packages. Key architectural patterns:
+
+- **Package dependency hierarchy**: `unity-react-core` is the foundational React component library that other packages depend on
+- **Theme system**: `unity-bootstrap-theme` provides Bootstrap 5-based CSS/SCSS foundation, built with Vite
+- **Shared utilities**: `shared` package contains common hooks, services, and utilities used across components
+- **Multi-output builds**: React packages generate UMD, ES, and CJS modules for different consumption patterns
+
+## Critical Build Dependencies
+
+**Build order matters**: `unity-react-core` must build first, then other packages. The build system enforces this via:
+```bash
+yarn build     # Builds packages in parallel. This also runs linting before building.
+```
+
+**Package registry**: All `@asu` scoped packages are published to GitHub Package Registry, not npm. Authentication via `.env.yarn` file with `GITHUB_AUTH_TOKEN`.
+
+## Development Workflows
+
+### Local Development
+```bash
+# Always start from project root
+yarn install
+yarn build
+cd packages/[package-name]
+yarn storybook  # Primary development environment
+```
+
+### Component Development Patterns
+- **Component structure**: Each React component follows pattern: `ComponentName.jsx`, `ComponentName.stories.jsx`, `ComponentName.test.jsx`, `init.js`
+- **Google Analytics integration**: Components use `GaEventWrapper` or custom `trackGAEvent` functions pushing to `window.dataLayer`
+- **Styling**: Components use Bootstrap classes from `unity-bootstrap-theme`, custom styles via CSS modules or SCSS. The exception is `component-header-footer` which is meant to be a standalone package not dependent on the theme. It uses React and styled components for styling.
+
+### Package Management
+- **Adding dependencies**: Always `cd` into specific package directory first, then `yarn add [package]`
+- **Version management**: Uses semantic-release with conventional commits for automated versioning
+- **Multi-target builds**: React packages output to `dist/` with multiple formats (`.umd.js`, `.es.js`, `.cjs.js`)
+
+## Project-Specific Conventions
+
+### Component Props & Types
+- All components use TypeScript JSDoc comments for prop documentation
+- Shared prop types in `shared/types`
+- Google Analytics data structure standardized across components
+
+### Build System Quirks
+- **Vite configs**: `unity-bootstrap-theme` uses separate configs for CSS (`vite.config.js`) and JS bundling (`vite.config.bundle.js`)
+- **Bootstrap integration**: Theme package copies Bootstrap JS files to `dist/js/` during build
+- **Storybook builds**: Generate to project root `/build/$npm_package_name` for unified documentation site
+
+### Testing & Quality
+- **Accessibility testing**: Playwright-based a11y tests in `unity-react-core`
+- **Linting**: ESLint + Stylelint with project-specific configs in `@asu/shared`
+
+## Integration Points
+
+### Cross-Package Dependencies
+- Components import shared utilities: `import { ... } from '@asu/shared'`
+- Theme consumption: React packages reference Bootstrap variables and mixins
+- Storybook integration: All packages use consistent Storybook configuration
+
+### External Systems
+- **Jenkins CI/CD**: Automated build, test, publish, and deploy pipeline (see below)
+- **Unity Web Platform**: Deployed to `https://unity.web.asu.edu` for QA
+- **CMS Integration**: UMD builds designed for Webspark 2 CMS consumption
+
+## CI/CD Pipeline (Jenkins)
+
+### Branch-Specific Workflows
+- **PR to `dev`**: Builds storybook → deploys to S3 staging → adds PR comment with preview URL
+- **Merge to `dev`**: Full pipeline: build → test → security check → publish packages → deploy to GitHub Pages → accessibility tests
+- **`testing` branch**: Developer releases with package publishing
+
+### Pipeline Stages
+1. **Build**: `yarn install` → `yarn build` (using GitHub auth token)
+2. **Security Check**: npm audit for critical/high vulnerabilities → Slack alerts on issues
+3. **Test**: Jest tests via Playwright container
+4. **Publish**: Packages published to GitHub Package Registry with semantic-release
+5. **Deploy**: Storybook built and deployed to GitHub Pages (`unity.web.asu.edu`)
+6. **Accessibility**: Playwright a11y tests → Slack alerts on failures
+
+### Infrastructure
+- **Kubernetes agents**: Node 20.15, Playwright, AWS CLI containers
+- **S3 staging**: PR previews at `unity-uds-staging.s3.us-west-2.amazonaws.com/pr-{number}/`
+- **Auto-cleanup**: Merged PR environments cleaned from S3 after 14 days or immediately after merging to dev branch (dev is main branch for this repo)
+- **Slack integration**: `#prd-uds` and `#prdfam-uds-ci` channels for alerts
+
+## Key Files for Understanding Context
+- `/packages/unity-react-core/src/components/` - Core React component patterns
+- `/packages/unity-bootstrap-theme/src/` - Theme structure (CSS/SCSS + JS)
+- `/packages/shared/` - Shared utilities and types
+- `/nx.json` - Build dependency configuration
+- `/lerna.json` - Monorepo package management settings