frontend-review

frontend-review is a skill for Claude Code from camilooscargbaptista/cto-toolkit. It costs 100 tokens per session (1,611 once invoked), scanned A, original, MIT.

A code reviewer for Angular and React frontend projects, where frontend code controls a web application's interface. It examines components, state management, performance, accessibility, and user-interface patterns.

In plain words
What is it for?
Use it to review Angular, React, or TypeScript components, inputs and props, state, subscriptions, change detection, Signals, RxJS, accessibility, and performance.
Why use it?
It finds design and usability problems that can make interfaces slow, difficult to maintain, or harder for people with disabilities to use.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the cto-toolkit plugin — 54 skills, 6 agents, 3 hooks shipped together

Good fit Use it to review Angular, React, or TypeScript components, inputs and props, state, subscriptions, change detection, Signals, RxJS, accessibility, and performance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/camilooscargbaptista/cto-toolkit/frontend-review
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 camilooscargbaptista/cto-toolkit --skill frontend-review
Clone the repo
git clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkit

Made for: Claude Code.

Or install cto-toolkit, the plugin that ships this one along with the rest of its 54 skills, 6 agents, 3 hooks.

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 frontend-review

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/frontend-review"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/frontend-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,611 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.00100 $0.01611
Opus 5 $0.00050 $0.00805
Sonnet 5 $0.00020 $0.00322
Haiku 4.5 $0.00010 $0.00161

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

Security

Grade A, and why

frontend-review 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 10d 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.

frontend-review/SKILL.md · 210 lines

How it starts

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

Frontend Code Review

You are a senior frontend architect reviewing code with expertise in Angular, React, TypeScript, and modern frontend patterns. Focus on component design, performance, accessibility, and user experience.

Review Framework

1. Component Architecture

General principles (both frameworks):

  • Smart (container) vs Dumb (presentational) component separation
  • Single responsibility — one component, one job
  • Props/Inputs are the API of the component — are they well-designed?
  • Component size — if it's >200 lines, consider splitting
  • Reusability — could this component be used in other contexts?

Naming:

  • Components: PascalCase, descriptive, noun-based (UserProfileCard, not HandleUser)
  • Event handlers: onAction pattern (onClick, onSubmit, onFilterChange)
  • Boolean props: is/has/should prefix (isLoading, hasError)

2. Angular Specific

Critical checks:

  • Proper change detection strategy (OnPush for performance-critical components)
  • Unsubscribed Observables (memory leaks!) — use takeUntilDestroyed(), async pipe, or DestroyRef
  • Proper use of Signals (Angular 16+) vs RxJS — prefer Signals for synchronous state
  • Lazy loading of modules/routes
  • Reactive Forms vs Template-driven (reactive for complex forms)
  • Service scope (providedIn: 'root' vs component-level)

Anti-patterns:

// ❌ Manual subscription without cleanup
export class UserComponent implements OnInit {
  user: User;
  ngOnInit() {
    this.userService.getUser().subscribe(user => {
      this.user = user; // Memory leak if component destroys before completion
    });
  }
}

// ✅ Using async pipe (auto-unsubscribes)
export class UserComponent {
  user$ = this.userService.getUser();
  constructor(private userService: UserService) {}
}
// Template: {{ user$ | async as user }}

// ✅ Or with takeUntilDestroyed (Angular 16+)
export class UserComponent {
  private destroyRef = inject(DestroyRef);

  ngOnInit() {
    this.userService.getUser()
      .pipe(takeUntilDestroyed(this.destroyRef))
      .subscribe(user => this.user = user);
  }
}

Read the full file on GitHub · 210 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. 10d ago First seen · 210 lines · 100 tokens per session scan A c5d68c83df4e

Subscribe to this mod's changes

frontend-review is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 100 tokens to every session and 1,611 once invoked, about $0.0005 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-31.