Skip to main content
Exécutez n'importe quel Skill dans Manus
en un clic
Dépôt GitHub

ui-components

ui-components contient 9 skills collectées depuis GovAlta, avec une couverture métier par dépôt et des pages de détail sur le site.

skills collectés
9
Stars
26
mis à jour
2026-07-20
Forks
36
Couverture métier
5 catégories métier · 100% classifié
explorateur de dépôts

Skills dans ce dépôt

using-goa-design-system
Concepteurs web et d'interfaces numériques

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.

2026-07-20
create-component
Développeurs web

Create a new design system component

2026-07-15
create-playground-page
Analystes en assurance qualité des logiciels et testeurs

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.

2026-07-15
ds-evolution-reference
Concepteurs web et d'interfaces numériques

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.

2026-07-15
open-pr
Développeurs de logiciels

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.

2026-07-15
write-design-system-content
Rédacteurs techniques

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.

2026-07-15
write-issue
Développeurs de logiciels

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.

2026-07-15
writing-specs
Analystes en assurance qualité des logiciels et testeurs

Writing tests and specs for components

2026-07-15
content-design
Rédacteurs techniques

Designs user-facing service content (service names, descriptions, guidance, microcopy, button labels, status messages, errors, empty states) for its specific reader: a citizen (public, plain language, grade-9) or a worker (internal, dense, domain-expert). Use when writing or editing any citizen-facing or worker-facing copy for a Government of Alberta service, or when checking whether existing copy fits the reader it is actually for.

2026-06-11