Henosia

Prompt library

Copy a prompt below, swap the roles, fields, and rules for your own team's, and send it in Plan unless the note says otherwise. For why these prompts work the way they do, see the Prompting guide.

Start a tool

Use in Plan when you know the problem you want to solve and want Henosia to ask clarifying questions before writing a plan.

I want to replace our new-hire onboarding spreadsheet with an internal tool for HR, hiring managers, and IT. Interview me until you have everything you need to write the plan.

Use in Plan when you want a working first version with sample data in the browser before connecting a database.

Build a quote builder for our 25-person electrical service company so office staff stop typing small-job quotes from scratch.

How it works:
1. Pick a job type, such as "New outlet", "Replace fuse box", or "EV charger installation".
2. Pre-fill the standard materials and hours for that job type, and let me adjust quantities, add items from the price list, or change hours.
3. Enter the customer's name, address, and email.
4. Show a print-ready quote with line items, subtotal, 25% VAT, and total in DKK.

Fill it with sample data: 6 job types, about 25 materials with unit prices, and an hourly rate of 595 DKK excluding VAT. Keep everything in the browser with sample data for now, without connecting a database.

Leave out emailing quotes, saving customers, and invoicing for now. It's done when I can pick "EV charger installation", change one quantity, and see the total update on the print view.

Use in Plan when several roles share one tool and may only view or approve specific records.

Build a holiday request tool for our 40-person warehouse team across three teams: Inbound, Picking, and Dispatch.

- Warehouse staff submit a start date, end date, leave type (holiday, time off in lieu, unpaid), and an optional note, and can cancel their own pending requests.
- Team leads view and approve or reject requests for their own team only, with a short reason when rejecting.
- Everyone sees a shared calendar of approved absences by team so shifts stay covered, without seeing other people's notes or rejected requests.

It's done when a staff member can submit a request, their team lead can approve or reject it, and another team's lead cannot view or act on that request.

Use in Plan after uploading a CSV or requirements file to Private assets in Assets.

Read private-assets/vendor-delays-q3.csv to see the columns, carrier names, and status codes we track today. Build a supplier delay tracker around that structure, use a few anonymized sample rows in the same format for the preview, and highlight shipments whose revised delivery date slips past the production date.

Add sign-in

Use in Build in a project with Henosia Auth or after setting up Supabase sign-in when a prototype still shows mock names.

Replace the hardcoded user "Alex" in the top bar, account menu, and new expense claims with the signed-in user's full name, falling back to their email address when no full name is set. Tie each new claim to the signed-in user instead of letting the form pick a person.

Use in Plan when visitors with the link should read public pages while staff views require sign-in.

Let anyone with the link view our clinic locations, therapist profiles, and opening hours without signing in. Require sign-in to open the staff schedule, manage appointments, or edit opening hours, and send people back to the page they asked for after signing in.

Use in Plan after connecting Supabase when different signed-in roles may view or edit different rows.

Add three roles to our store visit tool: Area manager, Store manager, and Head office.

- Store managers can view visits and mark open actions fixed for their assigned store only.
- Area managers can run visits and view actions for stores in their area.
- Head office can view all stores, visits, and actions, and assign users to stores and areas.

Enforce these rules in Supabase Row Level Security policies as well as in the UI so nobody can read or update another store's rows directly.

Use in Plan when you invite external email addresses or domains under Environment settings > Henosia Auth (Guest access).

I've turned on guest access so external clients can sign in and read announcements on the home page. Clients must never see or change internal project data: budgets, internal notes, or anything on the Projects page, even by querying the database from their browser. Only our own organization members should see and edit that.

Connect data

Use in Plan after connecting a Supabase project to review proposed tables and access policies before creating them.

Design the Supabase tables and Row Level Security policies for our equipment loan tracker:

- items: name, category, serial number, office location, condition, retired flag.
- checkouts: item, borrower (signed-in user), checkout date, expected return date, returned date, condition note.

Every signed-in teammate can view active items, check out an available item, and mark their own checkout returned. Only office admins can add, edit, or retire items, or mark someone else's checkout returned.

Use in Plan after connecting Supabase if Henosia didn't already propose moving your localStorage data during setup.

Move our shift handoff entries and acknowledgements from localStorage into Supabase so handoff notes are shared across day, evening, and night shifts. Keep the existing form fields and status filters working, remove the hardcoded demo rows once the table is connected, and show a clear empty state when a shift has no open items yet.

Use in Plan or Build after saving your secret key (without NEXT_PUBLIC_) under Environment variables in Environment settings.

Send a confirmation email through Resend when a coordinator marks a supply request as "Ordered", including the clinic name, ordered items, and expected delivery date. Read the API key on the server from RESEND_API_KEY so it is never exposed to the browser, and show a clear notice if sending the email fails while still saving the order status.

Use in Plan when server work belongs in a Supabase Edge Function, such as calling a webhook from Supabase's servers.

Create and deploy a Supabase Edge Function called by signed-in shift leads when a shift handoff item is saved with severity "Urgent", posting a short summary to our Slack incoming webhook. Keep JWT verification enabled so only signed-in users can call the function, read the webhook URL from a Supabase Edge Function secret named SLACK_OPS_WEBHOOK_URL rather than storing it in project files, and tell me the secret name to add in the Supabase dashboard.

Refine the look

Use in Build when a page looks generic and you want concrete visual rules Henosia can check against the preview.

Restyle this stock overview for daily warehouse use. Use our brand navy #1F4E79 for primary actions and active states, neutral gray borders, and plain white surfaces. Keep it calm and dense like a spreadsheet so at least 12 rows fit on screen on a laptop: no hero banner, no gradients, no frosted glass, no rounded pill buttons, no heavy drop shadows, and no emoji.

Use in Build with Attach images in the prompt field (and company logos uploaded to Public assets in Assets).

Use the attached screenshot of our existing finance portal as a visual reference: match its sidebar width, compact table spacing, muted status tags, and heading sizes, and place /logo.svg from Public assets at the top of the sidebar. Keep all of our current pages, columns, and filters as they are.

Use in Build when cleaning up one section while leaving the rest of the page alone (for single-element tweaks, Select is faster).

Only update the summary area and amounts column on the /orders page: place the four weekly totals in one compact horizontal row above the orders table, remove the decorative icons from those summary cards, and right-align all DKK figures with tabular numerals so digits line up. Leave filters, dialogs, and every other page untouched.

Use in Build when field or shop-floor staff use a page on a phone while managers review wide tables at a desk.

Optimize the store visit checklist page for 390px phone screens without changing the desktop head-office table: keep the store header and progress count sticky, make the OK and Not OK buttons large tap targets side by side, open the comment and photo fields inline only when "Not OK" is tapped, and keep a fixed "Finish visit" bar at the bottom.

Fix something

For build or runtime errors shown in a preview banner, try Attempt fix first. After two corrections in chat that still miss the mark, stop any active work, choose Restore on an earlier checkpoint, pick Restore Files & Task, and send one fresh prompt instead of adding a third correction (see Restore).

Use in Build when a button, filter, or form behaves wrongly without triggering an error banner.

On /requests, when I filter by "Pending", open a request, and click "Approve", the status updates inside the drawer, then jumps back to "Pending" in the table until I reload the browser, and the "Pending" filter clears itself. Find why the table state and filter reset after approval, fix both, and check the flow in the preview.

Use in Plan when signed-in users see missing rows or permission errors on data they should be allowed to view.

Signed-in team leads open /team-requests and see "No requests yet", even though rows for their team exist in Supabase. Check the query, table grants, and Row Level Security policies to find why those rows are filtered out, and propose the minimal policy or query fix without disabling or broadening Row Level Security.

Use in Plan or Build right after a build finishes when access rules, calculations, or edge cases matter to your team.

What did you check to confirm that a store manager cannot view or edit another store's open actions, and what still needs me to test in the preview with a second account?

Use in Build once you have corrected the same project convention twice so future tasks follow it automatically (Customize how it works).

Update AGENTS.md at the project root with three concise rules for every task: format all money as 1.250,00 kr. (Danish locale, DKK), format dates as dd-mm-yyyy, and never insert sample rows in Supabase migrations. Keep the file short and remove any outdated notes.

Prepare to publish

Use in the prompt box inside an expanded Supabase Security Advisor finding in Security (or in Plan in chat) so Henosia writes policies that match your team's rules.

Staff members may view, create, and cancel only their own pending leave requests. Team leads may view and approve or reject requests for members of their own team. HR admins may view all requests and manage team assignments. No signed-out visitor should have access to any table.

Use in Plan before opening Publish to verify who can reach each route, secret, and uploaded file.

Audit this project before we publish it for our organization:

1. List every page and API route, and report whether a signed-out visitor or a signed-in user in the wrong role can reach it.
2. Check that no secret key (anything other than the Supabase URL and publishable or anon key) uses a NEXT_PUBLIC_ variable or appears in client code.
3. Check public/ for any non-image files or internal documents that belong in private-assets/ instead.

Report what you find and propose a plan for anything that needs tightening.

Use in Plan when turning a prototype with demo copy into a live tool for your team.

Prepare the app for real team use before we publish: find any remaining hardcoded sample rows, placeholder names or test email addresses, broken links, and console.log debug output, and make sure every list and dashboard view shows a clear empty state and error message when the database has no rows yet.
Was this page helpful?

On this page