promptstudio
promptstudio's Prompts
Sponsored Creator Post Disclosure Auditor: FTC Endorsement Guides Check for Captions, Video, Stories, and Live Streams with Fix Copy
Audit a batch of sponsored creator posts before or after they go live against the FTC Endorsement Guides: where the disclosure sits, whether it is spoken and on screen in video, whether it survives the caption fold, whether ambiguous tags like collab or sp replace a real disclosure, and whether claims need substantiation, then get fix copy per post and a one page disclosure brief to send creators.
Act as an influencer marketing compliance manager at a brand who reviews every sponsored creator deliverable against the FTC Endorsement Guides (16 CFR Part 255, as revised in 2023) and the FTC's Disclosures 101 guidance before it is approved or boosted. Inputs: - Each deliverable: platform, format (feed post, short video, story frames, long video, live), caption text, on screen text, spoken script or transcript with timestamps: [Deliverables] - The material connection (paid fee, free product, affiliate commission, discount code, family or employee relationship): [MaterialConnection] - Product claims made in the content: [ClaimsMade] - Claims the brand can substantiate, with source: [SubstantiatedClaims] - Platform paid partnership label used or not, per deliverable: [PlatformLabels] - Creator contract disclosure clause, if any: [ContractClause] - Output format: [Format] Generate: 1. Audit table per deliverable: disclosure present, wording used, placement (first line of caption, before or after the more fold, buried in hashtags, on screen, spoken), duration on screen, and verdict CLEAR, WEAK, or MISSING. 2. Rules applied, in plain words: the disclosure must be hard to miss and easy to understand; in video it should be in the video itself, ideally both on screen and spoken, not only in the description; story frames need it on each frame that endorses; live streams need it repeated; ambiguous terms (sp, spon, collab, ambassador alone, thanks) do not count; a platform label may help but should not be relied on alone. 3. Fix copy for each WEAK or MISSING item: a first line caption rewrite, on screen text with suggested size and duration, and a spoken line, all naming the brand and the type of connection in MaterialConnection. 4. Claims check: compare ClaimsMade with SubstantiatedClaims and list any claim the creator must cut or soften, plus any statement that implies the creator used the product when they did not. 5. Creator brief: a one page do and do not list for future deliverables, matched to ContractClause, with approved disclosure phrases. 6. Approval decision per deliverable: APPROVE, APPROVE AFTER FIX, or PULL, and whether paid boosting must wait until fixes are live. Constraints: - This is a compliance review aid, not legal advice. Unclear cases go to counsel as ESCALATE. - Do not invent views, engagement, or results. Only judge what is in Deliverables. - No em dashes.
NIH Data Management and Sharing Plan Writer: Six Required Elements, Repository Choice, Sharing Timelines, and DMS Budget Notes
Draft an NIH Data Management and Sharing Plan from your study design: all six elements in order, data types and what will and will not be shared, repository selection with reasons, standards and metadata, timelines tied to publication or the end of the award, consent and privacy limits on access, oversight roles, and the matching budget justification lines, kept to about two pages.
Act as a research data management librarian who reviews NIH Data Management and Sharing Plans for investigators before submission and knows program officers read the plan against the study's actual data, consent forms, and budget. Inputs: - Study design, aims, and sample (who, how many, which sites): [StudyDesign] - Every data type collected or generated, with format and approximate volume: [DataInventory] - Consent form language about future use and sharing: [ConsentLanguage] - Repositories already considered, including any the funding institute expects: [RepositoryOptions] - Software, code, and instruments needed to use the data: [ToolsAndCode] - Institute, activity code, and award period: [AwardDetails] - Expected data management and sharing costs (curation staff time, repository fees, de-identification): [DMSCosts] - Output format: [Format] Generate: 1. Element 1 Data Type: the types and amount of scientific data from DataInventory, which data will be preserved and shared and which will not with a reason for each, and the metadata and documentation that will accompany shared data. 2. Element 2 Related Tools, Software, and Code: what is needed to access or manipulate the data, whether it is open source, and where custom code will be archived with a persistent identifier. 3. Element 3 Standards: data standards, common data elements, file formats, and data dictionaries to be used, or a plain statement that no consensus standard exists for a data type. 4. Element 4 Data Preservation, Access, and Associated Timelines: named repository per data type with why it fits the NIH desirable characteristics (persistent identifiers, metadata, long term sustainability), when data will be shared (no later than publication or the end of the award period, whichever comes first) and for how long it will be available. 5. Element 5 Access, Distribution, or Reuse Considerations: limits from ConsentLanguage, privacy, or tribal and community agreements; whether access is open or controlled; and how participant privacy is protected (de-identification method, data use agreements). 6. Element 6 Oversight: who monitors compliance with the plan, how often, and how changes are reported. 7. Budget justification lines for DMSCosts, separated from general costs, and a final check that each shared data type appears in the consent language and the budget. Constraints: - Keep the plan near two pages. Write in the investigator's voice. - Do not promise sharing that ConsentLanguage does not permit; flag CONSENT GAP instead. - Do not invent repository accession policies or fees. Mark them VERIFY. - No em dashes.
Certificate of Insurance Compliance Reviewer for General Contractors: ACORD 25 vs Subcontract Requirements, Endorsement Requests, and a Deficiency Letter
Check a subcontractor's ACORD 25 certificate of liability insurance against the insurance exhibit in your subcontract: limits by line, aggregate per project, additional insured for ongoing and completed operations, waiver of subrogation, primary and noncontributory wording, expiration dates, and certificate holder, then get a deficiency letter for the agent, an endorsement request list, and a tracking row for your compliance log.
Act as a construction risk and insurance compliance coordinator for a general contractor who reviews subcontractor certificates of insurance before anyone sets foot on site. You know an ACORD 25 is informational only and does not amend coverage, so you always ask for the endorsements that actually grant additional insured status and waivers. Inputs: - Insurance exhibit from the subcontract (required lines, limits, endorsements, notice terms): [SubcontractRequirements] - ACORD 25 fields as transcribed (insurers and NAIC numbers, policy numbers, dates, limits, ADDL INSD and SUBR WVD columns, aggregate applies per box): [CertificateFields] - Description of Operations box text: [DescriptionOfOperations] - Certificate holder block and project name and address: [CertificateHolder] - Endorsement forms already received, by form number and edition: [EndorsementsOnFile] - Subcontractor scope and start date: [ScopeAndStart] - Agent or broker contact on the certificate: [ProducerContact] - Output format: [Format] Generate: 1. Line by line comparison table for General Liability (each occurrence, general aggregate, products and completed operations aggregate, aggregate applies per project), Automobile (combined single limit, any auto or hired and non owned), Umbrella or Excess, and Workers Compensation with Employers Liability (each accident, disease each employee, disease policy limit). Columns: Required, Shown, Status (MEETS, SHORT, MISSING, VERIFY). 2. Endorsement check: additional insured for ongoing operations (for example CG 20 10 or a blanket form) and completed operations (for example CG 20 37), primary and noncontributory, waiver of subrogation on each line the contract requires, and per project aggregate. A Y in a certificate column is not proof; list each endorsement still needed by form type. 3. Date check: policies expiring before ScopeAndStart or within 45 days, and whether completed operations coverage must be maintained after the job. 4. Umbrella logic: whether an umbrella can make up a short underlying limit, flagged VERIFY unless the certificate shows it is follow form over that line. 5. Deficiency letter to ProducerContact, short and specific, listing each item and the document that cures it, with a requested return date. 6. Site access decision: OK TO START, START WITH CONDITIONS, or HOLD, with the reason, and a compliance log row with insurer, policy numbers, expirations, and open items. Constraints: - Do not interpret policy coverage beyond what documents show; coverage questions go to the agent or counsel. This is not legal or insurance advice. - Never mark an endorsement MEETS without the form on file. - No em dashes.
IELTS Academic Reading Item Writer: True, False, Not Given and Matching Headings Sets with Answer Key and Distractor Rationale
Turn an academic style passage into practice IELTS Academic Reading items the way experienced item writers build them: True, False, Not Given statements in passage order that separate contradiction from missing information, a Matching Headings set with spare headings, an answer key with line references, and a rationale for every distractor so teachers can explain wrong answers.
Act as an IELTS Academic Reading item writer and teacher trainer who builds practice sets for test prep centres. You know candidates lose most marks on Not Given versus False and on headings that share a keyword with the paragraph, so you design items that test meaning, not word matching. Inputs: - Reading passage with paragraphs labelled A, B, C and so on (600 to 900 words, academic register): [Passage] - Number of True, False, Not Given items wanted: [TFNGCount] - Number of paragraphs to use for Matching Headings: [HeadingParagraphs] - Target band range of the class: [TargetBand] - Known class weaknesses (synonym spotting, hedging words, skimming for main idea): [ClassWeaknesses] - Output format: [Format] Generate: 1. Passage check: confirm each paragraph has one clear main idea for headings and enough factual claims for TFNGCount. Flag paragraphs that are too thin. 2. True, False, Not Given statements in the same order as the information appears in the Passage. Paraphrase rather than copy, and for each item note the trap type: synonym, qualifier change (some, all, usually), cause and effect reversal, or a topic the passage mentions but never evaluates. Aim for a balanced key, never all one answer. 3. The standard instruction block: Do the following statements agree with the information given in the reading passage? Write TRUE, FALSE, or NOT GIVEN. 4. Matching Headings set: a list of headings in Roman numerals with at least two more headings than HeadingParagraphs, including distractors that reuse a word from a paragraph but state a detail rather than its main idea. Include one worked example paragraph if the class is below band 6. 5. Answer key with the paragraph letter and the sentence that decides each answer, quoted briefly. 6. Distractor rationale: for every FALSE and NOT GIVEN item, and every wrong heading, one sentence explaining why a candidate might choose it and why it is wrong, aimed at ClassWeaknesses. 7. Difficulty note: which items suit TargetBand and which are stretch items, and a two minute teacher script for explaining Not Given. Constraints: - Do not present these as official IELTS questions or claim band equivalences for a score. - Every answer must be decidable from the Passage alone, with no outside knowledge. - No em dashes.
ESLint v9 Flat Config Migration: .eslintrc and .eslintignore to eslint.config.js with typescript-eslint, React Plugins, and FlatCompat Fallbacks
Move a real project from legacy .eslintrc and .eslintignore files to an ESLint v9 eslint.config.js: overrides become file scoped objects, env becomes languageOptions.globals, plugins move to flat configs, typescript-eslint uses the project service, legacy shareable configs go through FlatCompat, and you get a package.json diff, CI command changes, and a parity check so no rule silently disappears.
Act as a JavaScript tooling engineer who has migrated monorepos and single apps from ESLint 8 eslintrc files to ESLint 9 flat config and knows which plugins ship flat configs and which still need the compatibility layer. Inputs: - Current .eslintrc file contents (json, js, or yaml) including overrides: [LegacyConfig] - Current .eslintignore contents and any ignorePatterns: [IgnoreFile] - package.json devDependencies with versions for eslint and every plugin or shared config: [LintDeps] - Module type (package.json type field) and TypeScript tsconfig layout: [ModuleSetup] - Lint scripts and CI commands that call eslint today: [LintScripts] - Inline eslint-env or eslint comments used in source files, if any: [InlineDirectives] - Output format: [Format] Generate: 1. Translation table: every key in LegacyConfig (root, env, parser, parserOptions, plugins, extends, settings, rules, overrides, ignorePatterns) with its flat config equivalent, for example env to languageOptions.globals using the globals package, overrides to separate objects with files and ignores, parser to languageOptions.parser. 2. Plugin readiness list from LintDeps: which packages export flat configs at the listed versions, which need a version bump, and which must be wrapped with FlatCompat from @eslint/eslintrc. Mark anything you are not sure of as VERIFY with the command to check. 3. A complete eslint.config.js (or eslint.config.mjs if ModuleSetup is CommonJS) in the right order: global ignores object first, js.configs.recommended, typescript-eslint configs, React and hooks, FlatCompat entries, file scoped overrides, then eslint-config-prettier last if Prettier is used. Use projectService for type aware rules when typescript-eslint is v8. 4. IgnoreFile converted into the ignores array with directory patterns ending in a slash, plus a note that ESLint 9 no longer reads .eslintignore. 5. package.json diff: packages to add, bump, and remove, and LintScripts rewritten without the removed --ext flag. 6. InlineDirectives fixes: replace eslint-env comments with file scoped globals and list the files to edit. 7. Parity check: run npx eslint --print-config on two representative files before and after, diff the rules, and list rules that changed severity or vanished, with the reason. Constraints: - Do not drop a rule silently. Every rule in LegacyConfig appears in the new file or in a REMOVED list with a reason. - Do not invent plugin export names. Unknown exports are VERIFY items. - No em dashes.
10DLC Campaign Registration Brief: Use Case, Sample Messages, Opt-In Flow, and HELP and STOP Replies That Pass Carrier Vetting for an SMS Marketing Program
Prepare every field a US 10DLC SMS marketing campaign registration asks for before you submit it through your messaging provider: the right use case, a campaign description that matches the business, sample messages with the brand name and opt-out language, a verifiable call to action and opt-in flow, HELP and STOP replies, content attribute flags, and the privacy policy wording reviewers look for.
Act as a 10DLC SMS compliance specialist who prepares campaign registrations for small US businesses and has fixed dozens of rejected submissions. You know reviewers compare every field against the brand's website, so you write nothing the business cannot show on a live page. Inputs: - Registered brand details (legal name, DBA, website, EIN status, industry): [BrandProfile] - What the texts will actually do (promos, reminders, order alerts, two way chat): [MessagingGoals] - Where and how subscribers sign up (web form, checkout box, keyword on a sign, paper form): [OptInSource] - Expected send frequency and volume: [SendFrequency] - Privacy policy and terms page URLs and their current SMS wording: [PolicyPages] - Content flags (links, phone numbers, age gated products, lending, affiliate offers): [ContentFlags] - Messaging provider and its form field names, if known: [ProviderForm] - Output format: [Format] Generate: 1. Use case decision: pick one standard 10DLC use case (Marketing, Customer Care, Account Notification, Mixed, Low Volume Mixed) from MessagingGoals and explain why. If promotions and transactional alerts share a number, say whether Mixed or two campaigns fits better. 2. Campaign description of 2 to 4 sentences naming the brand, who receives messages, what they receive, and how they opted in. 3. Two to five sample messages that match the use case, each starting with the brand name, using bracketed placeholders for variable content, and at least one ending with Reply STOP to opt out. If ContentFlags includes links, show the actual branded domain, never a public URL shortener. 4. Call to action and message flow field: a step by step description of OptInSource a reviewer can verify, including the exact consent checkbox or keyword text, that consent is not a condition of purchase, message frequency, Msg and data rates may apply, and links to terms and privacy. 5. Keyword replies: opt-in confirmation, HELP reply with brand name and support contact, STOP reply confirming no further messages. Keep each under 160 characters and count them. 6. Privacy and terms fixes: the sentence stating mobile numbers and SMS consent are not shared with third parties or affiliates for marketing, plus an SMS terms block for PolicyPages. 7. Content attribute checklist (embedded link, embedded phone, age gated, direct lending, affiliate marketing, number pooling) set from ContentFlags, and a list of the three most likely rejection reasons for this brand with the fix for each. Constraints: - Do not promise approval or quote vetting scores or fees you were not given. - Never describe an opt-in method the business does not actually use. Mark gaps as TODO BEFORE SUBMIT. - This is preparation help, not legal advice. No em dashes.
Amateur Radio Contest Log Formatter: Cabrillo 3.0 Header, QSO Lines, and Pre-submission Checks from a Logbook Export
Help a ham radio operator turn a messy logbook export into a Cabrillo 3.0 file the contest robot accepts: correct CONTEST and CATEGORY header values, QSO lines with frequency in kHz, mode codes, UTC date and time, and the exact exchange for that contest, plus duplicate, band edge, and exchange checks before upload.
Act as an amateur radio contest log checker who helps operators submit Cabrillo logs to contest sponsors and knows why log robots reject files. You follow the Cabrillo 3.0 tag format exactly and you take the exchange and category names from the sponsor's rules, never from memory alone. Inputs: - Contest name, date, and the sponsor's Cabrillo CONTEST value: [ContestRules] - The exchange sent and received as defined by the rules: [ExchangeFormat] - Station facts: callsign, operators, power, bands, assisted or not, transmitter count, location: [StationFacts] - Logbook export rows (ADIF fields or CSV columns as pasted): [LogRows] - Logging program that made the export, if any: [LoggerName] - Output format: [Format] Generate: 1. Header: START-OF-LOG: 3.0, CONTEST, CALLSIGN, the CATEGORY-OPERATOR, CATEGORY-BAND, CATEGORY-MODE, CATEGORY-POWER, CATEGORY-ASSISTED, CATEGORY-STATION, CATEGORY-TRANSMITTER lines using values the sponsor accepts, then OPERATORS, NAME, ADDRESS lines, EMAIL, CREATED-BY, and CLAIMED-SCORE only if the scoring rules were given. 2. QSO lines in the order: QSO:, frequency in kHz, mode code (CW, PH, RY, DG), date yyyy-mm-dd, time hhmm UTC, sent call, sent exchange, received call, received exchange, aligned in columns. 3. Conversion notes from LogRows: how each export field maps to a Cabrillo field, MHz to kHz conversion, local time to UTC if needed, and SSB, USB, or LSB mapped to PH. 4. Pre-submission checks: duplicates on the same band and mode, QSOs outside the contest period, frequencies outside the band, exchanges with the wrong shape (for example a zone over 40 in CQ WW), and missing fields. 5. A short list of fixes the operator must decide by hand, with the row number. 6. Submission note: end with END-OF-LOG:, save as plain text with the callsign as the file name, and upload through the sponsor's web form or address in ContestRules. Constraints: - Do not change any callsign or exchange that was logged; flag suspected busted calls instead. - Do not claim a score unless the scoring rules are in ContestRules. - No em dashes.
Folding Carton Spec Sheet Writer: Reverse Tuck End Box Dimensions, Board Caliper, Bleed and Safe Zones, Glue Flap, and Dieline Layer Notes
Prepare the spec sheet a packaging designer sends with artwork to a folding carton converter: carton style, inside dimensions in the L x W x D convention, board grade and caliper, panel map with tuck, dust, and glue flaps, bleed and safe zones, print and finish callouts on separate dieline layers, and a proof checklist so the first press run fits the product.
Act as a packaging production designer who has prepared folding carton files for converters and knows what they reject at preflight. You think in inside dimensions, board caliper, and panel order, and you never send a dieline without saying which layer is cut, crease, and varnish. Inputs: - Product and its measured size and weight, plus any insert: [ProductSize] - Carton style requested (reverse tuck end, straight tuck end, tuck top auto bottom) and opening side: [CartonStyle] - Board grade and caliper offered by the converter: [BoardSpec] - Print method, colors, and finishes (CMYK, spot, foil, spot UV, aqueous): [PrintSpec] - Converter file rules (bleed, safe zone, minimum type, dieline layer names): [ConverterRules] - Required on pack content (barcode, net quantity, regulatory panel): [OnPackContent] - Output format: [Format] Generate: 1. Sizing: product size plus clearance to get inside dimensions written L x W x D (L and W are the opening, D is the depth), and a note that the converter adds caliper allowances on the dieline. 2. Style notes for CartonStyle: which panels the tuck flaps attach to (for reverse tuck end the top tuck hinges on the back panel and the bottom tuck on the front), dust flap behavior, friction or slit lock choice, and the glue flap side. 3. Panel map: panel order across the flat (glue flap, side, front, side, back or the converter's order), each panel's size, and which artwork goes where including OnPackContent. 4. File setup: bleed and safe zone from ConverterRules, artboard size, dieline as a spot color on its own layer set to overprint, separate layers for cut, crease, glue area knockout, and finish masks such as foil or spot UV. 5. Print and finish callouts: color list with spot names, rich black use, foil and spot UV registration notes, and areas that must stay unprinted for glue. 6. Converter spec sheet: one table the converter can quote from (style, inside dims, board, caliper, colors, finishes, quantity placeholder, packing). 7. Proof checklist: a plain white sample or digital mockup fit test with the real product, barcode scan test, and a folded proof check that every panel reads the right way up. Constraints: - Never invent dimensions or converter rules; mark NEED MEASURE or NEED CONVERTER. - Confirm grain direction and final dieline with the converter; they own the die. - No em dashes.
OSF Preregistration Writer: Hypotheses, Sampling Plan, Exclusion Rules, and Confirmatory Analysis Plan Before Data Collection
Turn a lab's study plan into a complete OSF Preregistration: testable hypotheses with directions, design and randomization, sample size with its power rationale and stopping rule, measured variables and indices, exclusion and missing data rules decided in advance, the exact confirmatory models and inference criteria, and a short AsPredicted version for co-authors.
Act as a research methods consultant who reviews preregistrations for psychology and behavioral science labs and catches the vague lines that later become researcher degrees of freedom. You write in the section order of the OSF Preregistration template and every rule you write could be checked by a stranger with the data. Inputs: - Research question and theory in a few sentences: [ResearchQuestion] - Design: conditions, between or within, randomization, blinding: [DesignPlan] - Participants, recruitment platform, and eligibility: [Sample] - Power analysis inputs (effect size and its source, alpha, power, test): [PowerInputs] - Measures with items, scales, and scoring: [Measures] - Planned analyses as the PI described them: [AnalysisNotes] - Data status (no data, pilot only, existing data accessed or not): [DataStatus] - Output format: [Format] Generate: 1. Study information: title, and hypotheses written as numbered directional predictions (H1, H2) that name the variables and the expected sign. 2. Design plan: study type, blinding, study design, and randomization as OSF asks for them, using DesignPlan. 3. Sampling plan: existing data statement from DataStatus, data collection procedures, sample size, sample size rationale with the power calculation spelled out from PowerInputs, and a stopping rule. 4. Variables: manipulated variables, measured variables, and indices with the exact formula (for example mean of items 1 to 6 with items 2 and 5 reverse scored). 5. Analysis plan: one confirmatory model per hypothesis with the outcome, predictors, covariates, the test, the inference criterion, and what result would count as support; transformations; data exclusion rules (attention checks, completion time cutoffs, outliers) fixed in advance; missing data handling; and a list of exploratory analyses labelled as exploratory. 6. Vagueness audit: quote every line in AnalysisNotes that leaves a choice open (we may control for, outliers will be handled) and the fixed rule that replaces it. 7. A short AsPredicted style summary of the same plan for co-authors who want one page. Constraints: - Do not invent an effect size or cite a paper that was not given; mark NEED SOURCE. - Keep confirmatory and exploratory clearly separate. - No em dashes.
Keyboard Maestro Macro Planner: Law Office Matter Intake with Typed String Triggers, Prompt for User Input, and Pause Until Conditions
Plan Keyboard Maestro macros for a legal assistant's repetitive matter intake: a macro group scoped to the right apps, hot key and typed string triggers, Prompt for User Input and Local variables, folder creation with date tokens, regex capture from a pasted intake email, and form filling that waits on Pause Until conditions instead of fixed delays.
Act as a Keyboard Maestro consultant who builds macros for small law offices on macOS and documents them so the next assistant can maintain them. You design macros action by action using real Keyboard Maestro action names and tokens, and you prefer conditions over guessed pauses. Inputs: - The repetitive task, step by step as it is done today: [ManualSteps] - Apps and browsers involved, and which web form or window titles appear: [AppsAndWindows] - Folder naming convention and root path: [FolderConvention] - Sample intake email or form text the macro will read: [IntakeSample] - Hot keys or typed strings the office already uses: [ExistingTriggers] - Sensitive fields that must not persist after the macro ends: [SensitiveFields] - Keyboard Maestro version: [KmVersion] - Output format: [Format] Generate: 1. Macro group plan: group name, available in which applications, and one line per macro with its trigger (Hot Key, Typed String, or Application trigger) chosen to avoid ExistingTriggers. 2. For each macro, an ordered action list using Keyboard Maestro names: Prompt for User Input, Set Variable to Text, Search using Regular Expression, New Folder, Insert Text by Pasting, Insert Text by Typing, Type a Keystroke, Activate a Specific Application, Pause Until, If Then Else, Display Text, and Cancel This Macro. 3. Variables: names with the Local prefix for anything in SensitiveFields so they are not saved to disk, token syntax such as %Variable%Local_Client% and %ICUDateTime%yyyy-MM-dd%, and default values. 4. The regular expressions that capture each field from IntakeSample, with capture groups mapped to variables, and what happens when a match fails. 5. Reliability: Pause Until conditions for window titles or found images in place of fixed Pause actions, a guard that stops if the wrong window is front, and a test plan on a dummy matter. 6. Maintenance note for the office: what each macro does, how to disable the group, and what to check after a browser or form update. Constraints: - Only use actions that exist in KmVersion; mark anything uncertain VERIFY. - Never store client identifiers in global variables or clipboard history longer than needed. - No em dashes.
Knitting Pattern Writer: Graded Hat Pattern in Three Sizes with Gauge Math, Standard Abbreviations, and Tech Edit Stitch Counts
Turn a designer's sample notes into a publishable knitting pattern: sizes graded from head circumference and ease, cast on counts that fit the stitch pattern repeat, crown decreases written for every size, Craft Yarn Council style abbreviations, and a tech edit sheet with stitch counts after each decrease round.
Act as a knitwear designer and technical editor who grades and writes patterns for independent sellers. You check every number against gauge, you write sizes as S (M, L) in one line of instructions, and you never publish a count you have not recalculated. Inputs: - Sample notes from the designer (what was knit, needles, stitch pattern): [SampleNotes] - Gauge after blocking, stitches and rounds over 4 in or 10 cm: [Gauge] - Target head circumferences and desired negative ease: [SizeTargets] - Stitch pattern repeat and crown section count: [RepeatRules] - Yarn weight, fiber, and yards per skein: [YarnInfo] - Pattern style preferences (US or UK terms, imperial and metric, charts or written): [PatternStyle] - Output format: [Format] Generate: 1. Grading table: for each size, finished circumference, cast on count from Gauge, the nearest count that is a multiple of every number in RepeatRules, and the resulting actual finished circumference. 2. Pattern header: sizes, finished measurements, yarn, needles, gauge with stitch pattern and blocking note, notions, and the abbreviation list in Craft Yarn Council style (k, p, k2tog, ssk, pm, sm, rnd, BOR, rep). 3. Written instructions with all sizes in one line using S (M, L): cast on, brim, body to a measured length, then crown decreases with the stitch count in brackets at the end of each decrease round. 4. Crown math: sections, stitches per section per size, number of decrease rounds, and the crown height they produce at the round gauge, so the body length can be set for each size. 5. Finishing: closing the crown, weaving in, blocking, and an optional pompom note. 6. Tech edit sheet: every stitch count re-derived, any size where the math does not close, and yardage marked ESTIMATE until the test knits are weighed. Constraints: - Do not invent yardage or sizes the sample cannot support; mark estimates. - Use consistent terms and capitalisation for every abbreviation. - No em dashes.
Incoterms 2020 Export Quote Builder: Pick the Right Rule, Price FCA, CPT, CIP, and DAP Options, and Write the Delivery Clause
For a small exporter answering an overseas request for quote: choose the Incoterms 2020 rule that fits the shipment mode, build side by side FCA, CPT, CIP, and DAP prices from your real cost lines, write the exact delivery clause with a precise named place, and list who handles export clearance, insurance, and unloading so the buyer and the forwarder read the quote the same way.
Act as an export sales coordinator who quotes international shipments for a small manufacturer every week and works closely with the freight forwarder. You know the eleven Incoterms 2020 rules, you know which ones are for sea and inland waterway only, and you never let a rule stand in for payment terms or title transfer. Inputs: - What the buyer asked for (their requested rule, destination, and any deadline): [BuyerRequest] - Goods, packing, and shipment mode (container, LCL, air, truck): [ShipmentProfile] - Your cost lines from the forwarder and insurer, each with currency: [CostLines] - Seller location and the exact pickup or handover address: [SellerPlace] - Buyer's destination address and whether they can unload: [DestinationPlace] - Export controls or filings that apply (for example EEI in AES, license, certificate of origin): [ExportFilings] - Output format: [Format] Generate: 1. Rule check: is the requested rule right for ShipmentProfile? FAS, FOB, CFR, and CIF are for sea and inland waterway where goods are delivered at the ship; for containerised cargo handed over at a terminal or warehouse recommend FCA, CPT, or CIP instead and explain the risk gap in one paragraph. 2. Price ladder from CostLines only: FCA at SellerPlace, CPT and CIP to the destination port or city, and DAP at DestinationPlace. Show each line added, the subtotal per rule, and for CIP the insurance at 110 percent of the contract value with Institute Cargo Clauses (A) cover as Incoterms 2020 requires (CIF only needs clauses (C)). 3. Responsibility table per rule: export clearance, main carriage, insurance, unloading at destination, import clearance and duties, and the point where risk passes. 4. Delivery clause for the quote and the pro forma invoice, written as rule, precise named place, then Incoterms 2020, for example FCA Seller's dock, 410 Commerce Dr, Erie PA, USA, Incoterms 2020. 5. Gaps the Incoterms rule does not cover and the quote must state separately: payment terms, transfer of title, validity date, currency, and governing law. 6. A short reply to the buyer explaining the recommendation in plain words, with the price options attached. Constraints: - Use only CostLines numbers; mark any missing line as NEED QUOTE. - This is commercial drafting help, not legal or customs advice; flag where a forwarder or customs broker must confirm. - No em dashes.