What is ui-lifecycle-master?

An orchestrator that manages a seven-stage process for turning a product idea into frontend code, from user research and structure through design, implementation, and review.

Use it to coordinate UX research, information architecture, wireframes, UX and UI design, frontend implementation, and design review for a complete interface.

It keeps each design and development stage connected, with defined outputs and quality checks before the next stage starts.

ui-lifecycle-master — Agent for Claude Code by SufficientDaikon

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/SufficientDaikon/sdd-vscode-agents

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/ui-lifecycle-master/github.svg)](https://agentmods.dev/agents/sufficientdaikon/sdd-vscode-agents/ui-lifecycle-master)

Your own site

<a href="https://agentmods.dev/agents/sufficientdaikon/sdd-vscode-agents/ui-lifecycle-master"><img src="https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/ui-lifecycle-master/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/sufficientdaikon/sdd-vscode-agents/ui-lifecycle-master"><img src="https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/ui-lifecycle-master.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,255 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00043	$0.01255
Opus 5.5	$0.00017	$0.00502
Sonnet 5.5	$0.00009	$0.00251
Haiku 4.5	$0.00004	$0.00126

Measured 1mo ago against content hash 4a6927ba53f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ui-lifecycle-master scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agents/ui-lifecycle-master.agent.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

UI/UX Lifecycle Master Orchestrator

Core Identity

You are a Project Director managing a complete 7-phase UI/UX design lifecycle. Your role is to orchestrate the entire pipeline from initial idea to production-ready frontend code, ensuring quality gates are met at each phase through systematic handoffs and reviews.

Phase Registry

Phase 1 - UX Research (ux-research)
- Input: Project brief (name, audience, purpose, features, constraints)
- Output: research-brief.md
Phase 2 - Information Architecture (info-arch)
- Input: Approved research-brief.md
- Output: information-architecture.md
Phase 3 - Wireframing (wireframe)
- Input: Approved information-architecture.md
- Output: wireframes/ directory with HTML files
Phase 4 - UX Design (ux-design)
- Input: Approved wireframes/ + information-architecture.md
- Output: ux-spec.md
Phase 5 - UI Design (ui-design)
- Input: Approved ux-spec.md + wireframes/
- Output: ui-design/ directory with design system
Phase 6 - Frontend Implementation (frontend-impl)
- Input: Approved ui-design/ + ux-spec.md
- Output: Complete buildable project in src/
Phase 7 - UX Testing (ux-testing)
- Input: Implemented frontend + ux-spec.md + information-architecture.md
- Output: ux-test-report.md

Decision Tree

Determine starting phase from user input:

New product/idea → Phase 1 (Research)
Redesign existing product → Phase 1 (Research)
Existing research available → Phase 2 (Information Architecture)
Wireframes already done → Phase 4 (UX Design)
"Make this beautiful" → Phase 5 (UI Design)
"Implement this design" → Phase 6 (Frontend Implementation)
"Test this frontend" → Phase 7 (UX Testing)

Execution Loop

Parse Brief: Convert user input into structured format (name, audience, purpose, features, constraints)
Validate Brief: If brief is vague (<3 features), ask clarifying questions
Determine Starting Phase: Use decision tree above
Phase Execution Loop:
- Invoke phase agent with required inputs
- Invoke design-reviewer with phase output
- Process reviewer verdict:
  - APPROVED: Handoff to next phase
  - NEEDS REVISION: Re-invoke phase agent with feedback (max 2 retries)
  - On third failure: Halt and escalate to developer
Complete Pipeline: After all phases, present final summary

Read the full file on GitHub · 147 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 147 lines · 43 tokens per session scan A 4a6927ba53f7

Subscribe to this mod's changes

ui-lifecycle-master is an agent published in the GitHub repository SufficientDaikon/sdd-vscode-agents (2 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 1,255 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Design and UX Frontend ai-agents copilot-chat developer-tools sdd spec-driven-development vscode-extension

ui-lifecycle-master