Support inbox
Move customer requests from intake to assigned and resolved.
Customize the recipe
Prompt preview
# Support inbox Move customer requests from intake to assigned and resolved. ## Deliverable A seeded support inbox whose core triage and reply-draft flows persist. ## Stack and visual direction - Recommended starting stack: Next.js, TypeScript and shadcn/ui. Use local fixtures for development and a database for records that must persist across users. - Swiss grid: Use a visible modular grid, aligned baselines, asymmetric composition and tight typographic hierarchy. Reflow the grid without shrinking essential text. Apply this direction to the interface while keeping data and controls easy to read. - Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace. ## Tools and setup · Universal Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have. Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment. - [shadcn/ui Skill](https://ui.shadcn.com/docs/skills) (Skill) — Inspect the project's component registry and assemble accessible UI primitives. Project with compatible React and styling configuration. Follow the skill's agent-specific setup. Fallback: Reuse established controls in the project, or start with semantic native controls and test keyboard and error states. - [shadcn/ui](https://github.com/shadcn-ui/ui) (Repository) — Use and adapt relevant component source with established keyboard behavior. - [Supabase](https://github.com/supabase/supabase) (Repository) — Consider PostgreSQL persistence, authentication and row-level permissions for shared applications. Use a local stack or configure an authorized project for integration checks. ## Workflow 1. Model queues, assignments and status transitions. Show a thread, internal notes and a reply draft, with clear markers for customer-facing content. 2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable. 3. Run the applicable checks and report what actually passed along with any checks you could not run. ## Acceptance checks - [ ] An agent can assign a ticket, draft a reply and resolve it after reload. - [ ] Internal notes stay visually and structurally separated from customer replies. - [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess. - [ ] Verify real actions and persisted data where required. Exercise relevant loading, empty, invalid, pending, failure and success states. Provide a clear recovery path. - [ ] Use fixtures to verify core flows, including a narrow-screen layout and any applicable permission boundaries.
Recipe resources
Source, setup, and compatibility details.
shadcn/ui Skill
Inspect the project's component registry and assemble accessible UI primitives.
Project with compatible React and styling configuration. Follow the skill's agent-specific setup.
License · MIT
shadcn/ui
Use and adapt relevant component source with established keyboard behavior.
License · MIT
Supabase
Consider PostgreSQL persistence, authentication and row-level permissions for shared applications.
Use a local stack or configure an authorized project for integration checks.
License · Apache-2.0
Compound Engineering
Plan a substantial change, review the implementation and capture durable project knowledge.
Use the installation instructions for the receiving agent.
Upstream documents Codex, Claude Code, Antigravity.
Setup guide for Compound EngineeringPlaywright CLI
Walk real browser interactions and collect screenshots or evidence for regressions.
Node.js and supported browser binaries. Use a local build or authorized test environment.
License · Apache-2.0
Setup guide for Playwright CLI