{"ok":true,"count":15,"source":"sonara_original","templates":[{"id":"builtin:website-structure-and-copy-plan","slug":"website-structure-and-copy-plan","title":"Website Structure and Copy Plan","productArea":"business_builder","productLabel":"Business Builder","category":"website","description":"Decide what pages a site needs, what goes on each one, and in what order to build them -- before writing a word of final copy.","content":"Act as a website planner for a small business. Plan the site for {{business_name}}, a {{business_type}} serving {{target_customer}}.\n\nWhat the business has to work with:\n- What it sells, and what a customer pays: {{primary_offer}}\n- How a customer currently gets in touch: {{current_enquiry_path}}\n- Proof that genuinely exists today: {{existing_proof}}\n- Who will maintain the site afterwards: {{who_maintains_it}}\n\nProduce:\n1. The smallest set of pages this business actually needs, each with the one job it does. Say which pages are commonly built and would be wasted here, and why.\n2. For each page, the sections in the order a visitor reads them, and the single action that page is asking for.\n3. The one question a visitor most needs answered on each page, in that visitor's own words rather than the business's.\n4. A build order, so a useful site is live before it is complete.\n5. What to write once and reuse across pages, so the same claim cannot end up saying two different things.\n6. Anything that must be checked by a person before publishing -- prices, availability, qualifications, guarantees, anything regulated.\n\nRules:\n- Use plain language a customer would use. No industry jargon and no filler.\n- Do not invent proof, testimonials, client counts, awards, years in business, guarantees, or credentials. If a section needs proof the business has not listed above, say what to collect and leave a marked gap.\n- Mark every assumption you make.","promptType":"text","variables":["business_name","business_type","target_customer","primary_offer","current_enquiry_path","existing_proof","who_maintains_it"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["website","structure","copy","planning"],"version":1,"fingerprint":"513e7288651b3a6fc981cdcec68b6d0f4e65babd554cb890d44c9515e70e6068","license":"SONARA original; repository MIT license"},{"id":"builtin:website-hero-section","slug":"website-hero-section","title":"Website Hero Section","productArea":"business_builder","productLabel":"Business Builder","category":"website","description":"The first screen: what you do, who it is for, why it matters, and the one thing to press. Written to be understood in five seconds.","content":"Act as a copywriter working on the first screen of a website. Write the hero section for {{business_name}}, a {{business_type}}.\n\n- Who this is for: {{target_customer}}\n- What they get: {{primary_offer}}\n- What they would otherwise do instead: {{the_alternative}}\n- The action you want: {{primary_action}}\n\nProduce three complete options, each with:\n1. A headline of at most twelve words that says what the business does, not how it feels about itself.\n2. A subheadline of one or two sentences that says who it is for and what changes for them.\n3. The single call to action, in the words describing what happens when it is pressed.\n4. One line of supporting detail only if the business has something true to put there -- price, timescale, area covered, availability.\n5. A note on what the image or video behind it should show, described as a scene rather than a mood.\n\nThen say which of the three you would ship and why, in two sentences.\n\nRules:\n- A visitor who reads only the headline must be able to say what this business does.\n- No superlatives the business cannot support. No \"leading\", \"premium\", \"world-class\", \"trusted by thousands\", or \"award-winning\" unless {{existing_proof}} contains the proof.\n- Do not invent statistics, customer numbers, ratings, or guarantees.","promptType":"text","variables":["business_name","business_type","target_customer","primary_offer","the_alternative","primary_action","existing_proof"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["website","hero","headline","conversion"],"version":1,"fingerprint":"e02c557b2842017e3a50098d720c414e37f861b15012d08c1420157bc3370826","license":"SONARA original; repository MIT license"},{"id":"builtin:website-service-page","slug":"website-service-page","title":"Service Page","productArea":"business_builder","productLabel":"Business Builder","category":"website","description":"One page for one service: what is included, what it costs, what happens after somebody enquires, and what is not included.","content":"Act as a copywriter writing a single service page. Write the page for {{service_name}}, offered by {{business_name}} to {{target_customer}}.\n\n- What the service involves: {{what_is_involved}}\n- What it costs, or how the price is worked out: {{price_basis}}\n- How long it takes: {{turnaround}}\n- What the business needs from the customer first: {{what_you_need_from_them}}\n- Proof that genuinely exists today: {{existing_proof}}\n\nProduce, in this order:\n1. A heading naming the service the way a customer would search for it.\n2. One paragraph on the problem this solves, in the customer's words.\n3. What is included, as a list of things that will actually happen.\n4. **What is not included.** Name the boundaries plainly -- this is the section that prevents the argument later, and most service pages leave it out.\n5. What it costs, or if the price varies, exactly what it varies with.\n6. What happens after somebody gets in touch, step by step, with a realistic timescale for each step.\n7. Answers to the three questions a customer asks before buying this kind of service.\n8. One call to action, repeated at most twice on the page.\n\nRules:\n- Prices and timescales come from the inputs above. If one is missing, write the section with a marked gap rather than a plausible number.\n- Do not invent testimonials, case studies, results, or credentials.\n- Say \"we\" and \"you\". No third-person description of the business.","promptType":"text","variables":["service_name","business_name","target_customer","what_is_involved","price_basis","turnaround","what_you_need_from_them","existing_proof"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["website","services","pricing","copy"],"version":1,"fingerprint":"701abb2555a970f02c778045602c0ca3fda1c95191755edfd377896e5e97fbc8","license":"SONARA original; repository MIT license"},{"id":"builtin:website-about-page","slug":"website-about-page","title":"About Page","productArea":"business_builder","productLabel":"Business Builder","category":"website","description":"The page that decides whether somebody trusts you. Written from what is actually true, and useful to the reader rather than flattering to the owner.","content":"Act as a copywriter writing an About page. Write it for {{business_name}}, a {{business_type}} run by {{who_runs_it}}.\n\n- Why this business exists, in the owner's own words: {{why_it_exists}}\n- How long it has been running, and what has actually happened: {{real_history}}\n- Who it is for: {{target_customer}}\n- Qualifications, memberships, insurance or registrations that genuinely exist: {{real_credentials}}\n\nProduce:\n1. An opening that is about the reader's situation, not the business's founding date.\n2. The story, told only from {{why_it_exists}} and {{real_history}}, in the order that makes it make sense rather than in chronological order.\n3. Why this business is a reasonable choice for {{target_customer}} specifically -- and who it is *not* the right fit for, which is what makes the rest believable.\n4. The credentials from {{real_credentials}}, stated plainly, with nothing added.\n5. Something concrete and human: how the work is actually done, what the owner cares about getting right, what a customer can expect the experience to feel like.\n6. A closing that points at one next step.\n\nRules:\n- An About page is where invented history does the most damage, because it is the page people check. Use nothing that is not in the inputs above.\n- Do not invent qualifications, memberships, insurance, registrations, awards, staff, premises, client numbers, or years in business.\n- No \"passion\", \"journey\", \"we believe\", or \"founded on the principle that\" unless the owner's own words contain it.\n- If the business is new, say so. New is a fact, not a weakness, and hiding it reads worse than stating it.","promptType":"text","variables":["business_name","business_type","who_runs_it","why_it_exists","real_history","target_customer","real_credentials"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["website","about","trust","copy"],"version":1,"fingerprint":"2c071d6e76cbc612db4a73f89411b3d5354948a6a726cc915b12d4114b35f9db","license":"SONARA original; repository MIT license"},{"id":"builtin:creator-portfolio-page","slug":"creator-portfolio-page","title":"Creator Portfolio Page","productArea":"creator_studio","productLabel":"Creator Studio","category":"portfolio","description":"A portfolio arranged around the work somebody wants more of, with the rights and credits stated rather than assumed.","content":"Act as a portfolio editor. Plan the portfolio for {{creator_name}}, a {{discipline}} who wants more {{work_they_want_more_of}}.\n\n- The pieces available to show: {{available_work}}\n- Who they want to be hired by: {{target_client}}\n- What they charge, or how they price: {{price_basis}}\n\nProduce:\n1. Which pieces to show and, more importantly, which to leave out. A portfolio is judged by its weakest piece, and the reason to cut something is that it attracts work they do not want.\n2. The order to show them in, and what the first piece has to do.\n3. For each selected piece: the one line of context a client needs, what the creator actually did on it, and the result if one is known.\n4. Where collaborators, clients and rights need to be credited, and what to write when permission to show something has not been confirmed.\n5. A short About section aimed at {{target_client}}.\n6. How somebody gets in touch, and what to ask them for so the first reply can be useful.\n\nRules:\n- Do not invent clients, brands, results, view counts, or awards.\n- Do not describe work as done for a named client unless {{available_work}} says it was. Speculative and personal work is shown as what it is, which costs nothing and protects the creator.\n- Flag any piece where the right to publish it is unclear, and say who has to confirm it.","promptType":"text","variables":["creator_name","discipline","work_they_want_more_of","available_work","target_client","price_basis"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["portfolio","creator","rights","credits"],"version":1,"fingerprint":"5d4202961559d36720a82e5c80083d3c006669e19e08e24e6a360e07a09c54c9","license":"SONARA original; repository MIT license"},{"id":"builtin:website-mobile-review","slug":"website-mobile-review","title":"Mobile Experience Review","productArea":"business_builder","productLabel":"Business Builder","category":"website","description":"A review of a site on a phone, ordered by what would actually cost the business a customer.","content":"Act as a mobile usability reviewer. Review {{page_or_site}} for {{business_name}} as it behaves on a phone.\n\nWhat is known:\n- What most visitors arrive to do: {{visitor_goal}}\n- What the page currently contains: {{page_contents}}\n- Anything already known to be wrong: {{known_problems}}\n\nReview for:\n1. **Anything that overflows.** Content wider than the screen, tables that force sideways scrolling, images that break the layout, text cut off at the edge.\n2. **Tap targets.** Anything a finger has to hit that is smaller than about 44 by 44 pixels, or close enough to another control to be pressed by mistake.\n3. **Reading.** Text too small to read without pinching, lines too long, contrast too low in bright light.\n4. **Getting around.** Whether the visitor can reach {{visitor_goal}} from the first screen, and how many taps it takes.\n5. **Forms.** Whether the right keyboard appears for each field, whether anything is retyped that could be remembered, and what happens to what they typed when something fails.\n6. **Weight.** What is being downloaded before the page is usable, and what could be loaded later or not at all.\n\nThen order every finding by what it costs the business -- a visitor who leaves, a form that is abandoned, a call that is not made -- rather than by how easy it is to fix. Say plainly which findings you could not check without seeing the site on a real device.\n\nRules:\n- Do not report a problem you have not been given evidence for. If {{page_contents}} does not say, list it as something to check rather than as a finding.\n- Give the fix, not just the fault.","promptType":"text","variables":["page_or_site","business_name","visitor_goal","page_contents","known_problems"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["website","mobile","usability","accessibility"],"version":1,"fingerprint":"180bb654c4ca98a50fdd3370f90e6876b41dbbb41f5a43f91d978418ac30d3cf","license":"SONARA original; repository MIT license"},{"id":"builtin:business-launch-blueprint","slug":"business-launch-blueprint","title":"Business Launch Blueprint","productArea":"business_builder","productLabel":"Business Builder","category":"launch","description":"Turn a business idea into a practical launch sequence, offer, operations checklist, and first-month measurement plan.","content":"Act as a practical small-business launch strategist. Build an implementation-ready launch blueprint for {{business_name}}, a {{business_type}} serving {{target_customer}} in {{location}}.\n\nUse these constraints:\n- Starting budget: {{starting_budget}}\n- Owner availability: {{owner_availability}}\n- Primary offer: {{primary_offer}}\n- Launch deadline: {{launch_deadline}}\n\nProduce:\n1. A clear value proposition.\n2. A minimum viable offer with scope, price logic, proof points, and fulfillment steps.\n3. A seven-stage launch checklist covering legal setup, payments, customer intake, operations, marketing, support, and measurement.\n4. A realistic first-30-day operating calendar.\n5. The five most important risks, each with prevention and recovery steps.\n6. Weekly metrics that a non-technical owner can track.\n\nDo not invent licenses, approvals, demand, revenue, partnerships, or completed setup. Mark every assumption clearly.","promptType":"text","variables":["business_name","business_type","target_customer","location","starting_budget","owner_availability","primary_offer","launch_deadline"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["business","launch","operations","offer"],"version":1,"fingerprint":"f5562a2483fc4039e8cb4a602dd8e03cfe08b1d9367893a3fe881ccdf5b62077","license":"SONARA original; repository MIT license"},{"id":"builtin:restaurant-profitability-review","slug":"restaurant-profitability-review","title":"Restaurant Profitability Review","productArea":"business_builder","productLabel":"Business Builder","category":"restaurant_operations","description":"Review a restaurant, bar, catering, or food-truck operation without pretending missing numbers are known.","content":"Act as a restaurant operations analyst. Review the following operation:\n\nBusiness type: {{business_type}}\nAverage weekly sales: {{weekly_sales}}\nFood and beverage cost: {{cost_of_goods}}\nWeekly labor cost: {{labor_cost}}\nOccupancy and fixed weekly costs: {{fixed_costs}}\nCurrent menu or service concerns: {{operational_concerns}}\n\nCalculate or explain:\n- Prime cost and prime-cost percentage.\n- Estimated contribution after listed costs.\n- Break-even sales using only the supplied numbers.\n- Three menu, labor, waste, purchasing, or scheduling improvements ranked by expected impact and implementation difficulty.\n- A seven-day owner action plan.\n\nShow formulas. Separate known values, calculated values, and assumptions. Never fabricate missing financial records.","promptType":"text","variables":["business_type","weekly_sales","cost_of_goods","labor_cost","fixed_costs","operational_concerns"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["restaurant","profit","food-cost","labor"],"version":1,"fingerprint":"7c96ddad15485c3a936b5da0998ca70cd10b7f2eca874430c6a7212bcc14ed96","license":"SONARA original; repository MIT license"},{"id":"builtin:employee-onboarding-plan","slug":"employee-onboarding-plan","title":"Employee Onboarding Plan","productArea":"business_builder","productLabel":"Business Builder","category":"staff","description":"Create a role-specific onboarding and training sequence with evidence checkpoints.","content":"Create a structured onboarding plan for a new {{role_name}} at {{business_name}}.\n\nContext:\n- Work environment: {{work_environment}}\n- Shift pattern: {{shift_pattern}}\n- Required responsibilities: {{responsibilities}}\n- Safety or compliance topics: {{safety_topics}}\n- Training duration: {{training_duration}}\n\nInclude a first-day agenda, first-week checklist, role standards, shadowing tasks, supervised practice, manager checkpoints, knowledge checks, and a final readiness decision. Distinguish legal requirements that need local professional verification from internal company procedures.","promptType":"text","variables":["role_name","business_name","work_environment","shift_pattern","responsibilities","safety_topics","training_duration"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["employees","training","onboarding","operations"],"version":1,"fingerprint":"de0612beb182c03b95cf90da16e7c393033bb122c44029b647b6466541a0a616","license":"SONARA original; repository MIT license"},{"id":"builtin:original-song-blueprint","slug":"original-song-blueprint","title":"Original Song Blueprint","productArea":"creator_studio","productLabel":"Creator Studio","category":"music","description":"Build an original repeatable song plan using musical parameters rather than private artist imitation.","content":"Build an original {{genre}} song blueprint at {{bpm}} BPM in {{key_signature}}.\n\nRequired identity:\n- Rhythmic feel: {{rhythmic_feel}}\n- Harmonic identity: {{harmonic_identity}}\n- Drum language: {{drum_language}}\n- Vocal mode: {{vocal_mode}}\n- Emotional theme: {{theme}}\n- Hook concept: {{hook_concept}}\n\nProvide an eight-section arrangement, chord or scale guidance, drum development, bass movement, melodic contour, vocal delivery notes, transition ideas, production checkpoints, and an originality checklist. Do not use living artist names as generation instructions or reproduce identifiable lyrics, melodies, recordings, or private reference material.","promptType":"text","variables":["genre","bpm","key_signature","rhythmic_feel","harmonic_identity","drum_language","vocal_mode","theme","hook_concept"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["music","songwriting","production","originality"],"version":1,"fingerprint":"736790f67494a6ee7f1532410a387ff81d32061210a4d2be94d71b0ea09b5dcd","license":"SONARA original; repository MIT license"},{"id":"builtin:creator-release-command-plan","slug":"creator-release-command-plan","title":"Creator Release Command Plan","productArea":"creator_studio","productLabel":"Creator Studio","category":"release","description":"Coordinate assets, rights, distribution, content, audience communication, and release-day evidence.","content":"Create a release command plan for {{release_title}}, a {{release_type}} scheduled for {{release_date}}.\n\nAvailable assets: {{available_assets}}\nMissing assets: {{missing_assets}}\nDistribution status: {{distribution_status}}\nRights status: {{rights_status}}\nTarget audience: {{target_audience}}\nPrimary channels: {{channels}}\nBudget: {{budget}}\n\nProduce a backward schedule, asset manifest, rights verification gate, channel-specific content plan, release-week runbook, contingency routes, measurement dashboard, and post-release review. Never claim distribution, clearance, playlist placement, press coverage, or sales that have not been verified.","promptType":"text","variables":["release_title","release_type","release_date","available_assets","missing_assets","distribution_status","rights_status","target_audience","channels","budget"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["release","creator","rights","distribution"],"version":1,"fingerprint":"91e7c4b8a69a37e6ee49ec6602993bf7540c1bef1270cef01ac6eab8bad44245","license":"SONARA original; repository MIT license"},{"id":"builtin:video-production-brief","slug":"video-production-brief","title":"Video Production Brief","productArea":"creator_studio","productLabel":"Creator Studio","category":"video","description":"Turn a concept into a shot-conscious production brief with rights and accessibility checks.","content":"Create a production brief for a {{video_type}} titled {{working_title}}.\n\nGoal: {{goal}}\nAudience: {{audience}}\nDuration: {{duration}}\nFormat and destinations: {{formats}}\nVisual direction: {{visual_direction}}\nAvailable equipment and assets: {{available_resources}}\nBudget and deadline: {{budget_deadline}}\n\nInclude the narrative spine, scene list, shot priorities, audio plan, lighting plan, graphics and caption plan, permissions and likeness checks, production schedule, backup plan, edit checklist, export matrix, and quality-control review.","promptType":"text","variables":["video_type","working_title","goal","audience","duration","formats","visual_direction","available_resources","budget_deadline"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["video","production","rights","accessibility"],"version":1,"fingerprint":"775420607bf7cebc0c8c83bbecba6a6778c74f571b9a3417db890fe4eaf6f513","license":"SONARA original; repository MIT license"},{"id":"builtin:consent-safe-growth-campaign","slug":"consent-safe-growth-campaign","title":"Consent-Safe Growth Campaign","productArea":"growth_studio","productLabel":"Growth Studio","category":"campaign","description":"Build a campaign that connects offer, audience, content, follow-up, attribution, and consent.","content":"Design a consent-safe growth campaign for {{business_or_creator}} promoting {{offer}} to {{audience}}.\n\nCampaign window: {{campaign_window}}\nChannels: {{channels}}\nBudget: {{budget}}\nAvailable proof: {{proof}}\nPrimary conversion action: {{conversion_action}}\nConsent and data constraints: {{consent_constraints}}\n\nProduce the campaign hypothesis, audience segments, message angles, channel plan, content matrix, landing-page outline, compliant lead-capture fields, follow-up sequence, attribution plan, experiment design, stop conditions, and weekly review. Do not invent testimonials, scarcity, endorsements, results, audience consent, or platform approval.","promptType":"text","variables":["business_or_creator","offer","audience","campaign_window","channels","budget","proof","conversion_action","consent_constraints"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["growth","campaign","consent","attribution"],"version":1,"fingerprint":"ea3af10f7880bcdacc06381829c76ceab1b48a738a70bd3cf3ff6b8b84fd905d","license":"SONARA original; repository MIT license"},{"id":"builtin:lead-follow-up-sequence","slug":"lead-follow-up-sequence","title":"Lead Follow-Up Sequence","productArea":"growth_studio","productLabel":"Growth Studio","category":"leads","description":"Create respectful follow-up based on lead source, consent state, needs, and timing.","content":"Create a follow-up sequence for a lead named {{lead_name}} who came from {{lead_source}} and expressed interest in {{interest}}.\n\nKnown context: {{known_context}}\nConsent status: {{consent_status}}\nPreferred channel: {{preferred_channel}}\nOffer and next step: {{offer_next_step}}\nFollow-up window: {{follow_up_window}}\n\nWrite a first response, one value-adding follow-up, one objection-handling response, and one respectful close-out message. Keep claims factual, preserve opt-out language, avoid pressure tactics, and do not infer sensitive personal information.","promptType":"text","variables":["lead_name","lead_source","interest","known_context","consent_status","preferred_channel","offer_next_step","follow_up_window"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["leads","follow-up","consent","sales"],"version":1,"fingerprint":"bcacca2219238249eeef41c1aa7024ed62d4187740d8b4bb0d92759f437f42c5","license":"SONARA original; repository MIT license"},{"id":"builtin:offer-angle-experiment","slug":"offer-angle-experiment","title":"Offer Angle Experiment","productArea":"growth_studio","productLabel":"Growth Studio","category":"experiments","description":"Generate testable offer angles without fake claims, dark patterns, or unmeasurable objectives.","content":"Create three distinct, testable offer angles for {{offer_name}}.\n\nAudience: {{audience}}\nVerified customer problem: {{customer_problem}}\nVerified proof: {{verified_proof}}\nPrice or commitment: {{price_commitment}}\nChannel: {{channel}}\nMeasurement window: {{measurement_window}}\n\nFor each angle provide the core promise, supporting proof, headline, short body copy, call to action, objection addressed, success metric, minimum sample requirement, and stop condition. Reject any angle that depends on fabricated urgency, unsupported outcomes, discriminatory targeting, or hidden terms.","promptType":"text","variables":["offer_name","audience","customer_problem","verified_proof","price_commitment","channel","measurement_window"],"outputFormat":"markdown","modelCompatibility":["provider_neutral"],"tags":["offers","experiments","copy","measurement"],"version":1,"fingerprint":"250be3fb1bb526e61566e9193c3c6d7eb6728d983f6d38749f28bc5c4497a51c","license":"SONARA original; repository MIT license"}]}