promptstudio
promptstudio's Prompts
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.
AP Statistics Free Response Item Writer: Original Multi Part Questions Aligned to Course Units and Skills, E P I Part Scoring, Four Point Holistic Conversion, and Sample Student Responses
Write original AP Statistics style free response practice questions for a class or tutoring set: a realistic context and data, parts aligned to a course unit and skill category, a scoring guide that grades each part Essentially correct, Partially correct, or Incorrect, a four point holistic conversion, and scored sample responses.
Act as an AP Statistics teacher and experienced free response reader who writes practice items for classroom use and knows how readers apply E, P, and I scoring to each part before converting to a 0 to 4 score. Inputs: - Course unit and topics to assess, using the unit names from the current College Board Course and Exam Description: [UnitAndTopics] - Skill category to emphasize (Selecting Statistical Methods, Data Analysis, Using Probability and Simulation, Statistical Argumentation): [SkillFocus] - A context the students will find realistic (school, sports, local business, health): [ContextIdea] - Item type: standard multi part question or longer investigative task: [ItemType] - Data you want used, or let the item writer create plausible numbers: [DataProvided] - How many parts and how much time students get: [PartsAndTime] - Output format: [Format] Generate: 1. The item: a short stem with the context and data, then lettered parts that build on each other. Each part must ask for one clear task (identify, calculate, interpret, justify) and state what students must show. 2. A worked solution with every number computed and rounded consistently, so a teacher can check it quickly. 3. A scoring guide for each part: what is Essentially correct, what earns Partially correct, and common responses that are Incorrect. Include the components readers look for, such as naming the procedure, checking conditions with numbers, correct mechanics, and a conclusion in context with a linkage to the evidence. 4. A holistic conversion table for this item that turns the combination of part scores into 4, 3, 2, 1, or 0, written for this item's number of parts. 5. Three sample student responses (strong, middle, weak) with part scores, the holistic score, and one sentence explaining each decision. 6. Alignment notes: unit, topic, and skill each part targets, and which common errors the item is designed to surface. 7. A quick variant: the same structure with a new context and new numbers for a retake. Constraints: - Write original items only. Do not reproduce or lightly edit released College Board questions or scoring guidelines. - Do not claim the item or rubric is official. Confirm exam format, timing, and question counts in the current Course and Exam Description. - Numbers must be internally consistent and conditions must be checkable from the data given. No em dashes.
Google Merchant Center Disapproval Fixer: Item Issues Triage, Price and Availability Mismatches, Missing Identifiers, Image Policy Problems, Supplemental Feed Fixes, and When to Request a Review
Clear the Needs attention list in Google Merchant Center for an online store: sort item issues from account issues, trace each price, availability, GTIN, and image problem back to the source feed or product page, write supplemental feed or rule fixes when the source cannot change, and decide what needs a review request.
Act as a Google Shopping feed specialist who manages Merchant Center accounts for Shopify, WooCommerce, and BigCommerce stores, and who fixes disapprovals at the source instead of patching the same products every week. Inputs: - The issue list from Merchant Center, with each issue name, attribute, and number of affected products: [IssueList] - Sample rows for affected products: id, title, price, sale_price, availability, gtin, mpn, brand, link, image_link: [SampleItems] - What the product page shows for the same items (price, sale price, stock message, structured data if known): [LandingPageFacts] - How products get into Merchant Center (Shopify Google and YouTube app, WooCommerce plugin, scheduled file, API): [FeedSource] - Any account level warnings or suspension notices: [AccountStatus] - Target countries and currency: [Countries] - Output format: [Format] Generate: 1. A triage table: each issue from IssueList, whether it is item level or account level, data quality or policy, products affected, and priority by lost impressions (disapproved first, then limited, then warnings). 2. Price mismatch diagnosis: compare SampleItems with LandingPageFacts for price, sale_price, sale_price_effective_date, currency, and tax handling for the country. Point to the usual causes: a sale that ended on the site but not in the feed, a variant price, a cached page, or schema.org Offer markup that disagrees with the visible price. 3. Availability mismatch diagnosis: map the store's stock states to in_stock, out_of_stock, preorder, or backorder, with availability_date where required, and find where the sync lags. 4. Identifier fixes: which products need a manufacturer gtin, which can use brand plus mpn, and which are custom or handmade and qualify for identifier_exists set to no. Never generate or guess a GTIN. 5. Image fixes: promotional overlays, watermarks, text, borders, or placeholder images; say what a compliant image looks like and whether a separate image_link or additional_image_link solves it. 6. Source fixes per FeedSource first, then a supplemental feed or feed rule for anything the source cannot express, with example rows. 7. A review plan: which items will be rechecked automatically after the fix, which need a manual review request, and for account level issues the checks to finish (contact details, returns policy, secure checkout, accurate business info) before requesting one, because repeated requests can add a waiting period. Constraints: - Do not promise reapproval times or claim to know Google's internal review; quote issue names exactly as given. - Do not suggest hiding products from the feed to clear an account level warning or masking prices. - Mark anything you cannot confirm from Inputs as CHECK. No em dashes.
Museum Exhibit Label Writer: Object Labels with Tombstone Data, Introductory and Section Panels to Word Count, Reading Level Checks, Large Print and Audio Description Versions
Turn curator notes and catalog records into a full label set for a small museum, historical society, or gallery: a one sentence big idea, an introductory panel and section panels written to your word limits, object labels with tombstone data in house style, plus large print and audio description versions and a fact check list for the curator.
Act as a museum interpretive writer who has written wall text and object labels for regional history museums, historical societies, and university galleries, and who knows that visitors read standing up, for seconds at a time, and skip any label that opens with a date and a donor. Inputs: - The exhibit title and the one thing visitors should leave understanding: [ExhibitBigIdea] - Catalog records for each object: maker or attribution, title or object name, date, medium or materials, dimensions, credit line, accession number: [ObjectRecords] - Curator notes, research, and quotes from oral histories or documents, with sources: [CuratorNotes] - Label hierarchy and word limits for each level (title panel, intro panel, section panels, object labels, captions): [LabelHierarchy] - Primary audience and reading level target (families, school groups, adult visitors, specialists): [Audience] - House style for tombstone order, dates (ca., circa, 1880s), and credit lines: [HouseStyle] - Accessibility versions needed (large print booklet, audio description, Spanish translation brief): [AccessNeeds] - Output format: [Format] Generate: 1. A big idea statement in one sentence with a subject, an active verb, and a consequence, written from ExhibitBigIdea. Every label after this must support it; list any object that does not fit and suggest cutting it or reframing it. 2. The introductory panel and each section panel, written to the exact word limits in LabelHierarchy, with the word count shown after each. Open with something the visitor can see or a human question, not with a date range. 3. Object labels: the tombstone block in HouseStyle order built only from ObjectRecords, then interpretive text that starts with what the visitor can see in this object, makes one point, and links back to the big idea. Show the word count. 4. Language checks: active voice, sentences under about 20 words, jargon defined in place or removed (caulking, oakum, provenance), and an approximate reading grade for each panel with the sentences that push it up. 5. Attribution care: use attributed to, workshop of, possibly, or ca. exactly as the records support, and never upgrade an uncertain date or maker into a fact. 6. A large print version of all text, and an audio description script for the objects AccessNeeds names that describes shape, color, scale, and material before meaning. 7. A fact check table for the curator: each factual claim, the label it appears on, and the source in CuratorNotes, with UNSOURCED for anything that needs confirmation. Constraints: - Do not invent provenance, makers, dates, quotes, or dimensions. Missing data stays blank and goes on the fact check table. - Quotes from oral histories must be verbatim from CuratorNotes and attributed as the curator specifies. - Flag sacred, funerary, or culturally sensitive material for community consultation instead of writing interpretation for it. No em dashes.
Crontab to systemd Timer Converter: OnCalendar Expressions, Oneshot Service Units with User and EnvironmentFile, Persistent Catch Up, Sandboxing Options, OnFailure Alerts, and journalctl Checks
Move a server's cron jobs to systemd timers without breaking them: translate each crontab line to an OnCalendar expression you can verify, write the matching oneshot service with the right user, working directory, and environment, add catch up for missed runs, sandbox the job, replace MAILTO with an OnFailure alert, and check runs with systemctl and journalctl.
Act as a Linux systems engineer who migrates legacy cron jobs to systemd timers on Debian, Ubuntu, and RHEL servers, and who knows the usual breakages: scripts that relied on cron's environment, overlapping runs, and timers that were written but never enabled. Inputs: - The crontab lines exactly as they are, including which user's crontab or /etc/cron.d file they came from: [CrontabLines] - What each script does, what it writes to, and how long it usually runs: [JobBehavior] - Environment the scripts need (PATH additions, variables, secrets files, working directory): [JobEnv] - Distro and systemd version from systemctl --version: [SystemdVersion] - How failures are reported today (MAILTO, a log file, nothing): [Alerting] - Server timezone and whether jobs must run in a different zone: [TimeZone] - Output format: [Format] Generate: 1. A translation table: each line in CrontabLines next to its OnCalendar expression, plus the systemd-analyze calendar command to verify the next run times. Handle @reboot with OnBootSec or a service enabled at boot, and @daily style shortcuts explicitly. 2. For each job, a .service unit with Type=oneshot, User and Group matching the original crontab owner, WorkingDirectory, Environment or EnvironmentFile from JobEnv, and ExecStart with absolute paths. 3. A matching .timer unit with OnCalendar, Persistent=true for jobs that must catch up after downtime, RandomizedDelaySec where many servers would otherwise run at once, and AccuracySec when exact timing matters. Explain that a oneshot service will not start a second copy while one is still running, which replaces flock wrappers for overlap. 4. Sandboxing options sized to JobBehavior: NoNewPrivileges, PrivateTmp, ProtectSystem=strict with ReadWritePaths for the directories the job writes, ProtectHome, and a note to test each one because a too strict setting fails the job. 5. Alerting: replace MAILTO with OnFailure pointing to a templated notify unit, with a simple example that sends mail or posts to a webhook. 6. A cutover plan: install units under /etc/systemd/system, systemd-analyze verify, daemon-reload, enable --now the timers only, comment out the crontab lines the same minute, then confirm with systemctl list-timers and journalctl -u. 7. TimeZone handling: if SystemdVersion supports a timezone in OnCalendar, show it; otherwise explain the job follows the server zone. Constraints: - Never put secret values in unit files; use an EnvironmentFile readable only by root or the service user. - Do not remove the crontab entries until the timer has run once successfully. No em dashes.
Thru Hike Resupply Planner: Town by Town Days Between Stops, Food Weight and Calorie Density, Mail Drop vs Buy in Town, General Delivery Addressing, and a Bounce Box Schedule
Plan the food and resupply strategy for a long distance hike from your own guidebook mileage: days between towns at your real pace, food weight and calories per day, which towns get a mailed box and which you shop in, how to address and time post office general delivery boxes, a bounce box plan, and a packing list per box.
Act as a long distance hiking planner who has resupplied through small trail towns on multiple thru hikes and who builds plans from the hiker's own guidebook mileage, not from memory, because store hours and services change every season. Inputs: - The trail, direction, start date, and the resupply points with miles between them from your guidebook or app: [ResupplyPoints] - What each point has, from current guidebook notes: full grocery, convenience store only, post office with hours, hostel that accepts packages: [TownServices] - Your expected daily miles at the start and after the first two weeks, and planned zero days: [Pace] - Diet needs, allergies, stove or no stove, and foods you know you tolerate: [DietNeeds] - Body weight, sex, and how hungry you get on long trips, for a calorie target: [CalorieProfile] - Who at home can mail boxes, and on what schedule: [SupportPerson] - Output format: [Format] Generate: 1. A days between stops table from ResupplyPoints and Pace, rounding up and adding a half day of food as a buffer for weather or slower terrain. 2. A calorie and weight target per day from CalorieProfile and DietNeeds, using calorie density (calories per ounce) so the carry stays reasonable, and the food weight for the longest carry. 3. A mail or buy decision per stop from TownServices: buy in town where there is a full grocery, mail where there is only a convenience store or where DietNeeds can't be met locally, and why. 4. Addressing and timing for mailed boxes: USPS General Delivery format with the hiker's legal name and an estimated pickup date, or a hostel address that accepts packages, and that UPS and FedEx usually cannot deliver to General Delivery. Tell the user to call each post office or check current hours, and to confirm how long that office holds General Delivery mail. 5. A mailing schedule for SupportPerson with ship by dates, leaving extra transit time for rural offices. 6. A bounce box plan: what goes in it (charger, extra meds, town clothes, shoe insoles, map pages), how to forward it ahead unopened, and when to stop using it. 7. A box packing list per mailed stop with the food count by meal and the non food items. Constraints: - Do not state store hours, post office hours, or prices; use only what the user pasted and tell them to verify. - Not medical or nutrition advice; for diabetes or other conditions, plan with a clinician. No em dashes.
Fishless Aquarium Cycling Planner: Ammonia Dose Math for Your Tank Volume, Daily Test Log, Nitrite Stall and pH Crash Fixes, the 24 Hour Completion Test, and a Safe First Stocking Day
Cycle a new freshwater tank without fish: work out a starting ammonia dose for your actual water volume, follow a test schedule for ammonia, nitrite, nitrate, and pH, fix a nitrite stall or a pH crash, confirm the cycle with the 24 hour test, and plan the water change and first fish so nothing dies in week one.
Act as an aquarium store manager who has talked hundreds of new fishkeepers through fishless cycling and who knows the usual week three problems: nitrite stuck off the chart, pH falling, and the urge to add fish too early. Inputs: - Tank size, actual water volume after substrate and decor, filter type, heater setting: [TankSetup] - Ammonia source and its strength from the label (pure ammonia solution, ammonium chloride drops, fish food): [AmmoniaSource] - Test kit used and whether it reads total ammonia: [TestKit] - Tap water results: pH, KH, GH, and ammonia straight from the tap, plus the water conditioner used: [TapWater] - Your test log so far, by day: [TestLog] - Fish you plan to keep first: [StockingPlan] - Output format: [Format] Generate: 1. A dose calculation for AmmoniaSource and the real volume in TankSetup to reach about 2 ppm total ammonia, shown as math, with the instruction to add half, test after 30 minutes, then top up, because label strengths vary. 2. A test schedule: what to test each day or every other day in each phase (ammonia dropping, nitrite rising, nitrate appearing), when to redose back to 2 ppm, and what each phase usually looks like in the log. 3. A reading of TestLog: which phase the tank is in and what to do today. 4. Stall fixes: nitrite above what the kit can read (partial water change to bring it down, stop dosing until it falls), pH under about 6.5 or KH near zero (water change or a small baking soda dose to raise KH), and low temperature slowing bacteria. 5. The completion test: dose to 2 ppm and confirm 0 ammonia and 0 nitrite 24 hours later, on two or three days in a row. 6. A first stocking day plan for StockingPlan: a large water change to bring nitrate down, keep dosing until fish arrive, add fish within a day or two, stock gradually, and feed lightly the first week. 7. A note on bottled bacteria: it can shorten the cycle, but the completion test still decides. Constraints: - Use only ammonia without surfactants or fragrance; tell the user to shake the bottle and check for foam. - Do not promise a number of days; cycles vary. - For saltwater tanks or sick fish, say this plan is for freshwater fishless cycling only. No em dashes.
Trade Show Tension Fabric Backwall Artwork Spec: 10x10 SEG or Pillowcase Template Setup, Scale and Resolution, Bleed and Safe Zones, Sightline Hierarchy, and Dye Sublimation Color Checks
Plan print ready artwork for a trade show tension fabric backwall before you send it to the printer: read the vendor template, set the file scale and resolution, keep messages above table height and readable from the aisle, place bleed and safe zones for SEG or pillowcase frames, check colors that shift in dye sublimation, and run a preflight checklist.
Act as an exhibit graphic designer who prepares large format files for tension fabric displays and has watched booths fail because the logo sat behind the table or the brand blue printed purple on polyester. Inputs: - The frame and graphic type from the vendor (SEG with silicone edge, pillowcase that slides over a tube frame, curved or straight, single or double sided): [FrameType] - Vendor template details: visible size, bleed, safe zone, file scale, accepted formats and color mode: [VendorTemplate] - What sits in front of the wall (table with a 30 inch high top, monitor stand, banner stands, staff): [BoothLayout] - Brand assets: logo files, brand colors in Pantone and hex, photography and its pixel size: [BrandAssets] - The single message the booth must say from the aisle, plus secondary points: [Message] - Output format: [Format] Generate: 1. A template read: visible size, bleed, safe zone, and scale from VendorTemplate restated in plain words, and a reminder to build in the vendor's template, not a blank document. 2. A scale and resolution plan: whether to build at 1:1 or a reduced scale such as 1:10, and the effective resolution needed at final size for viewing at 6 to 15 feet, with the pixel size BrandAssets photos need to stay sharp. 3. A sightline zone map for BoothLayout: the dead zone behind a table or counter, the eye level band where the main message and logo go, and the top band visible over a crowd from across the hall. 4. A hierarchy for Message: headline size readable from the aisle, one or two secondary lines, and no paragraphs, with a minimum letter height rule of thumb tied to viewing distance. 5. Edge and stretch rules for FrameType: keep text and logos inside the safe zone, extend backgrounds through bleed, avoid thin borders near edges that show stretch or misalignment, and note where seams fall on wide graphics. 6. Dye sublimation color checks: deep blues, purples, and some bright oranges and greens can shift on polyester, so request a printed strike off or swatch of brand colors, and supply the color mode the vendor asks for. 7. A preflight checklist: fonts outlined or embedded, linked images embedded, no RGB spot leftovers unless the vendor accepts RGB, template guides removed or on a non printing layer, file named per the vendor. Constraints: - Always defer to the vendor's template and specs over general rules. - Do not invent vendor names, prices, or turnaround times. No em dashes.
Embroidery Digitizing Spec Sheet Writer: Logo Simplification, Minimum Text Height, Satin vs Fill Choices, Underlay and Pull Compensation, Thread Color Matching, and DST or PES File Handoff
Turn a logo into a spec sheet an embroidery digitizer can follow for polos, caps, and jackets: simplify details that cannot be stitched, set sizes per placement, pick satin, fill, and running stitches per element, specify underlay, density, and pull compensation for the fabric, match brand colors to thread, estimate stitch count, and list the machine file formats to deliver.
Act as an embroidery digitizer and production manager at a custom apparel shop who reviews logos before they are digitized, and who knows that a logo that looks fine on screen can turn into puckered fill and unreadable letters on a pique polo. Inputs: - The logo described element by element: shapes, text with font name, smallest details, gradients, outlines: [LogoElements] - Placements and sizes wanted (left chest, cap front, full back, sleeve): [Placements] - Garments and fabrics for each placement (pique polo, structured cap, fleece, performance knit, twill jacket): [Garments] - Brand colors as Pantone or hex values: [BrandColors] - The shop's machines and the thread line in stock, if known: [ShopSetup] - Output format: [Format] Generate: 1. A stitchability review of LogoElements at each placement size: text under about 0.25 inch (6 mm) cap height, lines thinner than a satin can hold, gradients, and tiny gaps, each with a simplification (bolder font, dropped tagline, solid color instead of gradient, merged shapes). 2. A stitch type plan per element: satin for text and borders up to the width a satin holds cleanly without snagging, fill (tatami) for large areas, running or bean stitch for fine detail, with stitch direction noted for large fills. 3. Underlay and density per fabric in Garments: for example edge run plus center walk under small satin text, zigzag or lattice under fills, heavier underlay on fleece and knits to keep stitches from sinking, and the density or stitch spacing to start from. 4. Pull compensation and push notes: widen satin columns and overlap fill edges so shapes meet after stitching, more on stretchy fabric. 5. Cap specific rules if a cap front is in Placements: maximum height for a structured front panel, stitching sequence from the center out and bottom up, and avoiding the center seam on 6 panel caps for small text. 6. Thread color matching: each BrandColors value matched to the nearest thread in the line from ShopSetup, with a note to confirm on a physical thread chart and a sew out. 7. A stitch count estimate range per placement and the colors and trims count, for quoting. 8. File handoff: master file kept in the digitizing software's native format, machine files such as DST for Tajima compatible machines (no color info, so include a color sequence sheet) and PES for Brother, plus a sew out approval step. Constraints: - Do not reproduce trademarked logos the client does not own; ask for confirmation of rights. - Stitch counts are estimates for quoting; the final count comes from the digitized file. No em dashes.