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.
npx skills add cenconq25/claude-code-app-studio --skill team-frontendgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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.
[](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/team-frontend)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/team-frontend"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/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.
<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/team-frontend"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/team-frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00047 | $0.01891 |
| Opus 5 | $0.00023 | $0.00945 |
| Sonnet 5 | $0.00009 | $0.00378 |
| Haiku 4.5 | $0.00005 | $0.00189 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Frontend
Front-end-of-the-mobile-app orchestrator. Once a design package and a
PRD exist, this skill coordinates the engineering roles that turn it
into screens, animations, and state plumbing. It does not build the
backend (see /team-backend).
Team Composition
- lead-developer — feature owner, integration glue, sign-off on the diff.
- framework specialist — chosen per project: react-native-specialist, flutter-specialist, ios-specialist, or android-specialist (and their UI sub-specialists).
- state-management specialist — Redux / Zustand / Riverpod / Provider / Combine / MVI / Compose state.
- animation-specialist — motion + haptic implementation.
Spawn each via Task. Parallelize where dependencies allow.
Phase 1: Resolve Feature Scope
Parse argument:
--feature=<name>-> glob related stories.--epic=<slug>-> readproduction/epics/[slug]/.- No argument -> ask the user which feature.
Read in parallel:
- The design package at
design/packages/[feature]-design.md(if produced via/team-design). - The PRD under
design/prd/. - Governing ADRs from
docs/architecture/. - Stories under the epic — read each story's status.
.claude/docs/technical-preferences.mdfor framework + state conventions.
Confirm scope: "[N] stories under [epic]. Build front-end layer now?"
Phase 2: Routing — Pick the Specialists
Read the framework. Resolve specialists:
| Framework | UI specialist | State specialist | Animation specialist |
|---|---|---|---|
| React Native | rn-screens-specialist | redux-or-zustand-specialist | rn-reanimated-specialist |
| Flutter | flutter-widgets-specialist | riverpod-or-bloc-specialist | flutter-animation-specialist |
| iOS | swiftui-specialist | combine-specialist | swiftui-animation-specialist |
| Android | jetpack-compose-specialist | mvi-specialist | compose-animation-specialist |
If specialists are not declared in technical-preferences, fall back to the umbrella framework specialist.
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.
- 6d ago First seen · 279 lines · 47 tokens per session scan A b320f650586c
team-frontend is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 1,891 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-09-03.
Other skills, from other repositories
animate-expo
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and…
leanback-to-compose-tv-migration
Provides instructions and architectural patterns for migrating Android TV applications from legacy Leanback UI Toolkit, Android Views, or Support Fragments to Jetpack Compose for TV (androidx.tv). Use this skill for Leanback to Compose migrations, including browse screen, settings screen, authentication screen, login…
maui-data-binding
Guidance for .NET MAUI XAML and C# data bindings — compiled bindings, INotifyPropertyChanged / ObservableObject, value converters, binding modes, multi-binding, relative bindings, fallbacks, and MVVM best practices. USE FOR: setting up compiled bindings with x:DataType, implementing INotifyPropertyChanged or…
migrate-xml-views-to-jetpack-compose
Provides a structured workflow for migrating an Android XML View to Jetpack Compose. This skill details the step-by-step process, from planning and dependency setup, to theming and layout migration, validation and XML cleanup. Use this skill when you need to migrate an XML View to Jetpack Compose in an Android…
web-haptics
Add haptic feedback to web apps using the web-haptics library. Use when building mobile-facing UIs that need tactile feedback on buttons, toggles, forms, pickers, and other interactive elements.
axiom-swiftui
Use when building, fixing, or improving ANY SwiftUI UI — views, navigation, layout, animations, performance, architecture, gestures, debugging, iOS 26 features.