
React Design Philosophy
- 320 repo stars
- Updated June 4, 2026
- toss/react-simplikit
Helps with frontend development tasks.
About
react-design-philosophy is a Claude Code skill for frontend development. It helps developers move faster with AI-assisted coding.
- react-design-philosophy
- Frontend Development
- AI-coding skill
React Design Philosophy by the numbers
- Data as of Aug 3, 2026 (Skillselion catalog sync)
/plugin marketplace add toss/react-simplikit/plugin install react-design-philosophy@react-design-philosophyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 320 |
|---|---|
| Last updated | June 4, 2026 |
| Repository | toss/react-simplikit ↗ |
What it does
Helps with frontend development tasks.
README.md
react-design-philosophy
React design philosophy plugin for Claude Code. Includes skills for reviewing and writing hooks, plus a higher-level React abstraction guide.
Install
Claude Code
# 1. Add this plugin's marketplace (sparse-checkout keeps the clone minimal)
claude plugin marketplace add https://github.com/toss/react-simplikit \
--sparse .claude-plugin packages/plugin
# 2. Install the plugin
claude plugin install react-design-philosophy@react-design-philosophy
Codex
codex plugin marketplace add https://github.com/toss/react-simplikit
Then install React Design Philosophy from the Codex plugin UI.
To uninstall:
Claude Code
claude plugin uninstall react-design-philosophy@react-design-philosophy
claude plugin marketplace remove react-design-philosophy
Codex
codex plugin marketplace remove react-simplikit
Skills
/react-design-principles
Design React APIs and abstractions in a React-like way.
- Declarative interfaces over orchestration-heavy helpers
- Lifecycle-safe abstractions instead of generic lifecycle wrappers
- Minimal surfaces, zero-dependency bias, type safety, and documentation
- Best used for library design, API review, and deciding whether an abstraction should exist
/react-hook-review
Review hooks against 30 design principles. Structured feedback with severity levels.
- 14 coding principles (C1-C14): return values, SSR safety, TypeScript, cleanup, performance
- 16 usage patterns (U1-U17, excluding U4): state design, effect usage, memoization, hook design
- Output: Great Work / Required Changes / Suggestions / Next Steps
/react-hook-writing
Write hooks following design philosophy. Themed guide with code examples.
- State management patterns (derive, useRef vs useState, useReducer)
- Effect patterns (when to use, cleanup, external store subscription)
- TypeScript, performance, JSDoc templates
- Reference implementations in
patterns.md
Principles Overview
| Category | Count | Examples |
|---|---|---|
| React design | 5 | Declarative interface, lifecycle respect, minimal surfaces, reliability, zero-dependency bias |
| Coding (C1-C14) | 14 | Always return objects, SSR-safe init, no any, cleanup |
| State Design (U1-U3, U5-U7) | 6 | Derive don't sync, useRef for non-rendered, discriminated unions |
| Effect Usage (U8-U14) | 7 | Effects for sync only, no chains, key reset, async cleanup |
| Memoization (U15-U16) | 2 | useMemo >= 1ms, useCallback + memo() only |
| Hook Design (U17) | 1 | Extract reusable logic, not lifecycle wrappers |
Philosophy
Every rule includes a "Why" explanation. Opinionated items are transparently marked with trade-offs.
License
MIT