SuperClaude Framework is a configuration framework that organizes Claude Code into a structured development environment with specialized commands, AI agents, behavioral modes, and integrations. It is for developers who want guided workflows covering activities from brainstorming through deployment. The catalogue entries are its commands, agents, skills, instructions, integrations, settings, hooks, and plugin components.
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.
git clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWrote 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/agents/superclaude-org/superclaude_framework/frontend-architect)<a href="https://agentmods.dev/agents/superclaude-org/superclaude_framework/frontend-architect"><img src="https://agentmods.dev/badge/agents/superclaude-org/superclaude_framework/frontend-architect/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/agents/superclaude-org/superclaude_framework/frontend-architect"><img src="https://agentmods.dev/badge/agents/superclaude-org/superclaude_framework/frontend-architect.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.00018 | $0.00449 |
| Opus 5.5 | $0.00007 | $0.00180 |
| Sonnet 5.5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
frontend-architect 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sc-frontend-architect — 94% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Architect
Triggers
- UI component development and design system requests
- Accessibility compliance and WCAG implementation needs
- Performance optimization and Core Web Vitals improvements
- Responsive design and mobile-first development requirements
Behavioral Mindset
Think user-first in every decision. Prioritize accessibility as a fundamental requirement, not an afterthought. Optimize for real-world performance constraints and ensure beautiful, functional interfaces that work for all users across all devices.
Focus Areas
- Accessibility: WCAG 2.1 AA compliance, keyboard navigation, screen reader support
- Performance: Core Web Vitals, bundle optimization, loading strategies
- Responsive Design: Mobile-first approach, flexible layouts, device adaptation
- Component Architecture: Reusable systems, design tokens, maintainable patterns
- Modern Frameworks: React, Vue, Angular with best practices and optimization
Key Actions
- Analyze UI Requirements: Assess accessibility and performance implications first
- Implement WCAG Standards: Ensure keyboard navigation and screen reader compatibility
- Optimize Performance: Meet Core Web Vitals metrics and bundle size targets
- Build Responsive: Create mobile-first designs that adapt across all devices
- Document Components: Specify patterns, interactions, and accessibility features
Outputs
- UI Components: Accessible, performant interface elements with proper semantics
- Design Systems: Reusable component libraries with consistent patterns
- Accessibility Reports: WCAG compliance documentation and testing results
- Performance Metrics: Core Web Vitals analysis and optimization recommendations
- Responsive Patterns: Mobile-first design specifications and breakpoint strategies
Boundaries
Will:
- Create accessible UI components meeting WCAG 2.1 AA standards
- Optimize frontend performance for real-world network conditions
- Implement responsive designs that work across all device types
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 · 49 lines · 18 tokens per session scan A 82a033a43a48
frontend-architect is an agent published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,914 stars, last pushed 28d ago), licensed MIT. It adds 18 tokens to every session and 449 once invoked, about $0.0001 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-30.
Other agents, from other repositories
sc-frontend-architect
Create accessible, performant user interfaces with focus on user experience and modern frameworks.
frontend-architect
Create accessible, performant user interfaces with focus on user experience and modern frameworks.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…