The UI Programmer implements user interface systems: menus, HUDs, inventory screens, dialogue boxes, and UI framework code. Use this agent for UI system implementation, widget development, data binding, or screen flow programming.
Tier 3 Specialist agent focused on bridging the gap between requirements (PRD) and implementation. Creates detailed UI Specifications including component decomposition, state matrices, and interaction definitions.
The UX Designer owns user experience flows, interaction design, accessibility, and information architecture for software products. Use this agent for user flow mapping, interaction pattern design, accessibility audits, onboarding flow design, and wireframe feedback.
The UX Researcher generates user insights through research methods: interviews, usability tests, surveys, and behavioral analysis. Use this agent to plan and analyze user research, synthesize findings into actionable insights, validate design assumptions, identify user pain points, and generate evidence-based design…
Runs when you submit a prompt, before the agent sees it, executing prompt-context.sh, persist-memory.sh and log-skill.sh via bash (3 commands). From tranhieutt/software_development_department.
Runs before the agent uses a tool for Bash, Task, Write, Edit and Read tool calls, executing bash-guard.ps1, validate-commit.ps1, validate-push.ps1, circuit-guard.sh, pre-code-gate.ps1 and file-history.sh (6 commands). From tranhieutt/software_development_department.
Runs after a tool call finishes for Write, Edit, Bash and Task tool calls, executing log-writes.sh, extract-decisions.sh, log-commit.sh, decision-ledger-writer.sh and circuit-updater.sh via bash (5 commands). From tranhieutt/software_development_department.
Reads production/traces/agent-metrics.jsonl and displays a per-agent performance summary table for the current or a specified session. Highlights agents with high error rates or OPEN circuit breaker state.
Provides the vendored agent-style v0.3.5 prose rule pack as a portable Claude skill. Use when installing, syncing, applying, or auditing SDD Agent-Style support in another project, or when a style-review workflow needs the bundled rules.
Provides Angular best practices for components, modules, services, and reactive patterns. Use when working with Angular TypeScript files, component templates, NgModules, RxJS observables, or when the user mentions Angular, ng, or Angular CLI.
Records unexpected API behaviors, undocumented caveats, version bugs, or non-obvious workarounds into .claude/memory/annotations.md. Use immediately when an undocumented behavior or surprising caveat is discovered during development.
Defines REST and GraphQL API contracts including endpoints, request/response schemas, auth flows, and versioning strategy. Use when designing a new API, reviewing an API spec, or when the user mentions API design, OpenAPI, or endpoint contracts.
Manages the ADR (Architecture Decision Record) registry. Use when recording tech-stack choices, design patterns, or infrastructure decisions with context, alternatives, and rationale. Supports listing, searching, or creating formal ADR documents.
Provides AWS serverless architecture patterns for Lambda, API Gateway, DynamoDB, SQS, and SAM/CDK. Use when working with AWS serverless files (serverless.yml, CDK stacks) or when the user mentions Lambda, API Gateway, serverless, or AWS SAM.
Designs scalable backend architectures covering microservices, event-driven systems, API gateways, and data stores. Use when designing a backend system or when the user mentions backend architecture, scalability, or distributed systems.
Applies production backend patterns: middleware, error handling, auth, database integration, and API design. Use when working with backend service files or when the user mentions Express, Fastify, NestJS, backend patterns, or service architecture.
Facilitates structured product ideation to define user needs, core value, and product direction. Use when the user wants to explore a new product idea, has a vague concept to develop, or mentions brainstorming or ideation.
Creates a structured bug report with reproduction steps, expected vs actual behavior, environment details, and severity assessment. Use when a bug or defect is found and needs to be formally documented.
Generates a structured changelog from git history following Keep a Changelog format and conventional commits. Use when creating a CHANGELOG.md, preparing release notes, or when the user mentions changelog or release history.