Yoizen UI design system standards. Trigger: Yoizen UI components, styling, colors, typography, visual polish or correction of any Yoizen Angular frontend.

2026-07-082

tdd

YoizenSA/dev-ai-workflow

Test-driven development loop — drive features through tests one vertical slice at a time (red → green → refactor). Use when the user asks for test-first development, mentions TDD or red-green-refactor, wants to build a feature through tests, or the orchestrator runs the TDD flow.

2026-07-012

ado

YoizenSA/dev-ai-workflow

Trigger: Azure DevOps PRs, work items, profiles; review/vote/comment a PR; list/create/update work items. Drive Azure DevOps via the `ado` CLI instead of plugin tools.

2026-06-302

docker

YoizenSA/dev-ai-workflow

Author and harden Dockerfiles for NestJS/Node, .NET, and Angular/nginx services on AKS. Use when creating a Dockerfile, reviewing/auditing/hardening one, shrinking image size or attack surface, or fixing container findings — root user, leaked secret, writable code, vuln scan. Reaches the .dockerignore, compose, and the entrypoints/configs baked into the image.

2026-06-222

teach

YoizenSA/dev-ai-workflow

Teach the user a new skill or concept, within this workspace.

2026-06-202

codebase-design

YoizenSA/dev-ai-workflow

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

2026-06-192

name	frontend-worker
description	Frontend implementation worker

frontend-worker

Required Skills and Tools

Work Procedure

Read the feature description and expected behavior
Write failing tests first (TDD)
Implement the feature to make tests pass
Run tests and verify they pass
Manually verify the implementation in browser
Return a structured handoff

Example Handoff

{ "salientSummary": "Implemented user profile page with edit form", "whatWasImplemented": "Created UserProfile component with form validation and API integration", "whatWasLeftUndone": "", "verification": { "commandsRun": [ {"command": "npm test -- UserProfile.test.tsx", "exitCode": 0, "observation": "All tests passed"} ] }, "tests": { "added": [{"file": "src/components/UserProfile.test.tsx", "cases": [{"name": "testRendersProfile", "verifies": "Component renders user data"}]}], "coverage": "80%" }, "discoveredIssues": [] }

When to Return to Orchestrator

Return to orchestrator if: requirements are ambiguous, existing bugs affect this feature, or you cannot complete within mission boundaries