菜单
Use when adding a PR playground test page for a bug fix or feature in apps/prs. Covers the React and Angular wiring, which differ. Every PR needs BOTH a React and an Angular page so reviewers can verify the change in each framework.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when building or scoping a screen, page, or feature with the Government of Alberta Design System starting from a user-facing intent ("worker tool for case management", "public form for licence renewal", "error page for payment failure") rather than from a specific component or token.
Create a new design system component
Use to answer questions about the Government of Alberta Design system evolution, including approved terminology, the migration timeline and support windows, version changes for Web components, Angular, and React, and what the change means for product teams. Source of truth for evolution terms, FAQs, and glossary definitions.
Use when opening a pull request for a fix or feature in GovAlta/ui-components. Covers rebasing onto latest dev (to avoid stale-branch CI failures), filling the PR template, the draft-and-do-not-mark-ready convention, and commit and PR message style.
Use when writing or revising longer-form content for the Design system website, including component and pattern documentation, usage guidance, how-to steps, release notes, and FAQ-style explanations. Enforces plain-language voice, mechanics, inclusive language, and approved terminology. Do not use for in-component microcopy or code.
Use when filing a new GitHub issue for the Design system (bug, feature, or task). Covers the title and body template, the required priority and component labels, and setting the issue Type via GraphQL rather than a label. Do not use for writing PR descriptions.
| name | create-playground-page |
| description | Use when adding a PR playground test page for a bug fix or feature in apps/prs. Covers the React and Angular wiring, which differ. Every PR needs BOTH a React and an Angular page so reviewers can verify the change in each framework. |
Every fix or feature PR ships a playground page so reviewers can verify it visually. You need both a React and an Angular page. They wire up differently, and missing the Angular one is the most common gap.
Use the issue number throughout. Bugs go under bugs/, features under features/. Naming is bug{N} / feat{N}, no hyphen, where {N} is the issue number.
See apps/prs/react/src/routes/README.md for the canonical steps.
If not provided, ask the user whether this is a bug or a feature, and what the issue number is.
Files live flat in apps/prs/react/src/routes/bugs/ (or features/).
cp apps/prs/react/src/routes/_TEMPLATE.tsx to either apps/prs/react/src/routes/bugs/bug{N}.tsx or apps/prs/react/src/routes/features/feat{N}.tsx.TemplateRoute to Bug{N}Route or Feat{N}Route.See apps/prs/react/src/routes/README.md for the canonical steps.
Angular does NOT hand-wire routes in a main file. Each page is a folder with its own .route.json, and a build step regenerates the manifest.
apps/prs/angular/src/routes/bugs/bug{N}/ or apps/prs/angular/src/routes/features/feat{N}/ with:
bug{N}.component.tsbug{N}.component.htmlbug{N}.route.json with { "title": "...", "path": "bugs/bug{N}", "id": "{N}", "type": "bug" }apps/prs/angular/src/routes/bugs/2547/) as the pattern.Run each playground and confirm the page loads and the side-menu link navigates:
npm run serve:prs:react
npm run serve:prs:angular