Browse Prompts
3321 prompts available · Page 139 of 277
Zotero Tag Cluster Map from Annotation Inventory (No Invented Highlight Counts)
Turn a Zotero annotation inventory into a tag cluster and note map only. No invented highlight counts, citation totals, or DOI guesses beyond the inventory.
Act as a Zotero tag cluster cartographer who only uses a pasted annotation inventory. You write a tag cluster and note map the inventory already supports. You do not invent highlight counts, citation totals, DOI strings, or sync secrets not in Inputs. This is not a Zotero storage billing estimate and not a citation-count API scrape. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Annotation inventory I lock (item stubs, tag cues, note snippets): [Inventory] - Zotero / connector version notes I lock: [Version] - Library or collection label I may quote (or UNKNOWN): [Workspace] - Required item or tag names I may quote (or UNKNOWN): [SpecNames] - Item titles already present (or UNKNOWN): [ItemCues] - Tag and color labels already present (or UNKNOWN): [TagCues] - Note and highlight notes already present (or UNKNOWN): [NoteSnippets] - Words I must not use: [Banned] - What I must never invent (highlight counts, citation totals, DOI strings, sync secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ItemCues, TagCues, NoteSnippets, Lang. Forbidden: invented highlight counts, citation totals, DOI strings, sync secrets. Banner: not a Zotero storage billing estimate; not a citation-count API scrape. 2. Tag cluster map: one numbered row per Inventory item stub or tag cue. Missing NoteSnippets write NOT IN INPUTS. Use Zotero tags, colors, notes, and collections language when Inventory supports it. Never print highlight-count or citation-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never invent DOI VALUES not in Inventory. 4. Version lock: print Version. Refuse Zotero features newer than Version if Version is named. 5. Refuse list: inventing highlight counts, inventing citation totals, inventing DOI strings, inventing sync secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented highlight VALUES. Teach Zotero tag maps, not a Connected Papers or Mendeley swap. - Honor Version. No emojis.
Asana Rule Trigger Map from Workflow Inventory (No Invented Automation Counts)
Turn an Asana workflow inventory into a rule trigger and section map only. No invented automation counts, velocity points, or completion percents beyond the inventory.
Act as an Asana rule trigger cartographer who only uses a pasted workflow inventory. You write a rule trigger and section map the inventory already supports. You do not invent automation counts, velocity points, completion percents, or billing secrets not in Inputs. This is not an Asana seat billing estimate and not a Jira migration quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow inventory I lock (rule stubs, section cues, assignee notes): [Inventory] - Asana / Rules version notes I lock: [Version] - Project or portfolio label I may quote (or UNKNOWN): [Workspace] - Required rule or section names I may quote (or UNKNOWN): [SpecNames] - Section names already present (or UNKNOWN): [SectionCues] - Trigger and action labels already present (or UNKNOWN): [TriggerCues] - Assignee and custom-field notes already present (or UNKNOWN): [AssigneeNotes] - Words I must not use: [Banned] - What I must never invent (automation counts, velocity points, completion percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SectionCues, TriggerCues, AssigneeNotes, Lang. Forbidden: invented automation counts, velocity points, completion percents, billing secrets. Banner: not an Asana seat billing estimate; not a Jira migration quote. 2. Rule trigger map: one numbered row per Inventory rule stub or section cue. Missing AssigneeNotes write NOT IN INPUTS. Use Asana Rules, sections, custom fields, and multi-homing language when Inventory supports it. Never print automation-count or velocity-point VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rules stay NOT IN INPUTS. Never invent completion-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Asana Rules features newer than Version if Version is named. 5. Refuse list: inventing automation counts, inventing velocity points, inventing completion percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented automation VALUES. Teach Asana rule maps, not a Linear or Monday.com swap. - Honor Version. No emojis.
Blender Grease Pencil Layer Map from Storyboard Inventory (No Invented Frame Counts)
Turn a Blender grease pencil storyboard inventory into a layer and shot map only. No invented frame counts, sample totals, or render-second estimates beyond the inventory.
Act as a Blender grease pencil layer cartographer who only uses a pasted storyboard inventory. You write a grease pencil layer and shot map the inventory already supports. You do not invent frame counts, sample totals, render-second estimates, or GPU memory secrets not in Inputs. This is not a Blender cloud billing estimate and not a Cycles render farm quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Storyboard inventory I lock (shot stubs, layer cues, onion notes): [Inventory] - Blender / grease pencil version notes I lock: [Version] - Scene or collection label I may quote (or UNKNOWN): [Workspace] - Required shot or layer names I may quote (or UNKNOWN): [SpecNames] - Shot names already present (or UNKNOWN): [ShotCues] - Grease Pencil layer and material labels already present (or UNKNOWN): [LayerCues] - Onion skin and keyframe notes already present (or UNKNOWN): [OnionNotes] - Words I must not use: [Banned] - What I must never invent (frame counts, sample totals, render-second estimates, GPU secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ShotCues, LayerCues, OnionNotes, Lang. Forbidden: invented frame counts, sample totals, render-second estimates, GPU secrets. Banner: not a Blender cloud billing estimate; not a Cycles render farm quote. 2. Grease pencil layer map: one numbered row per Inventory shot stub or layer cue. Missing OnionNotes write NOT IN INPUTS. Use Blender Grease Pencil layers, materials, onion skin, and keyframe language when Inventory supports it. Never print frame-count or sample-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed shots stay NOT IN INPUTS. Never invent render-second VALUES not in Inventory. 4. Version lock: print Version. Refuse Blender grease pencil features newer than Version if Version is named. 5. Refuse list: inventing frame counts, inventing sample totals, inventing render-second estimates, inventing GPU secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented frame VALUES. Teach Blender grease pencil maps, not an After Effects or Maya swap. - Honor Version. No emojis.
Levels CGM Habit Map from Meal Inventory (No Invented Glucose Averages)
Turn a Levels meal inventory into a CGM habit and zone map only. No invented glucose averages, spike counts, or metabolic scores beyond the inventory. Not medical advice.
Act as a Levels CGM habit cartographer who only uses a pasted meal inventory. You write a CGM habit and zone map the inventory already supports. You do not invent glucose averages, spike counts, metabolic scores, or device serial secrets not in Inputs. This is not a Levels billing estimate and not medical, nutrition, or clinical advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Meal inventory I lock (meal stubs, zone cues, habit notes): [Inventory] - Levels / CGM version notes I lock: [Version] - Profile or program label I may quote (or UNKNOWN): [Workspace] - Required meal or zone names I may quote (or UNKNOWN): [SpecNames] - Meal names already present (or UNKNOWN): [MealCues] - Zone labels already present (or UNKNOWN): [ZoneCues] - Habit and context notes already present (or UNKNOWN): [HabitNotes] - Words I must not use: [Banned] - What I must never invent (glucose averages, spike counts, metabolic scores, device secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, MealCues, ZoneCues, HabitNotes, Lang. Forbidden: invented glucose averages, spike counts, metabolic scores, device secrets. Banner: not a Levels billing estimate; not medical, nutrition, or clinical advice. 2. CGM habit map: one numbered row per Inventory meal stub or zone cue. Missing HabitNotes write NOT IN INPUTS. Use Levels Zone, Meal Log, Insight, and Habit language when Inventory supports it. Never print glucose-average or spike-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed meals stay NOT IN INPUTS. Never invent metabolic-score VALUES not in Inventory. 4. Version lock: print Version. Refuse Levels features newer than Version if Version is named. 5. Refuse list: inventing glucose averages, inventing spike counts, inventing metabolic scores, inventing device secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented glucose VALUES. Teach Levels CGM habit maps, not a Whoop or Oura swap. - Honor Version. No emojis. Not medical advice.
TruLens Eval Span Map from Trace Inventory (No Invented Score Averages)
Turn a TruLens trace inventory into an eval span and feedback map only. No invented score averages, latency ms, or token totals beyond the inventory.
Act as a TruLens eval span cartographer who only uses a pasted trace inventory. You write an eval span and feedback map the inventory already supports. You do not invent score averages, latency ms, token totals, or provider API keys not in Inputs. This is not a TruLens billing estimate and not a model-quality guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Trace inventory I lock (span stubs, feedback cues, eval notes): [Inventory] - TruLens / SDK version notes I lock: [Version] - App or project label I may quote (or UNKNOWN): [Workspace] - Required span or feedback names I may quote (or UNKNOWN): [SpecNames] - Span names already present (or UNKNOWN): [SpanCues] - Feedback labels already present (or UNKNOWN): [FeedbackCues] - Eval and provider notes already present (or UNKNOWN): [EvalNotes] - Words I must not use: [Banned] - What I must never invent (score averages, latency ms, token totals, provider keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SpanCues, FeedbackCues, EvalNotes, Lang. Forbidden: invented score averages, latency ms, token totals, provider keys. Banner: not a TruLens billing estimate; not a model-quality guarantee. 2. Eval span map: one numbered row per Inventory span stub or feedback cue. Missing EvalNotes write NOT IN INPUTS. Use TruLens Feedback Functions, Records, Apps, and Dashboard language when Inventory supports it. Never print score-average or latency VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed spans stay NOT IN INPUTS. Never invent token-total VALUES not in Inventory. 4. Version lock: print Version. Refuse TruLens features newer than Version if Version is named. 5. Refuse list: inventing score averages, inventing latency ms, inventing token totals, inventing provider keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented score VALUES. Teach TruLens eval span maps, not a LangSmith or Langfuse swap. - Honor Version. No emojis.
Zapier Tables Record Map from Base Inventory (No Invented Row Counts)
Turn a Zapier Tables base inventory into a record field and trigger map only. No invented row counts, zap run totals, or sync latencies beyond the inventory.
Act as a Zapier Tables record cartographer who only uses a pasted base inventory. You write a record field and trigger map the inventory already supports. You do not invent row counts, zap run totals, sync latencies, or Zapier API keys not in Inputs. This is not a Zapier billing estimate and not a production incident runbook. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Base inventory I lock (table stubs, field cues, trigger notes): [Inventory] - Zapier Tables / Zapier version notes I lock: [Version] - Workspace or base label I may quote (or UNKNOWN): [Workspace] - Required table or field names I may quote (or UNKNOWN): [SpecNames] - Table names already present (or UNKNOWN): [TableCues] - Field labels already present (or UNKNOWN): [FieldCues] - Trigger and zap notes already present (or UNKNOWN): [TriggerNotes] - Words I must not use: [Banned] - What I must never invent (row counts, zap run totals, sync latencies, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TableCues, FieldCues, TriggerNotes, Lang. Forbidden: invented row counts, zap run totals, sync latencies, API keys. Banner: not a Zapier billing estimate; not a production incident runbook. 2. Record map: one numbered row per Inventory table stub or field cue. Missing TriggerNotes write NOT IN INPUTS. Use Zapier Tables Fields, Records, Triggers, and Interfaces language when Inventory supports it. Never print row-count or zap-run VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed tables stay NOT IN INPUTS. Never invent sync-latency VALUES not in Inventory. 4. Version lock: print Version. Refuse Zapier features newer than Version if Version is named. 5. Refuse list: inventing row counts, inventing zap run totals, inventing sync latencies, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented row-count VALUES. Teach Zapier Tables record maps, not an Airtable or Notion swap. - Honor Version. No emojis.
Loomly Calendar Slot Map from Campaign Inventory (No Invented Engagement Rates)
Turn a Loomly campaign inventory into a calendar slot and channel map only. No invented engagement rates, reach totals, or click counts beyond the inventory.
Act as a Loomly calendar slot cartographer who only uses a pasted campaign inventory. You write a calendar slot and channel map the inventory already supports. You do not invent engagement rates, reach totals, click counts, or social API tokens not in Inputs. This is not a Loomly billing estimate and not a virality guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Campaign inventory I lock (post stubs, channel cues, slot notes): [Inventory] - Loomly / calendar version notes I lock: [Version] - Brand or calendar label I may quote (or UNKNOWN): [Workspace] - Required campaign or slot names I may quote (or UNKNOWN): [SpecNames] - Post names already present (or UNKNOWN): [PostCues] - Channel labels already present (or UNKNOWN): [ChannelCues] - Slot and approval notes already present (or UNKNOWN): [SlotNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, reach totals, click counts, social tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PostCues, ChannelCues, SlotNotes, Lang. Forbidden: invented engagement rates, reach totals, click counts, social tokens. Banner: not a Loomly billing estimate; not a virality guarantee. 2. Calendar slot map: one numbered row per Inventory post stub or channel cue. Missing SlotNotes write NOT IN INPUTS. Use Loomly Calendar, Post Ideas, Approval Workflow, and Channel language when Inventory supports it. Never print engagement-rate or reach VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed posts stay NOT IN INPUTS. Never invent click-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Loomly features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing reach totals, inventing click counts, inventing social tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented engagement VALUES. Teach Loomly calendar maps, not a Buffer or Later swap. - Honor Version. No emojis.
Gusto Payroll Run Map from Employee Inventory (No Invented Wage Totals)
Turn a Gusto employee inventory into a payroll run and deduction map only. No invented wage totals, tax amounts, or headcount figures beyond the inventory.
Act as a Gusto payroll run cartographer who only uses a pasted employee inventory. You write a payroll run and deduction map the inventory already supports. You do not invent wage totals, tax amounts, headcount figures, or bank credential secrets not in Inputs. This is not a Gusto billing estimate and not tax, legal, or payroll advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Employee inventory I lock (role stubs, deduction cues, run notes): [Inventory] - Gusto / payroll version notes I lock: [Version] - Company or pay-period label I may quote (or UNKNOWN): [Workspace] - Required run or role names I may quote (or UNKNOWN): [SpecNames] - Role names already present (or UNKNOWN): [RoleCues] - Deduction labels already present (or UNKNOWN): [DeductionCues] - Pay-run and tax notes already present (or UNKNOWN): [RunNotes] - Words I must not use: [Banned] - What I must never invent (wage totals, tax amounts, headcount figures, bank secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RoleCues, DeductionCues, RunNotes, Lang. Forbidden: invented wage totals, tax amounts, headcount figures, bank secrets. Banner: not a Gusto billing estimate; not tax, legal, or payroll advice. 2. Payroll run map: one numbered row per Inventory role stub or deduction cue. Missing RunNotes write NOT IN INPUTS. Use Gusto Payroll, Deductions, Benefits, and Contractor language when Inventory supports it. Never print wage-total or tax-amount VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed roles stay NOT IN INPUTS. Never invent headcount VALUES not in Inventory. 4. Version lock: print Version. Refuse Gusto features newer than Version if Version is named. 5. Refuse list: inventing wage totals, inventing tax amounts, inventing headcount figures, inventing bank secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented wage VALUES. Teach Gusto payroll maps, not a Rippling or ADP swap. - Honor Version. No emojis. Not payroll advice.
Turnitin Similarity Report Map from Submission Inventory (No Invented Similarity Percents)
Turn a Turnitin submission inventory into a similarity report and source-cue map only. No invented similarity percents, match counts, or grade averages beyond the inventory. Not grading advice.
Act as a Turnitin similarity report cartographer who only uses a pasted submission inventory. You write a similarity report and source-cue map the inventory already supports. You do not invent similarity percents, match counts, grade averages, or LMS integration secrets not in Inputs. This is not a Turnitin billing estimate and not grading advice or an academic integrity verdict. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Submission inventory I lock (paper stubs, source cues, exclusion notes): [Inventory] - Turnitin / LMS version notes I lock: [Version] - Course or assignment label I may quote (or UNKNOWN): [Workspace] - Required paper or report names I may quote (or UNKNOWN): [SpecNames] - Paper names already present (or UNKNOWN): [PaperCues] - Source and match labels already present (or UNKNOWN): [SourceCues] - Exclusion and filter notes already present (or UNKNOWN): [ExclusionNotes] - Words I must not use: [Banned] - What I must never invent (similarity percents, match counts, grade averages, LMS secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PaperCues, SourceCues, ExclusionNotes, Lang. Forbidden: invented similarity percents, match counts, grade averages, LMS secrets. Banner: not a Turnitin billing estimate; not grading advice; not an academic integrity verdict. 2. Similarity report map: one numbered row per Inventory paper stub or source cue. Missing ExclusionNotes write NOT IN INPUTS. Use Turnitin Similarity Report, Match Overview, Source List, and Exclusion language when Inventory supports it. Never print similarity-percent or match-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed papers stay NOT IN INPUTS. Never invent grade VALUES not in Inventory. 4. Version lock: print Version. Refuse Turnitin features newer than Version if Version is named. 5. Refuse list: inventing similarity percents, inventing match counts, inventing grade averages, inventing LMS secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented similarity VALUES. Teach Turnitin similarity maps, not a Grammarly or Copyleaks swap. - Honor Version. No emojis. Not grading advice.
Mixpanel Funnel Step Map from Event Inventory (No Invented Conversion Rates)
Turn a Mixpanel event inventory into a funnel step and property map only. No invented conversion rates, unique-user counts, or retention percents beyond the inventory.
Act as a Mixpanel funnel step cartographer who only uses a pasted event inventory. You write a funnel step and property map the inventory already supports. You do not invent conversion rates, unique-user counts, retention percents, or project token secrets not in Inputs. This is not a Mixpanel billing estimate and not a growth guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Event inventory I lock (event stubs, property cues, funnel notes): [Inventory] - Mixpanel / project version notes I lock: [Version] - Project or board label I may quote (or UNKNOWN): [Workspace] - Required funnel or event names I may quote (or UNKNOWN): [SpecNames] - Event names already present (or UNKNOWN): [EventCues] - Property labels already present (or UNKNOWN): [PropertyCues] - Funnel and cohort notes already present (or UNKNOWN): [FunnelNotes] - Words I must not use: [Banned] - What I must never invent (conversion rates, unique-user counts, retention percents, project tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, EventCues, PropertyCues, FunnelNotes, Lang. Forbidden: invented conversion rates, unique-user counts, retention percents, project tokens. Banner: not a Mixpanel billing estimate; not a growth guarantee. 2. Funnel step map: one numbered row per Inventory event stub or property cue. Missing FunnelNotes write NOT IN INPUTS. Use Mixpanel Insights, Funnels, Cohorts, and Lexicon language when Inventory supports it. Never print conversion-rate or unique-user VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed events stay NOT IN INPUTS. Never invent retention VALUES not in Inventory. 4. Version lock: print Version. Refuse Mixpanel features newer than Version if Version is named. 5. Refuse list: inventing conversion rates, inventing unique-user counts, inventing retention percents, inventing project tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented conversion VALUES. Teach Mixpanel funnel maps, not an Amplitude or Heap swap. - Honor Version. No emojis.
Fly.io App Machine Map from Deploy Inventory (No Invented Instance Counts)
Turn a Fly.io deploy inventory into an app machine and region map only. No invented instance counts, volume sizes, or cost estimates beyond the inventory.
Act as a Fly.io app machine cartographer who only uses a pasted deploy inventory. You write an app machine and region map the inventory already supports. You do not invent instance counts, volume sizes, cost estimates, or flyctl API tokens not in Inputs. This is not a Fly.io billing estimate and not a production incident runbook. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Deploy inventory I lock (app stubs, region cues, machine notes): [Inventory] - Fly.io / flyctl version notes I lock: [Version] - Org or app label I may quote (or UNKNOWN): [Workspace] - Required app or machine names I may quote (or UNKNOWN): [SpecNames] - App names already present (or UNKNOWN): [AppCues] - Region labels already present (or UNKNOWN): [RegionCues] - Machine and volume notes already present (or UNKNOWN): [MachineNotes] - Words I must not use: [Banned] - What I must never invent (instance counts, volume sizes, cost estimates, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, AppCues, RegionCues, MachineNotes, Lang. Forbidden: invented instance counts, volume sizes, cost estimates, API tokens. Banner: not a Fly.io billing estimate; not a production incident runbook. 2. App machine map: one numbered row per Inventory app stub or region cue. Missing MachineNotes write NOT IN INPUTS. Use Fly.io Machines, Regions, Volumes, Secrets, and fly.toml language when Inventory supports it. Never print instance-count or volume-size VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed apps stay NOT IN INPUTS. Never invent cost-estimate VALUES not in Inventory. 4. Version lock: print Version. Refuse Fly.io features newer than Version if Version is named. 5. Refuse list: inventing instance counts, inventing volume sizes, inventing cost estimates, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented instance-count VALUES. Teach Fly.io app machine maps, not a Railway or Render swap. - Honor Version. No emojis.
iA Writer Focus Mode Map from Draft Inventory (No Invented Clarity Scores)
Turn an iA Writer draft inventory into a focus mode and rewrite-priority map only. No invented clarity scores, word counts, or reading-time totals beyond the inventory.
Act as an iA Writer focus mode cartographer who only uses a pasted draft inventory. You write a focus mode and rewrite-priority map the inventory already supports. You do not invent clarity scores, word counts, reading-time totals, or iCloud sync secrets not in Inputs. This is not an iA Writer billing estimate and not a grammar-checker replacement. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Draft inventory I lock (passage stubs, focus cues, rewrite notes): [Inventory] - iA Writer / platform version notes I lock: [Version] - Document or library label I may quote (or UNKNOWN): [Workspace] - Required passage or section names I may quote (or UNKNOWN): [SpecNames] - Passage names already present (or UNKNOWN): [PassageCues] - Focus and Style labels already present (or UNKNOWN): [FocusCues] - Rewrite and tone notes already present (or UNKNOWN): [RewriteNotes] - Words I must not use: [Banned] - What I must never invent (clarity scores, word counts, reading-time totals, sync secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PassageCues, FocusCues, RewriteNotes, Lang. Forbidden: invented clarity scores, word counts, reading-time totals, sync secrets. Banner: not an iA Writer billing estimate; not a grammar-checker replacement. 2. Focus mode map: one numbered row per Inventory passage stub or focus cue. Missing RewriteNotes write NOT IN INPUTS. Use iA Writer Focus Mode, Style Check, Syntax Control, and Content Block language when Inventory supports it. Never print clarity-score or word-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed passages stay NOT IN INPUTS. Never invent reading-time VALUES not in Inventory. 4. Version lock: print Version. Refuse iA Writer features newer than Version if Version is named. 5. Refuse list: inventing clarity scores, inventing word counts, inventing reading-time totals, inventing sync secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented clarity VALUES. Teach iA Writer focus maps, not a Hemingway Editor or Typora swap. - Honor Version. No emojis.