A build prompt for an internal tool or admin panel with role-based permissions, bulk actions, an audit log and reporting.
Built for: Developers building tools for operations, finance or support teams
Processes that run on spreadsheets and email threads can save hours with the right internal tool. But internal tools have rules too: who can see what, who approves, and is every change on record?
With the Staff Engineer, Design Director and Security personas, the prompt defines SSO sign-in, role-based permissions, bulk editing, approval flows, an audit log and reports.
Each expert adds its own task block, constraints and success criteria to the prompt. Default selection for Internal Tool / Admin Panel:
Design the system architecture. Edge-first, 100ms p95. DB schema, API contract, caching strategy, multi-tenancy, RLS, idempotency. Explain why the chosen backend + DB combination is the right call, and write the scaling plan.
Build the design system: Tailwind tokens, shadcn/ui, dark mode only, Linear-like density, command palette, keyboard-first. Describe wireframes for the 3 critical flows.
Threat model (STRIDE), OWASP Top 10 checklist, auth/session hardening, data classification, GDPR/KVKK compliance map (data inventory, retention periods, deletion flow), audit log schema.
Event tracking plan: North Star and supporting metrics, event/property dictionary, funnel and retention definitions, data warehouse schema, dashboard list, data quality tests.
Preloaded in step 2 of the Studio; change any of the 7 layers.
Every feature appears in the prompt as a "Spec + API + UI + Tests" line.
Sample idea: "An internal panel where the support team approves and tracks refund requests". Below are the master prompt's header and the first expert's block; the Studio generates the full text as 4 experts × 8 steps.
# Internal Tool / Admin Panel - MASTER BUILD PROMPT Stack: Next.js 16 (App Router), tRPC + Next Goal: An internal panel where the support team approves and tracks refund requests This prompt builds a full-stack Internal Tool in 8 steps. Each step consumes the previous step's output. 4 experts' knowledge combined. Steps: 1. PRD & User Stories 2. Design System (Figma tokens) 3. DB Schema & API Contract 4. Auth & Billing Implementation 5. Core Features Build 6. AI Integration (RAG + Agents) 7. SEO/AEO & Analytics 8. Launch & Growth Checklist --- <prompt> <role name="Staff Engineer / CTO" org="ex-Stripe, ex-Vercel" specialty="System Architecture" experience="12y"> You are a Staff Engineer / CTO with 12 years of experience. Specialty: System Architecture. You have shipped world-class products at the level of Stripe, Linear and Vercel. </role> <context> Project: Internal Tool / Admin Panel - An internal panel where the support team approves and tracks refund requests Type: Internal Tool Vision: Requests arrive automatically from the order system; the team works through them with search, filters and bulk actions. Amounts above a threshold need a manager's approval, every decision lands in the audit log, and there's a weekly refund report with Slack notifications. Target user: Developers building tools for operations, finance or support teams - Pain: - Budget: Competitors: USP: Monetization: | Payments: Tech Stack: Next.js 16 (App Router), tRPC + Next, PostgreSQL + pgvector, WorkOS SSO, Meilisearch Features: RBAC + Permissions, Advanced CRUD + Bulk Ops, Audit Logs, Global Search (⌘K), Kanban / Board View, Analytics Charts, Admin Panel + Impersonate Compliance: KVKK/GDPR, SOC2 Lang: EN </context> <task> Design the system architecture. Edge-first, 100ms p95. DB schema, API contract, caching strategy, multi-tenancy, RLS, idempotency. Explain why the chosen backend + DB combination is the right call, and write the scaling plan. General: production quality, copy-paste ready level of detail. </task> <technical_architecture> - Frontend: Next.js 16 (App Router) - App Router, Server Components, partial prerendering - Backend: tRPC + Next - Edge runtime, RPC, zod validation - DB: PostgreSQL + pgvector - pgvector for semantic search, type-safe ORM, RLS policies - Auth: WorkOS SSO - Passkeys first, org/team model - Search: Meilisearch - typo-tolerant, faceted - Realtime: - presence, CRDT-ready Payment flow: -> Webhook -> Background job -> Entitlement update -> Audit log </technical_architecture> <feature_matrix> …
Unlimited flexibility on your own database and rules, with no per-seat fees; the prompt still designs reusable table / form components for a fast setup.
A role + permission table, server-side checks and row-level access (RLS) are mandatory; every write is logged with who, when and what changed.
Claude Code, Cursor, Windsurf, v0, Lovable, Bolt and ChatGPT. You pick the output format (Claude XML, ChatGPT Markdown, Cursor Rules, v0, Lovable/Bolt) in step 4 of the Studio, and you can also download it as .cursorrules or CLAUDE.md.
Yes. On the Free plan you generate unlimited prompts with 3 experts and 2 formats — no card required. 18 experts, the Mega Chain and Export to Builders come with Monster Pro ($29/mo).
A build prompt that gets Claude Code to set up a business WordPress and Elementor site with a theme, page structure, SEO, forms, speed and security.
A build prompt for a conversion-focused landing page or a personal portfolio, with copy, design, animation, SEO and form flows.
A build prompt for an iOS and Android app with Expo / React Native: push notifications, offline mode, in-app purchases and app store optimization.
A build prompt that ships a Manifest V3 Chrome extension together with its companion web app: accounts, sync and billing.
A fast, SEO-ready storefront on Next.js + headless commerce: product catalog, cart, Stripe or Iyzico/PayTR checkout and search. Build prompt ready.
The build prompt for a multi-vendor marketplace with seller onboarding, commissions, split payments, order management and search.
Experts, stack and features come preloaded like on this page — you add the name and the idea. Free, no card required.