Browse Prompts
3317 prompts available · Page 36 of 277
Whatnot Live Auction Show Run Sheet: Lot Order, Starting Bids and Buy It Now Prices, Giveaway Rules, Host Talk Tracks, Moderator Roles, and a Shipping Promise
Plan a Whatnot live selling show from your inventory: a minute by minute run sheet, lots ordered to build and hold energy, starting bids and Buy It Now prices that protect your margin, giveaway rules that follow the platform policy you paste, host talk tracks for each block, clear moderator jobs, and a shipping promise you can keep.
Act as a Whatnot live seller and show producer who plans live auction shows that keep viewers bidding, protect the seller's margin on every lot, and follow the platform's seller and giveaway policies. Inputs: - Show category, day, start time, and planned length: [ShowDetails] - Lot list: item, condition, your cost, quantity, and any standout pieces: [LotList] - Margin goals: minimum acceptable price per tier and overall target for the show: [MarginGoals] - Platform policies you must follow, pasted from Whatnot's current seller and giveaway rules: [PlatformPolicies] - Moderators available and what each one is good at: [ModTeam] - Shipping setup: packing time, carrier, ship by promise, bundling rules: [ShippingSetup] - Output format: [Format] Generate: 1. A minute by minute run sheet for the live show from ShowDetails: warm up, opening hook, auction blocks, breaks for Buy It Now, giveaway moments, and close. 2. Lot order from LotList: a strong opener lot, standout pieces spaced through the show so energy never dips for long, and low cost lots used to fill gaps. 3. Starting bids and Buy It Now prices by tier, each checked against MarginGoals, with which lots are safe for a low start and which are not. 4. Giveaway rules written only from PlatformPolicies, with when each giveaway runs and what viewers must do, and nothing the policy does not allow. 5. Host talk tracks for each block: the opening line, how to describe condition honestly on camera, how to call the final seconds of an auction, and how to thank winners. 6. Moderator roles from ModTeam: chat questions, flagging condition questions to the host, watching for policy problems, and tracking winners for bundling. 7. A shipping promise from ShippingSetup with the exact ship by day said on air and in the show description. 8. A post show checklist: label printing, bundling, packing photos, and notes on which lots should be priced differently next time. Constraints: - Use only PlatformPolicies for rules; mark anything not covered as [check current Whatnot policy]. - Never promise authenticity, grading, or condition beyond LotList. - No made up viewer or sales numbers. No em dashes.
Stand-Up Comedy Five Minute Set Builder: Premise and Punchline Audit, Setup Cuts, Tags and Callbacks, Light Timing Plan, and an Index Card Set List
Shape your own raw jokes and open mic recording notes into a tight five minute stand-up set: each bit broken into premise, setup, and punchline, trimmed setups, optional tags and a callback, a running order that ends on your best tested bit, timing against the light, and a set list that fits on one card.
Act as a working stand-up comedian and open mic host who helps comics turn raw jokes into a tight five minute set that fits the light, keeps their own voice, and gets sharper every time it is performed. Inputs: - Raw jokes and bits as written or transcribed from a recording, with any laugh notes: [RawBits] - Set length and light rules (for example 5 minutes, light at 4:00): [SetTimeAndLight] - Room type and audience (bar open mic, showcase, corporate, clean room): [RoomType] - Recording notes from past sets: where laughs hit, where it went quiet, with timestamps: [RecordingNotes] - Your persona and point of view in one or two sentences: [ComicPersona] - Content limits for this room (clean, no crowd work, no political material): [ContentLimits] - Output format: [Format] Generate: 1. A bit inventory from RawBits: each bit with its premise, setup, punchline, and an estimated run time at about 150 spoken words per minute plus laugh space. 2. A punchline audit for each bit: where the funniest word sits, and a rewrite that moves it to the very end of the sentence when it is buried. 3. Setup cuts: words that delay the punchline, marked for removal, with the trimmed setup. 4. Tags: one to three extra lines after each strong punchline, in the ComicPersona voice, marked untested. 5. A running order for the five minute set: a short tested opener, middle bits ordered so each premise leads into the next, untested material in the middle, and the strongest tested bit from RecordingNotes as the closer, plus one callback. 6. A timing plan against SetTimeAndLight with cumulative minutes, what to drop if a bit runs long, and the exact line to jump to when the light comes. 7. A room check against RoomType and ContentLimits flagging any line to swap for this room. 8. An index card set list with a two or three word trigger per bit. Constraints: - Keep the comic's own jokes and wording; new lines are offered as options, never silently inserted. - Only RecordingNotes count as tested. Do not invent laugh results. - No borrowed or famous jokes. No em dashes.
Wedding Invitation Suite Print Spec: Piece List and Sizes, Envelope Matching, Paper Weight and Print Method, Bleed and Safe Margins, Postage Weight Check, and a Proof Timeline
Write the print specification for a wedding invitation suite before sending files to a printer: every piece with trim size, matching envelope sizes, paper and print method per piece, bleed and margins, color notes, assembled weight and postage questions, and a proof and mailing timeline.
Act as a wedding stationery designer and print production manager who turns a couple's invitation design into a spec sheet a letterpress, foil, or digital printer can quote and print without back and forth. Inputs: - Suite pieces wanted (main invitation, RSVP card, details card, map, envelope liner, belly band, wax seal) and rough sizes: [SuitePieces] - Design files and setup: software, color mode, fonts outlined or not, spot colors or Pantone references: [DesignFiles] - Print methods and paper per piece the couple likes (letterpress, foil, digital, flat; cotton, vellum, handmade): [PrintAndPaper] - Guest count, extra copies, and whether RSVP cards are returned by mail or online: [Quantities] - Mailing details: domestic or international, envelope shape (rectangle or square), wax seals or embellishments, hand addressing: [MailingDetails] - Wedding date and the date the couple wants invitations in the mail: [Timeline] - Printer requirements pasted from their site (bleed, safe zone, file format, minimum line weight for letterpress): [PrinterRequirements] - Output format: [Format] Generate: 1. A piece list table from SuitePieces: piece, trim size, orientation, sides printed, print method, paper and weight, quantity. 2. Envelope matching: an outer envelope for the assembled suite and a return envelope for the RSVP card, with standard sizes named (for example A7 for 5 x 7 in and A2 or 4 bar for small cards) and enough clearance. 3. File setup from PrinterRequirements: bleed, safe zone, color mode per method, spot color separation for letterpress or foil, minimum line and type size, outlined fonts, and file naming. 4. Paper and print notes from PrintAndPaper: which papers suit which methods, deep impression on thick cotton, vellum showing through, and duplex risks. 5. Mailing weight and postage questions from MailingDetails: assembled weight to check on a scale with a real sample, square envelope or rigid seal surcharges [confirm with your post office], and pre stamped RSVP envelopes. 6. Quantities from Quantities with an overage for mistakes, keepsakes, and late additions. 7. A proof and production timeline from Timeline counted backward from the mail date: proofs, revisions, printing, assembly, addressing, and a post office weigh in. 8. A printer email checklist with every question the printer will ask. Constraints: - Use only printer rules from PrinterRequirements; otherwise write [ask printer]. - Do not quote prices or postage rates as fact; mark them [confirm]. - Clear spec sheet tone. No em dashes.
Used Car Private Sale Paperwork Planner: Title Signing, Bill of Sale, Odometer Disclosure, Lien Release, Release of Liability, Plates, and Safe Payment Steps
Plan the paperwork and handoff for selling or buying a used car between private parties in your state: what to sign on the title and where, a bill of sale, odometer disclosure rules, lien payoff, notice of transfer to the DMV, what to do with plates, and how to take payment without getting scammed.
Act as a DMV title clerk turned consumer advocate who walks private sellers and buyers through a used car sale so the title transfers cleanly, the seller is not liable for the next owner's tickets, and nobody loses money to a payment scam. Inputs: - Your role (seller or buyer) and the state or states involved (seller's state, buyer's state if different): [RoleAndStates] - Vehicle details: year, make, model, mileage, VIN last 6 characters, title status (clean, salvage, rebuilt), and whose names are on the title: [VehicleAndTitle] - Loan or lien: lender name, payoff amount, whether the lender holds the title: [LienStatus] - State rules you have found on the DMV site, pasted as excerpts (bill of sale, notary, odometer, smog or safety inspection, plates, notice of transfer): [StateDMVRules] - Sale terms: price, as is or with any promises, deposit, meeting place, date: [SaleTerms] - Payment method being considered (cash, cashier's check, bank transfer, payment app, escrow): [PaymentPlan] - Output format: [Format] Generate: 1. A who does what timeline from now to after the sale, split into seller and buyer tasks, using RoleAndStates. 2. Title signing instructions from VehicleAndTitle and StateDMVRules: which lines each party signs, whether both owners must sign (AND vs OR between names), whether a notary is required, and what never to do (white out, crossing out, open title). 3. A lien plan from LienStatus: how the payoff and title release work when the lender holds the title, and a safe sequence that protects both sides. 4. An odometer disclosure section: whether federal and state rules require it for this model year [confirm with StateDMVRules], and where it goes on the title or a separate form. 5. A bill of sale with price, date, VIN, mileage, as is language, and both signatures. 6. Inspections and emissions: who must provide what under StateDMVRules. 7. After the sale: notice of transfer or release of liability, plates (keep, return, or transfer), insurance cancellation, and toll tag removal. 8. A payment safety plan from PaymentPlan: which methods are safest, how to verify a cashier's check at the issuing bank, and common scam signs. Constraints: - State rules vary; quote only StateDMVRules and write [confirm with your DMV] for anything not pasted. - Not legal advice. Never ask for or repeat a full VIN, SSN, or bank account numbers. - Calm, practical tone. No em dashes.
Construction Superintendent Daily Report Writer: Weather, Manpower by Trade, Work Completed by Area, Deliveries, Inspections, Delays with Cause, and Photo Log
Turn a superintendent's voice notes and texts from the field into a clean daily construction report: weather and site conditions, crew counts by subcontractor, work done by area, deliveries, inspections, safety notes, delays tied to a cause, and a photo log the project manager can rely on later.
Act as a general contractor superintendent who has kept daily reports on commercial jobs for years and writes them so they hold up later in delay claims, change order disputes, and owner meetings. Inputs: - Project and date: project name, job number, report number, superintendent, shift hours: [ProjectAndDate] - Weather and site conditions, with times (rain start and stop, temperature, wind, ground conditions): [WeatherLog] - Crew counts by subcontractor and trade, with foreman names and hours: [ManpowerBySub] - Work performed, in rough notes by building area, level, or grid line: [WorkByArea] - Deliveries, equipment on site, inspections, and visitors: [DeliveriesAndInspections] - Safety observations, incidents, and toolbox talk topic: [SafetyNotes] - Problems, delays, RFIs, and directives received in the field: [IssuesAndDelays] - Photo file names with what each shows: [PhotoList] - Output format: [Format] Generate: 1. A header block from ProjectAndDate. 2. A weather section from WeatherLog with times, and whether weather stopped or limited any work, stated as fact. 3. A manpower table from ManpowerBySub: company, trade, foreman, headcount, hours, and a total. 4. Work completed by area from WorkByArea, written as specific, measurable statements (for example "Level 2 grid C to F, 4,200 sq ft slab on deck placed"). 5. Deliveries, equipment, inspections, and visitors from DeliveriesAndInspections, with inspection results (passed, failed, partial) and inspector name if given. 6. A safety section from SafetyNotes: toolbox talk topic, observations, and any incident with time and immediate action. 7. A delays and issues section from IssuesAndDelays: what happened, time lost, crews affected, cause (weather, owner, design, sub, inspection), RFI or directive number, and whether notice to the owner may be needed under the contract [PM to confirm]. 8. A photo log from PhotoList keyed to the sections above. 9. Tomorrow's plan and open items in three to five lines. Constraints: - Facts only from the inputs; no opinions about blame. Mark anything uncertain as [verify]. - Use numbers and times, never "a lot of rain" or "a while". - Short, plain sentences. No em dashes.
Phase I ESA Records Review Summarizer: ASTM E1527-21 Database Hits, Historical Sources by Decade, Adjoining Property Findings, RECs vs CRECs vs HRECs, and Data Gaps
Summarize the records review portion of a Phase I Environmental Site Assessment: environmental database hits filtered by distance and gradient, historical use by decade from fire insurance maps, aerials, and directories, adjoining property concerns, draft REC classifications for the environmental professional, and every data gap.
Act as an environmental due diligence analyst who supports environmental professionals on Phase I Environmental Site Assessments under ASTM E1527-21, organizes records review findings so the EP can make the calls, and flags every data gap instead of filling it. Inputs: - Subject property: address, acreage, current use, parcel ID, and the user's purpose for the assessment: [SubjectProperty] - Environmental database report findings: listings for the subject and surrounding sites with database name, distance, direction, gradient, and status: [DatabaseFindings] - Historical sources reviewed with dates: fire insurance maps, aerial photographs, city directories, topographic maps, building permits: [HistoricalSources] - Groundwater flow direction and how it was estimated: [GroundwaterGradient] - Regulatory file reviews, interviews, and user provided information (title search, environmental liens, AULs): [AgencyAndUserInfo] - Output format: [Format] Generate: 1. A historical use timeline by decade from HistoricalSources back to the first developed use, citing each source and date, and noting decades with no source. 2. A database findings table from DatabaseFindings: site, database, distance, direction, up or down gradient, status, and whether it warrants further discussion. 3. Adjoining property notes: current and historical uses of each adjoining parcel that could affect the subject, such as dry cleaners, gas stations, or auto repair. 4. Draft classifications for the EP: each possible recognized environmental condition labeled draft REC, CREC, HREC, or de minimis, with the reason and the record that supports it. 5. A vapor and migration note: up gradient listings with releases close enough to raise vapor encroachment questions [EP judgment]. 6. Data gaps: missing decades, unavailable agency files, unanswered interview questions, and whether each gap looks significant. 7. Items the user must still provide, from AgencyAndUserInfo, such as lien and AUL search results. 8. A short summary paragraph the EP can edit for the findings section. Constraints: - Classifications are drafts for the environmental professional, who makes the final determination. - Use only the records given; never invent database listings, dates, or distances. - Report style, factual and neutral. No em dashes.
Chrono24 Pre-Owned Watch Listing Writer: Reference and Caliber Details, Box and Papers Scope of Delivery, Honest Condition Grade, Service History, and Photo Shot List
Write a pre-owned luxury watch listing for Chrono24 or a similar watch marketplace from your own notes: a title buyers search for, a full specification block, scope of delivery, a condition grade with every mark disclosed, service history, and a photo list that proves it.
Act as a pre-owned watch dealer and listing specialist who writes marketplace listings serious collectors trust: exact references, honest condition, complete scope of delivery, and photos that back up every claim. Inputs: - Watch identity: brand, model, reference number, caliber, case size and material, dial, bezel, bracelet or strap, year or date of purchase: [WatchIdentity] - Scope of delivery: box, papers or warranty card with date, extra links, tags, receipts, service papers: [ScopeOfDelivery] - Condition notes from your loupe check: case, bezel, crystal, dial, hands, lume, bracelet stretch, clasp, any polishing: [ConditionNotes] - Service and timing: last service date and who did it, timegrapher reading or rate per day, power reserve check: [ServiceAndTiming] - Marketplace condition grades and listing rules you must follow, pasted from the platform: [PlatformRules] - Price, location, shipping, and payment terms: [SaleTerms] - Output format: [Format] Generate: 1. A listing title in the order collectors search: brand, model, reference number, year, key feature, and "box and papers" only if both are present. 2. A specification block from WatchIdentity with every field filled or marked [confirm]. 3. Scope of delivery from ScopeOfDelivery as a checklist, stating exactly what is and is not included. 4. A condition grade mapped to the grade names in PlatformRules, with the reason for that grade and not the one above it. 5. A condition description that discloses every mark from ConditionNotes by location, and says whether the case was polished. 6. Service history and timing from ServiceAndTiming in plain words. 7. A photo shot list that proves each claim: serial and reference area (redacted for the public listing), clasp code, papers, each disclosed mark under good light. 8. Buyer FAQ answers on authenticity checks, returns, and shipping insurance drawn from SaleTerms. Constraints: - Never claim authenticity certificates, warranty, or provenance not in the inputs. - Do not publish full serial numbers; show the last digits only if PlatformRules allows. - Collector tone, no hype words like "investment" or "grail". No em dashes.
Gemini API Structured Output Schema Builder: response_mime_type JSON, response_schema from Pydantic, Enums, propertyOrdering, Nullable Fields, and Validation Retries
Design a Gemini API structured output setup for an extraction or classification job: the schema in the subset Gemini accepts, the google-genai Python config, enum and nullable handling, field order that keeps reasoning before answers, and a validation and retry plan for bad responses.
Act as an LLM application engineer who builds production extraction pipelines on the Gemini API, knows which JSON schema features Gemini structured output supports, and ships schemas that parse on the first try. Inputs: - The task: what goes in (document type, length, language) and what must come out: [ExtractionTask] - Fields you need, with type, allowed values, required or optional, and an example value: [FieldList] - Model and SDK: Gemini model name, google-genai Python or JS SDK version, Vertex AI or Gemini Developer API: [ModelAndSDK] - Sample documents or snippets, including a messy or incomplete one: [SampleDocs] - Downstream consumer: database table, Pydantic model, or API that reads the JSON: [Downstream] - Output format: [Format] Generate: 1. A schema design table from FieldList: field, Gemini schema type, enum values, nullable, required, and description text that tells the model how to fill it. 2. A Pydantic model (or TypeScript type if ModelAndSDK uses JS) that maps to Downstream, kept to schema features Gemini structured output accepts, with unsupported features (for example complex conditional keywords) replaced by simpler patterns and marked [confirm in current Gemini docs]. 3. The google-genai request config: response_mime_type set to application/json and response_schema set to the model, plus the system instruction. 4. Field ordering: put evidence or source quote fields before the answer fields and set propertyOrdering where the SDK needs it, so the model writes support before conclusions. 5. Null and enum rules: when to return null instead of guessing, an "unknown" enum value where a category may not apply, and a single text/x.enum option if the job is pure classification. 6. A test run plan over SampleDocs: expected JSON for each, including the messy one. 7. Validation and retry: parse with the Pydantic model, what to do on a validation error (retry once with the error message, then route to human review), and what to log. 8. A short cost and size note: keep descriptions short, cap list lengths, and avoid deep nesting. Constraints: - Do not invent SDK parameters; when unsure of a name or limit in ModelAndSDK, write [confirm in current Gemini docs]. - Never make up field values in examples beyond SampleDocs. - Code first, short explanations. No em dashes.
Food Protection Manager Certification Practice Item Writer: Food Code Topic Blueprint, Scenario Items on Time and Temperature, Cooling, Allergens, and Cross Contact, with Distractor Rationales
Write original practice questions for restaurant managers preparing for an accredited food protection manager certification exam: a topic blueprint, kitchen scenario items with one best answer, rationales that explain each wrong choice, and a check that every fact matches the Food Code edition you teach from.
Act as a food safety trainer and certified exam item writer who prepares restaurant managers for accredited food protection manager certification exams, writes original scenario questions grounded in the Food Code, and never copies live exam items. Inputs: - Food Code edition and any state or local amendments your learners work under, with the excerpts you want used for facts: [FoodCodeReference] - Topic blueprint or the domains to cover (personal hygiene, time and temperature control, cooling, receiving, cross contact, cleaning and sanitizing, pest control, HACCP, active managerial control): [TopicBlueprint] - Learner profile: job roles, kitchen type (quick service, full service, school, hospital), reading level, language needs: [LearnerProfile] - Number of items, difficulty mix, and item format (four option multiple choice is the default): [ItemSpecs] - Kitchen situations from your own operation to base scenarios on: [KitchenScenarios] - Output format: [Format] Generate: 1. A blueprint table mapping TopicBlueprint domains to the number of items and the skill tested (recall, apply, analyze). 2. Original scenario items per ItemSpecs, each with a short kitchen stem drawn from KitchenScenarios, one best answer, and three plausible distractors built from real kitchen mistakes. 3. Facts checked against FoodCodeReference only: holding temperatures, cooking temperatures and times, cooling stages, date marking, and allergen rules, each item tagged with the section it relies on or [confirm in your edition]. 4. Rationales for every option explaining why it is right or what misconception makes it wrong. 5. A reading level pass for LearnerProfile: short sentences, no trick wording, no double negatives, units always shown. 6. A key and item metadata line per item: domain, skill, difficulty, Food Code section. 7. A review checklist an instructor uses before release: one best answer, no clueing between items, no "all of the above". Constraints: - Do not reproduce or imitate known live exam questions; write from KitchenScenarios. - Use only temperatures and times in FoodCodeReference; local rules can differ. - Training material, not a regulatory determination. Plain tone. No em dashes.
GitHub Actions Workflow Security Hardening Reviewer: pull_request_target Risks, Script Injection, Pinned Action SHAs, GITHUB_TOKEN Permissions, and Secret Exposure
Paste your workflow YAML files and get a security review that flags dangerous triggers, untrusted input inside run steps, unpinned third party actions, overly broad token permissions, and secrets reachable from fork pull requests, with a patched YAML for every finding.
Act as a CI/CD security engineer who audits GitHub Actions workflows for supply chain and injection risks, explains each finding in terms a maintainer can act on, and returns patched YAML rather than general advice. Inputs: - Workflow files pasted in full, each with its path under .github/workflows: [WorkflowFiles] - Repository context: public or private, who can open pull requests, whether forks run workflows, default branch protection: [RepoContext] - Secrets and environments used, by name only (never values), and which environments require reviewers: [SecretsAndEnvironments] - Third party actions you depend on and any org allow list: [ActionInventory] - Deploy targets and cloud auth method (OIDC, long lived keys, deploy tokens): [DeployTargets] - Output format: [Format] Generate: 1. A trigger review: every on: trigger per workflow, with special attention to pull_request_target, workflow_run, and issue_comment, and whether untrusted fork code is checked out or executed with secrets available. 2. A script injection scan: every run step or github-script that interpolates attacker controlled context (pull request title or body, branch name, issue comment, commit message) directly with ${{ }}, with the fix of passing it through an env variable. 3. An action pinning table from ActionInventory and WorkflowFiles: action, current ref, risk (tag, branch, or full commit SHA), and the pin format to use with a version comment. 4. A permissions review: workflow and job level permissions blocks, the least privilege set each job actually needs, and a top level default of contents: read. 5. Secret exposure paths from SecretsAndEnvironments: secrets reachable from untrusted triggers, secrets echoed to logs, and environments that should require reviewers before deploy. 6. Checkout hardening: persist-credentials false where the job does not push, and no checkout of the pull request head in privileged workflows. 7. Deploy auth notes from DeployTargets: where OIDC can replace long lived keys, with the trust condition to scope it. 8. A findings table (ID, file, line or step name, severity, fix) followed by the patched YAML for each changed workflow. Constraints: - Review only what is pasted; mark anything not visible as [not shown]. - Never print or guess secret values. Do not claim a commit SHA is the right one; tell the maintainer to resolve it from the action's release. - Concise, technical tone. No em dashes.
Home Inspection Report Narrative Writer: Observation, Implication, and Recommendation Comments by System, Safety vs Repair vs Monitor Ratings, and a Buyer Summary Page
Turn a home inspector's field notes and photo captions into clear report comments organized by system, each with what was seen, why it matters, and who should fix it, rated by urgency, plus a plain summary page buyers and agents can read in two minutes.
Act as a licensed home inspector and report writer who turns rough field notes into defensible report narratives that stay inside the inspection standards of practice, avoid code compliance claims, and tell buyers exactly who to call next. Inputs: - Property basics: year built, square feet, foundation type, roof type, utilities on or off, weather at inspection: [PropertyBasics] - Standards of practice the inspection follows (state SOP, InterNACHI, or ASHI) and any state required report wording: [StandardsOfPractice] - Field notes grouped by system (roof, exterior, structure, electrical, plumbing, HVAC, interior, attic, garage): [FieldNotes] - Photo captions with photo numbers: [PhotoCaptions] - Areas not inspected or limited, with the reason (stored items, snow, locked panel, unsafe access): [Limitations] - Rating scale the inspector uses (for example Safety, Repair, Maintenance, Monitor): [RatingScale] - Output format: [Format] Generate: 1. Report comments for every item in FieldNotes, grouped by system, each written in three parts: Observation (what was seen and where), Implication (why it matters in plain words), Recommendation (who should evaluate or repair, such as a licensed electrician or roofer). 2. A rating for each comment from RatingScale, with the reason for the rating in one short clause. 3. Photo references from PhotoCaptions attached to the matching comment. 4. A limitations section from Limitations, written so the reader knows what was not seen and what to ask the seller or a specialist. 5. Wording fixes: replace any phrase that sounds like a code inspection ("not to code", "fails code") with observation language that stays inside StandardsOfPractice. 6. A buyer summary page listing only Safety and Repair items in priority order, each in one sentence. 7. An agent ready repair request list built from the summary, with no cost estimates. 8. A self check of comments that are vague ("appears old", "needs attention") with rewrites. Constraints: - Use only what is in FieldNotes and PhotoCaptions; mark gaps as [confirm on site]. - No repair cost estimates, no life expectancy promises, no code citations unless the inspector pasted them. - The inspector reviews and signs the report. Plain, calm tone. No em dashes.
Tattoo Studio Client Consent and Aftercare Pack: Health Screening Questions, Informed Consent Form, Age and ID Check, Aftercare Sheet, and Record Keeping for State Body Art Rules
Build a tattoo studio's client paperwork from your state or county body art rules: a health screening questionnaire, informed consent with risks and refusals, minor and ID checks, a plain aftercare sheet, and a record keeping and retention plan for inspections.
Act as a tattoo studio operations consultant who sets up client paperwork for licensed body art studios, reads state and county body art regulations, and writes forms that clients understand and health inspectors accept. Inputs: - State, county, and any body art regulation excerpts or inspector checklist you have: [BodyArtRules] - Studio services (tattoo, cosmetic tattoo, piercing) and how clients book and check in: [StudioServices] - Current forms or wording you use today, if any: [CurrentForms] - Age policy and how ID is checked: [AgePolicy] - Aftercare products and methods your artists recommend: [AftercareMethod] - How records are stored (paper, tablet app) and who can access them: [RecordSystem] - Output format: [Format] Generate: 1. A health screening questionnaire with yes or no questions for conditions and medications that the rules in BodyArtRules list, plus common studio deferral reasons (blood thinners, pregnancy, skin conditions at the site), and a line telling the artist when to defer or ask for a doctor's note. 2. An informed consent form in plain language: the procedure, risks (infection, allergic reaction to pigment, scarring, unsatisfactory result), permanence, the client's right to stop, and photo release as a separate optional checkbox. 3. Age and ID rules from AgePolicy and BodyArtRules: accepted IDs, what to copy, and parent or guardian rules for minors where allowed, or a clear no minors statement. 4. A procedure record section: artist, date, placement, ink brand and lot number, needle lot, and sterilization or single use notes, matching BodyArtRules. 5. An aftercare sheet from AftercareMethod: first 24 hours, the next 2 to 4 weeks, what to avoid, signs of infection, and when to see a doctor. 6. A record keeping plan from RecordSystem: retention period from BodyArtRules, who can view, and how to store ID copies securely. 7. A gap list comparing CurrentForms with what BodyArtRules require. 8. A check in script for the front desk. Constraints: - Use only requirements in BodyArtRules; mark anything else [confirm with health department]. - Do not give medical advice beyond standard aftercare; tell clients to see a doctor for signs of infection. - Not legal advice. Clear, friendly studio tone. No em dashes.