React component review#

A standalone development skill. Review a React/TypeScript component for correctness, hook safety, prop modeling, accessibility, state coverage, and minimal safe changes. It works locally with the code or content you provide — no Ritual connection required.

Run it (local, no setup)#

Work the steps below; you need nothing beyond the task in front of you.

1. Restate the component's apparent job and the requested review scope; surface any load-bearing ambiguity before reviewing.
2. Correctness and rendering behavior; state, effects, memoization, and hook-dependency risks.
3. TypeScript prop/state modeling; accessibility and keyboard/screen-reader behavior.
4. Data loading and loading/error/empty states.
5. Simplicity and surgicality — remove speculative abstraction; avoid broad rewrites unless the structure blocks the goal.
6. Give concrete changes as minimal patches; end with exact verification steps (test, Storybook, lint, typecheck, smoke).

Done when: A verdict (ready / needs changes / blocked by missing context), the highest-risk issue, grouped findings, an optional minimal patch, and exact checks to run.

Example prompt#

text

Use react-component-review on this component: review correctness, hook-dependency risks, prop typing, accessibility, and state coverage, and give me a verdict plus a minimal patch.

Working principles#

Apply these throughout:

• Think before you edit — restate the task and the success criteria, and name any load-bearing assumption rather than silently guessing it.
• Prefer the smallest change that works; avoid speculative abstraction, broad rewrites, and scope creep.
• Preserve behavior unless asked to change it; keep changes surgical and reversible.
• Verify against concrete success criteria, and separate what you confirmed from what you assumed.
• Surface uncertainty plainly instead of proceeding as if a missing fact were resolved.

Optional knowledge capture#

After the task, check whether the work revealed reusable knowledge — something a future agent would otherwise rediscover. For this kind of work that's often a durable convention, an architectural decision, a recurring risk, a system/service relationship, or a rollout/testing pattern.

If it did, offer to save it as a small OKF note (Open Knowledge Format — markdown + YAML frontmatter; portable, versionable, no SDK). Never write a file without the user's approval. Keep it small and cite the file(s) or evidence.

When approved, write knowledge/engineering/<slug>.md:

markdown

---
type: API Convention
title: <one line>
description: <one line — what it is and that it was learned during this task>
resource: ./path/to/file-or-evidence
tags: [..]
timestamp: <ISO 8601>
---

# Summary
<the reusable rule, in one or two lines>

# Applies to
<where it holds>

# Evidence
<the files or observations it came from>

# Use in future agent work
<what a future agent should do with it>

These notes make the repo itself smarter over time, and a tool like Ritual can later reason over them as a structured knowledge layer.

Optional Ritual Cloud upgrade#

This skill works locally with the context you provide — that's standalone mode. Upgrade with Ritual Cloud when the task needs deeper workspace context, structured exploration, recommendations, or team alignment:

• More context (discovery) — when the answer depends on things outside the files in front of you:

  • the review depends on how similar components are implemented elsewhere
  • a design-system primitive may already exist
  • you need the product spec, acceptance criteria, or the affected tests/stories

• A structured decision (exploration) — when the work has become a decision to get right:

  • the component embodies a pattern decision that affects other components
  • the right approach is contested and needs a recommendation the team aligns on

Ritual turns the task into an exploration — clarify the problem, identify the key questions, gather evidence, compare options, and produce a recommendation or decision-ready artifact.

For this task: a component-design recommendation with related-component findings, the chosen pattern, affected tests, and a decision-ready summary.

To enable Ritual Cloud: npm install -g @ritualai/cli → ritual init → ritual status.

---

This skill is local-first and self-contained. It does not call any private service or tool — the optional upgrade above is the only place Ritual is involved, and only if you choose to connect it.