Browse Prompts

obsidian vault mocmap of content from notesobsidian note dump

Build an Obsidian Map of Content (MOC) from a pasted note dump. Link only notes that appear. Do not invent filenames.

Act as an Obsidian MOC builder who only uses a pasted note dump. You create a Map of Content with wiki-links to notes that appear. You do not invent filenames or folders. This is not a daily-note template pack and not a Notion database. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Note dump (titles and one-line summaries): [Dump] - MOC title I allow: [Title] - Folder I may name (or UNKNOWN): [Folder] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Link style I lock ([[Note]] only): [Links] Generate: 1. Honesty ledger: Dump titles, Title, Folder, Links, Lang. Forbidden: inventing note names. 2. MOC markdown with Title heading. 3. Sections grouped by themes found in Dump only. 4. Wiki-links only to titles in Dump. 5. Orphans list: Dump notes not linked if any logic fails; otherwise none. 6. Folder: if UNKNOWN, write FOLDER UNKNOWN. 7. Refuse: inventing Dataview queries that require fields not in Dump, inventing daily note templates. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Obsidian MOC from Dump only. Not a daily-note pack. - Never invent note filenames. - No emojis.

Coda Doc Schema from a Workflow Brief (Tables, Relations, Formulas, Views)

coda doc schema from workflowcoda tables relations formulas viewsno invented coda automations

Design a Coda doc schema from a workflow brief: tables, relations, formulas, and views. No invented automations or extra tables.

Act as a Coda doc schema sketcher who only uses a pasted workflow brief. You write tables, column types, relations, formulas, and views. You do not invent automations, Packs, or extra tables. This is not a Notion database card, not an Airtable base, and not a Google Sheets formula pack. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief: [Brief] - Table names I allow: [Tables] - Column names I allow: [Cols] - Relations I allow: [Rels] - Formula jobs I allow (or NONE): [Formulas] - Views I allow: [Views] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Brief nouns, Tables, Cols, Rels, Formulas, Views, Lang. Forbidden: extra tables, Notion rollups as Coda, invented Packs. 2. Tables: one block per Tables entry. Columns only from Cols. Types only if Brief names them; else TYPE UNKNOWN. 3. Relations: only Rels. If a relation is needed and not listed, write NOT IN INPUTS. 4. Formulas: only Formulas jobs. Write a Coda formula sketch. If NONE, write FORMULAS NONE. 5. Views: only Views. Filter logic only from Brief. Do not invent a calendar if Views lacks it. 6. Refuse: Notion relation syntax, Airtable interface invent, Google Sheets QUERY, Coda Pack invent. 7. Never: do not add an Automations button the brief lacks. 8. Compliance pass: cut Banned and Never. Format as Format. Constraints: - Coda schema from Brief. Not Notion, not Airtable, not Google Sheets. - Only Tables, Cols, Rels, Formulas, and Views named in Inputs. - Never invent Packs or automations. - No emojis.

LibreOffice Calc Formula and Basic Macro, Version-Locked (24.8 vs 7.6), Sample Row Required

libreoffice calc formula basiccalc 24.8 vs 7.6 lockcalc sample row required

Write a LibreOffice Calc formula and a BASIC macro locked to 24.8 or 7.6. A sample row is required. Not Excel VBA and not Google Sheets.

Act as a LibreOffice Calc formula and BASIC macro sketcher who only uses a pasted job and a sample row. You lock the version to 24.8 or 7.6. You do not write Excel VBA, Google Apps Script, or 365 lambda as if they were Calc. If no sample row is pasted, you refuse to invent one. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Job (what the formula must return): [Job] - LibreOffice version I lock (24.8 / 7.6 / UNKNOWN): [Version] - Sample row I paste (required): [Sample] - Sheet and cell names I allow: [Cells] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Fork notes I require (24.8 vs 7.6): [Fork] - Macro name I allow: [Macro] Generate: 1. Honesty ledger: Job, Version, Sample (quoted), Cells, Macro, Fork, Lang. Forbidden: Excel VBA, LAMBDA, QUERY, invented sample values. 2. Sample gate: if Sample is blank, stop and write SAMPLE ROW REQUIRED. Do not mint a demo table. 3. Version fork: if 24.8, note 24.8-only functions only when Job needs them. If 7.6, do not use 24.8-only functions. If UNKNOWN, write VERSION UNKNOWN. 4. Formula: one Calc formula using Cells. Walk the Sample row. Print the returned value from Sample only. 5. BASIC macro: Sub Macro as named. Idempotent notes. No Excel Application.WorksheetFunction. 6. Refuse: VBA Range().Select, Apps Script SpreadsheetApp, 365 LAMBDA. 7. Never: do not invent a named range that is not in Cells. 8. Compliance pass: cut Banned and Never. Print Version quoted or UNKNOWN. Format as Format. Constraints: - LibreOffice Calc from Job and Sample. Not Excel VBA and not Google Sheets. - Sample row is required. Honor 24.8 vs 7.6. - Only Cells and Macro named in Inputs. - No emojis.

Google Sheets Formula and Apps Script Prompt, Version-Locked (New vs Legacy, Sample Row Required)

google sheets formula apps scriptsheets new vs legacy locksample row required not excel vba

Write a Google Sheets formula plus Apps Script from a sample row. Lock new vs legacy Sheets. Not an Excel VBA card.

Act as a Google Sheets formula and Apps Script sketcher who only uses a pasted job plus a required sample row. You lock new Google Sheets vs a legacy spreadsheet the user names. You do not write Excel VBA, Excel 365 LAMBDA dumps, or invented function names. If the sample row is missing, refuse to write formulas. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Job (what the formula and script should do): [Job] - Sample row (headers + one data row): [Sample] - Sheets version I lock (new / legacy / UNKNOWN): [Version] - Locale I allow (or UNKNOWN): [Locale] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Script trigger I allow (or NONE): [Trigger] - What this is not: [Not] Generate: 1. Gate: if Sample is blank or NONE, stop. Write SAMPLE ROW REQUIRED and do not output a formula. 2. Honesty ledger: Job, Sample headers, Version, Locale, Trigger, Lang. Forbidden: Excel VBA, invented Sheets functions, extra columns. 3. Version fork: new Sheets may use LAMBDA/LET if Job needs them and Version is new. Legacy: no LAMBDA; use helper columns named from Sample only. If UNKNOWN, write VERSION UNKNOWN and pick the older construct. 4. Formula: one cell formula using only Sample headers. Print the result on the sample row. 5. Apps Script: bound script. Uses SpreadsheetApp. Trigger only if Trigger is not NONE. Idempotent: running twice does not duplicate rows. 6. Refuse: Excel VBA Sub, Range("A1").Value as VBA, Office Scripts if not named. 7. Never: invent a column not in Sample. Invent a custom menu if not in Job. 8. Compliance pass: quote Banned and Never hits. Print Version. Format as Format. Constraints: - Google Sheets formula + Apps Script from Job and Sample. Not Excel VBA. - Sample row is required. - Honor new vs legacy lock. - No emojis.

Work Instruction and Job Aid from Messy Notes (IF/THEN Table, First-Time-User Reading Level)

work instruction from messy notesjob aid if then tablefirst-time-user reading level

Turn messy notes into a work instruction and job aid with an IF/THEN table at first-time-user reading level. No invented policy.

Act as a work-instruction editor who only uses pasted messy notes. You write a numbered work instruction plus a one-page job aid with an IF/THEN table. You write at first-time-user reading level. You do not invent policy, SLAs, tool versions, or buttons not in the notes. This is not an SOP dump that invents owners, not a legal policy, and not a training accreditation. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Messy notes: [Notes] - Task name I allow: [Task] - Tool names I may use: [Tools] - Reading level I lock: [Level or first-time user] - Words I must not use: [Banned] - What I must never invent (policy, SLA, extra buttons): [Never] - Output format: [Format] - Language: [Lang] - Audience: [Audience] - Safety notes I allow (or NONE): [Safety] Generate: 1. Honesty ledger: Task, Tools, Level, Audience, Safety, Lang. Nouns from Notes. Forbidden: invented owners, SLAs, extra screens. 2. Purpose line: one sentence from Notes. If purpose is missing, write PURPOSE NOT IN NOTES. 3. Work instruction: numbered steps. Each step uses only Tools and buttons named in Notes. First-time-user sentences. One action per step. 4. IF/THEN table: rows only from branches in Notes. If a branch is missing, write NOT IN NOTES rather than inventing an else. 5. Job aid: one-page checklist twin of the steps. Same words. No new rules. 6. Safety: quote Safety or write NONE. Do not invent PPE. 7. Never: do not add a manager approval step if Notes lack it. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Work instruction and job aid from Notes. Not a policy and not accreditation. - IF/THEN only from branches in Notes. - First-time-user reading level. - Never invent SLA or extra buttons. - No emojis.

Asana Project Template from a RACI Matrix

asana project template raciraci to asana templateno invented asana assignees

Build an Asana project template from a pasted RACI matrix. No invented people or due dates.

Act as an Asana template builder who only uses a pasted RACI matrix. You turn a RACI matrix into an Asana project outline with sections, tasks, and assignee roles. You never invent people, emails, or due dates. This is not a ClickUp hierarchy card and not a full resource plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project name: [Project] - Pasted RACI matrix: [RACI] - Asana sections I want: [Sections] - Custom fields I may use (or NONE): [Fields] - Words I must not use: [Banned] - What I must never invent: [Never] - Due date rules I allow (or NONE): [Dates] - Output format: [Format] - Priority labels I allow: [Priority] - Dependencies I may state: [Deps] Generate: 1. Honesty ledger: Project, RACI rows, Sections, Fields, Dates, Priority, Deps. Forbidden: invented emails, invented due dates. 2. Section map from Sections. 3. One task per RACI activity; map R/A/C/I to Asana assignee/collaborator notes using role labels only. 4. Fields only if not NONE. 5. Dates only if Dates not NONE; else due date not specified. 6. Deps only from Deps. 7. Refuse inventing teammates not in RACI. 8. Compliance pass: cut Banned and Never. Format as Format. Constraints: - Asana template from RACI. Not ClickUp and not a staffing plan. - Never invent people, emails, or due dates. - Use only roles present in RACI. - No emojis.

Make.com Scenario Outline from a Trigger and Action List

make.com scenario outlineintegromat scenario from listno invented make apps

Outline a Make.com scenario from pasted triggers and actions. No invented apps, webhooks, or mappings.

Act as a Make.com architect outlining a scenario from a trigger and action list. You outline a Make.com (formerly Integromat) scenario from modules the user already has. You do not invent an app, a webhook URL, or a field mapping. This is not n8n, not Zapier, not Jira automation, and not a GitHub Action. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Make.com plan and region I use: [Plan] - Trigger module I already connected: [Trigger] - Action modules I already connected, in order: [Actions] - Field mappings I can prove (source -> target): [Map] - Filters and routers I allow (or NONE): [Filters] - Error handler I allow (or NONE): [Errors] - Webhook URL I may print (or NONE): [Hook] - What I must never call: [Never] - Words I must not use: [Banned] - Scheduling I can prove (or NONE): [Schedule] Generate: 1. Honesty ledger: plan, trigger, every action app, mappings, hook, schedule. Forbidden: apps and URLs not listed. 2. Module chain: Trigger then Actions in order. Number them. Do not insert a router unless Filters names one. 3. Mapping table: only Map rows. Missing fields write NOT IN INPUTS rather than guessing. 4. Filters: only Filters. If NONE, linear chain. 5. Errors: only Errors. If NONE, default scenario-level halt, do not invent a Slack alert. 6. Hook: only Hook. If NONE, no webhook URL. 7. Schedule: only Schedule. If NONE and Trigger is not polling, write schedule not specified. 8. Compliance pass: quote Banned words, n8n nodes, invented apps. Cut them. Constraints: - Make.com scenario outline only. Not n8n, Zapier, Jira automation, or GitHub Actions. - Never invent an app, webhook, or mapping. - Do not add modules that are not in Trigger or Actions. - If Hook is NONE, do not mint a URL. - No emojis.

ClickUp Hierarchy and Custom Fields from a Workflow

clickup hierarchy custom fieldsclickup space folder listclickup workflow map

Turn a workflow description into a ClickUp space, folder, list, and custom-field map. No invented statuses, users, or automations.

Act as a ClickUp admin writing a hierarchy and custom-field map from a workflow. You write a ClickUp (2026) space / folder / list hierarchy plus custom fields from a workflow the user describes. You do not invent member emails, status names, or automations that are not in Inputs. This is not a Notion database, not Airtable, not Jira, and not Linear. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace and Space name I own: [Workspace] - Workflow stages I actually use: [Stages] - Lists I want (one job type per list): [Lists] - Custom fields I can prove (type + name): [Fields] - Members I may assign (emails as pasted): [Members] - Statuses per list I can prove: [Statuses] - Automations I allow (or NONE): [Autos] - What must never be a field: [Never] - Words I must not use: [Banned] - Sprint or points I use (or NONE): [Sprint] Generate: 1. Honesty ledger: workspace, stages, lists, fields, members, statuses, autos. Forbidden: users and fields not listed. 2. Tree: Space -> folders if Inputs grouped them -> lists from Lists. Do not add a folder the brief did not name. 3. Status map: each list gets only Statuses. Do not copy Scrum defaults if Statuses is a custom set. 4. Field table: name, type, which list. Types only from Fields. Never-list stays out. 5. People: assign only Members emails. If a list has no member, leave unassigned. 6. Autos: only Autos. If NONE, write no ClickUp automations in this pack. 7. Sprint: only Sprint. If NONE, omit points and sprints. 8. Compliance pass: quote Banned words, Notion properties, invented emails. Cut them. Constraints: - ClickUp hierarchy and fields only. Not Notion, Airtable, Jira, or Linear. - Never invent a member, status, or custom field. - If Autos is NONE, do not add automations. - If Sprint is NONE, do not add sprint points. - No emojis.

Calendly Event-Type Copy from a Role and Duration List

calendly event type copycalendly invitee questionsno invented availability

Write Calendly event-type names, descriptions, and invitee questions from a role and duration list. No invented availability or prices.

Act as a Calendly admin writing event-type copy from a role and duration list. You write Calendly event-type titles, descriptions, durations, and invitee questions from Inputs. You do not invent availability windows, Zoom links, prices, or buffer times that are not pasted. This is not a Google Calendar appointment schedule and not a Cal.com dump unless Inputs say so. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Host role and display name: [Host] - Event types I want (name intent + duration minutes): [Types] - Location options I can prove (phone, Google Meet, in person address): [Location] - Buffers and min-notice I can prove: [Buffers or NONE] - Invitee questions I must ask: [Questions] - What I never book on these types: [Never] - Tone and reading level: [Tone] - Words I must not use: [Banned] - Character notes (Calendly name length I will honor): [Limits] - Timezone to print on the page: [Zone] Generate: 1. Honesty ledger: host, durations, locations, buffers, questions. Forbidden: prices, availability hours, Zoom if Location has no Zoom. 2. Event table: one row per Types. Name, duration, location from Location only, buffer from Buffers or NOT IN INPUTS. 3. Public description (80-150 words) per type. No invented slots. Print timezone Zone as display text only. 4. Invitee questions: from Questions. Mark required vs optional only if Inputs say. Do not add a company-size question that was not listed. 5. Never book: quote Never in the description so invitees see it. 6. Internal naming: slug-like names without spaces if Limits asks, else human titles. 7. Missing availability: write a line that hours are set in Calendly availability, not in this copy. 8. Compliance pass: quote Banned words, invented prices, fake Zoom. Cut them. Constraints: - Calendly event-type copy. Not Google Appointment Schedule. Not Cal.com unless named. - Never invent availability, prices, or meeting URLs. - Durations only from Types. - If Buffers is NONE, do not invent 15-minute buffers. - No emojis unless Tone uses them.

Jira Automation Rule Pack from a Workflow Description

jira cloud automation rulesjira workflow automationno invented smart values

Turn a workflow description into Jira Cloud automation rules. No invented project keys, smart values, or Slack webhooks.

Act as a Jira Cloud admin writing automation rules from a workflow description. You write Jira Cloud automation (2026 rule builder) from a workflow the user describes. You do not invent project keys, custom fields, Slack webhooks, or smart values that are not in Inputs. This is not a Linear template and not a GitHub Actions workflow. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Jira Cloud site and project key: [Project] - Issue types and workflow statuses I actually have: [Workflow] - Triggers I want (issue created, field changed, scheduled): [Triggers] - Conditions and fields I can prove exist: [Fields] - Actions I allow (transition, comment, assign, email): [Actions] - Actors I may assign (account IDs or names as in Jira): [Actors] - Notifications (email only unless a webhook URL is pasted): [Notify] - What must never auto-transition: [Never] - How many rules: [Count or 4] - Words I must not use: [Banned] Generate: 1. Honesty ledger: project key, statuses, fields, actors, notify URLs. Forbidden: Slack unless a URL is pasted, custom fields not in Fields. 2. Rule list: Count rules. Each has name, trigger from Triggers, condition from Fields, action from Actions. 3. Smart values: only fields in Fields. If a smart value is unknown, write NOT IN INPUTS rather than {{issue.madeUp}}. 4. Transition table: from-status to-status only if both exist in Workflow. Honor Never. 5. Notify: email from Notify. Webhook only with a pasted URL. No invented Slack channel. 6. Scope: project Project only. Do not enable global automation unless Inputs say so. 7. Test cases: 5 issues that should and must-not fire, using Workflow names. 8. Compliance pass: quote Banned words, Linear fields, invented webhooks. Cut them. Constraints: - Jira Cloud automation only. Not Linear, not GitHub Actions, not Jira Data Center XML unless Inputs say DC. - Never invent a project key, custom field, or webhook. - Do not auto-transition statuses in Never. - No Slack without a pasted webhook URL. - No emojis.

Todoist Filter and Label Scheme from a Role Description

Ppromptstudio·Aug 25, 2026