A prompt template for integrating Bootstrapware Feedback

If you are using an AI coding agent, the easiest way to waste time is to ask it to build an entire public feedback portal from scratch.

A better prompt treats Feedback as the product and the agent as the integrator, embed, identity, adapter or Hosted props, no invented APIs.

Generic prompt template

Integrate Bootstrapware Feedback into this application.

Goal:
Add an embeddable feature-request board for [audience] inside the authenticated product.

Requirements:
- Create a page at [route]
- Render the Bootstrapware Feedback component
- Import @bootstrapware/feedback/styles.css
- Pass user={{ id, name? }} from our signed-in session (opaque stable id)
- Mode: [local createLocalAdapter | BYO FeedbackAdapter | Hosted boardId + publishableKey]
- If Hosted/config: use boardId [BOARD_ID] and publishable key from [ENV_VAR]
- If BYO: implement listPosts, createPost, vote, unvote against [BACKEND]
- Title max 200, body max 5000, plain text
- Statuses only: open | planned | in_progress | shipped | declined (not "completed")
- Embed-only: no public board URL
- Do not expose secret keys (bsw_*_sec_) or privileged backend logic in the client
- Never send post title/body through MCP, MCP configures boards only
- Live publishable config needs BYO ($9.99) or Hosted ($19.99); live Hosted writes need Hosted ($19.99)
- Use the existing design system where reasonable
- Keep the implementation modular and easy to maintain

Non-goals:
- Do not rebuild list/submit/vote UI from scratch
- Do not invent Bootstrapware REST routes beyond documented board management
- Do not put Feedback identity (login) on Bootstrapware, we assert user.id

Example for product ideas (Hosted)

Integrate Bootstrapware Feedback into this Next.js app.

Goal:
Add a feature-request page at /dashboard/feedback.

Requirements:
- Render the Feedback component
- Import @bootstrapware/feedback/styles.css
- Use boardId "brd_product_ideas"
- Read NEXT_PUBLIC_BOOTSTRAPWARE_PUBLISHABLE_KEY from environment variables
- Pass user from the existing session (id + name)
- Omit adapter (Hosted mode)
- Show loading and error states around submit/vote
- Keep styling consistent with the existing dashboard
- Do not expose secret keys or database credentials
- Do not create a public /b/... board route

(Env var name is illustrative. Match whatever you use in the app.)

Example for BYO adapter

Integrate Bootstrapware Feedback with a BYO adapter.

Goal:
Embed Feedback at /settings/ideas; store posts in our Postgres API.

Requirements:
- Pass adapter with listPosts, createPost, vote, unvote calling /api/feedback*
- Enforce authz from the signed-in session on the API (do not trust browser alone)
- One vote per author.id per post
- Optional hosted boardId + publishable key for published toggles only
- Posts stay on our backend; Bootstrapware hosts board config
- Follow packages/feedback-react AGENTS.md boundaries

Why prompt templates help

Agent success is often downstream of scope discipline.

A good prompt sets the boundary, tells the model what not to rebuild, keeps your security model intact, and focuses the output on integration rather than novelty.

For an even shorter brief optimized for retrieval, see Give this to your coding agent. Formal package rules: AGENTS.md.

Related: Feedback · Quickstart · Cursor · Claude Code · Codex · AI coding agents