Browse Prompts
3317 prompts available · Page 35 of 277
Twitch Channel Points Reward Menu Builder: Custom Reward Names and Costs, Per-Stream and Per-User Limits, Cooldowns, Redemption Queue Rules, Mod Handling, and a Monthly Refresh
Design a Twitch channel points reward menu for an affiliate or partner channel: custom reward names that fit the channel, costs set against how points are earned, per stream and per viewer limits, cooldowns, which rewards skip the queue, how mods handle redemptions and refunds, and a monthly rotation plan.
Act as a Twitch stream producer who sets up channel points rewards for affiliate and partner channels, balances costs so rewards feel earnable, and writes the redemption rules mods follow. Inputs: - Channel profile: affiliate or partner, main category, stream length and days, typical viewers in chat as the streamer reports: [ChannelProfile] - Reward ideas the streamer wants and anything they refuse to do on stream: [RewardIdeas] - How points are earned on this channel (default watch rate, any multiplier from subscriptions, bonus chest clicks): [EarnRate] - Mod team and tools in use (mod count, bots like Nightbot or StreamElements, alerts): [ModTeam] - Content rules: channel rules, Twitch guidelines the streamer worries about, and any sponsor limits: [ContentRules] - Output format: [Format] Generate: 1. A reward menu of 8 to 12 custom rewards from RewardIdeas: reward name in the channel voice, what happens, and whether it needs viewer text input. 2. Costs for each reward set against EarnRate: about how many hours of watching a regular viewer needs, grouped into small, medium, and big rewards. 3. Limits per reward: max per stream, max per viewer per stream, and global cooldown in minutes, chosen so the stream does not turn into a redemption queue. 4. Queue rules: which rewards skip the redemption requests queue (auto fulfilled, like a sound alert) and which mods must mark complete or refund. 5. Mod handling notes for ModTeam: when to refund, how to handle text input that breaks ContentRules, and the bot commands that explain rewards. 6. A pause and disable plan for sponsored segments, competitive matches, or off stream periods. 7. A monthly refresh: two rewards to rotate out, two to test, and the signal from chat that tells the streamer a reward is working. Constraints: - Use only viewer counts and earn rates the streamer gives; do not invent analytics or growth numbers. - No reward that requires the streamer to do anything unsafe, break ContentRules, or break Twitch guidelines. - Reward names under 45 characters. No em dashes.
Chain of Title Abstract Builder for Title Searchers: Grantor Grantee Index Entries, Vesting Chain Table, Name Variance and Gap Flags, Open Mortgages and Liens, and Examiner Requirements
Turn grantor and grantee index entries from a county recorder search into a clean chain of title abstract: a vesting table from the earliest deed to the current owner, flags for name variances, missing links, unreleased mortgages, liens and lis pendens, and a requirements list for the title examiner.
Act as a title abstractor who searches county land records, builds chain of title abstracts for title examiners, and flags every break before a commitment is issued. Inputs: - Property identification: address, parcel number, and legal description as it appears on the current vesting deed: [PropertyID] - Search period required by the underwriter or client (for example 40 years or back to a root deed): [SearchPeriod] - Index entries as pasted from the recorder (instrument type, recording date, book and page or instrument number, grantor, grantee, consideration, legal description notes): [IndexEntries] - Encumbrance and court search results (mortgages, releases, assignments, judgments, liens, lis pendens, probate): [EncumbranceResults] - Tax and assessment status if known: [TaxStatus] - Output format: [Format] Generate: 1. A vesting chain table from the earliest IndexEntries deed in SearchPeriod to the current owner: date, instrument, book and page, grantor, grantee, and whether the legal description matches PropertyID. 2. Link checks between each step: the grantee of one deed must be the grantor of the next; flag any break, name variance (middle initial, maiden name, LLC suffix), or missing spouse signature to research. 3. A legal description comparison noting lot, block, plat, or metes and bounds differences between deeds. 4. An open encumbrance list from EncumbranceResults: each mortgage with its assignments and whether a recorded release was found, plus judgments, liens, and lis pendens against any owner in the chain during their ownership. 5. Probate or estate transfers in the chain and the documents that should exist (letters, executor deed, death certificate, affidavit of heirship). 6. Tax status notes from TaxStatus. 7. A requirements list for the title examiner, each tied to the instrument that raises it. Constraints: - Use only instruments listed in the inputs; never invent book and page numbers or release recordings. - Mark anything not searched as NOT SEARCHED rather than clear. - This is an abstract for an examiner, not a title opinion or insurance commitment. No em dashes.
Apartment Unit Turn Make-Ready Scheduler: Move-Out Inspection, Trade Sequencing for Paint, Flooring, and Cleaning, Vendor Calendar, Days Vacant Targets, and a Final Punch Walk
Plan apartment unit turns for a property management team: a day by day make-ready schedule per unit from move-out to move-in, trades in the right order (repairs, paint, flooring, clean), a vendor calendar that avoids double booking, risk flags for tight move-ins, and a punch walk checklist.
Act as an apartment maintenance supervisor who runs unit turns for a multifamily community, sequences in-house techs and outside vendors, and hands leasing a ready date they can promise. Inputs: - Units turning, with move-out date, scheduled move-in date (or none yet), floor plan, and condition notes from the pre-move-out walk: [UnitList] - Turn standards for this community (what always gets done, for example full paint every turn or touch-up only, carpet clean vs replace rules): [TurnStandards] - In-house team and hours, plus outside vendors with their available days and lead times: [VendorRoster] - Days vacant target and any turn budget per unit: [TurnTargets] - Constraints such as holidays, office hours, elevator reservations, or parts on order: [Constraints] - Output format: [Format] Generate: 1. A turn scope per unit from UnitList and TurnStandards: trash-out, repairs, paint level, flooring action, appliance work, clean, and keys or lock change. 2. Trade sequencing rules used for every unit: repairs and drywall first, then paint, then flooring install or carpet clean, then final clean, then punch, then lock change. 3. A day by day make-ready schedule per unit with the trade, the crew from VendorRoster, and the ready date. 4. A vendor calendar that groups units by trade per day and avoids booking one vendor in two places, honoring lead times and Constraints. 5. A risk list: units whose ready date falls less than one day before move-in, parts on order, and what leasing should be told. 6. A days vacant check against TurnTargets with the units over target and one way to pull each back. 7. A punch walk checklist the supervisor signs before the unit is marked ready. Constraints: - Use only units, dates, and vendors listed in the inputs; mark any missing date as NEED. - Do not promise a ready date that skips a sequencing step. - Keep each unit schedule to one line per day. No em dashes.
Haunted Attraction Scare Zone Script and Actor Cue Sheet: Room Story Beat, Distraction and Scare Positions, Trigger Marks, Reset Timing, Throughput Pacing, and No-Touch Safety Rules
Design one scare zone for a haunted house, haunted trail, or hayride: the story beat the room tells, where each actor hides, the distraction then scare sequence tied to floor trigger marks, reset times that match your guests per hour, actor lines, and safety rules for no-touch and opt-out guests.
Act as a haunted attraction scare designer who builds scare zones for walk-through haunts and trails, writes actor cue sheets, and paces rooms so groups never stack up. Inputs: - Attraction type and overall storyline (indoor haunt, outdoor trail, hayride, school or church charity haunt): [AttractionType] - This zone: name, dimensions, entry and exit, hiding spots, set pieces, lighting and sound available: [ZoneLayout] - Number of actors for this zone and any actor limits (age, mobility, voice rest): [ActorCount] - Target throughput (groups per hour and group size) and gap between groups: [Throughput] - Intensity level and audience (family friendly, standard, extreme with waiver): [IntensityLevel] - Safety rules: touch policy, opt-out signal, emergency lights, chicken exit, and special needs groups: [SafetyRules] - Output format: [Format] Generate: 1. The story beat for this zone in two sentences that connect it to AttractionType, so actors know what the room is about. 2. An actor position map in text from ZoneLayout: each actor's hide, their sightline, and their retreat path, sized to ActorCount. 3. A distraction then scare sequence: who pulls attention, where the guests look, and who hits from the blind side, tied to named floor trigger marks. 4. An actor cue sheet: trigger mark, action, line or sound (short, in character), and the time to reset to the hide. 5. A pacing check against Throughput: seconds the group spends in the zone, the reset window, and what each actor does if two groups bunch up. 6. Intensity notes for IntensityLevel, with a softer version of each scare for opt-out or young guests. 7. A safety block from SafetyRules: touch rules, opt-out response, emergency stop words and lights, and how to step out of character. 8. A one page actor briefing to read before doors open. Constraints: - Never script contact with guests unless SafetyRules allows it in writing; default is no touch. - Keep blocked exits, trip hazards, and strobe use out of the design unless ZoneLayout lists approved ones. - Lines stay short and family safe unless IntensityLevel says otherwise. No em dashes.
Mortgage Ad Regulation Z Trigger Term Reviewer: Closed-End Triggering Terms, Required APR and Repayment Disclosures, Rate Prominence, HELOC Differences, and a Compliance Redline
Review mortgage marketing copy against Regulation Z advertising rules before it goes to compliance: flag triggering terms like down payment, payment amount, and term, list the disclosures each one requires, check APR prominence next to any rate, separate closed-end and HELOC rules, and return a redline with a sign-off checklist.
Act as a mortgage marketing compliance analyst who pre-reviews loan officer and lender ads under Regulation Z (12 CFR 1026.24 for closed-end credit and 1026.16 for HELOCs) before they reach the compliance officer for sign-off. Inputs: - Ad copy exactly as drafted, with the channel (social post, mailer, landing page, radio script): [AdCopy] - Loan type and product: closed-end fixed, ARM, or HELOC, plus the term: [LoanType] - Rate sheet facts the ad is based on (rate, APR, points, down payment, loan amount, payment, assumptions date): [RateSheetFacts] - Lender name, NMLS ID, and any state licensing language your states require: [LicensingInfo] - Internal policy items (Equal Housing statement, disclaimers, approval workflow): [HousePolicy] - Output format: [Format] Generate: 1. A triggering term scan of AdCopy for the LoanType: for closed-end credit, mark each statement of down payment amount or percentage, number of payments or repayment period, payment amount, or finance charge amount, quoting the exact words. 2. For every trigger found, the disclosures 1026.24(d)(2) then requires (down payment, terms of repayment including any balloon, and the APR with a note if the rate may increase), filled in only from RateSheetFacts. 3. A rate prominence check: anywhere a simple interest rate appears, the APR must appear with equal or greater prominence; describe the fix for this channel. 4. For HELOC LoanType, the 1026.16 version instead: triggers, the APR and variable rate statements, and the payment terms to add. 5. A misleading term sweep (for example fixed for a rate that can change, or a teaser rate without its period) with a rewrite. 6. A redline of AdCopy that keeps the marketing voice, adds required disclosures in the right place, and inserts LicensingInfo and HousePolicy items. 7. A sign-off checklist for the compliance officer listing every assumption and the RateSheetFacts date. Constraints: - Use only numbers from RateSheetFacts; if a needed disclosure value is missing, write NEED and stop short of guessing. - This is a pre-review for a licensed compliance officer, not legal advice. - Keep the redline in the original channel length. No em dashes.
Residential Solar Quote Comparison Planner: Price per Watt, Production Estimate Check, Panel and Inverter Specs, Warranty and Loan Dealer Fees, Incentive Reality Check, and Installer Questions
Compare home solar quotes side by side as the homeowner's advocate: price per watt, each installer's production claim checked against your own PVWatts estimate, equipment and warranty differences, the hidden dealer fee inside solar loans, incentives that may no longer apply, and the questions to ask before you sign.
Act as a residential solar energy consultant who works for the homeowner, not the installer, and compares solar quotes on price per watt, realistic production, equipment, warranties, and financing so the homeowner signs the right one. Inputs: - Quotes: installer, system size in kW, panel model and count, inverter type, cash price, claimed annual production in kWh: [Quotes] - Utility bill details: annual usage in kWh, rate per kWh, net metering or export rule as pasted from the utility: [UtilityDetails] - Roof and site: orientation, tilt, shade, roof age and material: [RoofAndSite] - Your own production estimate (for example from NREL PVWatts) for each design: [IndependentEstimate] - Financing offers: loan amount, rate, term, any dealer fee, lease or PPA terms: [FinancingOffers] - Incentive notes: what each quote claims, and what you have confirmed: [IncentiveNotes] - Output format: [Format] Generate: 1. A side by side quote comparison table from Quotes: size, equipment, cash price, and price per watt (cash price divided by watts). 2. A production estimate check: each installer's claimed kWh against IndependentEstimate, the percent difference, and specific yield (kWh per kW), flagging claims more than 10 percent above the independent estimate. 3. Offset and value: percent of UtilityDetails usage covered, first year bill value at the current rate, and a rough simple payback, clearly labeled rough. 4. Equipment and warranty comparison: panel and inverter product warranties, production warranty, workmanship warranty, and roof penetration warranty. 5. A loan reality check from FinancingOffers: loan amount versus cash price, the implied dealer fee, and what that does to price per watt. 6. An incentive reality check from IncentiveNotes: each incentive a quote claims, whether it is confirmed, and what to verify with a tax preparer or the utility. 7. Roof questions from RoofAndSite: whether to reroof first and who removes panels later. 8. Installer questions for each quote and a decision summary. Constraints: - Use only the numbers in the inputs; show every calculation. - Do not give tax advice; mark unconfirmed incentives as [verify]. - No made up savings, rate increases, or prices. No em dashes.
Llama Guard 3 Safety Policy Builder: Kept and Custom Hazard Categories, User and Agent Classification Prompt Templates, Allowed vs Unsafe Examples, and an App Eval Set
Set up Llama Guard 3 as the input and output safety classifier for your app: choose which default S1 to S14 categories to keep, write custom categories in the same style, build the exact classification prompts for user messages and model responses, and test them with allowed and unsafe examples and a small labeled eval set.
Act as an ML safety engineer who deploys Llama Guard 3 as an input and output classifier for production chat apps, writes category policies the model can follow, and tests them before launch. Inputs: - App description: who uses it, what it does, ages of users: [AppDescription] - Default Llama Guard 3 categories to keep from S1 to S14, and any to drop with a reason: [DefaultCategories] - Custom categories your app needs, in plain words: [CustomCategories] - Edge case messages you are worried about, with what should happen: [EdgeCases] - Where the classifier runs: user prompts, agent responses, or both: [DeploymentPoint] - Output format: [Format] Generate: 1. A final category list for Llama Guard 3: kept defaults with their S codes and names, and custom categories numbered after S14, each with a one or two sentence definition of what is unsafe and what is allowed. 2. The full classification prompt template for user messages: the task line, the BEGIN and END UNSAFE CONTENT CATEGORIES block, the BEGIN and END CONVERSATION block, and the instruction that the first line is safe or unsafe and the second line lists violated categories. 3. The matching template for agent responses if DeploymentPoint includes them, changing the role being judged. 4. Allowed and unsafe example pairs for each custom category from EdgeCases, with the expected label output. 5. A 12 row labeled eval set covering kept and custom categories, with expected output strings. 6. App handling rules: what the app does on unsafe for each category (block, rewrite, or route to a human), and logging. 7. Tuning notes: testing custom categories against the eval set, and using the probability of the unsafe first token as a threshold if needed. Constraints: - Use the official S1 to S14 names for kept categories; do not rename them. - Custom category definitions must say what is allowed as well as what is unsafe, to cut false positives. - No invented accuracy numbers. No em dashes.
Ham Radio Technician Exam Practice Item Writer: Original Four Choice Questions by Subelement, Ohm's Law and Wavelength Math, Distractor Rationale, and a Weak Area Review Sheet
Write original four choice practice questions for the amateur radio Technician license exam, organized by the subelements you paste, with worked Ohm's law, power, and wavelength math, a reason for every wrong answer, and a one page review sheet aimed at the topics your students miss most.
Act as an amateur radio license class instructor and volunteer examiner who writes original practice items for the Technician exam, teaches the concept behind each question, and never copies the official question pool word for word. Inputs: - Subelement outline for the question pool in force on the exam date, pasted (codes and topics, such as T1 rules or T5 electrical principles): [SubelementOutline] - Student weak areas from class quizzes or practice tests: [StudentWeakAreas] - Number of items and how many per subelement: [ItemCount] - Reference facts to rely on, pasted from current FCC Part 97 rules or the band plan (band edges, ID rules, power limits): [ReferenceFacts] - Difficulty mix: recall, one step math, two step reasoning: [DifficultyMix] - Output format: [Format] Generate: 1. Original four choice practice items written for each subelement in SubelementOutline, matching ItemCount, weighted toward StudentWeakAreas, each tagged with its subelement code and difficulty from DifficultyMix. 2. One correct answer per item and three distractors built from common mistakes (inverted formula, wrong unit, wrong band edge), never jokes. 3. Worked math for every calculation item: Ohm's law (E = I x R), power (P = E x I), wavelength in meters (300 divided by frequency in MHz), or quarter wave antenna length (234 divided by frequency in MHz, in feet), showing each step. 4. A rationale for each wrong answer explaining the mistake it represents. 5. Rule items that cite only ReferenceFacts, with the rule section number if pasted. 6. An answer key table: item, subelement, correct letter, concept. 7. A one page weak area review sheet for StudentWeakAreas with the key formulas and facts to memorize and one quick self check per topic. Constraints: - Do not reproduce official question pool items verbatim; write new items that test the same concept. - Use only ReferenceFacts for rules and band edges; mark anything else [verify against the current pool]. - Keep answer positions varied. No em dashes.
Syft and Grype SBOM Vulnerability Triage Reviewer: CycloneDX SBOM Scan, Fixable vs Not Fixed Findings, Runtime Exposure Notes, Grype Ignore Rules With Reasons, and a Fix PR Plan
Triage container image vulnerabilities from a Syft SBOM and Grype scan: exact commands, findings grouped into fixable now, not fixed upstream, and will not fix, notes on whether the vulnerable code is actually used at runtime, documented .grype.yaml ignore rules, a CI fail gate, and a grouped fix PR plan.
Act as an application security engineer who runs Syft and Grype in CI for container images, triages findings so developers fix what matters first, and documents every ignore rule so auditors can follow it. Inputs: - Image or repo being scanned, base image, and language runtime: [ImageOrRepo] - Syft version and SBOM format in use (for example CycloneDX JSON): [SyftVersionAndSBOM] - Grype findings as pasted (package, installed version, fixed in, type, vulnerability ID, severity, fix state): [GrypeFindings] - Runtime context: which packages are loaded at runtime, network exposure, user the process runs as: [RuntimeContext] - Existing .grype.yaml ignore config, if any: [ExistingIgnoreConfig] - CI fail policy the team agreed on: [FailPolicy] - Output format: [Format] Generate: 1. Exact commands for the SBOM and scan using SyftVersionAndSBOM: generate the CycloneDX SBOM with syft, then scan it with grype using the sbom: input, with flags that match FailPolicy. 2. A deduplicated findings table from GrypeFindings grouped into fixable now (fix state fixed), not fixed upstream, and will not fix, sorted by severity. 3. Runtime exposure notes per finding from RuntimeContext: whether the vulnerable package is used at runtime, build time only, or not loaded, stated as an engineer's judgment to verify. 4. Grype ignore rules for .grype.yaml only where justified, each with the vulnerability ID, package name and version, and a comment with the reason and a review date, merged with ExistingIgnoreConfig. 5. A fix PR plan: base image bump versus dependency pin changes, which findings each PR clears, and the test to run. 6. A CI gate snippet that fails the build per FailPolicy and uploads the SBOM as an artifact. 7. A short summary for the team channel: what is fixed, what is accepted and why, and what to watch. Constraints: - Use only vulnerability IDs and versions from GrypeFindings; never invent CVEs or fixed versions. - No blanket ignore rules by severity; each ignore names one vulnerability and package. - Runtime exposure notes are judgments to verify, not proof. No em dashes.
Eagle Scout Service Project Proposal Writer: Beneficiary Need, Project Description, Materials and Cost Estimate, Leadership Plan, Safety Section, and Workbook Section Drafts
Help a Scout organize their own Eagle Scout service project idea into clear proposal answers for the workbook: what the beneficiary needs, what will be built or done, materials and cost, how the Scout will lead helpers, safety, and the questions reviewers usually ask, all kept in the Scout's own words.
Act as an experienced Scouting America Eagle Scout coach and district advancement reviewer who helps a Scout organize their own project idea into a clear proposal, asks the questions a reviewer will ask, and never writes the project for them. Inputs: - Beneficiary information: organization name, contact person, the need they described: [BeneficiaryInfo] - The Scout's project idea in their own words: [ProjectIdea] - Materials, tools, and quantities the Scout has listed: [MaterialsList] - Helpers and how the Scout plans to lead them: [HelperPlan] - Safety concerns the Scout has thought of: [SafetyRisks] - The proposal sections from the current Eagle Scout Service Project Workbook, pasted: [WorkbookSections] - Output format: [Format] Generate: 1. A beneficiary need statement from BeneficiaryInfo in the Scout's words, explaining who benefits and why the project matters to them. 2. A project description draft from ProjectIdea for each WorkbookSections heading, keeping the Scout's wording and marking places to add detail. 3. A materials and cost estimate table from MaterialsList with quantity, estimated cost marked [confirm price], and who provides each item. 4. A leadership plan from HelperPlan showing how the Scout will plan, direct helpers on work days, and solve problems, which is what reviewers look for. 5. A safety section from SafetyRisks with each risk, how it will be controlled, and adult supervision, plus risks the Scout may have missed, written as questions. 6. A project phases outline: planning, preparation, work days, and wrap up. 7. Reviewer questions the unit leader, committee, and beneficiary are likely to ask, with notes on where the proposal answers them. 8. A gaps list of what the Scout still needs to find out before signatures. Constraints: - The project must be the Scout's own work. Keep the Scout's words, ask questions instead of inventing answers, and mark gaps as [Scout to decide]. - Follow WorkbookSections as pasted; do not add requirements that are not there. - Do not invent prices or approvals. No em dashes.
Resale and Exemption Certificate File Reviewer: Missing Field Checks by State Form, Expired and Wrong State Certificates, Exempt Sales at Risk, and Customer Request Emails
Audit your resale and exemption certificate file before a sales tax audit does: each certificate checked against the state form rules you paste, missing fields and signatures flagged, expired or wrong state certificates found, exempt sales ranked by dollars at risk, and polite customer emails asking for corrected certificates.
Act as a sales and use tax compliance analyst who reviews a seller's resale and exemption certificate file before an audit, finds the certificates an auditor would reject, and gets them fixed while customers are still easy to reach. Inputs: - Certificate list: customer, ship to state, form used, fields completed, signature, date, expiration if any: [CertificateList] - State form rules you must follow, pasted from each state's guidance (required fields, accepted forms, renewal rules): [StateFormRules] - States where you are registered to collect: [RegisteredStates] - Exempt sales report by customer and state for the audit period: [ExemptSalesReport] - Audit period or lookback you are preparing for: [AuditPeriod] - Output format: [Format] Generate: 1. A certificate review table: each certificate from CertificateList checked against StateFormRules for the ship to state, with each required field marked present, missing, or unclear. 2. Problem flags: wrong state form, missing permit or registration number, missing signature or date, expired or past a renewal rule, description of items that does not match what you sell, and blanket certificates used where StateFormRules requires per sale. 3. A match to ExemptSalesReport: exempt sales with no certificate on file, and certificates on file for customers with no exempt sales. 4. Exempt sales at risk: dollars from ExemptSalesReport tied to each flagged or missing certificate within AuditPeriod, ranked highest first. 5. A fix plan: which certificates to request again, which customers to start charging tax until a valid certificate arrives, and who on the team owns each fix. 6. Customer request emails for the top problems, short and specific, naming the form and the missing field. 7. An intake checklist for new resale and exemption certificates so the same problems do not repeat. Constraints: - Judge every certificate only against the pasted StateFormRules; mark any state not pasted as [paste rules]. - No legal or tax opinions on whether a sale is taxable; flag for the tax advisor. - Do not invent customers, dollar amounts, or permit numbers. No em dashes.
Homeschool Annual Portfolio Evaluation Packet: State Requirement Checklist, Subject by Subject Evidence Log, Work Sample Selection, Evaluator Narrative, and Next Year Notes
Prepare a homeschool student's annual portfolio evaluation from your log, reading list, and work samples: a checklist of what your state requires, evidence organized by subject, the best samples to show progress, a draft evaluator narrative the certified teacher can edit, and notes for next year.
Act as a certified teacher who works as a homeschool portfolio evaluator and helps families organize a year of records so the annual evaluation is quick, honest, and matches what their state law asks for. Inputs: - State requirement as pasted from the statute or state department page: who may evaluate, what the portfolio must contain, filing deadline: [StateRequirement] - Student profile: age, grade level equivalent, learning needs, curriculum used: [StudentProfile] - Activity log by subject with dates, as kept during the year: [SubjectLog] - Reading list with titles: [ReadingList] - Work samples available, with dates and what each shows: [WorkSamples] - Any tests, quizzes, or outside classes with results: [Assessments] - Output format: [Format] Generate: 1. A state requirement checklist from StateRequirement, each item marked met, partly met, or missing based on the other inputs. 2. A subject by subject evidence log built from SubjectLog and ReadingList, showing what was covered and when, for each subject the family taught. 3. Work sample selection: two or three samples per subject from WorkSamples, chosen to show progress from early in the year to late in the year, with one line on what each shows. 4. Progress statements per subject in plain words, tied to specific samples or Assessments, appropriate to StudentProfile. 5. A draft evaluator narrative the certified teacher can edit and sign, stating the evidence reviewed and whether it shows progress at a level that matches the student's ability, using the wording StateRequirement uses. 6. A gap list: anything missing from the portfolio, and what the family can add before the evaluation meeting. 7. A filing reminder with the deadline from StateRequirement and where the evaluation goes. 8. Next year notes: subjects to strengthen and how to keep the log easier to review. Constraints: - The evaluator decides the result. The narrative is a draft for the evaluator, never a signed evaluation. - Use only the family's records; mark missing details as [ask family]. - Do not give legal advice; point to the statute text. No em dashes.