backoffice-react
CommunityClarify backoffice React screen boundaries
System Documentation
What problem does it solve?
It helps teams decide how to structure an optional backoffice React screen by defining the target archetype (list, detail, form, dashboard, or bulk-action) and clarifying who owns each state (query parameters, component state, and form state). It also guides boundary separation for search, table, confirm, and export flows to reduce coupling and rework.
Core Features & Use Cases
- Decide screen archetype early to prevent over-engineering and redundant routes.
- Define state ownership so that query params, UI state, and draft data are managed in a single source of truth.
- Establish clear boundaries for common backoffice patterns (QueryBar, ResultTable, DetailPanel, FormSections, BulkToolbar, ConfirmFlow) and handoff to provider skills when needed.
Quick Start
Inspect existing repository guidance and read references/screen-archetypes.md, references/data-boundary.md, and references/bulk-actions-and-forms.md to start crafting your backoffice screen layout tomorrow.
Dependency Matrix
Required Modules
None requiredComponents
💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: backoffice-react Download link: https://github.com/jingjing2222/create-rn-miniapp/archive/main.zip#backoffice-react Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.