alma-oss
- 14 skills
- 0 followers
- 1 day ago last updated
- ▌ Spirit Create Pr · alma-oss bundleCreate or update a GitHub PR for the current branch. Drafts a short why-first description from branch changes and conversation context, asks for any missing info (issue URL, draft status), then creates or updates the PR via gh CLI.
- ▌ Spirit Upgrade Node · alma-oss bundleUpgrade Spirit Design System Node.js minimum version, .nvmrc, engines, CI matrix, migration docs, and @types/node catalog. Use when the user asks to upgrade Node.js, drop an old Node LTS, or bump the required Node version in the monorepo.
- ▌ Spirit Accessibility · alma-oss bundleAudit and improve web accessibility, semantics, ARIA, keyboard operability, focus management, contrast, following WCAG 2.2 guidelines. Always apply when adding or reviewing Spirit components and features. Also triggered by "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
- ▌ Spirit Figma To Code · alma-oss bundleImplement production React UI from a Figma design using @alma-oss/spirit-web-react. Use when the requested output is React code and a Figma node, URL, selection, screenshot, or specification is provided. Do not use for design review, Code Connect authoring, code-to-Figma workflows, or non-React Spirit packages.
- ▌ Spirit Release Notes · alma-oss bundleGenerate human-readable Slack Canvas release notes for Spirit Design System. Use when the user asks to write, create, or generate release notes after a publish.
- ▌ Spirit Atomic Commits · alma-oss bundleCreate clean, atomic git commits following Spirit's commit message conventions. Splits a mixed working tree into one logical commit per change via hunk-level staging, then commits each through git hooks. Use whenever the user asks to commit, "commit my changes", "make a commit", "commit this", or "commit my work".
- ▌ Spirit Create Jira Issue · alma-oss bundleDraft, preview, and file a DS-project Jira Story with the team's required structure (WHO/WHAT/WHY opening, measurable acceptance criteria, detailed implementation notes) and avoid this Jira instance's known wiki-markup corruption bugs.
- ▌ Spirit Review Figma Design · alma-oss bundleReview a Figma design from a Spirit Design System perspective before handoff to development. Use when a designer asks for a DS review, a design needs to be checked for DS compliance, or a handoff review is required. Requires the Figma MCP to be available.
- ▌ Spirit V5 Migration · alma-oss bundleMigrates consumer apps from Spirit Design System v4 to v5, focusing on @alma-oss/spirit-web-react breaking APIs, codemods, feature flags, styles, markup, and design-token renames. Use when the user asks to upgrade to Spirit v5, migrate to v5, fix v5 breaking changes, or update deprecated Spirit React APIs.
- ▌ Spirit Stabilize Component · alma-oss bundleStabilize an experimental Spirit component by promoting UNSTABLE_X to X across web-react (React) and web (vanilla SCSS/JS). Covers folder/identifier renames, exports, docsite categories and slugs, stories, tests, e2e snapshots, rename codemods, migration guides, and removal of any superseded component. Use when the user asks to stabilize or graduate a component (for example promoting UNSTABLE_X to its stable name).
- ▌ Spirit Component Deprecation · alma-oss bundleDeprecate or remove deprecations for Spirit components and props across web-react (React) and web (vanilla SCSS/JS). Covers useDeprecationMessage, DEPRECATIONS.md, README notices, and optional web JS warnings. Use when deprecating a component, preparing a major release, or mirroring deprecations in both packages.
- ▌ Spirit Conventional Comments · alma-oss bundleConventional Comments vocabulary (labels, decorations, ordering) for Spirit code review. Loaded only when a review is run with `--conventional-comments`; it overlays label markings onto the finding format from the code-review methodology. Use when the team explicitly wants CC-formatted review output. Off by default.
- ▌ Spirit Address Review Comments · alma-oss bundleSystematic approach to responding to PR review comments. Guides through analyzing feedback, implementing changes, adding responses, and resolving conversations. Use when you receive PR reviews and need to address feedback efficiently and professionally.
- ▌ Spirit Breaking Change Checklist · alma-oss bundleChecklist for what a breaking change to a stable Spirit API must ship with: migration guide entries in both packages, and a web-react-only codemod with fixtures. Use whenever introducing a breaking change (removing a feature flag, removing/renaming a prop, changing a default) that isn't already a component stabilization or deprecation removal.