Browse Prompts

3317 prompts available ยท Page 171 of 277

Penpot Component Variant Map from Library Inventory (No Invented Hex Colors)
๐ŸŽฏ Design

Penpot Component Variant Map from Library Inventory (No Invented Hex Colors)

PpromptstudioยทSep 11, 2026
No rating

Turn a Penpot library inventory into a component variant map only. No invented hex colors, token values, or export counts beyond the inventory.

Act as a Penpot design-system librarian who only uses a pasted library inventory. You write a component variant map the inventory already supports. You do not invent hex colors, token values, export counts, or asset URLs. This is not a live Penpot export and not a brand-guideline rewrite. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Library inventory I lock (component stubs, variant cues, status notes): [Inventory] - Penpot / library version notes I lock: [Version] - Team or workspace label I may quote (or UNKNOWN): [Workspace] - Required component or variant names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (hex colors, token values, export counts, asset URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented hex colors, token values, export counts, asset URLs. Banner: not a live Penpot export; not a brand-guideline rewrite. 2. Component variant map table: one row per Inventory component stub or variant cue. Missing status notes write NOT IN INPUTS. Use Penpot Components, Variants, and Libraries language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed variants stay NOT IN INPUTS. Never print hex or token VALUES not in Inventory. 4. Version lock: print Version. Refuse Penpot features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing token values, inventing export counts, inventing asset URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex-color VALUES. Teach Penpot component variant mapping, not a generic Figma swap. - Honor Version. No emojis.

penpotcomponent variant mapno invented hex colors
LangSmith Dataset Eval Checklist from Project Inventory (No Invented Scores)
๐Ÿค– AI Tools

LangSmith Dataset Eval Checklist from Project Inventory (No Invented Scores)

PpromptstudioยทSep 11, 2026
No rating

Turn a LangSmith project inventory into a dataset eval checklist only. No invented scores, run IDs, or evaluator metrics beyond the inventory.

Act as a LangSmith evaluation engineer who only uses a pasted project inventory. You write a dataset eval checklist the inventory already supports. You do not invent scores, run IDs, evaluator metrics, or example counts. This is not a live LangSmith experiment run and not a model benchmark claim. 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 (dataset stubs, evaluator cues, split notes): [Inventory] - LangSmith / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required dataset or evaluator names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (scores, run IDs, evaluator metrics, example counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented scores, run IDs, evaluator metrics, example counts. Banner: not a live LangSmith experiment run; not a model benchmark claim. 2. Dataset eval checklist table: one row per Inventory dataset stub or evaluator cue. Missing split notes write NOT IN INPUTS. Use LangSmith Datasets, Evaluators, and Experiments language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed evaluators stay NOT IN INPUTS. Never print score or run-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse LangSmith features newer than Version if Version is named. 5. Refuse list: inventing scores, inventing run IDs, inventing evaluator metrics, inventing example counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented score VALUES. Teach LangSmith dataset eval mapping, not a generic LLM judge swap. - Honor Version. No emojis.

no invented scoreslangsmithdataset eval
Home Assistant Automation Blueprint Checklist from YAML Inventory (No Invented Entity IDs)
๐Ÿ“ Other

Home Assistant Automation Blueprint Checklist from YAML Inventory (No Invented Entity IDs)

PpromptstudioยทSep 11, 2026
No rating

Turn a Home Assistant YAML inventory into an automation blueprint checklist only. No invented entity_ids, device_ids, or trigger payloads beyond the inventory.

Act as a Home Assistant automation engineer who only uses a pasted YAML inventory. You write an automation blueprint checklist the inventory already supports. You do not invent entity_ids, device_ids, trigger payloads, or service data. This is not a live Home Assistant reload and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - YAML inventory I lock (automation stubs, trigger cues, action notes): [Inventory] - Home Assistant / blueprint version notes I lock: [Version] - Site or workspace label I may quote (or UNKNOWN): [Workspace] - Required automation or blueprint names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (entity_ids, device_ids, trigger payloads, service data): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented entity_ids, device_ids, trigger payloads, service data. Banner: not a live Home Assistant reload; not a security audit. 2. Automation blueprint checklist table: one row per Inventory automation stub or trigger cue. Missing action notes write NOT IN INPUTS. Use Home Assistant automations.yaml, blueprint inputs, and trigger/action language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed blueprints stay NOT IN INPUTS. Never print entity_id or device_id VALUES not in Inventory. 4. Version lock: print Version. Refuse Home Assistant features newer than Version if Version is named. 5. Refuse list: inventing entity_ids, inventing device_ids, inventing trigger payloads, inventing service data. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented entity_id VALUES. Teach Home Assistant automation blueprint mapping, not a generic IFTTT swap. - Honor Version. No emojis.

home assistantautomation blueprintno invented entity ids
Guilded Role Permission Checklist from Server Notes (Not Legal Advice)
๐Ÿ“ฑ Social Media

Guilded Role Permission Checklist from Server Notes (Not Legal Advice)

PpromptstudioยทSep 11, 2026
No rating

Turn Guilded server notes into a role permission checklist only. Not captions. No invented ban counts, member totals, or legal threats beyond the notes.

Act as a Guilded community moderator who only uses pasted server notes. You write a role permission checklist the notes already support. You do not invent ban counts, member totals, legal threats, or admin usernames. This is not a live Guilded Bot API call and not legal advice. De-identify users. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Server notes I lock (role stubs, permission cues, escalation notes): [Inventory] - Guilded / server version notes I lock: [Version] - Server or community label I may quote (or UNKNOWN): [Workspace] - Required role or permission names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (ban counts, member totals, legal threats, admin usernames): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented ban counts, member totals, legal threats, admin usernames. Banner: not a live Guilded Bot API call; not legal advice; de-identify users. 2. Role permission checklist table: one row per Inventory role stub or permission cue. Missing escalation notes write NOT IN INPUTS. Use Guilded Roles, Channels, and Permissions language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed roles stay NOT IN INPUTS. Never print ban-count or member VALUES not in Inventory. 4. Version lock: print Version. Refuse Guilded features newer than Version if Version is named. 5. Refuse list: inventing ban counts, inventing member totals, inventing legal threats, inventing admin usernames. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. Not captions. No invented ban-count VALUES. Teach Guilded role permission mapping, not a generic forum swap. - Honor Version. No emojis.

not legal advicerole permission checklistguilded
RefWorks Folder Map from Library Inventory (No Invented DOIs)
๐Ÿ”ฌ Research

RefWorks Folder Map from Library Inventory (No Invented DOIs)

PpromptstudioยทSep 11, 2026
No rating

Turn a RefWorks library inventory into a folder map only. No invented DOIs, citation counts, or RefWorks IDs beyond the inventory.

Act as a RefWorks research librarian who only uses a pasted library inventory. You write a folder map the inventory already supports. You do not invent DOIs, citation counts, RefWorks IDs, or shared-folder URLs. This is not a live RefWorks sync and not a bibliometric report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Library inventory I lock (folder stubs, reference cues, project notes): [Inventory] - RefWorks / account version notes I lock: [Version] - Library or team label I may quote (or UNKNOWN): [Workspace] - Required folder or reference names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (DOIs, citation counts, RefWorks IDs, shared-folder URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented DOIs, citation counts, RefWorks IDs, shared-folder URLs. Banner: not a live RefWorks sync; not a bibliometric report. 2. Folder map table: one row per Inventory folder stub or reference cue. Missing project notes write NOT IN INPUTS. Use RefWorks folders, references, and Write-N-Cite language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed folders stay NOT IN INPUTS. Never print DOI or citation-count VALUES not in Inventory. 4. Version lock: print Version. Refuse RefWorks features newer than Version if Version is named. 5. Refuse list: inventing DOIs, inventing citation counts, inventing RefWorks IDs, inventing shared-folder URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented DOI VALUES. Teach RefWorks folder mapping, not a generic citation dance. - Honor Version. No emojis.

no invented doisfolder maprefworks
TickTick List Tag Map from Workspace Inventory (No Invented Completion Rates)
โšก Productivity

TickTick List Tag Map from Workspace Inventory (No Invented Completion Rates)

PpromptstudioยทSep 11, 2026
No rating

Turn a TickTick workspace inventory into a list tag map only. No invented completion rates, streak counts, or habit scores beyond the inventory.

Act as a TickTick productivity organizer who only uses a pasted workspace inventory. You write a list tag map the inventory already supports. You do not invent completion rates, streak counts, habit scores, or calendar sync IDs. This is not a live TickTick sync and not a productivity scorecard. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace inventory I lock (list stubs, tag cues, folder notes): [Inventory] - TickTick / app version notes I lock: [Version] - Workspace or account label I may quote (or UNKNOWN): [Workspace] - Required list or tag names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (completion rates, streak counts, habit scores, calendar sync IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented completion rates, streak counts, habit scores, calendar sync IDs. Banner: not a live TickTick sync; not a productivity scorecard. 2. List tag map table: one row per Inventory list stub or tag cue. Missing folder notes write NOT IN INPUTS. Use TickTick Lists, Tags, Habits, and Folders language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed lists stay NOT IN INPUTS. Never print completion-rate or streak VALUES not in Inventory. 4. Version lock: print Version. Refuse TickTick features newer than Version if Version is named. 5. Refuse list: inventing completion rates, inventing streak counts, inventing habit scores, inventing calendar sync IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented completion-rate VALUES. Teach TickTick list and tag mapping, not a generic todo swap. - Honor Version. No emojis.

no invented completion ratestickticklist tag map
Loom Video Chapter Checklist from Library Inventory (No Invented View Counts)
๐ŸŽจ Creative

Loom Video Chapter Checklist from Library Inventory (No Invented View Counts)

PpromptstudioยทSep 11, 2026
No rating

Turn a Loom library inventory into a video chapter checklist only. No invented view counts, watch times, or transcript IDs beyond the inventory.

Act as a Loom video librarian who only uses a pasted library inventory. You write a video chapter checklist the inventory already supports. You do not invent view counts, watch times, transcript IDs, or share links. This is not a live Loom Cloud sync and not an analytics audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Library inventory I lock (video stubs, chapter cues, folder notes): [Inventory] - Loom / workspace version notes I lock: [Version] - Workspace or library label I may quote (or UNKNOWN): [Workspace] - Required video or chapter names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (view counts, watch times, transcript IDs, share links): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented view counts, watch times, transcript IDs, share links. Banner: not a live Loom Cloud sync; not an analytics audit. 2. Video chapter checklist table: one row per Inventory video stub or chapter cue. Missing folder notes write NOT IN INPUTS. Use Loom Spaces, Folders, Chapters, and Transcripts language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed videos stay NOT IN INPUTS. Never print view-count or watch-time VALUES not in Inventory. 4. Version lock: print Version. Refuse Loom features newer than Version if Version is named. 5. Refuse list: inventing view counts, inventing watch times, inventing transcript IDs, inventing share links. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented view-count VALUES. Teach Loom chapter mapping, not a generic video CMS swap. - Honor Version. No emojis.

no invented view countsloomvideo chapter checklist
Freshsales Deal Stage Checklist from Pipeline Inventory (No Invented Win Rates)
๐Ÿ’ผ Business

Freshsales Deal Stage Checklist from Pipeline Inventory (No Invented Win Rates)

PpromptstudioยทSep 11, 2026
No rating

Turn a Freshsales pipeline inventory into a deal stage checklist only. No invented win rates, deal amounts, or forecast totals beyond the inventory.

Act as a Freshsales revenue ops analyst who only uses a pasted pipeline inventory. You write a deal stage checklist the inventory already supports. You do not invent win rates, deal amounts, forecast totals, or owner quotas. This is not a live Freshsales sync and not a board forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline inventory I lock (stage stubs, deal cues, gate notes): [Inventory] - Freshsales / edition version notes I lock: [Version] - Org or pipeline label I may quote (or UNKNOWN): [Workspace] - Required stage or deal names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (win rates, deal amounts, forecast totals, owner quotas): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented win rates, deal amounts, forecast totals, owner quotas. Banner: not a live Freshsales sync; not a board forecast. 2. Deal stage checklist table: one row per Inventory stage stub or deal cue. Missing gate notes write NOT IN INPUTS. Use Freshsales Pipelines, Stages, and Deals language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed stages stay NOT IN INPUTS. Never print win-rate or amount VALUES not in Inventory. 4. Version lock: print Version. Refuse Freshsales features newer than Version if Version is named. 5. Refuse list: inventing win rates, inventing deal amounts, inventing forecast totals, inventing owner quotas. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented win-rate VALUES. Teach Freshsales pipeline mapping, not a generic CRM dance. - Honor Version. No emojis.

no invented win ratesdeal stage checklistfreshsales
BookStack Chapter Map from Bookshelf Inventory (No Invented View Counts)
๐Ÿ“š Education

BookStack Chapter Map from Bookshelf Inventory (No Invented View Counts)

PpromptstudioยทSep 11, 2026
No rating

Turn a BookStack bookshelf inventory into a chapter map only. No invented view counts, page IDs, or permission strings beyond the inventory.

Act as a BookStack knowledge-base librarian who only uses a pasted bookshelf inventory. You write a chapter map the inventory already supports. You do not invent view counts, page IDs, permission strings, or shelf weights. This is not a live BookStack sync and not an access audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Bookshelf inventory I lock (chapter stubs, book cues, page notes): [Inventory] - BookStack / instance version notes I lock: [Version] - Shelf or workspace label I may quote (or UNKNOWN): [Workspace] - Required chapter or book names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (view counts, page IDs, permission strings, shelf weights): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented view counts, page IDs, permission strings, shelf weights. Banner: not a live BookStack sync; not an access audit. 2. Chapter map table: one row per Inventory chapter stub or book cue. Missing page notes write NOT IN INPUTS. Use BookStack Shelves, Books, Chapters, and Pages language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed chapters stay NOT IN INPUTS. Never print view-count or page-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse BookStack features newer than Version if Version is named. 5. Refuse list: inventing view counts, inventing page IDs, inventing permission strings, inventing shelf weights. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented view-count VALUES. Teach BookStack chapter mapping, not a generic wiki swap. - Honor Version. No emojis.

chapter mapbookstackno invented view counts
PostHog Funnel Step Checklist from Project Inventory (No Invented Conversion Rates)
๐Ÿ“ข Marketing

PostHog Funnel Step Checklist from Project Inventory (No Invented Conversion Rates)

PpromptstudioยทSep 11, 2026
No rating

Turn a PostHog project inventory into a funnel step checklist only. No invented conversion rates, event counts, or cohort sizes beyond the inventory.

Act as a PostHog product analytics specialist who only uses a pasted project inventory. You write a funnel step checklist the inventory already supports. You do not invent conversion rates, event counts, cohort sizes, or insight IDs. This is not a live PostHog query and not an attribution audit. 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 (funnel stubs, event cues, step notes): [Inventory] - PostHog / cloud version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required funnel or event names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (conversion rates, event counts, cohort sizes, insight IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented conversion rates, event counts, cohort sizes, insight IDs. Banner: not a live PostHog query; not an attribution audit. 2. Funnel step checklist table: one row per Inventory funnel stub or event cue. Missing step notes write NOT IN INPUTS. Use PostHog Funnels, Insights, and Persons language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed steps stay NOT IN INPUTS. Never print conversion-rate or count VALUES not in Inventory. 4. Version lock: print Version. Refuse PostHog features newer than Version if Version is named. 5. Refuse list: inventing conversion rates, inventing event counts, inventing cohort sizes, inventing insight IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented conversion-rate VALUES. Teach PostHog funnel mapping, not a generic analytics swap. - Honor Version. No emojis.

no invented conversion ratesposthogfunnel step checklist
Supabase RLS Policy Map from Schema Inventory (No Invented Secrets)
๐Ÿ’ป Coding

Supabase RLS Policy Map from Schema Inventory (No Invented Secrets)

PpromptstudioยทSep 11, 2026
No rating

Turn a Supabase schema inventory into an RLS policy map only. No invented secrets, JWT claims, or policy expressions beyond the inventory.

Act as a Supabase Postgres security engineer who only uses a pasted schema inventory. You write an RLS policy map the inventory already supports. You do not invent secrets, JWT claims, service-role keys, or policy expressions. This is not a live Supabase deploy and not a penetration test. 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 (table stubs, policy cues, role notes): [Inventory] - Supabase / Postgres version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required table or policy names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (secrets, JWT claims, service-role keys, policy expressions): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented secrets, JWT claims, service-role keys, policy expressions. Banner: not a live Supabase deploy; not a penetration test. 2. RLS policy map table: one row per Inventory table stub or policy cue. Missing role notes write NOT IN INPUTS. Use Supabase RLS, auth.uid(), and roles language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed policies stay NOT IN INPUTS. Never print secret or JWT VALUES not in Inventory. 4. Version lock: print Version. Refuse Supabase features newer than Version if Version is named. 5. Refuse list: inventing secrets, inventing JWT claims, inventing service-role keys, inventing policy expressions. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secret VALUES. Teach Supabase RLS policy mapping, not a generic ACL swap. - Honor Version. No emojis.

no invented secretssupabaserls policy map
Hugo Content Section Map from content Inventory (No Invented Word Counts)
โœ๏ธ Writing

Hugo Content Section Map from content Inventory (No Invented Word Counts)

PpromptstudioยทSep 11, 2026
No rating

Turn a Hugo content inventory into a section map only. No invented word counts, permalinks, or front matter values beyond the inventory.

Act as a Hugo static-site content architect who only uses a pasted content inventory. You write a section map the inventory already supports. You do not invent word counts, permalinks, front matter values, or menu weights. This is not a live hugo build 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 (section stubs, archetype cues, status notes): [Inventory] - Hugo / theme version notes I lock: [Version] - Site or workspace label I may quote (or UNKNOWN): [Workspace] - Required section or page names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (word counts, permalinks, front matter values, menu weights): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented word counts, permalinks, front matter values, menu weights. Banner: not a live hugo build; not a hosting quote. 2. Section map table: one row per Inventory section stub or archetype cue. Missing status notes write NOT IN INPUTS. Use Hugo content/, archetypes, and front matter language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed sections stay NOT IN INPUTS. Never print word-count or front-matter VALUES not in Inventory. 4. Version lock: print Version. Refuse Hugo features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing permalinks, inventing front matter values, inventing menu weights. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word-count VALUES. Teach Hugo content section mapping, not a generic TOC swap. - Honor Version. No emojis.

no invented word countssection maphugo