Prompt Library

Paste-ready prompts for building Neo apps

Use these prompts as the working documentation. Start with discovery, then blueprint, build, verify, and hand off. Replace bracketed fields before pasting into Neo.

Discovery Build Plugins QA Handoff

Recommended workflow Prompt ladder

1Use the discovery prompt to frame the customer’s operating job.
2Generate the app blueprint and data model before asking Neo to build.
3Use the Plugin plan prompt before enabling read or write actions.
4Run the QA and handoff prompts before submitting the app.

Prompt quality bar

Names the operator, workflow, records, and decision point
Specifies Plugin setup and action approval boundaries
Requests seed data and exception cases
Asks for acceptance evidence, not generic confidence

Prompt pattern

Context: [customer/team/workflow]
Build: [records, screens, forms, actions]
Constraints: [permissions, Plugins, approval boundaries]
Evidence: [tests, seed data, expected outputs]
Return: [specific format]

Neo Builder Design System

Operations Desk for implementation training

This system turns Neo Builder Academy into a reusable product language: compact, calm, auditable, and explicit about Plugins, actions, verification, and customer handoff.

Satoshi 8px base radius 32px controls Hairline borders

Foundations

North star

Teach builders through an app-like workbench, not a marketing site. Every surface should help someone learn, evaluate, submit, or verify.

Information density

Use compact controls and shallow panels so FDEs can scan modules, rubrics, test evidence, and app quality without excessive scrolling.

Trust posture

Make sensitive actions legible. Plugin setup, write actions, permissions, and submission verdicts must expose status and rationale.

Reuse boundary

Extend these primitives for academy, onboarding, enablement, and implementation QA surfaces. Do not use them for external marketing pages.

Tokens

Component Families

Core Patterns

Voice And Copy

Use

Plugins, actions, Ready, Setup needed, Loading plugins..., Updating plugins..., Run test suite, Approved for implementation review.

Avoid

Internal implementation labels, offline wording for configured idle integrations, duplicate setup buttons, count-only summaries, and secret-oriented instructions.

Implementation Contract

System maturity v1 ready

Use this as the default source for new academy screens, implementation rubrics, and customer-facing training flows.

Live component preview

Switch density to see how the same primitives adapt without changing the visual language.

4 Plugin SafetyConnections and actions

Plugin readiness

Ready Setup needed

PASSVerification
Happy path and exception path covered.

WARNHandoff
Add owner and support path before launch.

QA Checklist

No horizontal overflow at desktop or mobile widths
Primary accent appears only for current state or next action
All Plugin and action copy stays user-facing
Forms, tabs, drawers, and buttons have visible states
Submission verdicts include evidence, not just confidence

App submission

Submit an app plan for automated review

The evaluator checks whether a proposed Neo-built app is specific, testable, permission-aware, and ready for implementation handoff.

App name Primary owner

Business problem Users and permissions Data model Workflow and screens Plugins and actions Verification evidence

Assessment rubric

What “best app” means in Neo

A good implementation app is not a prettier spreadsheet. It gives the customer a reliable operating surface: clear records, auditable workflows, safe plugins, and repeatable verification.

Area	Pass condition	Common failure