asu-unity-stack

Use this skill after problem framing to produce a locked architecture document. Creates data flow diagrams, state machines, error paths, test matrices, and bite-sized task breakdowns.

Design + accessibility skill for ASU UI work (WCAG 2.1 AA). Use when designing, building, or reviewing any ASU component or page in Unity or Webspark. Covers semantics/landmarks, keyboard + focus, contrast, reflow at 320px, forced-colors mode, labels/forms, and a pre-delivery checklist. Prefer Unity/Bootstrap components over hand-rolled div+ARIA.

Evaluate code structure, maintainability, and engineering standards alongside adversarial review.

Phase 3 of code review: run tests, verify behavior, check edge cases, confirm no regressions.

Use during REVIEW to compare a rendered UI component against its design references (screenshots in .intake/ and/or the Figma frame). Drives a running Storybook (Unity) or local Webspark page with agent-browser to screenshot the build at multiple viewports, then reports P1/P2/P3 visual-fidelity findings to .pipeline/visual-report.md. Used by the acp-visual agent.

Use at the END of the Unity stage to enforce the PR-ready gate and write the cross-stage handoff. Defines the gate (build+lint, Storybook story + interaction/a11y tests, HTML-parity) and writes handoff.json (+ markup.html) to the shared peer handoff/ directory, keyed by Jira key or component slug, for the Webspark stage to consume. Validate with .kiro/scripts/validate-handoff.sh.

Use at pipeline INTAKE to turn a component request into an enriched intake brief. A component name is ALWAYS required; a Jira key, a Figma URL, and/or one-or-more screenshots in .intake/ are optional enrichment. Reads Jira via mcp-atlassian (read-only), design specs/tokens via the Figma Dev Mode MCP, and screenshots via vision. Ask clarifying questions when inputs are sparse or conflicting. Produces .pipeline/intake-brief.md for the architect.

Component/framework skill for the ASU Unity design system (Bootstrap 5 + React monorepo). Use when designing, building, or reviewing any Unity component. Covers the Storybook MCP discovery workflow, the unity-bootstrap-theme token system (_custom-asu-variables.scss), the HTML-parity requirement, TypeScript-first rules for unity-react-core, GA event preservation, and the build/lint/story-test validators.

Use this skill when asked to implement a feature, build something, or execute a coding task. Orchestrates the full adversarial coding pipeline across architect, coder, and reviewer subagents.

Phase 2 of code review: think like an attacker and chaos engineer. Find edge cases, race conditions, security holes, and resource leaks.

Brand skill for Arizona State University UI. Use when designing, building, or reviewing any ASU component or page. Defines the approved color palette, typography, spacing scale, and tone, expressed as Unity theme tokens (_custom-asu-variables.scss). Enforces token usage over raw values. Candidate for upstreaming to the foundry as a reusable institutional brand skill.

Use this skill when starting a new coding task or feature request. Frames the problem using six forcing questions before any design or implementation begins.

Use this skill when addressing review findings from the reviewer-agent. Maps every finding to a specific code change and verification evidence.

Phase 1 of code review: verify the implementation matches the architect's design document exactly.

Use this skill when implementing code. Enforces strict test-driven development with the RED-GREEN-REFACTOR cycle. No production code without a failing test first.