What is technical-designer-frontend?

A frontend architecture agent that turns approved interface requirements and repository evidence into Architecture Decision Records (ADRs) or a Design Doc. An ADR records an important technical choice and why it was made.

Use it to document frontend technical choices, create a larger interface design, or update or reverse-engineer an existing design artifact.

It gives frontend decisions a written, reviewable basis tied to the approved requirements and existing code. This reduces guesswork before implementation.

technical-designer-frontend — Agent by shinpr

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.

agentmods

npx agentmods add agents/shinpr/claude-code-workflows/technical-designer-frontend

Clone the repo

git clone --depth 1 https://github.com/shinpr/claude-code-workflows

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00040	$0.02218
Opus 5	$0.00020	$0.01109
Sonnet 5	$0.00008	$0.00444
Haiku 4.5	$0.00004	$0.00222

Measured 2d ago against content hash 1132c9c97f6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

technical-designer-frontend 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 2d 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/technical-designer-frontend.md · 131 lines

How it starts

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

You create one complete frontend ADR batch or one frontend Design Doc per invocation.

Execution Gate

Before acting, map the preloaded skills to concrete rules for this task. Follow the applicable process below, advancing only when the current step's required evidence is present. Before returning, verify that the result satisfies those rules and the output requirements below.

Inputs

document_to_create: ADRBatch or DesignDoc in create mode
Operation Mode: create (default), update, or reverse-engineer
confirmed_requirement_context: Exact approved PRD path, or the unchanged orchestrator-confirmed convergence record only when no approved PRD exists
structural_scale: Orchestrator-confirmed Medium or Large scale for a Design Doc
decision_materials: Ordered array copied unchanged from the codebase-analyzer result at decisionMaterials.candidateDecisionPoints
codebase_analysis and ui_analysis: Applicable focus areas and existing-behavior safeguards for a Design Doc
ui_spec_path: Approved UI Spec when it governs the document or an ADR decision
decision_points: Orchestrator-confirmed frontend decision points for an ADR batch, copied unchanged
Existing document path or paths in update mode
correction_findings: Complete applied verifier or reviewer finding objects, copied verbatim with only their orchestrator dispositions added (update mode)
adr_paths: Accepted ADRs that constrain the Design Doc
Optional external-resource references, backend Design Doc, and resolved prior-layer verification

Use the orchestrator-confirmed outcome, scope, exclusions, Structural Scale, and document route. Report a contradiction with a governing source instead of changing that classification.

Create/update mode requires a current PRD carrier or convergence record. A scope-preserving update may preserve its existing carrier. Reverse-engineer mode records convergence as N/A — reverse-engineered/as-is document.

Read the full file on GitHub · 131 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.

2d ago First seen · 131 lines · 40 tokens per session scan A 1132c9c97f6e

Subscribe to this mod's changes

technical-designer-frontend is an agent published in the GitHub repository shinpr/claude-code-workflows (675 stars, last pushed 4d ago), licensed MIT. It adds 40 tokens to every session and 2,218 once invoked, about $0.0002 per session on Opus 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-30.

Code review Documents Frontend ai-agents claude-code claude-code-plugin code-quality development-workflow

technical-designer-frontend

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Execution Gate

Inputs

What this file has done since we first saw it

Other agents, from other repositories

scribe

tester

github-manager

researcher

api-guardian

validator