✍️

Writing

246 prompts in this category · Page 11 of 21

Typora Export Spec Map from Doc Inventory (No Invented Word Counts)
✍️ Writing

Typora Export Spec Map from Doc Inventory (No Invented Word Counts)

Ppromptstudio·Sep 16, 2026
No rating

Turn a Typora document inventory into an export spec map only. No invented word counts, PDF page totals, or sync folder paths beyond the inventory.

Act as a Typora documentation export specialist who only uses a pasted document inventory. You write an export spec map the inventory already supports. You do not invent word counts, PDF page totals, sync folder paths, or image counts not in Inputs. This is not a Typora license quote and not a publishing contract review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Document inventory I lock (export stubs, format cues, style notes): [Inventory] - Typora / theme version notes I lock: [Version] - Team or vault label I may quote (or UNKNOWN): [Workspace] - Required export or doc names I may quote (or UNKNOWN): [SpecNames] - Document titles already present (or UNKNOWN): [DocCues] - Export format labels already present (or UNKNOWN): [FormatCues] - Style and theme notes already present (or UNKNOWN): [StyleNotes] - Words I must not use: [Banned] - What I must never invent (word counts, PDF page totals, sync folder paths, image counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DocCues, FormatCues, StyleNotes, Lang. Forbidden: invented word counts, PDF page totals, sync folder paths, image counts. Banner: not a Typora license quote; not a publishing contract review. 2. Export spec map: one numbered row per Inventory export stub or format cue. Missing StyleNotes write NOT IN INPUTS. Use Typora Themes, Export, Outline, Math, and Diagrams language when Inventory supports it. Never print word-count or PDF-page VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed docs stay NOT IN INPUTS. Never invent sync-folder-path VALUES not in Inventory. 4. Version lock: print Version. Refuse Typora features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing PDF page totals, inventing sync folder paths, inventing image counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word-count VALUES. Teach Typora export specs, not an Obsidian or Scrivener swap. - Honor Version. No emojis.

no invented word countstyporaexport spec map
Ulysses Scene Continuity Map from Sheet Inventory (No Invented Word Counts)
✍️ Writing

Ulysses Scene Continuity Map from Sheet Inventory (No Invented Word Counts)

Ppromptstudio·Sep 15, 2026
No rating

Turn a Ulysses sheet inventory into a scene continuity map only. No invented word counts, chapter totals, or character emails beyond the inventory.

Act as a Ulysses developmental editor who only uses a pasted sheet inventory. You write a scene continuity map the inventory already supports. You do not invent word counts, chapter totals, character emails, or ISBNs not in Inputs. This is not a Ulysses Plus billing estimate and not a publishing contract. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Sheet scene inventory I lock (sheet stubs, continuity cues, beat notes): [Inventory] - Ulysses / library version notes I lock: [Version] - Group or project label I may quote (or UNKNOWN): [Workspace] - Required map or scene names I may quote (or UNKNOWN): [SpecNames] - Sheet titles already present (or UNKNOWN): [SheetCues] - Continuity and beat cues already present (or UNKNOWN): [BeatCues] - Character and prop notes already present (or UNKNOWN): [PropNotes] - Words I must not use: [Banned] - What I must never invent (word counts, chapter totals, character emails, ISBNs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SheetCues, BeatCues, PropNotes, Lang. Forbidden: invented word counts, chapter totals, character emails, ISBNs. Banner: not a Ulysses Plus billing estimate; not a publishing contract. 2. Continuity map: one row per Inventory sheet stub or beat cue. Missing PropNotes write NOT IN INPUTS. Use Ulysses Sheets, Groups, Keywords, Goals, and Filters language when Inventory supports it. Never print word-count or chapter-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed sheets stay NOT IN INPUTS. Never invent character-email VALUES not in Inventory. 4. Version lock: print Version. Refuse Ulysses features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing chapter totals, inventing character emails, inventing ISBNs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word-count VALUES. Teach Ulysses scene continuity maps, not a Scrivener or Final Draft swap. - Honor Version. No emojis.

no invented word countsulyssesscene continuity map
Scrivener Scene Outline from Manuscript Inventory (No Invented Word Counts)
✍️ Writing

Scrivener Scene Outline from Manuscript Inventory (No Invented Word Counts)

Ppromptstudio·Sep 15, 2026
No rating

Turn a Scrivener manuscript inventory into a scene outline only. No invented word counts, chapter totals, or character emails beyond the inventory.

Act as a Scrivener developmental editor who only uses a pasted manuscript inventory. You write a scene outline the inventory already supports. You do not invent word counts, chapter totals, character emails, or ISBN claims not in Inputs. This is not a Scrivener license quote and not a publishing contract certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Manuscript scene inventory I lock (scene stubs, beat cues, binder notes): [Inventory] - Scrivener / project version notes I lock: [Version] - Project or manuscript label I may quote (or UNKNOWN): [Workspace] - Required scene or chapter names I may quote (or UNKNOWN): [SpecNames] - Scene titles already present (or UNKNOWN): [SceneCues] - Beat and POV cues already present (or UNKNOWN): [BeatCues] - Binder and status notes already present (or UNKNOWN): [BinderNotes] - Words I must not use: [Banned] - What I must never invent (word counts, chapter totals, character emails, ISBNs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SceneCues, BeatCues, BinderNotes, Lang. Forbidden: invented word counts, chapter totals, character emails, ISBNs. Banner: not a Scrivener license quote; not a publishing contract certificate. 2. Scene outline: one numbered beat block per Inventory scene stub or beat cue. Missing BinderNotes write NOT IN INPUTS. Use Scrivener Binder, Scenes, Documents, Labels, and Status language when Inventory supports it. Never print word-count or chapter-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed scenes stay NOT IN INPUTS. Never invent ISBN VALUES not in Inventory. 4. Version lock: print Version. Refuse Scrivener features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing chapter totals, inventing character emails, inventing ISBNs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented word-count VALUES. Teach Scrivener scene outlining, not a Final Draft or Word swap. - Honor Version. No emojis.

scrivenerno invented word countsscene outline
ProWritingAid Style Report Map from Draft Inventory (No Invented Score Claims)
✍️ Writing

ProWritingAid Style Report Map from Draft Inventory (No Invented Score Claims)

Ppromptstudio·Sep 15, 2026
No rating

Turn a ProWritingAid draft inventory into a style report map only. No invented score claims, plagiarism percentages, or rewrite guarantees beyond the inventory.

Act as a ProWritingAid style cartographer who only uses a pasted draft inventory. You write a style report map the inventory already supports. You do not invent score claims, plagiarism percentages, rewrite guarantees, or reader emails not in Inputs. This is not a ProWritingAid billing estimate and not a plagiarism certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Draft style inventory I lock (draft stubs, report cues, style notes): [Inventory] - ProWritingAid / report version notes I lock: [Version] - Project or doc label I may quote (or UNKNOWN): [Workspace] - Required draft or report names I may quote (or UNKNOWN): [SpecNames] - Draft titles already present (or UNKNOWN): [DraftCues] - Report and check cues already present (or UNKNOWN): [ReportCues] - Style and tone notes already present (or UNKNOWN): [StyleNotes] - Words I must not use: [Banned] - What I must never invent (score claims, plagiarism %, rewrite guarantees, reader emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DraftCues, ReportCues, StyleNotes, Lang. Forbidden: invented score claims, plagiarism %, rewrite guarantees, reader emails. Banner: not a ProWritingAid billing estimate; not a plagiarism certificate. 2. Report map table: one row per Inventory draft stub or report cue. Missing StyleNotes write NOT IN INPUTS. Use ProWritingAid Reports, Style checks, Consistency, and Readability language when Inventory supports it. Never print score or plagiarism VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed drafts stay NOT IN INPUTS. Never invent reader-email VALUES not in Inventory. 4. Version lock: print Version. Refuse ProWritingAid features newer than Version if Version is named. 5. Refuse list: inventing score claims, inventing plagiarism %, inventing rewrite guarantees, inventing reader emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented score VALUES. Teach ProWritingAid style report mapping, not a Grammarly or Hemingway swap. - Honor Version. No emojis.

no invented score claimsprowritingaidstyle report map
Grammarly Tone Pass Map from Draft Inventory (No Invented Score Claims)
✍️ Writing

Grammarly Tone Pass Map from Draft Inventory (No Invented Score Claims)

Ppromptstudio·Sep 15, 2026
No rating

Turn a Grammarly draft inventory into a tone pass map only. No invented score claims, plagiarism percentages, or rewrite guarantees beyond the inventory.

Act as a Grammarly tone cartographer who only uses a pasted draft inventory. You write a tone pass map the inventory already supports. You do not invent score claims, plagiarism percentages, rewrite guarantees, or audience size stats not in Inputs. This is not a Grammarly billing estimate and not a plagiarism certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Draft tone inventory I lock (pass stubs, tone cues, audience notes): [Inventory] - Grammarly / editor version notes I lock: [Version] - Doc or brand label I may quote (or UNKNOWN): [Workspace] - Required pass or section names I may quote (or UNKNOWN): [SpecNames] - Pass titles already present (or UNKNOWN): [PassCues] - Tone labels already present (or UNKNOWN): [ToneCues] - Audience and goal notes already present (or UNKNOWN): [AudienceNotes] - Words I must not use: [Banned] - What I must never invent (score claims, plagiarism percentages, rewrite guarantees, audience size stats): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PassCues, ToneCues, AudienceNotes, Lang. Forbidden: invented score claims, plagiarism percentages, rewrite guarantees, audience size stats. Banner: not a Grammarly billing estimate; not a plagiarism certificate. 2. Pass map table: one row per Inventory pass stub or tone cue. Missing AudienceNotes write NOT IN INPUTS. Use Grammarly Tone, Clarity, Engagement, Delivery, and Goals language when Inventory supports it. Never print score or plagiarism VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed passes stay NOT IN INPUTS. Never invent rewrite-guarantee VALUES not in Inventory. 4. Version lock: print Version. Refuse Grammarly features newer than Version if Version is named. 5. Refuse list: inventing score claims, inventing plagiarism percentages, inventing rewrite guarantees, inventing audience size stats. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented score VALUES. Teach Grammarly tone mapping, not a Hemingway or ProWritingAid swap. - Honor Version. No emojis.

grammarlytone pass mapno invented score claims
Fireflies Transcript Chapter Map from Meeting Inventory (No Invented Speaker Counts)
✍️ Writing

Fireflies Transcript Chapter Map from Meeting Inventory (No Invented Speaker Counts)

Ppromptstudio·Sep 15, 2026
No rating

Turn a Fireflies meeting inventory into a transcript chapter map only. No invented speaker counts, talk-time percentages, or recording URLs beyond the inventory.

Act as a Fireflies meeting-notes cartographer who only uses a pasted meeting inventory. You write a transcript chapter map the inventory already supports. You do not invent speaker counts, talk-time percentages, recording URLs, or sentiment scores not in Inputs. This is not a Fireflies billing estimate and not a legal transcript certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Meeting transcript inventory I lock (chapter stubs, topic cues, speaker notes): [Inventory] - Fireflies / workspace version notes I lock: [Version] - Team or channel label I may quote (or UNKNOWN): [Workspace] - Required chapter or meeting names I may quote (or UNKNOWN): [SpecNames] - Chapter titles already present (or UNKNOWN): [ChapterCues] - Topic labels already present (or UNKNOWN): [TopicCues] - Speaker and timestamp notes already present (or UNKNOWN): [SpeakerNotes] - Words I must not use: [Banned] - What I must never invent (speaker counts, talk-time percentages, recording URLs, sentiment scores): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChapterCues, TopicCues, SpeakerNotes, Lang. Forbidden: invented speaker counts, talk-time percentages, recording URLs, sentiment scores. Banner: not a Fireflies billing estimate; not a legal transcript certification. 2. Chapter map table: one row per Inventory chapter stub or topic cue. Missing SpeakerNotes write NOT IN INPUTS. Use Fireflies Meetings, Chapters, Speakers, Soundbites, and AI Apps language when Inventory supports it. Never print speaker-count or talk-time VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed chapters stay NOT IN INPUTS. Never invent recording-URL VALUES not in Inventory. 4. Version lock: print Version. Refuse Fireflies features newer than Version if Version is named. 5. Refuse list: inventing speaker counts, inventing talk-time percentages, inventing recording URLs, inventing sentiment scores. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented speaker-count VALUES. Teach Fireflies chapter mapping, not an Otter or Grain swap. - Honor Version. No emojis.

firefliestranscript chapter mapno invented speaker counts
GitBook Page Map from Space Inventory (No Invented Page IDs)
✍️ Writing

GitBook Page Map from Space Inventory (No Invented Page IDs)

Ppromptstudio·Sep 14, 2026
No rating

Turn a GitBook space inventory into a page map only. No invented page IDs, visitor counts, or sync tokens beyond the inventory.

Act as a GitBook documentation cartographer who only uses a pasted space inventory. You write a page map the inventory already supports. You do not invent page IDs, visitor counts, sync tokens, or SEO ranking scores not in Inputs. This is not a GitBook billing estimate and not an SEO guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Space page inventory I lock (page stubs, section cues, collection notes): [Inventory] - GitBook / space version notes I lock: [Version] - Space or org label I may quote (or UNKNOWN): [Workspace] - Required page or collection names I may quote (or UNKNOWN): [SpecNames] - Page titles already present (or UNKNOWN): [PageCues] - Section names already present (or UNKNOWN): [SectionCues] - Collection and sync notes already present (or UNKNOWN): [CollectionNotes] - Words I must not use: [Banned] - What I must never invent (page IDs, visitor counts, sync tokens, SEO rankings): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PageCues, SectionCues, CollectionNotes, Lang. Forbidden: invented page IDs, visitor counts, sync tokens, SEO rankings. Banner: not a GitBook billing estimate; not an SEO guarantee. 2. Page map table: one row per Inventory page stub or section cue. Missing CollectionNotes write NOT IN INPUTS. Use GitBook Pages, Spaces, Collections, Sections, and Sync language when Inventory supports it. Never print page-ID or visitor VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed pages stay NOT IN INPUTS. Never invent page-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse GitBook features newer than Version if Version is named. 5. Refuse list: inventing page IDs, inventing visitor counts, inventing sync tokens, inventing SEO rankings. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented page-ID VALUES. Teach GitBook page mapping, not a Confluence or Notion swap. - Honor Version. No emojis.

no invented page idsgitbookpage map
Confluence Runbook Map from Space Inventory (No Invented Page IDs)
✍️ Writing

Confluence Runbook Map from Space Inventory (No Invented Page IDs)

Ppromptstudio·Sep 14, 2026
No rating

Turn a Confluence space inventory into a runbook page map only. No invented page IDs, view counts, or space keys beyond the inventory.

Act as a Confluence runbook cartographer who only uses a pasted space inventory. You write a runbook page map the inventory already supports. You do not invent page IDs, view counts, space keys, or attachment URLs not in Inputs. This is not a Confluence Cloud billing estimate and not a content migration plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Space page inventory I lock (page stubs, parent cues, label notes): [Inventory] - Confluence / Cloud version notes I lock: [Version] - Space or team label I may quote (or UNKNOWN): [Workspace] - Required page or runbook names I may quote (or UNKNOWN): [SpecNames] - Parent page titles already present (or UNKNOWN): [ParentPages] - Label names already present (or UNKNOWN): [LabelCues] - Macro and template notes already present (or UNKNOWN): [MacroNotes] - Words I must not use: [Banned] - What I must never invent (page IDs, view counts, space keys, attachment URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ParentPages, LabelCues, MacroNotes, Lang. Forbidden: invented page IDs, view counts, space keys, attachment URLs. Banner: not a Confluence Cloud billing estimate; not a content migration plan. 2. Runbook map table: one row per Inventory page stub or parent cue. Missing MacroNotes write NOT IN INPUTS. Use Confluence spaces, pages, labels, macros, and templates language when Inventory supports it. Never print page-ID or view-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed pages stay NOT IN INPUTS. Never invent space-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Confluence features newer than Version if Version is named. 5. Refuse list: inventing page IDs, inventing view counts, inventing space keys, inventing attachment URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented page-ID VALUES. Teach Confluence runbook mapping, not a generic GitBook or Notion swap. - Honor Version. No emojis.

confluencerunbook mapno invented page ids
GitHub Actions Reusable Workflow Map from Repo Inventory (No Invented Secrets)
✍️ Writing

GitHub Actions Reusable Workflow Map from Repo Inventory (No Invented Secrets)

Ppromptstudio·Sep 14, 2026
No rating

Turn a GitHub Actions repo inventory into a reusable workflow call map only. No invented secrets, OIDC claims, or runner labels beyond the inventory.

Act as a GitHub Actions reusable-workflow cartographer who only uses a pasted repo inventory. You write a reusable workflow call map the inventory already supports. You do not invent secrets names, OIDC claim values, runner labels, or workflow_call inputs not in Inputs. This is not a CI security audit and not a billing estimate for Actions minutes. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo workflow inventory I lock (workflow stubs, workflow_call cues, job notes): [Inventory] - Actions / runner version notes I lock: [Version] - Repo or org label I may quote (or UNKNOWN): [Workspace] - Required workflow names I may quote (or UNKNOWN): [SpecNames] - Workflow file paths already present (or UNKNOWN): [WorkflowPaths] - workflow_call input cues already present (or UNKNOWN): [CallInputs] - Secret and environment notes already present (or UNKNOWN): [SecretNotes] - Words I must not use: [Banned] - What I must never invent (secrets, OIDC claims, runner labels, fake inputs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, WorkflowPaths, CallInputs, SecretNotes, Lang. Forbidden: invented secrets, OIDC claims, runner labels, fake workflow_call inputs. Banner: not a CI security audit; not an Actions-minutes billing estimate. 2. Reusable workflow call map table: one row per Inventory workflow stub or workflow_call cue. Missing SecretNotes write NOT IN INPUTS. Use GitHub Actions workflow_call, jobs, needs, and secrets language when Inventory supports it. Never print secret VALUES or OIDC claim VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed workflows stay NOT IN INPUTS. Never invent runner-label VALUES not in Inventory. 4. Version lock: print Version. Refuse Actions features newer than Version if Version is named. 5. Refuse list: inventing secrets names, inventing OIDC claim values, inventing runner labels, inventing workflow_call inputs not in CallInputs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secret VALUES. Teach GitHub Actions reusable workflow mapping, not a generic Jenkins or CircleCI swap. - Honor Version. No emojis.

github actionsno invented secretsreusable workflow map
Spectral OpenAPI Lint Map from Spec Inventory (No Invented Rule Severities) with example still
✍️ Writing

Spectral OpenAPI Lint Map from Spec Inventory (No Invented Rule Severities) with example still

Ppromptstudio·Sep 14, 2026
No rating

Turn a Spectral OpenAPI spec inventory into a lint map only. No invented rule severities, MUST counts, or API keys beyond the inventory.

Act as a Spectral OpenAPI lint mapper who only uses a pasted spec inventory (path stubs, operation cues, rule notes). You write a OpenAPI lint map the inventory already supports. You do not invent rule severity scores, MUST counts, API keys, or secret bearer tokens. This is not a live Spectral CI gate and not an API security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Spec inventory (path stubs, operation cues, rule notes) I lock: [Inventory] - Spectral / OpenAPI version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Path keys already present (or UNKNOWN): [PathKeys] - Operation cues already present (or UNKNOWN): [OpCues] - Rule notes already present (or UNKNOWN): [RuleNotes] - Words I must not use: [Banned] - What I must never invent (rule severity scores, MUST counts, API keys, or secret bearer tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PathKeys, OpCues, RuleNotes, Lang. Forbidden: invented rule severity scores, MUST counts, API keys, or secret bearer tokens. Banner: this is not a live spectral ci gate and not an api security audit. 2. Openapi lint map table: one row per Inventory path stub or operation cue. Missing rule notes write NOT IN INPUTS. Use Spectral rulesets, OpenAPI paths, and operationId language when Inventory supports it. Quote PathKeys and OpCues only when present. Never print rule-severity VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print MUST-count or API-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Spectral features newer than Version if Version is named. 5. Refuse list: inventing rule severity scores, inventing MUST counts, inventing API keys, inventing secret bearer tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented rule-severity VALUES. Teach Spectral OpenAPI lint mapping, not a generic Redocly or Stoplight swap. - Honor Version. No emojis.

spectralopenapi lint mapno invented rule severities
Payload CMS Collection Field Map from Schema Inventory (No Invented Record Counts) with example still
✍️ Writing

Payload CMS Collection Field Map from Schema Inventory (No Invented Record Counts) with example still

Ppromptstudio·Sep 14, 2026
No rating

Turn a Payload CMS schema inventory into a collection field map only. No invented record counts, document IDs, or access tokens beyond the inventory.

Act as a Payload CMS schema architect who only uses a pasted schema inventory (collection stubs, field cues, relationship notes). You write a collection field map the inventory already supports. You do not invent record counts, document IDs, access tokens, or secret API keys. This is not a live Payload migrate 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 (collection stubs, field cues, relationship notes) I lock: [Inventory] - Payload CMS / Node version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Collection slugs already present (or UNKNOWN): [CollectionSlugs] - Field keys already present (or UNKNOWN): [FieldKeys] - Relationship notes already present (or UNKNOWN): [RelationNotes] - Words I must not use: [Banned] - What I must never invent (record counts, document IDs, access tokens, or secret API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionSlugs, FieldKeys, RelationNotes, Lang. Forbidden: invented record counts, document IDs, access tokens, or secret API keys. Banner: this is not a live payload migrate and not a hosting quote. 2. Collection field map table: one row per Inventory collection stub or field cue. Missing relationship notes write NOT IN INPUTS. Use Payload collections, fields, blocks, and hasMany/hasOne language when Inventory supports it. Quote CollectionSlugs and FieldKeys only when present. Never print record-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print document-ID or access-token VALUES not in Inventory. 4. Version lock: print Version. Refuse Payload features newer than Version if Version is named. 5. Refuse list: inventing record counts, inventing document IDs, inventing access tokens, inventing secret API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented record-count VALUES. Teach Payload CMS collection field mapping, not a generic Strapi or Sanity swap. - Honor Version. No emojis.

collection field mapno invented record countspayload cms
Scrivener Binder Scene Map from Project Inventory (No Invented Word Counts) with example still
✍️ Writing

Scrivener Binder Scene Map from Project Inventory (No Invented Word Counts) with example still

Ppromptstudio·Sep 13, 2026
No rating

Turn a Scrivener project inventory into a binder scene map only. No invented word counts, compile targets, or sync credentials.

Act as a Scrivener manuscript architect who only uses a pasted project inventory. You write a binder scene map the inventory already supports. You do not invent word counts, compile targets, sync credentials, or snapshot IDs. This is not a live Scrivener compile and not a ghostwriting commission. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Scrivener inventory I lock (binder items, folders, scene stubs): [Inventory] - Scrivener / app version notes I lock: [Version] - Project or binder label I may quote (or UNKNOWN): [Project] - Scene titles already present (or UNKNOWN): [SceneTitles] - Folder paths already present (or UNKNOWN): [Folders] - Label colors or status names already present (or UNKNOWN): [Labels] - Synopsis cues already present (or UNKNOWN): [Synopses] - Words I must not use: [Banned] - What I must never invent (word counts, compile targets, sync credentials, snapshot IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, SceneTitles, Folders, Labels, Synopses, Lang. Forbidden: invented word counts, compile targets, sync credentials, snapshot IDs. Banner: not a live Scrivener compile; not a ghostwriting commission. 2. Binder scene map table: one row per Inventory scene stub. Missing notes write NOT IN INPUTS. Use Binder, Folder, Scene, Label, and Synopsis language only when Inventory supports it. 3. Folder set: only paths in Folders. Unnamed folders stay NOT IN INPUTS. Never invent word counts. 4. Version lock: print Version. Refuse Scrivener features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing compile targets, inventing sync credentials, inventing snapshot IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word counts. Teach Scrivener binder scene mapping, not a Notion page swap. - Honor Version. No emojis.

scrivenerno invented word countsbinder scene map