What NOT to say in an app description
2 min
Avoid implementation details ("use Tailwind", "add tRPC"). Avery picks the stack; you describe the product.
The wizard composes generator plugins against a single Prisma schema; the stack is fixed (Next.js 15, Tailwind v4, shadcn/ui, Prisma, NextAuth, Zod-validated forms). Trying to dictate stack choices wastes prompt tokens and confuses the planner:
Bad: "Use Tailwind and Headless UI" → already true; redundant. Bad: "Add tRPC" → not part of the stack today. Bad: "Use Drizzle instead of Prisma" → not a switch you can flip.
Good: "Has admin / public / authenticated user roles" → translates to an archetype + auth-generator config.
Good: "Send a welcome email on signup" → planner adds the email-generator + a welcome template.
Good: "Track every change to a Deal in an audit log" → audit-log-generator on the Deal model.
Focus the description on what the USER of the generated app sees and does. The how-it's-built side is Avery's job.
Live recipes need the desktop
This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.