A working prompt library is the main event, not an appendix. The industry still treats prompts as some half-baked spitball left in a README, or, worse, a plaintext blob stapled to package.json and forgotten. That's a waste of compute and credibility. What powers reliable AI-assisted refactoring, onboarding, or even next-gen code IDEs is not the size of the model but the clarity and context supplied by the actual, shipped prompt set.

OTF kits turn this lesson into a repeatable deliverable: every paid template includes 20+ production-tested prompts tied to the real file structure, component API, and product-specific conventions. This is not a suggestion; it's structural.

The takeaway: a real prompt library is as important as your component library. Treat it like one.

Start with the pain: why blank chat boxes don't scale

The web is full of “integrations” that paste a blank chat input over your codebase and call it an “AI coding assistant.” The result: hallucinated function names, invented conventions, broken import paths. Here’s what happens in real life:

Dev: "Add a social login button."
AI (blank prompt): "Sure! Insert <SocialLoginButton> in your LoginScreen.js."
Dev: (There’s no such component. There's not even a LoginScreen.js.)

Short: A generic prompt with zero context simply can't know your conventions, files, or patterns. The agent will either fail, hallucinate, or pepper you with clarifying questions you have already answered in your product architecture.

Takeaway: Prompting without context is coding without types — fragile guesses instead of structured outcomes.

What a first-class prompt library enables

When the prompt library ships with the codebase, it looks like this:

• Every prompt knows the folder structure (e.g., features/auth, screens/Settings/index.tsx).
• Conventions are hard-coded: naming, import styles, design token usage.
• Endpoints and integration points (e.g., “update the Stripe webhook handler in api/webhooks/stripe.ts”) are spelled out.
• The prompt language is focused, directive, full of worked examples — not meandering.

Because each is tested and versioned alongside the code, drift is minimal and “works on my machine” is real: you change the signature, you change the prompt.

Takeaway: Treating the prompt library as code is the difference between hope-driven and intent-driven agents.

Anatomy of a working prompt: local, explicit, and testable

A real prompt for an agent doesn't just say "add a feature" — it walks the tool through your internal structure, conventions, and gotchas, like a senior engineer onboarding a new team member.

Example: OTF SaaS Dashboard kit ships this inside ai/prompts/upgrade-billing.md:

You’re adding a billing option using Stripe. 
- All billing logic lives in `features/billing/`.
- Webhook handlers are in `api/webhooks/stripe.ts`.
- Use the `<BillingSettings />` component.
- Apply `@otfdashkit/tokens` for theme colors.
- Update docs in `docs/billing.md`.

A properly engineered CLI command feeds this prompt to Cursor, Claude, or any API-driven agent, binding real file names:

cursor run \
  --prompt-file ai/prompts/upgrade-billing.md \
  --project-root /full/path/to/kit \
  --output-mode patch

You get a controlled, repeatable outcome — no hallucinated file trees, no invented imports.

Takeaway: A localized, declarative prompt is a spec, not a guess.

Structuring prompts for agent execution: constraints over vibes

The test for a useful prompt isn’t “does this sound good in a README,” but “can a non-human tool execute this reliably against THIS codebase?” That means:

• File names, folders, and exports match the kit — zero ambiguity.
• Each prompt is tied to a specific job (e.g., "Migrate avatar to new CDN", "Wire up feature flag", "Refactor layout grid").
• Constraints are explicit; gotchas are called out (“Never edit node_modules”, “Always use tokens.colors.primary”).
• Examples are real, not hypothetical — they cite files actually present.

Bad prompt (README-level):

Add Stripe Billing.

Working prompt (kit-level):

Add billing with Stripe:
1. Create `features/billing/stripe.ts` for API integration.
2. Edit `pages/settings/billing.tsx` to add the UI.
3. Use the `StripeButton` component — see `features/billing/StripeButton.tsx`.

Every bullet line is an instruction the agent can map to a directory — or fail early if the file is missing.

Takeaway: A prompt an agent can’t run is just documentation. A prompt an agent can run is infrastructure.

Metrics: what a prompt library enables

Real prompt libraries cut failures — and wasted cycles — dramatically. Here’s what changes with a prompt set tied to your kit:

[[COMPARE: README-level prompt vs shipped prompt library]]

Takeaway: The delta is not subtle — the prompt library is the agent’s map.

Building the library: process, not afterthought

Most teams treat prompt engineering as an afterburner. OTF bakes it into every kit:

1. Declare the env: Each template has a fully specified ai/prompts/ folder mapping jobs to files.
2. Test with real agents: Each prompt gets a minimum working patch from an LLM — patched, run, and visually reviewed before shipping.
3. Update as code changes: Edit a feature; rewrite the affected prompts as part of the workflow.
4. Package, don’t paste: Prompts ship as files, not invisible comments; discoverable and composable.
5. Human review: All prompts are readable by another engineer, with examples in context.

ls ai/prompts/
add-billing.md
upgrade-auth-flow.md
write-email-reset.md

Each is parameterized and can be fed to any API-driven code agent without hacking.

Takeaway: A prompt library is not a TODO. It’s a tested, versioned asset.

How to use OTF’s prompts from day one

Nothing fluffy: cloning an OTF kit drops a working ai/prompts/ folder into your project. It already reflects every module and convention.

You can:

• Feed any prompt directly to OpenRouter, Claude Code, or Cursor — no rewriting.
• Swap in new agent endpoints (OPENROUTER_API_KEY, etc), all wiring is file-based.
• Use as source for in-editor completions, in-code CLI triggers, or pre-commit code gen.

Example: running a workflow step with your own key.

OPENROUTER_API_KEY=sk-... \
cursor run \
  --prompt-file ai/prompts/upgrade-billing.md \
  --project-root $PWD

And because every OTF kit ships AI config files (CLAUDE.md, .cursorrules) and tested prompt libraries, upgrade and automation flows behave — reproducible, extendable, modifiable.

Takeaway: Start with a prompt library built for agents, not for Slack threads.

OTF’s angle: the prompt library is the unchanging layer

Framework churn lands hardest on AI workflows: new models, better agents, changing file structures. But prompts — done right — are the durable contract between your codebase and the agent executing on it. Swap the LLM, test the outcome; the prompt library is the anchor in every kit.

You can adopt Cursor, Bolt, Lovable — it doesn’t matter. The prompt library persists, is testable, and you own it.

[[DIAGRAM: agent or tool layer changing rapidly above, prompt library and kit code staying durable underneath]]

Takeaway: The winners in AI-native dev aren’t the ones who chase every new model. They’re the ones who own the substrate the agent runs on: the codebase and the prompts.

Closing: prompts are product, not process

Shipping an OTF kit means inheriting the value of 20+ prompts tested against your actual structure. A chatbox is cheap; a working, evolving prompt library that every agent can use is use. Treat prompts as first-class — own the API your AI tools depend on. The agents will come and go. The contract lives in your prompt library.