One of the most underused things in every platform we sell is the prompt library that comes with it. It's not documentation about the code — it's the actual set of prompts and coding rules we used to build and maintain the platform. Used well, it turns a single developer into a small team.
Why a prompt library beats starting from scratch
When you ask an AI coding assistant to add a feature with no context, it guesses at your conventions. The results need heavy editing. When you give it the platform's prompt library first, it already knows:
- How your data layer and queries are structured.
- The naming and component conventions the codebase follows.
- The patterns for routes, validation, and error handling.
The difference in output quality is dramatic. You go from "plausible-looking code that doesn't fit" to "code that matches the rest of the platform."
A simple workflow
Adding a feature usually looks like this:
- Open the relevant prompt from the library as context in your editor.
- Describe the feature in plain language.
- Review the generated code against the platform's existing patterns.
- Test, refine, ship.
Our one engineer could build the things that actually make us different, because the platform handled the boring infrastructure.
That quote captures the point. The prompts don't replace your developer — they remove the busywork so your developer spends time on what's unique to you.
Start small
Pick something low-risk for your first extension — a new field, a small report, an extra filter. Get a feel for how the platform responds to the prompts, then take on bigger features with confidence.
New to the platform? The tutorials are the fastest way in, and the API reference covers the details.