team-frontend

team-frontend is a skill for Claude Code from tranhieutt/software_development_department. It costs 55 tokens per session (574 once invoked), scanned A, original, MIT.

A coordinated workflow for designing, building, and checking a user-interface feature with specialists in research, UX design, frontend code, and accessibility.

In plain words
What is it for?
Use it when a UI feature needs research, user flows, wireframes, responsive behavior, implementation, and accessibility validation.
Why use it?
It brings the related design and engineering work into one process, so important states and accessibility needs are less likely to be missed.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Good fit Use it when a UI feature needs research, user flows, wireframes, responsive behavior, implementation, and accessibility validation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tranhieutt/software_development_department/team-frontend
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.

Any agent
npx skills add tranhieutt/software_development_department --skill team-frontend
Clone the repo
git clone --depth 1 https://github.com/tranhieutt/software_development_department

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.

agentmods badge for team-frontend

README.md
[![agentmods](https://agentmods.dev/badge/skills/tranhieutt/software_development_department/team-frontend/github.svg)](https://agentmods.dev/skills/tranhieutt/software_development_department/team-frontend)
Your own site
<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/team-frontend"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/team-frontend/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.

agentmods 80×15 button for team-frontend

Your own site · 80×15
<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/team-frontend"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/team-frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 574 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.00574
Opus 5 $0.00028 $0.00287
Sonnet 5 $0.00011 $0.00115
Haiku 4.5 $0.00006 $0.00057

Measured 9d ago against content hash 2c954c8ed872, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

team-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 9d 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.

.claude/skills/team-frontend/SKILL.md · 63 lines

How it starts

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

When this skill is invoked, orchestrate the frontend team through a structured delivery pipeline.

Decision Points: At each phase, use AskUserQuestion to get user approval before proceeding.

Team Composition

  • ux-researcher — User insights and validation
  • ux-designer — User flows, wireframes, interaction design
  • frontend-developer — Component implementation and integration
  • accessibility-specialist — Accessibility audit and compliance

Pipeline

Phase 1: Research (if needed)

Delegate to ux-researcher (skip if sufficient prior research exists):

  • Define what user behavior/pain-point this feature addresses
  • Review any existing analytics or user feedback
  • Output: Research brief with key insights

Phase 2: UX Design

Delegate to ux-designer:

  • Define user flow (entry → states → exit)
  • Create wireframes for all states (default, loading, error, empty, success)
  • Specify interaction patterns and responsive breakpoints
  • Define accessibility requirements
  • Output: UX spec and wireframes for approval

Phase 3: Implementation

Delegate to frontend-developer:

  • Build components following the approved UX spec
  • Use design tokens — no hardcoded colors, sizes, or fonts
  • Handle all states: loading, error, empty, success
  • All user-facing strings through i18n layer
  • Write component unit tests
  • Output: Implemented UI feature

Phase 4: Accessibility Audit

Delegate to accessibility-specialist:

  • Test keyboard navigation (tab order, focus management)
  • Verify ARIA roles and labels
  • Check color contrast (WCAG AA minimum)
  • Test with screen reader if critical flow
  • Output: Accessibility report

Phase 5: Polish & Review

  • Address accessibility findings
  • Verify responsive behavior at all target breakpoints
  • Cross-browser test on target browsers
  • ux-designer validates final implementation against spec

Output

Summary covering: research insights used, UX spec status, implementation status, accessibility compliance, and any outstanding issues.

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

  1. 9d ago First seen · 63 lines · 55 tokens per session scan A 2c954c8ed872

Subscribe to this mod's changes

team-frontend is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 574 once invoked, about $0.0003 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-09-03.

Related

Other skills, from other repositories

frontend-design

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

HKUDS/DeepCode · 40 tokens

shiny-bslib-theming

Advanced theming for Shiny apps using bslib and Bootstrap 5. Use when customizing app appearance with bstheme(), Bootswatch themes, custom colors, typography, brand.yml integration, Bootstrap Sass variables, custom Sass/CSS rules, dark mode and color modes, dynamic theme switching, real-time theming, theme inspection…

posit-dev/skills · 87 tokens

interaction-skill

Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…

code-yeongyu/oh-my-openagent · 104 tokens

shiny-bslib

Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…

posit-dev/skills · 107 tokens

web-ui-best-practices

Signs of taste in web UI. Use when building or reviewing web interfaces, dashboards, SaaS apps, or internal tools.

jamditis/claude-skills-journalism · 32 tokens

vertical-site-conventions

Compose pages and sites that read as their vertical: ecommerce-catalog storefronts that look like storefronts, hospitality-food sites that look like restaurants, b2b-manufacturer sites that look industrial. Use this skill whenever the user wants to build a site that looks like the vertical it serves, fix a build that…

rampstackco/claude-skills · 190 tokens