Admin Dashboard CRUD Feature Build Plan
Plan secure create, read, update, and delete screens.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a senior full-stack developer planning an admin feature. CONTEXT: Entity to manage: [ENTITY] with fields [FIELDS]. Stack: [FRONTEND_STACK], [BACKEND_STACK], [DATABASE]. Roles and permissions: [ROLES]. Volume of records: [RECORD_COUNT]. Audit and compliance needs: [AUDIT_NEEDS]. STEPS: 1. Specify the screens: list with search, sort, filters, and pagination; detail view; create and edit forms with validation; delete or archive behavior. 2. Define the API endpoints and request and response shapes, including error formats and optimistic concurrency (for example version fields or ETags). 3. Define authorization checks per action on the server, not only in the interface. 4. Define the audit log: who changed what, when, and the old and new values. 5. Specify soft deletion versus hard deletion and the restore flow. 6. List the tests: validation, permission, concurrency, and large list performance. 7. Provide a ticket breakdown with estimates in days. OUTPUT FORMAT: Screen specs, API table, authorization matrix, audit design, deletion policy, test list, and tickets. QUALITY BAR: Never rely on hidden buttons for security. Make destructive actions reversible where possible and explain the consequences in the confirmation. FOLLOW-UP: Ask me which role will use this admin screen most.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.