Browse Prompts

3317 prompts available ยท Page 155 of 277

Metricool Queue Checklist from Calendar Inventory (No Invented Engagement Rates) with example still
๐Ÿ“ฑ Social Media

Metricool Queue Checklist from Calendar Inventory (No Invented Engagement Rates) with example still

PpromptstudioยทSep 14, 2026
No rating

Turn a Metricool calendar inventory into a queue checklist only. No invented engagement rates, follower counts, or API tokens beyond the inventory.

Act as a Metricool social queue planner who only uses a pasted calendar inventory (queue stubs, slot cues, channel notes). You write a queue checklist the inventory already supports. You do not invent engagement rates, follower counts, post IDs, or API tokens. This is not a live Metricool publish and not an engagement audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Calendar inventory I lock (queue stubs, slot cues, channel notes): [Inventory] - Metricool / brand version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Queue names already present (or UNKNOWN): [QueueNames] - Slot labels already present (or UNKNOWN): [SlotLabels] - Channel notes already present (or UNKNOWN): [ChannelNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, follower counts, post IDs, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, QueueNames, SlotLabels, ChannelNotes, Lang. Forbidden: invented engagement rates, follower counts, post IDs, API tokens. Banner: not a live Metricool publish; not an engagement audit. 2. Queue checklist table: one row per Inventory queue stub or slot cue. Missing channel notes write NOT IN INPUTS. Use Metricool planner queues, best-time slots, and brand channels when Inventory supports it. Quote QueueNames and SlotLabels only when present. Never print engagement-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print follower-count or post-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Metricool features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing follower counts, inventing post IDs, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented engagement-rate VALUES. Teach Metricool queue checklists, not a generic Later or Buffer swap. - Honor Version. No emojis.

queue checklistno invented engagement ratesmetricool
Zotero Collection Folder Map from Library Inventory (No Invented DOIs) with example still
๐Ÿ”ฌ Research

Zotero Collection Folder Map from Library Inventory (No Invented DOIs) with example still

PpromptstudioยทSep 14, 2026
No rating

Turn a Zotero library inventory into a collection folder map only. No invented DOIs, citation counts, or API keys beyond the inventory.

Act as a Zotero library curator who only uses a pasted library inventory (collection stubs, folder cues, item-type notes). You write a collection folder map the inventory already supports. You do not invent DOIs, citation counts, item keys, or API keys. This is not a live Zotero sync and not a systematic review claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Library inventory (collection stubs, folder cues, item-type notes) I lock: [Inventory] - Zotero / library version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Collection names already present (or UNKNOWN): [CollectionNames] - Folder labels already present (or UNKNOWN): [FolderLabels] - Item-type notes already present (or UNKNOWN): [ItemTypeNotes] - Words I must not use: [Banned] - What I must never invent (DOIs, citation counts, item keys, or API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionNames, FolderLabels, ItemTypeNotes, Lang. Forbidden: invented DOIs, citation counts, item keys, or API keys. Banner: this is not a live zotero sync and not a systematic review claim. 2. Collection folder map table: one row per Inventory collection stub or folder cue. Missing item-type notes write NOT IN INPUTS. Use Zotero collections, subcollections, item types, and tags when Inventory supports it. Quote CollectionNames and FolderLabels only when present. Never print DOI VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print citation-count or item-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Zotero features newer than Version if Version is named. 5. Refuse list: inventing DOIs, inventing citation counts, inventing item keys, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented DOI VALUES. Teach Zotero collection folder mapping, not a generic EndNote or Mendeley swap. - Honor Version. No emojis.

no invented doiszoterocollection folder map
Linear Workflow State Map from Team Inventory (No Invented Issue Counts) with example still
โšก Productivity

Linear Workflow State Map from Team Inventory (No Invented Issue Counts) with example still

PpromptstudioยทSep 14, 2026
No rating

Turn a Linear team inventory into a workflow state map only. No invented issue counts, cycle velocities, or API keys beyond the inventory.

Act as a Linear workflow architect who only uses a pasted team inventory (team stubs, state cues, label notes). You write a workflow state map the inventory already supports. You do not invent issue counts, cycle velocities, issue IDs, or API keys. This is not a live Linear sync and not a capacity plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Team inventory (team stubs, state cues, label notes) I lock: [Inventory] - Linear / workspace version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Team keys already present (or UNKNOWN): [TeamKeys] - State labels already present (or UNKNOWN): [StateLabels] - Label notes already present (or UNKNOWN): [LabelNotes] - Words I must not use: [Banned] - What I must never invent (issue counts, cycle velocities, issue IDs, or API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TeamKeys, StateLabels, LabelNotes, Lang. Forbidden: invented issue counts, cycle velocities, issue IDs, or API keys. Banner: this is not a live linear sync and not a capacity plan. 2. Workflow state map table: one row per Inventory team stub or state cue. Missing label notes write NOT IN INPUTS. Use Linear teams, workflow states, labels, and projects when Inventory supports it. Quote TeamKeys and StateLabels only when present. Never print issue-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print cycle-velocity or issue-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing issue counts, inventing cycle velocities, inventing issue IDs, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented issue-count VALUES. Teach Linear workflow state mapping, not a generic Jira or Asana swap. - Honor Version. No emojis.

linearworkflow state mapno invented issue counts
Substance Painter Channel Map from Project Inventory (No Invented Texture Resolutions) with example still
๐ŸŽจ Creative

Substance Painter Channel Map from Project Inventory (No Invented Texture Resolutions) with example still

PpromptstudioยทSep 14, 2026
No rating

Turn a Substance Painter project inventory into a channel map only. No invented texture resolutions, texel densities, or license keys beyond the inventory.

Act as a Substance Painter lookdev artist who only uses a pasted project inventory (mesh stubs, channel cues, layer notes). You write a channel map the inventory already supports. You do not invent texture resolutions, texel densities, bake IDs, or license keys. This is not a live Painter bake and not a 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: - Project inventory (mesh stubs, channel cues, layer notes) I lock: [Inventory] - Substance Painter / project version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Mesh names already present (or UNKNOWN): [MeshNames] - Channel labels already present (or UNKNOWN): [ChannelLabels] - Layer notes already present (or UNKNOWN): [LayerNotes] - Words I must not use: [Banned] - What I must never invent (texture resolutions, texel densities, bake IDs, or license keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, MeshNames, ChannelLabels, LayerNotes, Lang. Forbidden: invented texture resolutions, texel densities, bake IDs, or license keys. Banner: this is not a live painter bake and not a render farm quote. 2. Channel map table: one row per Inventory mesh stub or channel cue. Missing layer notes write NOT IN INPUTS. Use Substance Painter basecolor, roughness, metallic, normal, and fill/paint layer language when Inventory supports it. Quote MeshNames and ChannelLabels only when present. Never print texture-resolution VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print texel-density or bake-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Substance Painter features newer than Version if Version is named. 5. Refuse list: inventing texture resolutions, inventing texel densities, inventing bake IDs, inventing license keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented texture-resolution VALUES. Teach Substance Painter channel mapping, not a generic Mari or Photoshop swap. - Honor Version. No emojis.

channel mapno invented texture resolutionssubstance painter
Pipedrive Opportunity Stage Checklist from Pipeline Inventory (No Invented Win Rates) with example still
๐Ÿ’ผ Business

Pipedrive Opportunity Stage Checklist from Pipeline Inventory (No Invented Win Rates) with example still

PpromptstudioยทSep 14, 2026
No rating

Turn a Pipedrive pipeline inventory into an opportunity stage checklist only. No invented win rates, deal amounts, or API tokens beyond the inventory.

Act as a Pipedrive pipeline architect who only uses a pasted pipeline inventory (deal stubs, stage cues, status notes). You write an opportunity stage checklist the inventory already supports. You do not invent win rates, deal amounts, deal IDs, or API tokens. This is not a live Pipedrive sync and not a revenue 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 (deal stubs, stage cues, status notes): [Inventory] - Pipedrive / company version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Pipeline names already present (or UNKNOWN): [PipelineNames] - Stage labels already present (or UNKNOWN): [StageLabels] - Status notes already present (or UNKNOWN): [StatusNotes] - Words I must not use: [Banned] - What I must never invent (win rates, deal amounts, deal IDs, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineNames, StageLabels, StatusNotes, Lang. Forbidden: invented win rates, deal amounts, deal IDs, API tokens. Banner: not a live Pipedrive sync; not a revenue forecast. 2. Opportunity stage checklist table: one row per Inventory deal stub or stage cue. Missing status notes write NOT IN INPUTS. Use Pipedrive pipelines, stages, deals, and custom fields when Inventory supports it. Quote PipelineNames and StageLabels only when present. Never print win-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print deal-amount or deal-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Pipedrive features newer than Version if Version is named. 5. Refuse list: inventing win rates, inventing deal amounts, inventing deal IDs, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented win-rate VALUES. Teach Pipedrive opportunity stage checklists, not a generic Close CRM or HubSpot swap. - Honor Version. No emojis.

no invented win ratespipedriveopportunity stage checklist
LearnWorlds Curriculum Map from Course Inventory (No Invented Enrollment Counts) with example still
๐Ÿ“š Education

LearnWorlds Curriculum Map from Course Inventory (No Invented Enrollment Counts) with example still

PpromptstudioยทSep 14, 2026
No rating

Turn a LearnWorlds course inventory into a curriculum map only. No invented enrollment counts, quiz scores, or API keys beyond the inventory.

Act as a LearnWorlds curriculum designer who only uses a pasted course inventory (course stubs, section cues, learning-activity notes). You write a curriculum map the inventory already supports. You do not invent enrollment counts, quiz scores, completion rates, or API keys. This is not a live LearnWorlds enroll and not an accreditation claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Course inventory I lock (course stubs, section cues, learning-activity notes): [Inventory] - LearnWorlds / school version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Course names already present (or UNKNOWN): [CourseNames] - Section labels already present (or UNKNOWN): [SectionLabels] - Activity notes already present (or UNKNOWN): [ActivityNotes] - Words I must not use: [Banned] - What I must never invent (enrollment counts, quiz scores, completion rates, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CourseNames, SectionLabels, ActivityNotes, Lang. Forbidden: invented enrollment counts, quiz scores, completion rates, API keys. Banner: not a live LearnWorlds enroll; not an accreditation claim. 2. Curriculum map table: one row per Inventory course stub or section cue. Missing activity notes write NOT IN INPUTS. Use LearnWorlds courses, sections, learning activities, and drip language when Inventory supports it. Quote CourseNames and SectionLabels only when present. Never print enrollment-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print quiz-score or completion-rate VALUES not in Inventory. 4. Version lock: print Version. Refuse LearnWorlds features newer than Version if Version is named. 5. Refuse list: inventing enrollment counts, inventing quiz scores, inventing completion rates, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented enrollment-count VALUES. Teach LearnWorlds curriculum mapping, not a generic Thinkific or Kajabi swap. - Honor Version. No emojis.

curriculum mapno invented enrollment countslearnworlds
Brevo Automation Step Checklist from Campaign Inventory (No Invented Open Rates) with example still
๐Ÿ“ข Marketing

Brevo Automation Step Checklist from Campaign Inventory (No Invented Open Rates) with example still

PpromptstudioยทSep 14, 2026
No rating

Turn a Brevo campaign inventory into an automation step checklist only. No invented open rates, click rates, or API keys beyond the inventory.

Act as a Brevo automation architect who only uses a pasted campaign inventory (automation stubs, step cues, trigger notes). You write an automation step checklist the inventory already supports. You do not invent open rates, click rates, message IDs, or API keys. This is not a live Brevo send and not a deliverability audit. 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 (automation stubs, step cues, trigger notes): [Inventory] - Brevo / account version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Automation names already present (or UNKNOWN): [AutomationNames] - Step labels already present (or UNKNOWN): [StepLabels] - Trigger notes already present (or UNKNOWN): [TriggerNotes] - Words I must not use: [Banned] - What I must never invent (open rates, click rates, message IDs, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, AutomationNames, StepLabels, TriggerNotes, Lang. Forbidden: invented open rates, click rates, message IDs, API keys. Banner: not a live Brevo send; not a deliverability audit. 2. Automation step checklist table: one row per Inventory automation stub or step cue. Missing trigger notes write NOT IN INPUTS. Use Brevo automations, wait steps, email/SMS actions, and contact-attribute filters when Inventory supports it. Quote AutomationNames and StepLabels only when present. Never print open-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print click-rate or message-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Brevo features newer than Version if Version is named. 5. Refuse list: inventing open rates, inventing click rates, inventing message IDs, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented open-rate VALUES. Teach Brevo automation step checklists, not a generic Iterable or Klaviyo swap. - Honor Version. No emojis.

no invented open ratesautomation step checklistbrevo
Flyway Migration Map from Changelog Inventory (No Invented Checksums) with example still
๐Ÿ’ป Coding

Flyway Migration Map from Changelog Inventory (No Invented Checksums) with example still

PpromptstudioยทSep 14, 2026
No rating

Turn a Flyway changelog inventory into a migration map only. No invented checksums, row counts, or JDBC URLs beyond the inventory.

Act as a Flyway migration engineer who only uses a pasted changelog inventory (version stubs, script cues, description notes). You write a migration map the inventory already supports. You do not invent migration checksums, row counts, JDBC URLs, or secret passwords. This is not a live database migrate and not a production cutover. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Changelog inventory (version stubs, script cues, description notes) I lock: [Inventory] - Flyway / DBMS version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Version IDs already present (or UNKNOWN): [VersionIds] - Script names already present (or UNKNOWN): [ScriptNames] - Description labels already present (or UNKNOWN): [DescLabels] - Words I must not use: [Banned] - What I must never invent (migration checksums, row counts, JDBC URLs, or secret passwords): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, VersionIds, ScriptNames, DescLabels, Lang. Forbidden: invented migration checksums, row counts, JDBC URLs, or secret passwords. Banner: this is not a live database migrate and not a production cutover. 2. Migration map table: one row per Inventory version stub or script cue. Missing description notes write NOT IN INPUTS. Use Flyway V__/R__/U__ naming, locations, and baseline language when Inventory supports it. Quote VersionIds and ScriptNames only when present. Never print checksum VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print row-count or JDBC VALUES not in Inventory. 4. Version lock: print Version. Refuse Flyway features newer than Version if Version is named. 5. Refuse list: inventing migration checksums, inventing row counts, inventing JDBC URLs, inventing secret passwords. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented checksum VALUES. Teach Flyway migration mapping, not a generic Liquibase or Alembic swap. - Honor Version. No emojis.

flywaymigration mapno invented checksums
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
Whoop Strain Log Checklist from Recovery Inventory (No Invented HRV Scores)
๐ŸŒฟ Lifestyle

Whoop Strain Log Checklist from Recovery Inventory (No Invented HRV Scores)

PpromptstudioยทSep 13, 2026
No rating

Turn a Whoop recovery inventory into a strain log checklist only. No invented HRV scores, sleep stage totals, or medical diagnoses.

Act as a Whoop recovery coach who only uses a pasted recovery inventory. You write a strain log checklist the inventory already supports. You do not invent HRV scores, sleep stage totals, recovery percentages, or medical diagnoses. This is not a live Whoop sync and not medical or training advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Whoop inventory I lock (days, activities, recovery stubs): [Inventory] - Whoop / app version notes I lock: [Version] - Profile or team label I may quote (or UNKNOWN): [Profile] - Day labels already present (or UNKNOWN): [Days] - Activity names already present (or UNKNOWN): [Activities] - Strain band labels already present (or UNKNOWN): [StrainBands] - Recovery note labels already present (or UNKNOWN): [RecoveryNotes] - Words I must not use: [Banned] - What I must never invent (HRV scores, sleep stage totals, recovery percentages, medical diagnoses): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Profile, Days, Activities, StrainBands, RecoveryNotes, Lang. Forbidden: invented HRV scores, sleep stage totals, recovery percentages, medical diagnoses. Banner: not a live Whoop sync; not medical or training advice. Add not-advice de-identify note. 2. Strain log checklist: one row per Inventory day or activity stub. Missing notes write NOT IN INPUTS. Use Day, Activity, StrainBand, and RecoveryNote language only when Inventory supports it. 3. Activity set: only names in Activities. Unnamed activities stay NOT IN INPUTS. Never invent HRV scores. 4. Version lock: print Version. Refuse Whoop features newer than Version if Version is named. 5. Refuse list: inventing HRV scores, inventing sleep stage totals, inventing recovery percentages, inventing medical diagnoses. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented HRV scores. Teach Whoop strain log hygiene, not a training-plan ghostwriter. - Honor Version. No emojis.

whoopstrain log checklistno invented hrv scores
Zeplin Styleguide Component Map from Project Inventory (No Invented Hex Colors)
๐ŸŽฏ Design

Zeplin Styleguide Component Map from Project Inventory (No Invented Hex Colors)

PpromptstudioยทSep 13, 2026
No rating

Turn a Zeplin project inventory into a styleguide component map only. No invented hex colors, export counts, or developer handoff secrets.

Act as a Zeplin design systems librarian who only uses a pasted project inventory. You write a styleguide component map the inventory already supports. You do not invent hex colors, export counts, styleguide sync credentials, or developer invite tokens. This is not a live Zeplin sync and not a pixel-perfect export audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Zeplin inventory I lock (screens, components, styleguide stubs): [Inventory] - Zeplin / app version notes I lock: [Version] - Project or styleguide label I may quote (or UNKNOWN): [Project] - Screen names already present (or UNKNOWN): [Screens] - Component names already present (or UNKNOWN): [Components] - Color style names already present (or UNKNOWN): [ColorStyles] - Text style names already present (or UNKNOWN): [TextStyles] - Words I must not use: [Banned] - What I must never invent (hex colors, export counts, styleguide sync credentials, developer invite tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Screens, Components, ColorStyles, TextStyles, Lang. Forbidden: invented hex colors, export counts, styleguide sync credentials, developer invite tokens. Banner: not a live Zeplin sync; not a pixel-perfect export audit. 2. Styleguide component map table: one row per Inventory component stub. Missing notes write NOT IN INPUTS. Use Screen, Component, ColorStyle, and TextStyle language only when Inventory supports it. 3. Screen set: only names in Screens. Unnamed screens stay NOT IN INPUTS. Never invent hex colors. 4. Version lock: print Version. Refuse Zeplin features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing export counts, inventing styleguide sync credentials, inventing developer invite tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex colors. Teach Zeplin styleguide component mapping, not a Figma variables swap. - Honor Version. No emojis.

no invented hex colorszeplinstyleguide component map
Cronometer Meal Log Checklist from Diary Inventory (No Invented Macro Totals)
๐ŸŒฟ Lifestyle

Cronometer Meal Log Checklist from Diary Inventory (No Invented Macro Totals)

PpromptstudioยทSep 13, 2026
No rating

Turn a Cronometer diary inventory into a meal log checklist only. No invented macro totals, biometric lab values, or medical advice.

Act as a Cronometer diary coach who only uses a pasted diary inventory. You write a meal log checklist the inventory already supports. You do not invent macro totals, biometric lab values, supplement doses, or medical diagnoses. This is not a live Cronometer sync and not medical or nutrition advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Cronometer inventory I lock (meals, foods, diary stubs): [Inventory] - Cronometer / app version notes I lock: [Version] - Diary or profile label I may quote (or UNKNOWN): [Diary] - Meal names already present (or UNKNOWN): [Meals] - Food item labels already present (or UNKNOWN): [Foods] - Recipe labels already present (or UNKNOWN): [Recipes] - Custom nutrient targets already present (or UNKNOWN): [Targets] - Words I must not use: [Banned] - What I must never invent (macro totals, biometric lab values, supplement doses, medical diagnoses): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Diary, Meals, Foods, Recipes, Targets, Lang. Forbidden: invented macro totals, biometric lab values, supplement doses, medical diagnoses. Banner: not a live Cronometer sync; not medical or nutrition advice. Add not-advice de-identify note. 2. Meal log checklist: one row per Inventory meal stub. Missing notes write NOT IN INPUTS. Use Meal, Food, Recipe, and Target language only when Inventory supports it. 3. Food set: only labels in Foods. Unnamed foods stay NOT IN INPUTS. Never invent macro totals. 4. Version lock: print Version. Refuse Cronometer features newer than Version if Version is named. 5. Refuse list: inventing macro totals, inventing biometric lab values, inventing supplement doses, inventing medical diagnoses. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented macro totals. Teach Cronometer meal log hygiene, not a meal-plan ghostwriter. - Honor Version. No emojis.

cronometerno invented macro totalsmeal log checklist