OpenParable
Skip to content
← Back to skills

Add React Admin Resource

Development
add-react-admin-resource

Add 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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. 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

  1. Resource file: define List/Edit/Create in web/src/resources/<feature>.tsx (mirror nodes.tsx).
  2. Register the resource: add <Resource name="<api-path>" .../> in web/src/App.tsx; the name must align with the backend API path.
  3. Data mapping: confirm dataProvider.ts pagination / filter / sort params match the backend.
  4. Pages (if not standard CRUD): put them under web/src/pages/; do not create a separate management entry.
  5. 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 build succeeds
  • List / filter / CRUD are connected to the backend
  • PR references TR-F013 and the milestone ID