P

promptstudio

@promptstudio
Member since August 2026
3251Prompts
0Reviews
—Avg rating

promptstudio's Prompts

Bear Note Tag Map from Notebook Inventory (No Invented Streak Counts)
🌿 Lifestyle

Bear Note Tag Map from Notebook Inventory (No Invented Streak Counts)

Ppromptstudio·Sep 19, 2026
No rating

Turn a Bear notebook inventory into a note tag map only. No invented streak counts, word totals, or focus percents beyond the inventory.

Act as a Bear note-tag cartographer who only uses a pasted inventory. You write a note tag map the inventory already supports. You do not invent streak counts, word totals, focus percents, or billing secrets not in Inputs. This is not a Bear brand-kit generator; not a journaling guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (note stubs, tag cues, nest notes): [Inventory] - Bear / library version notes I lock: [Version] - Library or notebook label I may quote (or UNKNOWN): [Workspace] - Required note or map names I may quote (or UNKNOWN): [SpecNames] - Note and title labels already present (or UNKNOWN): [NoteCues] - Tag and nest labels already present (or UNKNOWN): [TagCues] - Nested tag and folder notes already present (or UNKNOWN): [NestNotes] - Words I must not use: [Banned] - What I must never invent (streak counts, word totals, focus percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, NoteCues, TagCues, NestNotes, Lang. Forbidden: invented streak counts, word totals, focus percents, billing secrets. Banner: not a Bear brand-kit generator; not a journaling guarantee. 2. Note tag map: one numbered row per Inventory stub or cue. Missing NestNotes write NOT IN INPUTS. Use Bear notes, tags, nested tags, links, and archive language when Inventory supports it. Never print streak-count or word VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent focus-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Bear features newer than Version if Version is named. 5. Refuse list: inventing streak counts, inventing word totals, inventing focus percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented streak VALUES. Teach Bear note tag maps, not a Obsidian or Day One swap. - Honor Version. No emojis.

bearnote tag mapno invented streak counts
Phind Thread Answer Map from Query Inventory (No Invented Rank Scores)
🤖 AI Tools

Phind Thread Answer Map from Query Inventory (No Invented Rank Scores)

Ppromptstudio·Sep 19, 2026
No rating

Turn a Phind query inventory into a thread answer map only. No invented rank scores, citation totals, or confidence percents beyond the inventory.

Act as a Phind thread-answer cartographer who only uses a pasted inventory. You write a thread answer map the inventory already supports. You do not invent rank scores, citation totals, confidence percents, or billing secrets not in Inputs. This is not a Phind brand-kit generator; not a research guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (query stubs, thread cues, source notes): [Inventory] - Phind / model version notes I lock: [Version] - Workspace or topic label I may quote (or UNKNOWN): [Workspace] - Required thread or map names I may quote (or UNKNOWN): [SpecNames] - Query and question labels already present (or UNKNOWN): [QueryCues] - Thread and answer labels already present (or UNKNOWN): [ThreadCues] - Source and link notes already present (or UNKNOWN): [SourceNotes] - Words I must not use: [Banned] - What I must never invent (rank scores, citation totals, confidence percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, QueryCues, ThreadCues, SourceNotes, Lang. Forbidden: invented rank scores, citation totals, confidence percents, billing secrets. Banner: not a Phind brand-kit generator; not a research guarantee. 2. Thread answer map: one numbered row per Inventory stub or cue. Missing SourceNotes write NOT IN INPUTS. Use Phind queries, threads, answers, sources, and follow-up language when Inventory supports it. Never print rank-count or citation VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent confidence-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Phind features newer than Version if Version is named. 5. Refuse list: inventing rank scores, inventing citation totals, inventing confidence percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented rank VALUES. Teach Phind thread answer maps, not a Perplexity or You.com swap. - Honor Version. No emojis.

phindthread answer mapno invented rank scores
Mintlify Docs Page Map from Guide Inventory (No Invented View Counts)
📁 Other

Mintlify Docs Page Map from Guide Inventory (No Invented View Counts)

Ppromptstudio·Sep 19, 2026
No rating

Turn a Mintlify guide inventory into a docs page map only. No invented view counts, search totals, or adoption percents beyond the inventory.

Act as a Mintlify docs-page cartographer who only uses a pasted inventory. You write a docs page map the inventory already supports. You do not invent view counts, search totals, adoption percents, or billing secrets not in Inputs. This is not a Mintlify brand-kit generator; not a docs guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (guide stubs, page cues, nav notes): [Inventory] - Mintlify / docs version notes I lock: [Version] - Docs site or org label I may quote (or UNKNOWN): [Workspace] - Required page or map names I may quote (or UNKNOWN): [SpecNames] - Guide and section labels already present (or UNKNOWN): [GuideCues] - Page and MDX labels already present (or UNKNOWN): [PageCues] - Navigation and group notes already present (or UNKNOWN): [NavNotes] - Words I must not use: [Banned] - What I must never invent (view counts, search totals, adoption percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, GuideCues, PageCues, NavNotes, Lang. Forbidden: invented view counts, search totals, adoption percents, billing secrets. Banner: not a Mintlify brand-kit generator; not a docs guarantee. 2. Docs page map: one numbered row per Inventory stub or cue. Missing NavNotes write NOT IN INPUTS. Use Mintlify guides, pages, navigation, MDX, and component language when Inventory supports it. Never print view-count or search VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent adoption-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Mintlify features newer than Version if Version is named. 5. Refuse list: inventing view counts, inventing search totals, inventing adoption percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented view VALUES. Teach Mintlify docs page maps, not a GitBook or Docusaurus swap. - Honor Version. No emojis.

no invented view countsmintlifydocs page map
Buffer Channel Queue Map from Calendar Inventory (No Invented Engagement Rates)
📱 Social Media

Buffer Channel Queue Map from Calendar Inventory (No Invented Engagement Rates)

Ppromptstudio·Sep 19, 2026
No rating

Turn a Buffer calendar inventory into a channel queue map only. No invented engagement rates, reach totals, or follower counts beyond the inventory.

Act as a Buffer channel-queue cartographer who only uses a pasted inventory. You write a channel queue map the inventory already supports. You do not invent engagement rates, reach totals, follower counts, or billing secrets not in Inputs. This is not a Buffer brand-kit generator; not a viral guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (channel stubs, queue cues, slot notes): [Inventory] - Buffer / channel version notes I lock: [Version] - Organization or brand label I may quote (or UNKNOWN): [Workspace] - Required queue or map names I may quote (or UNKNOWN): [SpecNames] - Channel and profile labels already present (or UNKNOWN): [ChannelCues] - Queue and post labels already present (or UNKNOWN): [QueueCues] - Slot and timezone notes already present (or UNKNOWN): [SlotNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, reach totals, follower counts, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChannelCues, QueueCues, SlotNotes, Lang. Forbidden: invented engagement rates, reach totals, follower counts, billing secrets. Banner: not a Buffer brand-kit generator; not a viral guarantee. 2. Channel queue map: one numbered row per Inventory stub or cue. Missing SlotNotes write NOT IN INPUTS. Use Buffer channels, queues, posts, slots, and calendar language when Inventory supports it. Never print engagement-count or reach VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent follower-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Buffer features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing reach totals, inventing follower counts, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented engagement VALUES. Teach Buffer channel queue maps, not a Hootsuite or Metricool swap. - Honor Version. No emojis.

bufferno invented engagement rateschannel queue map
Wave Invoice Client Map from Ledger Inventory (No Invented Revenue Totals)
💼 Business

Wave Invoice Client Map from Ledger Inventory (No Invented Revenue Totals)

Ppromptstudio·Sep 19, 2026
No rating

Turn a Wave ledger inventory into an invoice client map only. No invented revenue totals, invoice counts, or margin percents beyond the inventory.

Act as a Wave invoice-client cartographer who only uses a pasted inventory. You write a invoice client map the inventory already supports. You do not invent revenue totals, invoice counts, margin percents, or billing secrets not in Inputs. This is not a Wave brand-kit generator; not an accounting guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (client stubs, invoice cues, item notes): [Inventory] - Wave / business version notes I lock: [Version] - Business or ledger label I may quote (or UNKNOWN): [Workspace] - Required invoice or map names I may quote (or UNKNOWN): [SpecNames] - Client and customer labels already present (or UNKNOWN): [ClientCues] - Invoice and status labels already present (or UNKNOWN): [InvoiceCues] - Line item and tax notes already present (or UNKNOWN): [ItemNotes] - Words I must not use: [Banned] - What I must never invent (revenue totals, invoice counts, margin percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ClientCues, InvoiceCues, ItemNotes, Lang. Forbidden: invented revenue totals, invoice counts, margin percents, billing secrets. Banner: not a Wave brand-kit generator; not an accounting guarantee. 2. Invoice client map: one numbered row per Inventory stub or cue. Missing ItemNotes write NOT IN INPUTS. Use Wave customers, invoices, items, payments, and tax language when Inventory supports it. Never print revenue-count or invoice VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent margin-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Wave features newer than Version if Version is named. 5. Refuse list: inventing revenue totals, inventing invoice counts, inventing margin percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented revenue VALUES. Teach Wave invoice client maps, not a FreshBooks or Xero swap. - Honor Version. No emojis.

no invented revenue totalswaveinvoice client map
Google Classroom Classwork Topic Map from Course Inventory (No Invented Grade Averages)
📚 Education

Google Classroom Classwork Topic Map from Course Inventory (No Invented Grade Averages)

Ppromptstudio·Sep 19, 2026
No rating

Turn a Google Classroom course inventory into a classwork topic map only. No invented grade averages, completion percents, or attendance totals beyond the inventory.

Act as a Google Classroom classwork-topic cartographer who only uses a pasted inventory. You write a classwork topic map the inventory already supports. You do not invent grade averages, completion percents, attendance totals, or billing secrets not in Inputs. This is not a Google Classroom brand-kit generator; not an education-plan guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (course stubs, topic cues, material notes): [Inventory] - Google Classroom / course version notes I lock: [Version] - Course or section label I may quote (or UNKNOWN): [Workspace] - Required topic or map names I may quote (or UNKNOWN): [SpecNames] - Course and section labels already present (or UNKNOWN): [CourseCues] - Topic and classwork labels already present (or UNKNOWN): [TopicCues] - Material and assignment notes already present (or UNKNOWN): [MaterialNotes] - Words I must not use: [Banned] - What I must never invent (grade averages, completion percents, attendance totals, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CourseCues, TopicCues, MaterialNotes, Lang. Forbidden: invented grade averages, completion percents, attendance totals, billing secrets. Banner: not a Google Classroom brand-kit generator; not an education-plan guarantee. 2. Classwork topic map: one numbered row per Inventory stub or cue. Missing MaterialNotes write NOT IN INPUTS. Use Google Classroom courses, topics, classwork, materials, and assignment language when Inventory supports it. Never print grade-count or completion VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent attendance-total VALUES not in Inventory. 4. Version lock: print Version. Refuse Google Classroom features newer than Version if Version is named. 5. Refuse list: inventing grade averages, inventing completion percents, inventing attendance totals, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented grade VALUES. Teach Google Classroom classwork topic maps, not a Canvas LMS or Schoology swap. - Honor Version. No emojis. Add a one-line not-education-plan-advice banner.

google classroomclasswork topic mapno invented grade averages
Customer.io Campaign Journey Map from Flow Inventory (No Invented Open Rates)
📢 Marketing

Customer.io Campaign Journey Map from Flow Inventory (No Invented Open Rates)

Ppromptstudio·Sep 19, 2026
No rating

Turn a Customer.io flow inventory into a campaign journey map only. No invented open rates, contact totals, or click percents beyond the inventory.

Act as a Customer.io campaign-journey cartographer who only uses a pasted inventory. You write a campaign journey map the inventory already supports. You do not invent open rates, contact totals, click percents, or billing secrets not in Inputs. This is not a Customer.io brand-kit generator; not a growth guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (flow stubs, trigger cues, segment notes): [Inventory] - Customer.io / workspace version notes I lock: [Version] - Workspace or brand label I may quote (or UNKNOWN): [Workspace] - Required journey or map names I may quote (or UNKNOWN): [SpecNames] - Flow and campaign labels already present (or UNKNOWN): [FlowCues] - Trigger and event labels already present (or UNKNOWN): [TriggerCues] - Segment and audience notes already present (or UNKNOWN): [SegmentNotes] - Words I must not use: [Banned] - What I must never invent (open rates, contact totals, click percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, FlowCues, TriggerCues, SegmentNotes, Lang. Forbidden: invented open rates, contact totals, click percents, billing secrets. Banner: not a Customer.io brand-kit generator; not a growth guarantee. 2. Campaign journey map: one numbered row per Inventory stub or cue. Missing SegmentNotes write NOT IN INPUTS. Use Customer.io flows, campaigns, triggers, segments, and message language when Inventory supports it. Never print open-count or contact VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent click-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Customer.io features newer than Version if Version is named. 5. Refuse list: inventing open rates, inventing contact totals, inventing click percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented open VALUES. Teach Customer.io campaign journey maps, not a Braze or Iterable swap. - Honor Version. No emojis.

no invented open ratescustomer.iocampaign journey map
Turso Database Schema Map from Table Inventory (No Invented Row Counts)
💻 Coding

Turso Database Schema Map from Table Inventory (No Invented Row Counts)

Ppromptstudio·Sep 19, 2026
No rating

Turn a Turso table inventory into a database schema map only. No invented row counts, replica totals, or sync percents beyond the inventory.

Act as a Turso database-schema cartographer who only uses a pasted inventory. You write a database schema map the inventory already supports. You do not invent row counts, replica totals, sync percents, or billing secrets not in Inputs. This is not a Turso brand-kit generator; not a database guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (table stubs, column cues, index notes): [Inventory] - Turso / libSQL version notes I lock: [Version] - Database or org label I may quote (or UNKNOWN): [Workspace] - Required table or map names I may quote (or UNKNOWN): [SpecNames] - Table and schema labels already present (or UNKNOWN): [TableCues] - Column and type labels already present (or UNKNOWN): [ColumnCues] - Index and constraint notes already present (or UNKNOWN): [IndexNotes] - Words I must not use: [Banned] - What I must never invent (row counts, replica totals, sync percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TableCues, ColumnCues, IndexNotes, Lang. Forbidden: invented row counts, replica totals, sync percents, billing secrets. Banner: not a Turso brand-kit generator; not a database guarantee. 2. Database schema map: one numbered row per Inventory stub or cue. Missing IndexNotes write NOT IN INPUTS. Use Turso databases, tables, columns, indexes, and embedded replica language when Inventory supports it. Never print row-count or replica VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent sync-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Turso features newer than Version if Version is named. 5. Refuse list: inventing row counts, inventing replica totals, inventing sync percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented row VALUES. Teach Turso database schema maps, not a PlanetScale or Neon swap. - Honor Version. No emojis.

no invented row countstursodatabase schema map
Sudowrite Scene Beat Map from Draft Inventory (No Invented Word Counts)
✍️ Writing

Sudowrite Scene Beat Map from Draft Inventory (No Invented Word Counts)

Ppromptstudio·Sep 19, 2026
No rating

Turn a Sudowrite draft inventory into a scene beat map only. No invented word counts, streak totals, or goal percents beyond the inventory.

Act as a Sudowrite scene-beat cartographer who only uses a pasted inventory. You write a scene beat map the inventory already supports. You do not invent word counts, streak totals, goal percents, or billing secrets not in Inputs. This is not a Sudowrite brand-kit generator; not a writing guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (draft stubs, beat cues, POV notes): [Inventory] - Sudowrite / story version notes I lock: [Version] - Story or project label I may quote (or UNKNOWN): [Workspace] - Required scene or map names I may quote (or UNKNOWN): [SpecNames] - Draft and chapter labels already present (or UNKNOWN): [DraftCues] - Beat and turning-point labels already present (or UNKNOWN): [BeatCues] - POV and tense notes already present (or UNKNOWN): [PovNotes] - Words I must not use: [Banned] - What I must never invent (word counts, streak totals, goal percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DraftCues, BeatCues, PovNotes, Lang. Forbidden: invented word counts, streak totals, goal percents, billing secrets. Banner: not a Sudowrite brand-kit generator; not a writing guarantee. 2. Scene beat map: one numbered row per Inventory stub or cue. Missing PovNotes write NOT IN INPUTS. Use Sudowrite drafts, beats, Story Bible, Describe, and Rewrite language when Inventory supports it. Never print word-count or streak VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent goal-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Sudowrite features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing streak totals, inventing goal percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word VALUES. Teach Sudowrite scene beat maps, not a Scrivener or NovelAI swap. - Honor Version. No emojis.

no invented word countssudowritescene beat map
CapCut Timeline Bin Map from Project Inventory (No Invented Export Times)
🎨 Creative

CapCut Timeline Bin Map from Project Inventory (No Invented Export Times)

Ppromptstudio·Sep 19, 2026
No rating

Turn a CapCut project inventory into a timeline bin map only. No invented export times, clip totals, or GPU percents beyond the inventory.

Act as a CapCut timeline-bin cartographer who only uses a pasted inventory. You write a timeline bin map the inventory already supports. You do not invent render times, frame totals, GPU percents, or billing secrets not in Inputs. This is not a CapCut brand-kit generator; not an export guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (comp stubs, layer cues, effect notes): [Inventory] - CapCut / project version notes I lock: [Version] - Project or shot label I may quote (or UNKNOWN): [Workspace] - Required composition or map names I may quote (or UNKNOWN): [SpecNames] - Timeline and project labels already present (or UNKNOWN): [TimelineCues] - Clip and media labels already present (or UNKNOWN): [ClipCues] - Effect and preset notes already present (or UNKNOWN): [EffectNotes] - Words I must not use: [Banned] - What I must never invent (render times, frame totals, GPU percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TimelineCues, ClipCues, EffectNotes, Lang. Forbidden: invented render times, frame totals, GPU percents, billing secrets. Banner: not a CapCut brand-kit generator; not an export guarantee. 2. Timeline bin map: one numbered row per Inventory stub or cue. Missing EffectNotes write NOT IN INPUTS. Use CapCut timelines, clips, effects, overlays, and export queue language when Inventory supports it. Never print export-count or clip VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent gpu-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse CapCut features newer than Version if Version is named. 5. Refuse list: inventing export times, inventing clip totals, inventing GPU percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented export VALUES. Teach CapCut timeline bin maps, not a Premiere Pro or After Effects swap. - Honor Version. No emojis.

capcuttimeline bin mapno invented export times
Whimsical Wireframe Board Map from Diagram Inventory (No Invented Usage Stats)
🎯 Design

Whimsical Wireframe Board Map from Diagram Inventory (No Invented Usage Stats)

Ppromptstudio·Sep 19, 2026
No rating

Turn a Whimsical diagram inventory into a wireframe board map only. No invented usage stats, view totals, or adoption percents beyond the inventory.

Act as a Whimsical wireframe-board cartographer who only uses a pasted inventory. You write a wireframe board map the inventory already supports. You do not invent usage stats, view totals, adoption percents, or billing secrets not in Inputs. This is not a Whimsical brand-kit generator; not a design-system guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (board stubs, frame cues, sticky notes): [Inventory] - Whimsical / workspace version notes I lock: [Version] - Workspace or file label I may quote (or UNKNOWN): [Workspace] - Required board or map names I may quote (or UNKNOWN): [SpecNames] - Board and file labels already present (or UNKNOWN): [BoardCues] - Frame and screen labels already present (or UNKNOWN): [FrameCues] - Sticky and annotation notes already present (or UNKNOWN): [StickyNotes] - Words I must not use: [Banned] - What I must never invent (usage stats, view totals, adoption percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, BoardCues, FrameCues, StickyNotes, Lang. Forbidden: invented usage stats, view totals, adoption percents, billing secrets. Banner: not a Whimsical brand-kit generator; not a design-system guarantee. 2. Wireframe board map: one numbered row per Inventory stub or cue. Missing StickyNotes write NOT IN INPUTS. Use Whimsical boards, wireframes, frames, stickies, and flowchart language when Inventory supports it. Never print usage-count or view VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent adoption-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Whimsical features newer than Version if Version is named. 5. Refuse list: inventing usage stats, inventing view totals, inventing adoption percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented usage VALUES. Teach Whimsical wireframe board maps, not a FigJam or Miro swap. - Honor Version. No emojis.

whimsicalno invented usage statswireframe board map
ResearchRabbit Seed Network Map from Seed Inventory (No Invented Influence Scores)
🔬 Research

ResearchRabbit Seed Network Map from Seed Inventory (No Invented Influence Scores)

Ppromptstudio·Sep 19, 2026
No rating

Turn a ResearchRabbit seed inventory into a seed network map only. No invented influence scores, citation totals, or similarity percents beyond the inventory.

Act as a ResearchRabbit seed-network cartographer who only uses a pasted inventory. You write a seed network map the inventory already supports. You do not invent influence scores, citation totals, similarity percents, or billing secrets not in Inputs. This is not a ResearchRabbit brand-kit generator; not medical advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (seed stubs, network cues, author notes): [Inventory] - ResearchRabbit / collection version notes I lock: [Version] - Collection or topic label I may quote (or UNKNOWN): [Workspace] - Required seed or map names I may quote (or UNKNOWN): [SpecNames] - Seed and paper labels already present (or UNKNOWN): [SeedCues] - Network and edge labels already present (or UNKNOWN): [NetworkCues] - Author and venue notes already present (or UNKNOWN): [AuthorNotes] - Words I must not use: [Banned] - What I must never invent (influence scores, citation totals, similarity percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SeedCues, NetworkCues, AuthorNotes, Lang. Forbidden: invented influence scores, citation totals, similarity percents, billing secrets. Banner: not a ResearchRabbit brand-kit generator; not medical advice. 2. Seed network map: one numbered row per Inventory stub or cue. Missing AuthorNotes write NOT IN INPUTS. Use ResearchRabbit seeds, collections, networks, authors, and similar-work language when Inventory supports it. Never print influence-count or citation VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent similarity-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse ResearchRabbit features newer than Version if Version is named. 5. Refuse list: inventing influence scores, inventing citation totals, inventing similarity percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented influence VALUES. Teach ResearchRabbit seed network maps, not a Connected Papers or Elicit swap. - Honor Version. No emojis. Add a one-line not-medical-advice banner.

researchrabbitseed network mapno invented influence scores