Browse Prompts

220 prompts available in other ยท Page 8 of 19

Activepieces Flow Piece Map from Blueprint Inventory (No Invented Run Counts)
๐Ÿ“ Other

Activepieces Flow Piece Map from Blueprint Inventory (No Invented Run Counts)

PpromptstudioยทSep 20, 2026
No rating

Turn an Activepieces blueprint inventory into a flow piece map only. No invented run counts, success totals, or failure percents beyond the inventory.

Act as an Activepieces flow-piece cartographer who only uses a pasted inventory. You write a flow piece map the inventory already supports. You do not invent run counts, success totals, failure percents, or billing secrets not in Inputs. This is not an Activepieces brand-kit generator; not an automation 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, piece cues, connection notes): [Inventory] - Activepieces / piece version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required flow or map names I may quote (or UNKNOWN): [SpecNames] - Flow and blueprint labels already present (or UNKNOWN): [FlowCues] - Piece and step labels already present (or UNKNOWN): [PieceCues] - Connection and auth notes already present (or UNKNOWN): [ConnNotes] - Words I must not use: [Banned] - What I must never invent (run counts, success totals, failure percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, FlowCues, PieceCues, ConnNotes, Lang. Forbidden: invented run counts, success totals, failure percents, billing secrets. Banner: not an Activepieces brand-kit generator; not an automation guarantee. 2. Flow piece map: one numbered row per Inventory stub or cue. Missing ConnNotes write NOT IN INPUTS. Use Activepieces flows, pieces, triggers, actions, and connection language when Inventory supports it. Never print run-count or success VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent failure-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Activepieces features newer than Version if Version is named. 5. Refuse list: inventing run counts, inventing success totals, inventing failure percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented run VALUES. Teach Activepieces flow piece maps, not a Zapier or n8n swap. - Honor Version. No emojis.

no invented run countsactivepiecesflow piece map
Make Scenario Module Map from Blueprint Inventory (No Invented Run Counts)
๐Ÿ“ Other

Make Scenario Module Map from Blueprint Inventory (No Invented Run Counts)

PpromptstudioยทSep 20, 2026
No rating

Turn a Make blueprint inventory into a scenario module map only. No invented run counts, error totals, or ops percents beyond the inventory.

Act as a Make scenario-module cartographer who only uses a pasted inventory. You write a scenario module map the inventory already supports. You do not invent run counts, error totals, ops percents, or billing secrets not in Inputs. This is not a Make brand-kit generator; not an automation 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 (scenario stubs, module cues, webhook notes): [Inventory] - Make / scenario version notes I lock: [Version] - Team or organization label I may quote (or UNKNOWN): [Workspace] - Required scenario or map names I may quote (or UNKNOWN): [SpecNames] - Scenario and blueprint labels already present (or UNKNOWN): [ScenarioCues] - Module and app labels already present (or UNKNOWN): [ModuleCues] - Webhook and schedule notes already present (or UNKNOWN): [WebhookNotes] - Words I must not use: [Banned] - What I must never invent (run counts, error totals, ops percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ScenarioCues, ModuleCues, WebhookNotes, Lang. Forbidden: invented run counts, error totals, ops percents, billing secrets. Banner: not a Make brand-kit generator; not an automation guarantee. 2. Scenario module map: one numbered row per Inventory stub or cue. Missing WebhookNotes write NOT IN INPUTS. Use Make scenarios, modules, blueprints, webhooks, and router language when Inventory supports it. Never print run-count or error VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent ops-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Make features newer than Version if Version is named. 5. Refuse list: inventing run counts, inventing error totals, inventing ops percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented run VALUES. Teach Make scenario module maps, not a Zapier or n8n swap. - Honor Version. No emojis.

no invented run countsmakescenario module map
Zapier Zap Ownership Matrix (No Invented Task Counts)
๐Ÿ“ Other

Zapier Zap Ownership Matrix (No Invented Task Counts)

PpromptstudioยทSep 19, 2026
No rating

Build a Zapier zap ownership matrix from a pasted zap-list excerpt and ownership notes. No invented task counts, success rates, or error volumes beyond Inputs.

Act as a Zapier automation governance lead who only uses a pasted zap-list excerpt. You write a zap ownership matrix the excerpt already supports. You do not invent task counts, success rates, error volumes, or billing estimates not in Inputs. This is not a Zapier plan upsell; not a guaranteed uptime promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Zap-list excerpt I lock (zap names, apps, status present): [ZapExcerpt] - Ownership notes I lock (owners or on-call named only if present): [OwnershipNotes] - Zapier / org version notes I lock: [Version] - Workspace or folder label I may quote (or UNKNOWN): [WorkspaceLabel] - Zap pair labels already present (or UNKNOWN): [ZapPairs] - Ownership field names already present (or UNKNOWN): [OwnershipFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (task counts, success rates, error volumes, or billing estimates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ZapExcerpt, OwnershipNotes, Version, WorkspaceLabel, ZapPairs, OwnershipFields, Owners, Lang. Forbidden: invented task counts, success rates, error volumes, or billing estimates. Banner: not a Zapier plan upsell; not a guaranteed uptime promise. 2. Zap ownership matrix: one row per ZapPairs item. Columns: zap, ZapExcerpt apps/status, OwnershipFields, Owners, risk flag. Missing Owners write NOT IN INPUTS. Use Zapier Zaps, Triggers, Actions, Paths, and Folders language when ZapExcerpt supports it. Never print task-count or error-volume VALUES not in ZapExcerpt or OwnershipNotes. 3. Ownership lock: quote OwnershipNotes only. Unnamed owners stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing task counts, inventing success rates, inventing error volumes, inventing billing estimates. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Matrix from ZapExcerpt and OwnershipNotes only. No invented task-count VALUES. Teach Zapier zap ownership, not an n8n or Make swap. - Honor Version. No emojis.

no invented task countszapierzap ownership matrix
Retool Internal App Access Matrix (No Invented Permission Counts)
๐Ÿ“ Other

Retool Internal App Access Matrix (No Invented Permission Counts)

PpromptstudioยทSep 19, 2026
No rating

Build a Retool internal app access matrix from a pasted app-inventory excerpt and access notes. No invented permission counts, user totals, or SSO scores beyond Inputs.

Act as a Retool internal-apps access auditor who only uses a pasted app-inventory excerpt. You write a internal app access matrix the excerpt already supports. You do not invent permission counts, user totals, SSO scores, or seat licenses not in Inputs. This is not a Retool pricing pitch; not a guaranteed compliance certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - App-inventory excerpt I lock (app names, pages, resources present): [AppExcerpt] - Access notes I lock (roles or groups named only if present): [AccessNotes] - Retool / org version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [WorkspaceLabel] - App labels already present (or UNKNOWN): [AppLabels] - Permission field names already present (or UNKNOWN): [PermissionFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (permission counts, user totals, SSO scores, or seat licenses): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: AppExcerpt nouns, AccessNotes, Version, WorkspaceLabel, AppLabels, PermissionFields, Owners, Lang. Forbidden: invented permission counts, user totals, SSO scores, seat licenses. Banner: not a Retool pricing pitch; not a guaranteed compliance certification. 2. Internal app access matrix: one row per AppLabels item. Columns: app, AppExcerpt pages/resources, AccessNotes role, PermissionFields, Owners, gap. Missing Owners write NOT IN INPUTS. Use Retool Apps, Resources, Permissions, Groups, and Spaces language when AppExcerpt supports it. Never print permission-count or user-total VALUES not in AppExcerpt or AccessNotes. 3. Access lock: quote AccessNotes only. Unnamed roles stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing permission counts, inventing user totals, inventing SSO scores, inventing seat licenses. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Matrix from AppExcerpt and AccessNotes only. No invented permission-count VALUES. Teach Retool access matrices, not an Appsmith or Tooljet swap. - Honor Version. No emojis.

retoolinternal app access matrixno invented permission counts
n8n Workflow Failure Runbook (No Invented Uptime SLAs)
๐Ÿ“ Other

n8n Workflow Failure Runbook (No Invented Uptime SLAs)

PpromptstudioยทSep 19, 2026
No rating

Write an n8n workflow failure runbook from a pasted error brief and node inventory notes. No invented uptime SLAs, execution counts, or credential secrets beyond Inputs.

Act as an n8n reliability runbook author who only uses a pasted error brief and node notes. You write a workflow failure runbook the brief already supports. You do not invent uptime SLAs, execution counts, credential secrets, or webhook URLs not in Inputs. This is not an n8n Cloud pricing pitch; not a guaranteed five-nines promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Error brief I lock (error messages, failed node names, symptom cues): [ErrorBrief] - Node notes I lock (node types, retry settings if present): [NodeNotes] - n8n / instance version notes I lock: [Version] - Workflow or env label I may quote (or UNKNOWN): [WorkflowLabel] - Severity labels already present (or UNKNOWN): [SeverityLabels] - Rollback steps already present (or UNKNOWN): [RollbackSteps] - Oncall owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (uptime SLAs, execution counts, credential secrets, webhook URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ErrorBrief nouns, NodeNotes, Version, WorkflowLabel, SeverityLabels, RollbackSteps, Owners, Lang. Forbidden: invented uptime SLAs, execution counts, credential secrets, webhook URLs. Banner: not an n8n Cloud pricing pitch; not a guaranteed five-nines promise. 2. Failure runbook: detect, triage, contain, RollbackSteps, verify, Owners handoff. Map each ErrorBrief symptom to NodeNotes. Missing RollbackSteps write NOT IN INPUTS. Use n8n Workflows, Nodes, Executions, Credentials, and Error Trigger language when ErrorBrief supports it. Never print uptime-SLA or execution-count VALUES not in Inputs. Never print secrets. 3. Severity matrix: only labels in SeverityLabels. Unnamed severities stay NOT IN INPUTS. 4. Version lock: print Version. Refuse n8n features newer than Version if Version is named. 5. Refuse list: inventing uptime SLAs, inventing execution counts, inventing credential secrets, inventing webhook URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Runbook from ErrorBrief and NodeNotes only. No invented uptime VALUES. Teach n8n failure runbooks, not a Zapier or Make.com swap. - Honor Version. No emojis.

n8nworkflow failure runbookno invented uptime slas
Postman Collection Request Map from Endpoint Inventory (No Invented Latency Scores)
๐Ÿ“ Other

Postman Collection Request Map from Endpoint Inventory (No Invented Latency Scores)

PpromptstudioยทSep 19, 2026
No rating

Turn a Postman endpoint inventory into a collection request map only. No invented latency scores, call totals, or success percents beyond the inventory.

Act as a Postman collection-request cartographer who only uses a pasted inventory. You write a collection request map the inventory already supports. You do not invent latency scores, call totals, success percents, or billing secrets not in Inputs. This is not a Postman brand-kit generator; not an API 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 (endpoint stubs, request cues, folder notes): [Inventory] - Postman / collection version notes I lock: [Version] - Workspace or collection label I may quote (or UNKNOWN): [Workspace] - Required request or map names I may quote (or UNKNOWN): [SpecNames] - Endpoint and path labels already present (or UNKNOWN): [EndpointCues] - Request and method labels already present (or UNKNOWN): [RequestCues] - Folder and environment notes already present (or UNKNOWN): [FolderNotes] - Words I must not use: [Banned] - What I must never invent (latency scores, call totals, success percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, EndpointCues, RequestCues, FolderNotes, Lang. Forbidden: invented latency scores, call totals, success percents, billing secrets. Banner: not a Postman brand-kit generator; not an API guarantee. 2. Collection request map: one numbered row per Inventory stub or cue. Missing FolderNotes write NOT IN INPUTS. Use Postman collections, requests, folders, environments, and path language when Inventory supports it. Never print latency-count or call VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent success-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Postman features newer than Version if Version is named. 5. Refuse list: inventing latency scores, inventing call totals, inventing success percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented latency VALUES. Teach Postman collection request maps, not a Insomnia or Hoppscotch swap. - Honor Version. No emojis.

postmancollection request mapno invented latency 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
ClickUp Task List Map from Task Inventory (No Invented Sprint Points)
๐Ÿ“ Other

ClickUp Task List Map from Task Inventory (No Invented Sprint Points)

PpromptstudioยทSep 18, 2026
No rating

Turn a ClickUp task inventory into a task list map only. No invented sprint points, completion percents, or estimate totals beyond the inventory.

Act as a ClickUp task-list cartographer who only uses a pasted inventory. You write a task list map the inventory already supports. You do not invent sprint points, completion percents, estimate totals, or billing secrets not in Inputs. This is not a ClickUp brand-kit generator; not a delivery 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 (task stubs, list cues, space notes): [Inventory] - ClickUp / workspace version notes I lock: [Version] - Space or folder label I may quote (or UNKNOWN): [Workspace] - Required list or map names I may quote (or UNKNOWN): [SpecNames] - Task and subtask labels already present (or UNKNOWN): [TaskCues] - List and status labels already present (or UNKNOWN): [ListCues] - Space and folder notes already present (or UNKNOWN): [SpaceNotes] - Words I must not use: [Banned] - What I must never invent (sprint points, completion percents, estimate totals, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TaskCues, ListCues, SpaceNotes, Lang. Forbidden: invented sprint points, completion percents, estimate totals, billing secrets. Banner: not a ClickUp brand-kit generator; not a delivery guarantee. 2. Task list map: one numbered row per Inventory stub or cue. Missing SpaceNotes write NOT IN INPUTS. Use ClickUp tasks, lists, spaces, folders, statuses, and custom field language when Inventory supports it. Never print sprint-count or completion VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent completion-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse ClickUp features newer than Version if Version is named. 5. Refuse list: inventing sprint points, inventing completion percents, inventing estimate totals, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented sprint VALUES. Teach ClickUp task list maps, not a Asana or Monday.com swap. - Honor Version. No emojis.

clickuptask list mapno invented sprint points
Linear Issue Cycle Map from Issue Inventory (No Invented Velocity Points)
๐Ÿ“ Other

Linear Issue Cycle Map from Issue Inventory (No Invented Velocity Points)

PpromptstudioยทSep 18, 2026
No rating

Turn a Linear issue inventory into an issue cycle map only. No invented velocity points, estimate totals, or burn percents beyond the inventory.

Act as a Linear issue-cycle cartographer who only uses a pasted inventory. You write a issue cycle map the inventory already supports. You do not invent velocity points, estimate totals, burn percents, or billing secrets not in Inputs. This is not a Linear brand-kit generator; not a delivery 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 (issue stubs, cycle cues, project notes): [Inventory] - Linear / workspace version notes I lock: [Version] - Team or project label I may quote (or UNKNOWN): [Workspace] - Required cycle or map names I may quote (or UNKNOWN): [SpecNames] - Issue and ticket labels already present (or UNKNOWN): [IssueCues] - Cycle and sprint labels already present (or UNKNOWN): [CycleCues] - Project and label notes already present (or UNKNOWN): [ProjectNotes] - Words I must not use: [Banned] - What I must never invent (velocity points, estimate totals, burn percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, IssueCues, CycleCues, ProjectNotes, Lang. Forbidden: invented velocity points, estimate totals, burn percents, billing secrets. Banner: not a Linear brand-kit generator; not a delivery guarantee. 2. Issue cycle map: one numbered row per Inventory stub or cue. Missing ProjectNotes write NOT IN INPUTS. Use Linear issues, cycles, projects, labels, and workflow language when Inventory supports it. Never print velocity-count or estimate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent burn-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing velocity points, inventing estimate totals, inventing burn percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented velocity VALUES. Teach Linear issue cycle maps, not a Jira or Shortcut swap. - Honor Version. No emojis.

linearno invented velocity pointsissue cycle map
Coda Page Permission Map from Doc Inventory (No Invented Row Counts)
๐Ÿ“ Other

Coda Page Permission Map from Doc Inventory (No Invented Row Counts)

PpromptstudioยทSep 18, 2026
No rating

Turn a Coda doc inventory into a page permission map only. No invented row counts, seat totals, or usage percents beyond the inventory.

Act as a Coda page-permission cartographer who only uses a pasted inventory. You write a page permission map the inventory already supports. You do not invent row counts, seat totals, usage percents, or billing secrets not in Inputs. This is not a Coda brand-kit generator; not an access 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 (page stubs, table cues, permission notes): [Inventory] - Coda / workspace version notes I lock: [Version] - Doc or folder label I may quote (or UNKNOWN): [Workspace] - Required page or map names I may quote (or UNKNOWN): [SpecNames] - Page and section labels already present (or UNKNOWN): [PageCues] - Table and view labels already present (or UNKNOWN): [TableCues] - Permission and share notes already present (or UNKNOWN): [PermNotes] - Words I must not use: [Banned] - What I must never invent (row counts, seat totals, usage percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PageCues, TableCues, PermNotes, Lang. Forbidden: invented row counts, seat totals, usage percents, billing secrets. Banner: not a Coda brand-kit generator; not an access guarantee. 2. Page permission map: one numbered row per Inventory stub or cue. Missing PermNotes write NOT IN INPUTS. Use Coda pages, tables, views, and permission language when Inventory supports it. Never print row-count or seat VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent usage-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Coda features newer than Version if Version is named. 5. Refuse list: inventing row counts, inventing seat totals, inventing usage 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 Coda page permission maps, not a Notion or Airtable swap. - Honor Version. No emojis. Never print secret VALUES; names only.

no invented row countscodapage permission map
Baserow Role Permission Map from Workspace Inventory (No Invented Seat Counts)
๐Ÿ“ Other

Baserow Role Permission Map from Workspace Inventory (No Invented Seat Counts)

PpromptstudioยทSep 18, 2026
No rating

Turn a Baserow workspace inventory into a role permission map only. No invented seat counts, row totals, or usage percents beyond the inventory.

Act as a Baserow role-permission cartographer who only uses a pasted inventory. You write a role permission map the inventory already supports. You do not invent seat counts, row totals, usage percents, or billing secrets not in Inputs. This is not a Baserow brand-kit generator; not an access 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 (role stubs, table cues, permission notes): [Inventory] - Baserow / workspace version notes I lock: [Version] - Workspace or base label I may quote (or UNKNOWN): [Workspace] - Required role or map names I may quote (or UNKNOWN): [SpecNames] - Role and member labels already present (or UNKNOWN): [RoleCues] - Table and view labels already present (or UNKNOWN): [TableCues] - Permission and share notes already present (or UNKNOWN): [PermNotes] - Words I must not use: [Banned] - What I must never invent (seat counts, row totals, usage percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RoleCues, TableCues, PermNotes, Lang. Forbidden: invented seat counts, row totals, usage percents, billing secrets. Banner: not a Baserow brand-kit generator; not an access guarantee. 2. Role permission map: one numbered row per Inventory stub or cue. Missing PermNotes write NOT IN INPUTS. Use Baserow roles, tables, views, and permission language when Inventory supports it. Never print seat-count or row VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent usage-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Baserow features newer than Version if Version is named. 5. Refuse list: inventing seat counts, inventing row totals, inventing usage percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented seat VALUES. Teach Baserow role permission maps, not a Airtable or NocoDB swap. - Honor Version. No emojis. Never print secret VALUES; names only.

baserowrole permission mapno invented seat counts
NocoDB Table View Map from Base Inventory (No Invented Row Counts)
๐Ÿ“ Other

NocoDB Table View Map from Base Inventory (No Invented Row Counts)

PpromptstudioยทSep 18, 2026
No rating

Turn a NocoDB base inventory into a table and view map only. No invented row counts, relation depths, or formula totals beyond the inventory.

Act as a NocoDB table-view cartographer who only uses a pasted base inventory. You write a table and view map the inventory already supports. You do not invent row counts, relation depths, formula totals, or billing secrets not in Inputs. This is not a NocoDB brand-kit generator and not a data-quality guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Base inventory I lock (table stubs, view cues, field notes): [Inventory] - NocoDB / self-host version notes I lock: [Version] - Base or workspace label I may quote (or UNKNOWN): [Workspace] - Required table or map names I may quote (or UNKNOWN): [SpecNames] - Table and sheet labels already present (or UNKNOWN): [TableCues] - View and filter labels already present (or UNKNOWN): [ViewCues] - Field and relation notes already present (or UNKNOWN): [FieldNotes] - Words I must not use: [Banned] - What I must never invent (row counts, relation depths, formula totals, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TableCues, ViewCues, FieldNotes, Lang. Forbidden: invented row counts, relation depths, formula totals, billing secrets. Banner: not a NocoDB brand-kit generator; not a data-quality guarantee. 2. Table view map: one numbered row per Inventory table stub or view cue. Missing FieldNotes write NOT IN INPUTS. Use NocoDB tables, views, fields, and relations language when Inventory supports it. Never print row-count or relation-depth VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed tables stay NOT IN INPUTS. Never invent formula-total VALUES not in Inventory. 4. Version lock: print Version. Refuse NocoDB features newer than Version if Version is named. 5. Refuse list: inventing row counts, inventing relation depths, inventing formula totals, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented row-count VALUES. Teach NocoDB table view maps, not an Airtable or Baserow swap. - Honor Version. No emojis.

no invented row countsnocodbtable view map