القائمة
Use when creating, moving, or splitting React files, owner folders, component folders, hooks, presenters, utils, CSS modules, common folders, or shared/private dependencies.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when checking code for functional correctness, backwards compatibility, logic errors, security vulnerabilities, performance issues, or missing test coverage — not style.
Use when reviewing code, pull requests, branches, diffs, or changed files for quality, correctness, security, performance, and style issues.
Use when writing, fixing, editing, or refactoring TypeScript, Python, React, or CSS code. Not for PR or diff reviews — use clean-code-reviewer for those.
Use when writing, fixing, or editing comments or documentation in any language, especially commented-out code, stale docs, metadata comments, TODO banners, redundant comments, or unclear comment value.
Use when naming or renaming identifiers in any language, especially cryptic names, ambiguous parameters, type or scope encodings, misleading side effects, or requests for clearer names.
Use when writing, fixing, or editing code in any language with duplicated logic, magic values, unclear one-liners, mixed responsibilities, clutter, arbitrary code, or inconsistent abstraction levels.
| name | clean-react-file-organization |
| description | Use when creating, moving, or splitting React files, owner folders, component folders, hooks, presenters, utils, CSS modules, common folders, or shared/private dependencies. |
Organize files by dependency ownership. Keep private dependencies inside the owner that uses them, and move shared dependencies only as high as their nearest shared owner.
Give a React owner a folder when it has private dependencies.
A/
A.tsx
hooks.ts
B/
B.tsx
C.tsx
In this structure:
C.tsx is private to B.tsx.B.tsx is private to A.tsx.hooks.ts is owned by A/, so A.tsx, B.tsx, and C.tsx may use it.Use the same rule for hooks, presenters, utils, and similar helpers. If only one owner uses it, keep it with that owner.
If multiple nearby owners use the same dependency, move it to their nearest common/ folder.
common/
hooks.ts
A/
A.tsx
B.tsx
C/
C.tsx
Inside common/, create layer folders only when they are useful for that area: components/, hooks/, presenters/, or utils/. For single files, prefer MyHelperComponent.tsx, hooks.ts, presenters.ts, or utils.ts.
CSS modules are owner-scoped by default. Prefer one owner folder per CSS module, such as:
BattleStage/
BattleStage.tsx
BattleStage.module.css
Do not share a CSS module across unrelated features. If styling must be shared, keep it inside the nearest shared owner or common/, and prefer a shared component over shared CSS when possible.
For React owner folders, prefer PascalCase for the owner folder, owner component file, and owner CSS module:
BattleStage/
BattleStage.tsx
BattleStage.module.css
Apply the same ownership principle outside React. Non-UI modules do not need React-style layer folders unless they help. Do not create folders preemptively for one standalone file; add a folder when the owner gains private dependencies or enough internal structure to justify it.
components/, hooks/, or utils/ folders before ownership is clear.common/ when only one owner uses it.