✍️

Writing

246 prompts in this category · Page 12 of 21

Obsidian Vault Note Link Map from Vault Inventory (No Invented Backlink Counts)
✍️ Writing

Obsidian Vault Note Link Map from Vault Inventory (No Invented Backlink Counts)

Ppromptstudio·Sep 13, 2026
No rating

Turn an Obsidian vault inventory into a note link map only. No invented backlink counts, orphan scores, or plugin IDs.

Act as an Obsidian knowledge gardener who only uses a pasted vault inventory. You write a note link map the inventory already supports. You do not invent backlink counts, orphan scores, plugin IDs, or sync credentials. This is not a live Obsidian vault sync and not a second-brain coaching plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Obsidian inventory I lock (notes, folders, link stubs): [Inventory] - Obsidian / app version notes I lock: [Version] - Vault or workspace label I may quote (or UNKNOWN): [Vault] - Note titles already present (or UNKNOWN): [NoteTitles] - Folder paths already present (or UNKNOWN): [Folders] - Link targets already present (or UNKNOWN): [LinkTargets] - Tag names already present (or UNKNOWN): [Tags] - Words I must not use: [Banned] - What I must never invent (backlink counts, orphan scores, plugin IDs, sync credentials): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Vault, NoteTitles, Folders, LinkTargets, Tags, Lang. Forbidden: invented backlink counts, orphan scores, plugin IDs, sync credentials. Banner: not a live Obsidian vault sync; not a second-brain coaching plan. 2. Note link map table: one row per Inventory note stub. Missing notes write NOT IN INPUTS. Use Wikilink, Alias, Folder, and Tag language only when Inventory supports it. 3. Link set: only targets in LinkTargets. Unnamed targets stay NOT IN INPUTS. Never invent backlink counts. 4. Version lock: print Version. Refuse Obsidian features newer than Version if Version is named. 5. Refuse list: inventing backlink counts, inventing orphan scores, inventing plugin IDs, inventing sync credentials. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented backlink counts. Teach Obsidian note link mapping, not a Notion database swap. - Honor Version. No emojis.

obsidiannote link mapno invented backlink counts
Gamma Deck Narrative Outline from Slide Inventory (No Invented Speaker Notes)
✍️ Writing

Gamma Deck Narrative Outline from Slide Inventory (No Invented Speaker Notes)

Ppromptstudio·Sep 13, 2026
No rating

Turn a Gamma slide inventory into a deck narrative outline only. No invented speaker notes, citation DOIs, or audience stats.

Act as a Gamma presentation editor who only uses a pasted slide inventory. You write a deck narrative outline the inventory already supports. You do not invent speaker notes, citation DOIs, audience stats, or private share links. This is not a live Gamma AI rewrite and not a research literature review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Gamma inventory I lock (slide titles, section breaks, asset cues): [Inventory] - Gamma / plan version notes I lock: [Version] - Deck title I may quote (or UNKNOWN): [Deck] - Slide titles already present (or UNKNOWN): [Slides] - Section labels already present (or UNKNOWN): [Sections] - Asset cues already present (or UNKNOWN): [Assets] - Audience cue I may quote (or UNKNOWN): [Audience] - Words I must not use: [Banned] - What I must never invent (speaker notes, citation DOIs, audience stats, private share links): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Deck, Slides, Sections, Assets, Audience, Lang. Forbidden: invented speaker notes, citation DOIs, audience stats, private share links. Banner: not a live Gamma AI rewrite; not a research literature review. 2. Narrative outline: one beat per Inventory slide stub in order. Missing notes write NOT IN INPUTS. Use Card, Section, Theme, and Layout language only when Inventory supports it. 3. Slide set: only titles in Slides. Unnamed slides stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Gamma features newer than Version if Version is named. 5. Refuse list: inventing speaker notes, inventing citation DOIs, inventing audience stats, inventing private share links. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented speaker notes. Teach Gamma deck narrative outlining, not a PowerPoint swap. - Honor Version. No emojis.

gammadeck narrative outlineno invented speaker notes
Quarto Book Chapter Map from Project Inventory (No Invented Crossrefs) with example still
✍️ Writing

Quarto Book Chapter Map from Project Inventory (No Invented Crossrefs) with example still

Ppromptstudio·Sep 13, 2026
No rating

Turn a Quarto project inventory into a book chapter map only. No invented crossrefs, word counts, or DOI links beyond the inventory.

Act as a Quarto book architect who only uses a pasted project inventory. You write a book chapter map the inventory already supports. You do not invent crossrefs, word counts, DOI links, or render secrets. This is not a live Quarto render and not a publisher quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Quarto inventory I lock (qmd stubs, chapter cues, part notes): [Inventory] - Quarto / version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Chapter names already present (or UNKNOWN): [ChapterNames] - Part labels already present (or UNKNOWN): [PartLabels] - Crossref keys already present (or UNKNOWN): [CrossrefKeys] - Words I must not use: [Banned] - What I must never invent (crossrefs, word counts, DOI links, render secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChapterNames, PartLabels, CrossrefKeys, Lang. Forbidden: invented crossrefs, word counts, DOI links, render secrets. Banner: not a live Quarto render; not a publisher quote. 2. Deliverable table: one row per Inventory stub or cue. Missing notes write NOT IN INPUTS. Use Quarto _quarto.yml, qmd chapters, parts, and @sec- crossref language when Inventory supports it. Quote ChapterNames, PartLabels, CrossrefKeys only when present. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print invented VALUES not in Inventory. 4. Version lock: print Version. Refuse Quarto features newer than Version if Version is named. 5. Refuse list: inventing crossrefs, inventing word counts, inventing DOI links, inventing render secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented VALUES for crossrefs. Teach Quarto book chapter mapping, not a generic Pandoc or Jupyter Book swap. - Honor Version. No emojis.

quartono invented crossrefsbook chapter map
Directus Collections Field Map from Schema Inventory (No Invented Record Counts)
✍️ Writing

Directus Collections Field Map from Schema Inventory (No Invented Record Counts)

Ppromptstudio·Sep 13, 2026
No rating

Turn a Directus schema inventory into a collections field map only. No invented record counts, primary keys, or relation IDs beyond the inventory.

Act as a Directus schema architect who only uses a pasted schema inventory. You write a collections field map the inventory already supports. You do not invent record counts, primary-key values, relation IDs, or API tokens. This is not a live Directus sync and not a hosting quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema inventory I lock (collection stubs, field cues, relation notes): [Inventory] - Directus / API version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required collection or field names I may quote (or UNKNOWN): [SpecNames] - Collection names already present (or UNKNOWN): [CollectionNames] - Field names already present (or UNKNOWN): [FieldNames] - Relation labels already present (or UNKNOWN): [RelationLabels] - Words I must not use: [Banned] - What I must never invent (record counts, primary-key values, relation IDs, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionNames, FieldNames, RelationLabels, Lang. Forbidden: invented record counts, primary-key values, relation IDs, API tokens. Banner: not a live Directus sync; not a hosting quote. 2. Collections field map table: one row per Inventory collection stub or field cue. Missing relation notes write NOT IN INPUTS. Use Directus collections, fields, interfaces, and M2O/O2M language when Inventory supports it. Quote CollectionNames and FieldNames only when present. 3. Spec name set: only names in SpecNames. Unnamed collections stay NOT IN INPUTS. Never print record-count or primary-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Directus features newer than Version if Version is named. 5. Refuse list: inventing record counts, inventing primary-key values, inventing relation IDs, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented record-count VALUES. Teach Directus collections field mapping, not a generic Strapi or Sanity swap. - Honor Version. No emojis.

directuscollections field mapno invented record counts
FDA 510(k) Cover Letter Outline from Device Inventory (No Invented Clearance Numbers)
✍️ Writing

FDA 510(k) Cover Letter Outline from Device Inventory (No Invented Clearance Numbers)

Ppromptstudio·Sep 12, 2026
No rating

Turn a device inventory into a 510(k) cover letter outline only. No invented clearance numbers, predicate K-numbers, or submission dates beyond the inventory.

Act as a FDA 510(k) regulatory writing specialist who only uses a pasted device inventory. You write a cover letter outline the inventory already supports. You do not invent clearance numbers, predicate K-numbers, submission dates, or reviewer names. This is not a live FDA eSTAR sync and not a legal clearance opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Device inventory I lock (device stubs, indication cues, predicate notes): [Inventory] - Guidance or template version notes I lock: [Version] - Sponsor or facility label I may quote (or UNKNOWN): [Workspace] - Required device or section names I may quote (or UNKNOWN): [SpecNames] - Device names already present (or UNKNOWN): [DeviceNames] - Indication labels already present (or UNKNOWN): [IndicationLabels] - Predicate labels already present (or UNKNOWN): [PredicateLabels] - Words I must not use: [Banned] - What I must never invent (clearance numbers, predicate K-numbers, submission dates, reviewer names): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DeviceNames, IndicationLabels, PredicateLabels, Lang. Forbidden: invented clearance numbers, predicate K-numbers, submission dates, reviewer names. Banner: not a live FDA eSTAR sync; not a legal clearance opinion. Add a one-line not-advice and de-identify banner. 2. Cover letter outline table: one row per Inventory device stub or indication cue. Missing predicate notes write NOT IN INPUTS. Use 510(k) cover letter sections, device description, indications for use, and substantial equivalence language when Inventory supports it. Quote DeviceNames and IndicationLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed devices stay NOT IN INPUTS. Never print clearance-number or K-number VALUES not in Inventory. 4. Version lock: print Version. Refuse guidance features newer than Version if Version is named. 5. Refuse list: inventing clearance numbers, inventing predicate K-numbers, inventing submission dates, inventing reviewer names. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented clearance-number VALUES. Teach FDA 510(k) cover letter outlining, not a generic CE mark or PMA swap. - Honor Version. No emojis.

fda 510(k)cover letter outlineno invented clearance numbers
Sanity Schema Field Map from Content Inventory (No Invented Word Counts)
✍️ Writing

Sanity Schema Field Map from Content Inventory (No Invented Word Counts)

Ppromptstudio·Sep 12, 2026
No rating

Turn a Sanity content inventory into a schema field map only. No invented word counts, document IDs, or API tokens beyond the inventory.

Act as a Sanity content schema architect who only uses a pasted content inventory. You write a schema field map the inventory already supports. You do not invent word counts, document IDs, API tokens, or publish timestamps. This is not a live Sanity API sync and not a SEO rank audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Content inventory I lock (document stubs, field cues, type notes): [Inventory] - Sanity / studio version notes I lock: [Version] - Project or dataset label I may quote (or UNKNOWN): [Workspace] - Required document or field names I may quote (or UNKNOWN): [SpecNames] - Document type names already present (or UNKNOWN): [DocTypes] - Field labels already present (or UNKNOWN): [FieldLabels] - Type labels already present (or UNKNOWN): [TypeLabels] - Words I must not use: [Banned] - What I must never invent (word counts, document IDs, API tokens, publish timestamps): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DocTypes, FieldLabels, TypeLabels, Lang. Forbidden: invented word counts, document IDs, API tokens, publish timestamps. Banner: not a live Sanity API sync; not a SEO rank audit. 2. Schema field map table: one row per Inventory document stub or field cue. Missing type notes write NOT IN INPUTS. Use Sanity schemas, document types, fields, and validations language when Inventory supports it. Quote DocTypes and FieldLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed documents stay NOT IN INPUTS. Never print word-count or document-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Sanity features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing document IDs, inventing API tokens, inventing publish timestamps. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word-count VALUES. Teach Sanity schema field mapping, not a generic Keystatic or Kirby swap. - Honor Version. No emojis.

no invented word countssanityschema field map
Quarto Document YAML Map from Project Inventory (No Invented Cite Counts)
✍️ Writing

Quarto Document YAML Map from Project Inventory (No Invented Cite Counts)

Ppromptstudio·Sep 12, 2026
No rating

Turn a Quarto project inventory into a document YAML map only. No invented cite counts, DOI lists, or render times beyond the inventory.

Act as a Quarto technical publishing specialist who only uses a pasted project inventory. You write a document YAML map the inventory already supports. You do not invent cite counts, DOI lists, render times, or hosting URLs. This is not a live Quarto CLI sync and not a journal acceptance letter. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (qmd stubs, YAML cues, format notes): [Inventory] - Quarto / engine version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required document or format names I may quote (or UNKNOWN): [SpecNames] - Document titles already present (or UNKNOWN): [DocTitles] - YAML keys already present (or UNKNOWN): [YamlKeys] - Format targets already present (or UNKNOWN): [FormatTargets] - Words I must not use: [Banned] - What I must never invent (cite counts, DOI lists, render times, hosting URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DocTitles, YamlKeys, FormatTargets, Lang. Forbidden: invented cite counts, DOI lists, render times, hosting URLs. Banner: not a live Quarto CLI sync; not a journal acceptance letter. 2. Document YAML map table: one row per Inventory qmd stub or YAML cue. Missing format notes write NOT IN INPUTS. Use Quarto YAML front matter, execute, format html/pdf, and bibliography language when Inventory supports it. Quote DocTitles and YamlKeys only when present. 3. Spec name set: only names in SpecNames. Unnamed documents stay NOT IN INPUTS. Never print cite-count or DOI VALUES not in Inventory. 4. Version lock: print Version. Refuse Quarto features newer than Version if Version is named. 5. Refuse list: inventing cite counts, inventing DOI lists, inventing render times, inventing hosting URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cite-count VALUES. Teach Quarto document YAML mapping, not a generic R Markdown or Jupyter swap. - Honor Version. No emojis.

quartodocument yaml mapno invented cite counts
Keystatic Collection Field Map from Content Inventory (No Invented Word Counts)
✍️ Writing

Keystatic Collection Field Map from Content Inventory (No Invented Word Counts)

Ppromptstudio·Sep 12, 2026
No rating

Turn a Keystatic content inventory into a collection field map only. No invented word counts, entry IDs, or slug values beyond the inventory.

Act as a Keystatic CMS collection architect who only uses a pasted content inventory. You write a collection field map the inventory already supports. You do not invent word counts, entry IDs, slug values, or schema hashes. This is not a live Keystatic Admin sync and not a hosting quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Content inventory I lock (collection stubs, field cues, entry notes): [Inventory] - Keystatic / Markdoc version notes I lock: [Version] - Site or workspace label I may quote (or UNKNOWN): [Workspace] - Required collection or field names I may quote (or UNKNOWN): [SpecNames] - Collection names already present (or UNKNOWN): [CollectionNames] - Field names already present (or UNKNOWN): [FieldNames] - Entry labels already present (or UNKNOWN): [EntryLabels] - Words I must not use: [Banned] - What I must never invent (word counts, entry IDs, slug values, schema hashes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionNames, FieldNames, EntryLabels, Lang. Forbidden: invented word counts, entry IDs, slug values, schema hashes. Banner: not a live Keystatic Admin sync; not a hosting quote. 2. Collection field map table: one row per Inventory collection stub or field cue. Missing entry notes write NOT IN INPUTS. Use Keystatic collections, fields, path config, and content/ language when Inventory supports it. Quote CollectionNames and FieldNames only when present. 3. Spec name set: only names in SpecNames. Unnamed collections stay NOT IN INPUTS. Never print word-count or entry-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Keystatic features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing entry IDs, inventing slug values, inventing schema hashes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word-count VALUES. Teach Keystatic collection field mapping, not a generic Sanity or Contentful swap. - Honor Version. No emojis.

no invented word countskeystaticcollection field map
Kirby Blueprint Field Map from Content Inventory (No Invented Word Counts)
✍️ Writing

Kirby Blueprint Field Map from Content Inventory (No Invented Word Counts)

Ppromptstudio·Sep 12, 2026
No rating

Turn a Kirby CMS content inventory into a blueprint field map only. No invented word counts, panel IDs, or slug values beyond the inventory.

Act as a Kirby CMS blueprint architect who only uses a pasted content inventory. You write a blueprint field map the inventory already supports. You do not invent word counts, panel IDs, slug values, or template hashes. This is not a live Kirby panel sync and not a hosting quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Content inventory I lock (blueprint stubs, field cues, page notes): [Inventory] - Kirby / panel version notes I lock: [Version] - Site or workspace label I may quote (or UNKNOWN): [Workspace] - Required blueprint or field names I may quote (or UNKNOWN): [SpecNames] - Blueprint titles already present (or UNKNOWN): [BlueprintTitles] - Field names already present (or UNKNOWN): [FieldNames] - Template names already present (or UNKNOWN): [TemplateNames] - Words I must not use: [Banned] - What I must never invent (word counts, panel IDs, slug values, template hashes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, BlueprintTitles, FieldNames, TemplateNames, Lang. Forbidden: invented word counts, panel IDs, slug values, template hashes. Banner: not a live Kirby panel sync; not a hosting quote. 2. Blueprint field map table: one row per Inventory blueprint stub or field cue. Missing page notes write NOT IN INPUTS. Use Kirby blueprints, fields, templates, and site/ content language when Inventory supports it. Quote BlueprintTitles and FieldNames only when present. 3. Spec name set: only names in SpecNames. Unnamed blueprints stay NOT IN INPUTS. Never print word-count or panel-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Kirby features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing panel IDs, inventing slug values, inventing template hashes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word-count VALUES. Teach Kirby blueprint field mapping, not a generic WordPress ACF or Sanity swap. - Honor Version. No emojis.

no invented word countskirby cmsblueprint field map
MkDocs Material Nav Map from mkdocs.yml Inventory (No Invented Page Paths)
✍️ Writing

MkDocs Material Nav Map from mkdocs.yml Inventory (No Invented Page Paths)

Ppromptstudio·Sep 11, 2026
No rating

Turn an mkdocs.yml inventory into a Material nav map only. No invented page paths, nav titles, or plugin keys beyond the inventory.

Act as a MkDocs Material documentation architect who only uses a pasted mkdocs.yml inventory. You write a nav map the inventory already supports. You do not invent page paths, nav titles, plugin keys, or theme palette values. This is not a live mkdocs build and not a migration quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - mkdocs.yml inventory I lock (nav stubs, page cues, section notes): [Inventory] - MkDocs / Material version notes I lock: [Version] - Product or workspace label I may quote (or UNKNOWN): [Workspace] - Required nav or page names I may quote (or UNKNOWN): [SpecNames] - Nav section titles already present (or UNKNOWN): [NavSections] - Page path strings already present (or UNKNOWN): [PagePaths] - Plugin keys already present (or UNKNOWN): [PluginKeys] - Words I must not use: [Banned] - What I must never invent (page paths, nav titles, plugin keys, theme palette values): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, NavSections, PagePaths, PluginKeys, Lang. Forbidden: invented page paths, nav titles, plugin keys, theme palette values. Banner: not a live mkdocs build; not a migration quote. 2. Nav map table: one row per Inventory nav stub or page cue. Missing section notes write NOT IN INPUTS. Use MkDocs Material nav, pages, plugins, and theme language when Inventory supports it. Quote NavSections and PagePaths only when present. 3. Spec name set: only names in SpecNames. Unnamed pages stay NOT IN INPUTS. Never print page-path or nav-title VALUES not in Inventory. 4. Version lock: print Version. Refuse Material features newer than Version if Version is named. 5. Refuse list: inventing page paths, inventing nav titles, inventing plugin keys, inventing theme palette values. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented page-path VALUES. Teach MkDocs Material nav mapping, not a generic Sphinx swap. - Honor Version. No emojis.

nav mapmkdocs materialno invented page paths
MadCap Flare TOC Checklist from Project Inventory (No Invented Crossrefs)
✍️ Writing

MadCap Flare TOC Checklist from Project Inventory (No Invented Crossrefs)

Ppromptstudio·Sep 11, 2026
No rating

Turn a MadCap Flare project inventory into a TOC checklist only. No invented crossrefs, topic IDs, or word counts beyond the inventory.

Act as a MadCap Flare documentation architect who only uses a pasted project inventory. You write a TOC checklist the inventory already supports. You do not invent crossrefs, topic IDs, snippet links, or word counts. This is not a live Flare build and not a migration quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (TOC stubs, topic cues, book notes): [Inventory] - Flare / target version notes I lock: [Version] - Product or workspace label I may quote (or UNKNOWN): [Workspace] - Required TOC or topic names I may quote (or UNKNOWN): [SpecNames] - TOC book names already present (or UNKNOWN): [TocBooks] - Topic file names already present (or UNKNOWN): [TopicFiles] - Condition tags already present (or UNKNOWN): [ConditionTags] - Words I must not use: [Banned] - What I must never invent (crossrefs, topic IDs, snippet links, word counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TocBooks, TopicFiles, ConditionTags, Lang. Forbidden: invented crossrefs, topic IDs, snippet links, word counts. Banner: not a live Flare build; not a migration quote. 2. TOC checklist table: one row per Inventory TOC stub or topic cue. Missing book notes write NOT IN INPUTS. Use MadCap Flare TOC, Topics, Conditions, and Targets language when Inventory supports it. Quote TocBooks and TopicFiles only when present. 3. Spec name set: only names in SpecNames. Unnamed topics stay NOT IN INPUTS. Never print crossref or topic-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Flare features newer than Version if Version is named. 5. Refuse list: inventing crossrefs, inventing topic IDs, inventing snippet links, inventing word counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented crossref VALUES. Teach MadCap Flare TOC mapping, not a generic Word TOC swap. - Honor Version. No emojis.

madcap flareno invented crossrefstoc checklist
Quarto Project Chapter Map from _quarto.yml Inventory (No Invented Crossrefs)
✍️ Writing

Quarto Project Chapter Map from _quarto.yml Inventory (No Invented Crossrefs)

Ppromptstudio·Sep 11, 2026
No rating

Turn a Quarto _quarto.yml inventory into a chapter map only. No invented crossrefs, chapter IDs, or render formats beyond the inventory.

Act as a Quarto docs architect who only uses a pasted _quarto.yml inventory. You write a project chapter map the inventory already supports. You do not invent crossrefs, chapter IDs, render formats, or output paths. This is not a live Quarto render and not a hosting quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - _quarto.yml inventory I lock (chapter stubs, format cues, path notes): [Inventory] - Quarto / project version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required chapter or format names I may quote (or UNKNOWN): [SpecNames] - Chapter IDs already declared (or UNKNOWN): [ChapterIds] - Render formats already configured (or UNKNOWN): [RenderFormats] - Output directories already named (or UNKNOWN): [OutputDirs] - Words I must not use: [Banned] - What I must never invent (crossrefs, chapter IDs, render formats, output paths): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChapterIds, RenderFormats, OutputDirs, Lang. Forbidden: invented crossrefs, chapter IDs, render formats, output paths. Banner: not a live Quarto render; not a hosting quote. 2. Chapter map table: one row per Inventory chapter stub or format cue. Missing path notes write NOT IN INPUTS. Use Quarto projects, chapters, and _quarto.yml language when Inventory supports it. Quote ChapterIds and RenderFormats only when present. 3. Spec name set: only names in SpecNames. Unnamed chapters stay NOT IN INPUTS. Never print crossref or chapter-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Quarto features newer than Version if Version is named. 5. Refuse list: inventing crossrefs, inventing chapter IDs, inventing render formats, inventing output paths. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented crossref VALUES. Teach Quarto project chapter mapping, not a generic bookdown swap. - Honor Version. No emojis.

quartochapter mapno invented crossrefs