菜单
Add a resource or page in the React Admin management backend (TR-F013). Use when a new Admin API needs a corresponding management UI in the frontend.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Review merged PRs since the last Git tag and decide whether a ToughRADIUS release is warranted. Use when Codex is asked to prepare a version release, audit unreleased changes, decide whether to publish, create a new release tag, or tag origin/main after PR review.
Global orchestrator / dispatcher role. Activated when the user issues an "auto-delegate development / continue the roadmap / auto-delegate" command (without naming a specific subtask); runs the full loop - select task, pick SOP, dispatch, quality gates, open PR, self-iterate the roadmap.
Independent review gate for auto-delegation PRs (TR-F022). Use after an orchestration round opens a PR, and as the first step of every new round to clear in-flight PRs - run an adversarial, CI-anchored review, request changes via labels + comments, and auto-merge only when the review passes and CI is green.
Standard-library-style Go API documentation and comment conventions (TR-F024). Use when adding or changing exported Go identifiers, writing package comments, or backfilling godoc on a package so it reads like the Go standard library.
Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022). Use whenever a milestone subtask needs CI-backed acceptance, covering test/integration integration tests and unit tests.
Add a group of Admin REST endpoints in the management backend (TR-F012). Use when a feature needs management APIs such as create/read/update/delete.
| name | add-react-admin-resource |
| description | Add a resource or page in the React Admin management backend (TR-F013). Use when a new Admin API needs a corresponding management UI in the frontend. |
Feature ID:
TR-F013| Milestone: M2 and others
After adding an Admin API on the backend, when the React Admin backend needs to expose the corresponding resource or page.
view web/src/App.tsx # resource / route registration
file_search "web/src/resources/*.tsx" # resource references
view web/src/providers/dataProvider.ts # REST mapping
view web/src/resources/nodes.tsx # standard resource reference
web/src/resources/<feature>.tsx (mirror nodes.tsx).<Resource name="<api-path>" .../> in web/src/App.tsx; the name must align with the backend API path.dataProvider.ts pagination / filter / sort params match the backend.web/src/pages/; do not create a separate management entry.cd web && npm run build succeedsTR-F013 and the milestone ID