CRM pipeline
Move opportunities through stages and keep next steps visible.
Customize the recipe
Prompt preview
# CRM pipeline Move opportunities through stages and keep next steps visible. ## Deliverable A functional pipeline with sample opportunities and an activity history. ## Stack and visual direction - Recommended starting stack: Next.js and TypeScript with a small data model. Build the core workflow with fixtures before connecting external services. - 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. - [Twenty](https://github.com/twentyhq/twenty) (Repository) — Reference contacts, companies and opportunity stages when designing a CRM workflow. Hosted or self-hosted setup for a live integration. - [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 companies, contacts, deals and next activities. Provide stage movement through a keyboard-accessible control and capture dates and reasons for moves. 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 - [ ] The same stage change works by keyboard and pointer. - [ ] Reopening a deal preserves its activity history and updates stage totals. - [ ] 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
Twenty
Reference contacts, companies and opportunity stages when designing a CRM workflow.
Hosted or self-hosted setup for a live integration.
License · Check upstream terms for the chosen edition.
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
Playwright 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