Add React Admin Resource
Developmentadd-react-admin-resourceAdd React Admin Resource is an Agent Skill for development published in the talkincode/toughradius repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/talkincode/toughradius/blob/HEAD/.agents/skills/add-react-admin-resource/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/add-react-admin-resource, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Skill: Add a Frontend Management Resource / Page
Feature ID:
TR-F013| Milestone: M2 and others
When to use
After adding an Admin API on the backend, when the React Admin backend needs to expose the corresponding resource or page.
Pre-research
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
Implementation steps
- Resource file: define List/Edit/Create in
web/src/resources/<feature>.tsx(mirrornodes.tsx). - Register the resource: add
<Resource name="<api-path>" .../>inweb/src/App.tsx; the name must align with the backend API path. - Data mapping: confirm
dataProvider.tspagination / filter / sort params match the backend. - Pages (if not standard CRUD): put them under
web/src/pages/; do not create a separate management entry. - i18n: if the project has i18n keys, add the corresponding strings.
Boundaries
- Do not introduce a separate management entry; all pages hang under the unified Admin framework.
- The frontend only exposes backend-supported, verifiable, safe actions (especially CoA); never assemble protocol packets in the frontend.
Acceptance
-
cd web && npm run buildsucceeds - List / filter / CRUD are connected to the backend
- PR references
TR-F013and the milestone ID