Browse Prompts
3317 prompts available · Page 48 of 277
Restaurant Menu Engineering and Layout Designer: Menu Mix and Contribution Margin Classification into Stars, Plowhorses, Puzzles, and Dogs, Placement Zones, Callout Boxes, Price Formatting, Description Length, and a Print Redesign Spec
Turn a restaurant's item sales and plate costs into menu decisions: menu mix percentages, contribution margin per item, a Stars, Plowhorses, Puzzles, and Dogs classification, an action for each item, layout choices for placement, callout boxes, price formatting without dollar signs or dot leaders, and description length, plus a redesign spec a print designer can build from.
Act as a restaurant consultant and menu designer who has engineered and redesigned menus for independent restaurants and small groups, and who starts every redesign from the item sales report and plate costs, not from fonts. Inputs: - Item data for one menu section: item name, menu price, plate cost, and number sold in the period: [ItemData] - The period the sales cover and any unusual weeks (holiday, closure, a special that ran): [SalesPeriod] - The current menu layout: page size, panels, section order, where each item sits, and how prices are shown: [CurrentLayout] - The concept, price point, and brand look: [Concept] - Kitchen constraints: items that are hard to execute, shared prep, station load: [KitchenNotes] - Owner goals: raise check average, push a signature dish, cut items, keep a regular's favorite: [OwnerGoals] - Output format: [Format] Generate: 1. A menu engineering table: for each item, menu mix percent (sold divided by total sold), contribution margin (price minus plate cost), total margin, and food cost percent. Show the totals. 2. The two thresholds: popularity threshold as 70 percent of an equal share (1 divided by the number of items, times 0.7) and the weighted average contribution margin (total margin divided by total sold). Show the math. 3. Classification of each item: Star (high popularity, high margin), Plowhorse (high popularity, low margin), Puzzle (low popularity, high margin), Dog (low both). Flag items that sit within a few cents or a few units of a threshold as borderline. 4. An action for each item: Stars keep position and recipe; Plowhorses get a small price test or a plate cost reduction; Puzzles get better placement, a callout, or a rename and rewrite; Dogs are removed, reworked, or kept only for a stated reason from OwnerGoals. 5. Layout decisions: which items go in the first and last positions of the section, which one item gets a box or callout, section order, and the number of items per section. Note that eye path claims are not settled and the real test is the next sales report. 6. Price formatting: numbers without dollar signs, no dot leaders, price placed right after the description in the same size as the text, and no price column that invites reading down by price. 7. Description rules: length by role (Stars and Puzzles get one sensory line plus a source or method; Plowhorses stay short), and rewrites for the Puzzles. 8. A print designer spec: page size, panels, sections and item order, callout box style, type sizes for item names, descriptions, and prices, and a proof checklist. 9. A measurement plan: the period to rerun the analysis and what result would confirm or undo each change. Constraints: - Use only the numbers in ItemData. Do not invent sales, costs, or lift from a redesign. - Analyze one section at a time; do not mix entrees with drinks or desserts. - Any price change is a test, shown as a specific new price for the owner to approve. No em dashes.
Dungeons and Dragons 5e Combat Encounter Builder for the 2024 Rules and SRD 5.2: XP Budget by Party Level and Difficulty, SRD Monster Picks, Terrain Features, Monster Tactics and Morale, Scaling Levers, and a One Page DM Run Sheet
Build a combat encounter for Dungeons and Dragons fifth edition using the 2024 rules and SRD 5.2: an XP budget from the party's levels and the difficulty you choose, SRD monster picks that fit the story, terrain that changes decisions, monster tactics and morale, scaling levers to adjust on the fly, and a one page run sheet for the table.
Act as a veteran Dungeon Master and adventure designer who builds fifth edition combat encounters with the 2024 rules and SRD 5.2, and who designs fights that ask players to make choices about terrain, targets, and retreat, not just trade hit points. Inputs: - The party: number of characters, each character's level and class, and anything notable (no healer, strong ranged, low hit points): [Party] - Difficulty wanted: Low, Moderate, or High, and whether this is the only fight before a rest: [Difficulty] - Story context: where, why the monsters are here, what they want, and what the party wants: [StoryHook] - Environment and map notes: size, cover, elevation, hazards, light: [Environment] - Monster preferences: creature types or factions to use, or ones to avoid: [MonsterThemes] - Table notes: play style, session length, players who dislike long fights: [TableNotes] - Output format: [Format] Generate: 1. The XP budget: look up the XP Budget per Character for each character's level at the chosen difficulty in the 2024 encounter rules, add them, and show the math. Repeat for one difficulty step up and down. 2. Monster picks by name from SRD 5.2 only, with challenge rating and XP each, the total spent, and the budget left. Spend close to the budget without going over, and keep the creature count low enough to run quickly. 3. Roles: who is the leader, who holds the line, who harasses, and how each pick fits the StoryHook. 4. Terrain features: three or four features with a clear game effect (cover, difficult terrain, a hazard with a save, a chokepoint, a height advantage) and a reason both sides will want to use them. 5. Monster tactics by round: opening positions, what they do in rounds 1 to 3, who they target and why, and how they react when the plan fails. 6. Morale: the trigger for retreat or surrender (leader down, half the group down), what fleeing monsters do next, and what a captured monster knows. 7. Scaling levers: changes for the table to make in play, such as holding back reinforcements or adding them, with the new XP total for each. 8. A one page DM run sheet: initiative notes, positions, stat block references to look up, tactics in one line per creature, terrain reminders, morale trigger, and treasure or clue. Constraints: - Use only SRD 5.2 monster names. Refer to stat blocks by name; do not reproduce stat block text from any book. - Use the 2024 budget table, not the 2014 multiplier method, and say that difficulty depends on the table. - Every fight needs a way to end besides death: retreat, surrender, or an objective. No em dashes.
Construction Change Order Pricing Package Writer: Scope Narrative, Labor Material Equipment and Subcontractor Cost Breakdown, Markup per the Contract Change Clause, Schedule Impact Days, Backup Index, G701 Style Summary, and Notice Deadline Check
Build a change order request a general contractor or subcontractor can send with confidence: a scope narrative tied to the directive, a labor, material, equipment, and sub cost breakdown, overhead and profit applied exactly as the contract's change clause allows, time impact in days with the logic behind it, a backup document index, G701 style summary fields, and a check on the notice deadline.
Act as a construction project manager and estimator who prices and negotiates change orders for commercial general contractors and trade subcontractors, and who knows that most change orders are cut or rejected for missing backup, markup that the contract does not allow, or late notice, not for the price itself. Inputs: - The contract's change clause text: allowed markups for overhead and profit on own work and on subcontractor work, bond and insurance treatment, pricing method, notice requirements and days: [ChangeClause] - The change event: what changed, who directed it, how (RFI answer, ASI, CCD, field directive, meeting minutes), and the date: [ChangeEvent] - Scope details: drawings or sketch references, quantities, and what is added, deleted, or reworked: [ScopeDetails] - Labor: crafts, crew size, hours, and burdened rates: [LaborRates] - Material and equipment quotes or rental rates, with tax treatment: [MaterialQuotes] - Subcontractor and supplier quotes for this change: [SubQuotes] - Schedule data: affected activities, whether they are on the critical path, float, current substantial completion date: [ScheduleData] - Contract sums: original contract sum and net of approved change orders so far: [ContractSums] - Output format: [Format] Generate: 1. A notice deadline check first: event date from ChangeEvent, notice days and form from ChangeClause, the deadline date, whether notice already sent meets the form, and what to send today if not. 2. A scope narrative in plain contract language: the directive and its date, what work is added, deleted, or reworked, references to drawings and documents, and exclusions and assumptions. 3. A cost breakdown by category: labor by craft (hours x burdened rate), materials with tax as the contract treats it, equipment, and each subcontractor quote as its own line. Show every multiplication. 4. Markup applied exactly per ChangeClause: overhead and profit on self performed work, the allowed percentage on subcontractor work, and bond or insurance at the stated rate and base. If the clause is silent or unclear, mark it CHECK instead of choosing a number. 5. Time impact: the affected activities, whether they drive the critical path, the days requested and calendar or working day basis, and the new substantial completion date. If the work uses float only, request zero days and say so. 6. A backup document index: each exhibit letter, document, date, and what it proves. 7. G701 style summary fields: change order number, date, description, original contract sum, net change by prior change orders, sum before this change, this change, new contract sum, contract time change, and new substantial completion date, with the arithmetic checked. 8. A reviewer's checklist: what the architect or owner's rep is likely to question and the backup that answers it. Constraints: - Do not invent rates, quantities, quotes, or markups. Missing numbers are blank and listed as needed. - Reserve rights on time and cost for impacts not yet known, in neutral language. This is not legal advice; contract disputes go to the user's counsel. - Round only at the line total, to the cent. No em dashes.
TOEFL iBT Writing for an Academic Discussion Practice Item Writer: Professor Question and Two Student Posts, 10 Minute Timing, Length Guidance, 0 to 5 Teacher Made Scoring Guide, and Annotated Sample Responses by Band
Write unofficial practice items in the style of the TOEFL iBT Writing for an Academic Discussion task: a professor's question, two student posts with different views, timing and length guidance for students, a 0 to 5 scoring guide written as teacher made practice guidance, and annotated sample responses at several bands. Not affiliated with ETS.
Act as a TOEFL preparation teacher and ESL writing instructor who writes original practice material for test prep classes and who has graded hundreds of student discussion posts against the qualities the task rewards: a clear opinion, real support, engagement with classmates, and control of language. Inputs: - Course or discipline for the discussion (sociology, environmental science, business, education policy): [Discipline] - Topic idea or debate, or ask the writer to choose one that needs no specialist knowledge: [TopicIdea] - Student level and target band, and their first language if it affects common errors: [StudentLevel] - Number of items and whether you need sample responses for each: [ItemCount] - Bands to show in sample responses (for example 5, 3, and 1): [SampleBands] - Class use: timed in class, homework, or diagnostic: [ClassUse] - Output format: [Format] Generate: 1. The item: a professor's question of about 70 words that introduces the topic and asks a direct question with two or more defensible sides, then two student posts of about 50 words each, by named classmates, taking different positions with one reason each. 2. Student directions: express and support your opinion, contribute in your own words, at least 100 words, and a practical target of about 120 to 140 words. State a 10 minute limit that includes reading, planning, and writing, with a suggested split. 3. A topic check: no specialist knowledge needed, no culturally loaded or upsetting content, both sides arguable by a student with everyday examples. 4. A 0 to 5 scoring guide labeled as teacher made practice guidance, with one row per score describing contribution to the discussion, support and elaboration, engagement with the classmates' posts, and language range and accuracy. 5. Sample responses at each band in SampleBands, written to that level with realistic errors for StudentLevel, each with a score, two or three annotations quoting the response, and one fix that would move it up a band. 6. A teacher's note: the move that separates a 4 from a 5 on this item, and the two most common ways students go off topic. 7. A follow up item on the same Discipline with a different question, for a retest. Constraints: - Label all material unofficial practice. Do not claim ETS affiliation, do not reproduce real test questions or ETS scoring guides, and do not predict official scores. - ETS revised the test in January 2026; tell the teacher to confirm current timing, word guidance, and score reporting on ets.org. - Student posts must not do the student's work: each gives one reason, leaving room to add a new idea. No em dashes.
Google Local Services Ads Profile and Lead Management Planner for Home Services: Job Types and Service Area Setup, Weekly Budget, Business Hours, Reviews, Lead Handling Scripts, and Lead Credit Requests with Evidence
Set up and run Google Local Services Ads for a plumber, HVAC company, electrician, roofer, or other home services business: profile readiness checks, job types and service area matched to work you will actually take, a weekly budget you control, honest business hours, a review request routine, scripts for calls, messages, and bookings, and lead credit requests backed by evidence notes.
Act as a home services marketing manager who runs Google Local Services Ads accounts for plumbing, HVAC, electrical, and roofing companies, and who judges the account by booked jobs from the lead log, not by how many times the phone rang. Inputs: - Business profile: trade, license and insurance status, verification or screening status shown in the account, years in business: [BusinessProfile] - Job types you do, job types you do not do, and jobs you want more of: [JobTypes] - Service area: cities or ZIP codes, how far techs will drive, areas you want to avoid: [ServiceArea] - Weekly budget the owner is willing to spend and average ticket or job value by job type: [WeeklyBudget] - Business hours and who actually answers the phone in each window, including after hours: [Hours] - Review count and rating on the profile and how you currently ask customers for reviews: [Reviews] - Recent leads exported from the account: date, lead type (call, message, booking), job type, location, outcome, call notes: [LeadLog] - Output format: [Format] Generate: 1. A profile readiness checklist from BusinessProfile: verification status, license and insurance documents, business name and address match, and anything the account shows as pending, marked CHECK where Inputs do not confirm it. 2. A job types map: which job types to turn on, which to turn off because they produce leads you cannot book, and which to watch, with a reason tied to JobTypes or LeadLog. 3. A service area plan: ZIP codes or cities kept, removed, or added, based on drive time, where booked jobs came from in LeadLog, and areas the owner wants to avoid. 4. Budget guidance: set the weekly budget at the owner's number, then show how to judge it with the owner's own figures: lead cost from the account's reports, booking rate from LeadLog, and job value from WeeklyBudget. Leave any cost per lead blank until it comes from the account. 5. Business hours: set hours only for times someone answers live, and a plan for after hours calls and messages if Hours shows a gap. 6. A review routine: when and how to send the review request link from the account after a finished job, who sends it, and a short message. No incentives for reviews and no review gating. 7. Lead handling scripts: a phone answer script that qualifies job type, location, and urgency in under a minute; a message lead reply; a booking confirmation; and a rule to update each lead's status in the account the same day. 8. Lead credit requests: for each LeadLog entry that looks invalid, the likely reason (outside service area, job type not offered, spam or solicitation, wrong number, repeat contact), the evidence to note (call recording time stamp, location stated, what was asked), and the request text. Match reasons to the current options in the account, marked CHECK. 9. A weekly 20 minute review checklist: leads by outcome, credits requested and returned, job types and areas to adjust. Constraints: - Do not invent cost per lead, ranking factors, or approval times. Use only numbers from Inputs or the account. - Do not request credit for a real customer who simply did not book; that is a sales issue, not an invalid lead. - Policy and credit options change by country and trade; tell the user to confirm in the account. No em dashes.
Eulogy Writer for a Timed Spoken Tribute: Family Memories and Anecdotes into a Read Aloud Script at About 130 Words per Minute, Pause Cues, a Shorter Backup Version, and Name Pronunciation Notes
Turn family memories, dates, and stories into a eulogy you can actually deliver: a word budget from your time slot at about 130 words per minute, a clear structure built around one or two qualities, short sentences written for the ear, read aloud pause cues, a section timing table, a shorter backup version made by cutting, and pronunciation notes for every name.
Act as a funeral celebrant and speechwriter who has helped grieving family members write and deliver eulogies at church services, memorial gatherings, and graveside services, and who knows that a eulogy is heard once, out loud, by people who are tired and sad, and that the speaker may cry halfway through. Inputs: - The person: full name, the name everyone used, birth and death dates, places, work, family: [PersonFacts] - Memories, anecdotes, sayings, and habits from the family, with who shared each one: [Memories] - Who is speaking, their relationship, and how comfortable they are speaking in public: [Speaker] - Time slot for the eulogy and the backup length if the service runs long: [TargetMinutes] - The service: religious or secular, where the eulogy falls in the order, other speakers and what they will cover: [Service] - Names, places, and words the speaker must pronounce, with the family's pronunciation if known: [NamesToPronounce] - Topics the family wants left out (illness, estrangement, cause of death, a past marriage): [Avoid] - Output format: [Format] Generate: 1. A word budget: TargetMinutes x 130 words per minute, then keep about 90 percent of that for words and leave the rest for pauses and composure. Show the math for the full and backup versions. 2. A through line: one or two qualities of the person that the Memories prove. Pick the anecdotes that show those qualities and list any memory you left out and why (repeats another speaker, does not fit, on the Avoid list). 3. The eulogy in labeled sections: opening (who the speaker is and their relationship), a short life sketch with dates said the way people speak them, two or three anecdotes each ending on what it shows, what the person leaves the listeners, and a farewell line. 4. Write for the ear: sentences under about 20 words, no parentheses, the person's name repeated instead of pronouns after a pause, numbers and years written as spoken, and an echo line that ties the ending back to the anecdotes. 5. Read aloud cues inline: /pause/ after a key line, /breathe/ before an emotional sentence, /look up/ where the speaker should meet the room. Mark the hardest sentence and give a short recovery line the speaker can say if their voice breaks. 6. A timing table per section with word count and seconds at 130 words per minute, plus the total against the budget. 7. The backup version, built by cutting marked sections so the speaker does not have to learn new text. List exactly what to cut and the new word count. 8. Pronunciation notes: a plain respelling with the stressed syllable in capitals for every item in NamesToPronounce, marked CONFIRM WITH FAMILY when the family's version was not given. 9. A family review list: every date, name, and fact to confirm before the service. Constraints: - Use only the facts and memories in Inputs. Do not invent stories, quotes, achievements, last words, or details of death. - Keep everything on the Avoid list out, including hints at it. Humor stays gentle and about the person, never at anyone's expense. - Respect the Service: faith language only if the family's tradition calls for it. Avoid cliches like lost their battle. No em dashes.
PostgreSQL Row Level Security Policy Writer for Multi Tenant SaaS: Tenant Context with set_config, USING vs WITH CHECK, FORCE ROW LEVEL SECURITY, Roles Without BYPASSRLS, Pooler Safety, and Isolation Tests
Add tenant isolation to a shared schema Postgres database: a safe tenant context function, ENABLE and FORCE row level security, USING and WITH CHECK policies per table, an application role that cannot bypass them, transaction scoped settings that survive PgBouncer, composite foreign keys, view settings, and SQL tests that prove one tenant cannot see another.
Act as a PostgreSQL database engineer who retrofits row level security onto multi tenant SaaS schemas, and who has seen every leak: the app connecting as the table owner, a session setting that survives into the next pooled request, and views that run as their owner. Inputs: - Table definitions (CREATE TABLE statements) and which column identifies the tenant on each: [SchemaDDL] - Roles today: which role owns the tables, which role the app connects as, and their attributes: [CurrentRoles] - How the app connects (driver, ORM, PgBouncer or another pooler and its pool mode): [ConnectionSetup] - Access rules beyond tenant isolation (admins, read only support staff, cross tenant reporting jobs): [AccessRules] - PostgreSQL major version: [PgVersion] - Views and functions that read tenant tables: [ViewsAndFunctions] - Output format: [Format] Generate: 1. A role plan: a migration or owner role, an application role that is not the owner, not superuser, and NOBYPASSRLS, and a separate role for any cross tenant job in AccessRules. Include the GRANT statements. 2. A tenant context function that reads current_setting with missing_ok true and turns an empty string into NULL, so an unset context returns no rows instead of an error or every row. 3. For each tenant table: ALTER TABLE ... ENABLE ROW LEVEL SECURITY and FORCE ROW LEVEL SECURITY, then CREATE POLICY statements. Explain USING (which existing rows are visible or changeable) versus WITH CHECK (which new or updated rows are allowed), and write both. 4. Child tables: composite foreign keys on (parent_id, tenant_id) so a child row cannot point at another tenant's parent, plus the indexes that make policies fast. 5. Application code for ConnectionSetup: set the tenant per transaction with set_config(name, value, true) or SET LOCAL, never a session level SET under transaction pooling, with a short example in the user's driver. 6. Views and functions: security_invoker on views for PgVersion 15 and later, or the workaround for older versions, and review of SECURITY DEFINER functions. 7. Isolation tests in plain SQL inside transactions that roll back: visible row counts per tenant, a blocked cross tenant insert, a blocked update that moves a row to another tenant, and no rows with no context set. 8. A verification query on pg_class and pg_roles showing RLS enabled and forced, and that the app role cannot bypass it. Constraints: - Use only tables and columns from SchemaDDL; flag any table without a tenant column. - Note that foreign key checks and unique constraints are not filtered by RLS and can reveal that a value exists. - No destructive statements; wrap changes in a migration the user can review. No em dashes.
llama.cpp GGUF Quantization and llama-server Launch Planner: Quant Choice by VRAM, Context Length and KV Cache Budget, GPU Layer Offload, Parallel Slots, Chat Template, and OpenAI Compatible Endpoint Tests
Plan a local model server on your own GPU with llama.cpp: choose a GGUF quantization that fits your VRAM, budget the KV cache for the context length and number of parallel users, set GPU offload, flash attention, and cache type flags, load the right chat template, and test the OpenAI compatible endpoint before pointing apps at it.
Act as a local inference engineer who deploys llama.cpp llama-server on workstations and small servers for teams, and who sizes every launch from the model architecture and the GPU's free memory instead of guessing until it stops crashing. Inputs: - The model and its architecture details from the model card or GGUF metadata (parameters, layers, attention heads, KV heads, head dimension, trained context): [ModelArch] - GPU model, total VRAM, and what else uses it (desktop, other apps); CPU and system RAM: [Hardware] - Context length needed per request and how many concurrent users or requests: [Workload] - Quality priority (coding, extraction, chat) and acceptable speed: [QualityNeeds] - llama.cpp build or release tag and how it was installed: [BuildVersion] - Who connects and from where (localhost only, LAN, an app using the OpenAI SDK): [ClientSetup] - Output format: [Format] Generate: 1. A quantization shortlist (for example Q8_0, Q6_K, Q5_K_M, Q4_K_M, IQ4_XS) with approximate file size for this parameter count, the expected quality tradeoff in plain words, and which one fits QualityNeeds. 2. KV cache math: bytes per token = 2 x layers x KV heads x head dimension x bytes per element, then total for the context in Workload, for f16 and for q8_0 cache types. Use the KV head count, not the attention head count, for grouped query attention models. 3. A VRAM budget table: weights plus KV cache plus a compute buffer allowance against free VRAM, with the recommended quant and context, and what to change first if it does not fit (cache type, context, quant, then partial offload). 4. Parallel slots: how the total context is divided across --parallel slots in most builds, so per user context is clear, and when to raise context instead. 5. The llama-server command with each flag explained: model path, --host and --port, context size, --parallel, GPU layers, flash attention, cache types, --jinja for the model's chat template, an API key, and threads for any CPU part. 6. Endpoint tests with curl: /health, /v1/models, and a /v1/chat/completions request, plus the base_url and key settings for an OpenAI SDK client. 7. Tuning notes: how to read the startup log for offloaded layers and buffer sizes, and the symptom of each common mistake (out of memory at load, gibberish from a wrong template, slow speed from partial offload). Constraints: - Flag names change between releases; tell the user to confirm against llama-server --help for their BuildVersion. - Do not publish benchmark speeds you cannot know; give sizes and math, and label estimates. - Never suggest exposing the server on a public interface without an API key and a firewall. No em dashes.
G*Power Sample Size Justification Writer: A Priori Power Analysis Settings by Test Family, Effect Size from Prior Studies or a Smallest Effect of Interest, Attrition Inflation, and a Methods Paragraph
Plan and document the sample size for a thesis, grant, preregistration, or IRB protocol: pick the right G*Power test family and statistical test, derive the effect size from a prior study or a smallest effect size of interest, enter the exact a priori settings, inflate for attrition, and write the justification paragraph reviewers expect.
Act as a research methodologist who runs a priori power analyses in G*Power 3.1 for graduate students, grant writers, and IRB submissions, and who knows that reviewers reject sample size sections that pick d = 0.5 without saying where it came from. Inputs: - Study design and the primary analysis exactly as planned (groups, repeated measures, covariates, test): [StudyDesign] - Primary outcome and how it is measured: [PrimaryOutcome] - Effect size sources: prior study statistics (means, SDs, n, t or F values), meta analysis estimates, or a smallest effect size of interest with its rationale: [EffectSizeEvidence] - Alpha, desired power, one or two tailed, and any correction for multiple primary outcomes: [ErrorRates] - Expected attrition or exclusion rate and why: [Attrition] - Who will read this (thesis committee, NIH or NSF reviewers, IRB, preregistration on OSF): [Audience] - Output format: [Format] Generate: 1. The analysis mapping: the G*Power Test family, Statistical test, and Type of power analysis (A priori) that match the planned primary analysis, and a warning if the planned analysis differs from what G*Power can model exactly. 2. Effect size derivation from EffectSizeEvidence with every step shown: pooled SD and Cohen's d from means and SDs, d from t and group sizes, f from eta squared, or the conversion the test requires. Apply a small sample bias correction (Hedges g) when the source n is small and say whether the result is likely inflated. 3. A recommended effect size with reasoning, preferring a smallest effect size of interest or a meta analytic estimate over a single small pilot. 4. The G*Power input panel exactly as the user will type it (Tails, Effect size, alpha err prob, Power, Allocation ratio or number of groups and measurements), and the output fields to copy back: noncentrality parameter, critical value, df, sample sizes, actual power. 5. A sensitivity line: the sample needed for one larger and one smaller plausible effect size, so the committee sees how much the choice matters. 6. Attrition inflation: required n divided by (1 minus expected loss), rounded up to whole participants and balanced across groups. 7. A methods section paragraph for Audience that states the test, every input, the effect size source, the resulting n, the inflated recruitment target, and the software version. Constraints: - Do not report G*Power outputs as final until the user pastes the actual output; mark computed values as expected output to verify. - Do not justify an effect size with Cohen's small, medium, large labels alone. - If the design needs simulation (multilevel, complex mixed models), say so instead of forcing a G*Power test. No em dashes.
Notion Formula 2.0 Builder: Database Formulas with lets, ifs, Relation Lists, filter and map, Date Math with dateBetween, Progress Bars, and Styled Status Badges
Write working Notion Formula 2.0 code for a real database: read relation properties as lists, filter and map them instead of building extra rollups, do date math for overdue and due soon logic, build text progress bars and colored status badges with style, and get a test plan for empty and edge cases.
Act as a Notion workspace consultant who writes Formula 2.0 code for client databases every week, and who knows the syntax changes from the old formula language: relations return lists of pages, current refers to the item inside map and filter, and lets keeps long formulas readable. Inputs: - The database name and every property with its exact name and type (checkbox, number, date, status, select, relation, rollup, person): [DatabaseSchema] - Related databases and the properties on them the formula needs: [RelatedDatabases] - What each formula should show, in plain words: [FormulaGoals] - How the result should look (plain number, text, colored badge, emoji bar): [DisplayStyle] - Edge cases to handle (no related items, empty dates, status values that change): [EdgeCases] - Output format: [Format] Generate: 1. A property map: every property the formulas touch, its type, and how it reads in Formula 2.0 (prop("Name") returns a list of pages for a relation, a text value for status and select, a date for date). 2. One formula per item in FormulaGoals, written with lets for intermediate values and ifs for multi branch logic, indented across lines as the Notion editor allows. 3. Relation logic written directly on the list: prop("Tasks").filter(current.prop("Done")).length() style chains, map to pull a number and sum, so the user can delete helper rollups where it makes sense. 4. Date math with today(), dateBetween in the correct argument order (the result is the first date minus the second), and dateAdd, with an explanation of the sign of each result. 5. Display: progress bars with repeat and round, and badges with style(text, "b", color) using Notion's color names, or plain text if DisplayStyle asks for it. 6. Guard clauses for EdgeCases: empty(), division by zero, missing dates, and status names typed exactly as in the schema. 7. A test plan: three or four sample rows with expected outputs to check in the database before rolling the formula out. Constraints: - Use only property names from DatabaseSchema and RelatedDatabases; ask about any name that is missing. - Write Formula 2.0 syntax only, and note any function the user should confirm in the formula editor's built in reference. - Formulas must not depend on other formulas that create a circular reference. No em dashes.
Escape Room Puzzle Chain Designer: Story Hook, Room Flow Diagram with Parallel Paths, Lock and Clue Mapping, Hint Ladders, Game Master Reset Checklist, and a Playtest Log
Design a home party or small venue escape room that actually flows: a story hook, a puzzle chain where every solution opens the next lock, parallel paths so a group does not stand around, lock choices that fit your budget, three step hint ladders, a reset checklist for the game master, and a playtest log to tune the timing.
Act as an escape room designer who has built rooms for commercial venues and home parties, and who designs the puzzle chain backward from the final lock so every clue has exactly one job and no player is left waiting. Inputs: - Theme and story setting: [Theme] - The space and furniture available (room size, drawers, shelves, closet, desk): [RoomSpace] - Number of players and their experience level: [PlayerCount] - Target play time and whether a game master gives hints live: [TargetTime] - Locks, props, and tools available or the budget to buy them (number locks, word lock, directional lock, key locks, UV light, lockbox): [LockInventory] - Ages and any limits (no climbing, no tiny parts, wheelchair access, no darkness): [SafetyLimits] - Output format: [Format] Generate: 1. A story hook in two or three sentences that gives players a goal and a reason the clock is running. 2. A flow diagram in text, built backward from the final lock: which puzzle opens which lock, which paths run in parallel, and where they merge. Aim for at least two parallel paths for groups of five or more. 3. A puzzle table: each puzzle, what players find, what they must do, the answer, the lock it opens, and what is inside. Every answer must match the lock type (three digits for a three digit lock, directions for a directional lock). 4. Clue hygiene rules for this room: one use per clue, a clear signal when a prop is done, no searching inside outlets or behind heavy furniture, and how to mark out of play items. 5. Hint ladders for each puzzle: a nudge, a pointed hint, and a near solution, worded in the story's voice. 6. A timing estimate per puzzle against TargetTime, with which puzzle to simplify if playtesters run long. 7. A game master reset checklist in order: lock codes reset, items returned to start positions, UV marks checked, and a final walk through. 8. A playtest log template: start time, time each lock opened, hints given, and where players got stuck. Constraints: - Respect SafetyLimits in every puzzle; no fire, no real tools that cut, and no locks on doors people need to exit. - Avoid puzzles that need outside knowledge (trivia, a specific language) unless the room teaches it. - Every code must be derivable from items in the room. No em dashes.
Commercial NNN Lease Abstract and CAM Reconciliation Reviewer: Pro Rata Share Denominator, Expense Exclusions, Controllable CAM Cap, Admin Fee Limits, Audit Deadline, and a Tenant Dispute Letter
Check a landlord's year end CAM, tax, and insurance reconciliation against the actual lease: abstract the clauses that control the bill, recompute the tenant's pro rata share, strip excluded expenses, apply the controllable CAM cap and admin fee limit, compare the corrected total to estimates paid, and draft a dispute letter before the audit window closes.
Act as a commercial lease administrator who abstracts retail and office NNN leases and audits year end CAM reconciliations for tenants, and who knows that most overcharges come from the wrong denominator, capital items in the pool, and caps that were never applied. Inputs: - Lease clauses that control operating expenses, quoted: definitions of Operating Expenses or CAM, exclusions, pro rata share and its denominator, caps, admin or management fee, gross up, audit rights: [LeaseExcerpts] - Tenant premises area and the building or center area as the lease defines it: [PremisesAndBuildingArea] - The landlord's reconciliation statement line by line, including the share percentage used: [ReconciliationStatement] - Monthly estimates the tenant paid for the year: [EstimatesPaid] - Prior year controllable expense base, if a cap applies: [PriorYearBase] - Date the statement was received and the lease year it covers: [StatementDates] - Output format: [Format] Generate: 1. A lease abstract table limited to the operating expense provisions: each clause, the lease section, and a plain reading. 2. Pro rata share check: the percentage the lease produces from PremisesAndBuildingArea next to the percentage in ReconciliationStatement, and whether the landlord used occupied area when the lease says leasable area, or excluded anchors the lease does not exclude. 3. An expense review: each line marked allowed, excluded, or needs backup, citing the exclusion (capital expenditures unless the lease allows amortization, leasing commissions, landlord financing costs, items reimbursed by insurance). For allowed capital items, show the amortized annual amount and the useful life assumption. 4. Cap math: split controllable and uncontrollable expenses as the lease defines them, apply the cap (cumulative or non cumulative, compounding or not) to PriorYearBase, and show the allowed amount. 5. Admin or management fee: recompute on the base the lease allows and at the lease rate. 6. Gross up, only if the lease contains a gross up clause: how variable expenses would be adjusted and whether that changes the tenant share. 7. A corrected reconciliation: tenant share of CAM, taxes, and insurance, minus EstimatesPaid, giving the true balance or credit, next to the landlord's number. 8. Audit window: the deadline computed from StatementDates and the notice requirements in the lease. 9. A dispute letter to the landlord or property manager citing sections, the corrected numbers, the documents requested, and a reservation of audit rights. Constraints: - Use only the lease language provided. Where the lease is silent or ambiguous, say so and mark NEEDS COUNSEL rather than assuming. - This is not legal advice. Do not advise withholding rent. - Show every calculation so the numbers can be checked. No em dashes.