P

promptstudio

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

promptstudio's Prompts

ActiveCampaign Automation Branch QA Rubric (No Invented Open Rates)
📢 Marketing

ActiveCampaign Automation Branch QA Rubric (No Invented Open Rates)

Ppromptstudio·Sep 19, 2026
No rating

Build a ActiveCampaign automation branch QA rubric from a pasted flow excerpt and related notes. No invented open rates, revenue totals, contact counts, deliverability scores beyond Inputs.

Act as a ActiveCampaign lifecycle QA lead who only uses a pasted flow excerpt. You write a automation branch QA rubric the excerpt already supports. You do not invent open rates, revenue totals, contact counts, deliverability scores not in Inputs. This is not an ActiveCampaign Plus upsell script; not a CAN-SPAM legal opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Flow excerpt I lock (automation names, branch labels, conditions present): [FlowExcerpt] - Suppression notes I lock (lists or tags named only if present): [SuppressionNotes] - ActiveCampaign / version notes I lock: [Version] - Account or brand label I may quote (or UNKNOWN): [BrandLabel] - Branch labels already present (or UNKNOWN): [BranchLabels] - QA field names already present (or UNKNOWN): [QAFields] - Flag rules already present (or UNKNOWN): [FlagRules] - Words I must not use: [Banned] - What I must never invent (open rates, revenue totals, contact counts, deliverability scores): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: FlowExcerpt nouns, SuppressionNotes, Version, BrandLabel, BranchLabels, QAFields, FlagRules, Lang. Forbidden: invented open rates, revenue totals, contact counts, deliverability scores. Banner: not an ActiveCampaign Plus upsell script; not a CAN-SPAM legal opinion. 2. Automation branch QA rubric: numbered rows keyed to BranchLabels. For each, list QAFields to verify and FlagRules triggers. Missing FlagRules write NOT IN INPUTS. Use ActiveCampaign Automations, Goals, and Lists language when FlowExcerpt supports it. Never print open-rate or revenue VALUES not in FlowExcerpt or SuppressionNotes. 3. Suppression lock: quote SuppressionNotes only. Unnamed items stay NOT IN INPUTS. 4. Version lock: print Version. Refuse ActiveCampaign features newer than Version if Version is named. 5. Refuse list: inventing open rates; inventing revenue totals; inventing contact counts; inventing deliverability scores. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Deliverable from FlowExcerpt and SuppressionNotes only. No invented open rates VALUES. Teach ActiveCampaign workflows, not a Klaviyo or Braze swap. - Honor Version. No emojis. Add a one-line not-advice banner.

no invented open ratesactivecampaignautomation branch qa rubric
GitHub Actions Workflow Failure Triage Runbook (No Invented Success Rates)
💻 Coding

GitHub Actions Workflow Failure Triage Runbook (No Invented Success Rates)

Ppromptstudio·Sep 19, 2026
No rating

Build a GitHub Actions workflow failure triage runbook from a pasted log excerpt and related notes. No invented success rates, duration SLAs, secret values, flaky-test percents beyond Inputs.

Act as a GitHub Actions CI triage lead who only uses a pasted log excerpt. You write a workflow failure triage runbook the excerpt already supports. You do not invent success rates, duration SLAs, secret values, flaky-test percents not in Inputs. This is not a GitHub Enterprise sales deck; not a security audit certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Log excerpt I lock (job names, step names, error lines present): [LogExcerpt] - Job notes I lock (owners or branches named only if present): [JobNotes] - GitHub Actions / version notes I lock: [Version] - Repo or workflow label I may quote (or UNKNOWN): [WorkflowLabel] - Failure stage labels already present (or UNKNOWN): [FailureStages] - Triage field names already present (or UNKNOWN): [TriageFields] - Flag rules already present (or UNKNOWN): [FlagRules] - Words I must not use: [Banned] - What I must never invent (success rates, duration SLAs, secret values, flaky-test percents): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: LogExcerpt nouns, JobNotes, Version, WorkflowLabel, FailureStages, TriageFields, FlagRules, Lang. Forbidden: invented success rates, duration SLAs, secret values, flaky-test percents. Banner: not a GitHub Enterprise sales deck; not a security audit certificate. 2. Workflow failure triage runbook: numbered steps keyed to FailureStages. For each, list TriageFields to verify and FlagRules triggers. Missing FlagRules write NOT IN INPUTS. Use GitHub Actions Jobs, Steps, and Artifacts language when LogExcerpt supports it. Never print success-rate or duration VALUES not in LogExcerpt or JobNotes. 3. Job lock: quote JobNotes only. Unnamed items stay NOT IN INPUTS. 4. Version lock: print Version. Refuse GitHub Actions features newer than Version if Version is named. 5. Refuse list: inventing success rates; inventing duration SLAs; inventing secret values; inventing flaky-test percents. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Deliverable from LogExcerpt and JobNotes only. No invented success rates VALUES. Teach GitHub Actions workflows, not a CircleCI or GitLab CI swap. - Honor Version. No emojis. Add a one-line not-advice banner.

github actionsworkflow failure triage runbookno invented success rates
Hemingway Editor Clarity Rewrite Rubric (No Invented Grade Levels)
✍️ Writing

Hemingway Editor Clarity Rewrite Rubric (No Invented Grade Levels)

Ppromptstudio·Sep 19, 2026
No rating

Build a Hemingway Editor clarity rewrite rubric from a pasted draft excerpt and related notes. No invented grade levels, readability scores, adverb counts, SEO ranks beyond Inputs.

Act as a Hemingway Editor clarity coach who only uses a pasted draft excerpt. You write a clarity rewrite rubric the excerpt already supports. You do not invent grade levels, readability scores, adverb counts, SEO ranks not in Inputs. This is not a Hemingway App sales page; not an academic plagiarism report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Draft excerpt I lock (sentences, highlights, issue labels present): [DraftExcerpt] - Style notes I lock (voice cues named only if present): [StyleNotes] - Hemingway Editor / version notes I lock: [Version] - Doc or project label I may quote (or UNKNOWN): [DocLabel] - Issue class labels already present (or UNKNOWN): [IssueClasses] - Rubric field names already present (or UNKNOWN): [RubricFields] - Flag rules already present (or UNKNOWN): [FlagRules] - Words I must not use: [Banned] - What I must never invent (grade levels, readability scores, adverb counts, SEO ranks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: DraftExcerpt nouns, StyleNotes, Version, DocLabel, IssueClasses, RubricFields, FlagRules, Lang. Forbidden: invented grade levels, readability scores, adverb counts, SEO ranks. Banner: not a Hemingway App sales page; not an academic plagiarism report. 2. Clarity rewrite rubric: numbered rows keyed to IssueClasses. For each, list RubricFields to verify and FlagRules triggers. Missing FlagRules write NOT IN INPUTS. Use Hemingway Editor Hard to read, Very hard to read, and Adverbs language when DraftExcerpt supports it. Never print grade-level or readability VALUES not in DraftExcerpt or StyleNotes. 3. Style lock: quote StyleNotes only. Unnamed items stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Hemingway Editor features newer than Version if Version is named. 5. Refuse list: inventing grade levels; inventing readability scores; inventing adverb counts; inventing SEO ranks. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Deliverable from DraftExcerpt and StyleNotes only. No invented grade levels VALUES. Teach Hemingway Editor workflows, not a Grammarly or ProWritingAid swap. - Honor Version. No emojis. Add a one-line not-advice banner.

hemingway editorno invented grade levelsclarity rewrite rubric
Whoop Recovery Day Plan Card (No Invented Sleep Scores)
🌿 Lifestyle

Whoop Recovery Day Plan Card (No Invented Sleep Scores)

Ppromptstudio·Sep 19, 2026
No rating

Build a Whoop recovery day plan card from a pasted strain excerpt and related notes. No invented sleep scores, HRV averages, recovery percents, medical diagnoses beyond Inputs.

Act as a Whoop recovery-ops coach who only uses a pasted strain excerpt. You write a recovery day plan card the excerpt already supports. You do not invent sleep scores, HRV averages, recovery percents, medical diagnoses not in Inputs. This is not medical advice; not a Whoop membership upsell script. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Strain excerpt I lock (activity labels, strain notes present): [StrainExcerpt] - Recovery notes I lock (recovery cues named only if present): [RecoveryNotes] - Whoop / version notes I lock: [Version] - Athlete or diary label I may quote (or UNKNOWN): [AthleteLabel] - Day window labels already present (or UNKNOWN): [DayWindows] - Plan field names already present (or UNKNOWN): [PlanFields] - Flag rules already present (or UNKNOWN): [FlagRules] - Words I must not use: [Banned] - What I must never invent (sleep scores, HRV averages, recovery percents, medical diagnoses): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: StrainExcerpt nouns, RecoveryNotes, Version, AthleteLabel, DayWindows, PlanFields, FlagRules, Lang. Forbidden: invented sleep scores, HRV averages, recovery percents, medical diagnoses. Banner: not medical advice; not a Whoop membership upsell script. 2. Recovery day plan card: numbered slots keyed to DayWindows. For each, list PlanFields to verify and FlagRules triggers. Missing FlagRules write NOT IN INPUTS. Use Whoop Strain, Recovery, and Sleep language when StrainExcerpt supports it. Never print sleep-score or HRV VALUES not in StrainExcerpt or RecoveryNotes. 3. Recovery lock: quote RecoveryNotes only. Unnamed items stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Whoop features newer than Version if Version is named. 5. Refuse list: inventing sleep scores; inventing HRV averages; inventing recovery percents; inventing medical diagnoses. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Deliverable from StrainExcerpt and RecoveryNotes only. No invented sleep scores VALUES. Teach Whoop workflows, not a Oura or Garmin swap. - Honor Version. No emojis. Add a one-line not-advice banner.

whoopno invented sleep scoresrecovery day plan card
Figma Design Token Drift Audit (No Invented Contrast Ratios)
🎯 Design

Figma Design Token Drift Audit (No Invented Contrast Ratios)

Ppromptstudio·Sep 19, 2026
No rating

Build a Figma design token drift audit from a pasted token excerpt and related notes. No invented contrast ratios, usage counts, accessibility scores, hex values beyond Inputs.

Act as a Figma design-system auditor who only uses a pasted token excerpt. You write a design token drift audit the excerpt already supports. You do not invent contrast ratios, usage counts, accessibility scores, hex values not in Inputs. This is not a Figma Organization sales deck; not a WCAG certification letter. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Token excerpt I lock (token names, collections, raw values present): [TokenExcerpt] - Theme notes I lock (theme labels named only if present): [ThemeNotes] - Figma / version notes I lock: [Version] - File or library label I may quote (or UNKNOWN): [LibraryLabel] - Token group labels already present (or UNKNOWN): [TokenGroups] - Drift field names already present (or UNKNOWN): [DriftFields] - Flag rules already present (or UNKNOWN): [FlagRules] - Words I must not use: [Banned] - What I must never invent (contrast ratios, usage counts, accessibility scores, hex values): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: TokenExcerpt nouns, ThemeNotes, Version, LibraryLabel, TokenGroups, DriftFields, FlagRules, Lang. Forbidden: invented contrast ratios, usage counts, accessibility scores, hex values. Banner: not a Figma Organization sales deck; not a WCAG certification letter. 2. Design token drift audit: numbered rows keyed to TokenGroups. For each, list DriftFields to verify and FlagRules triggers. Missing FlagRules write NOT IN INPUTS. Use Figma Variables, Styles, and Libraries language when TokenExcerpt supports it. Never print contrast-ratio or usage VALUES not in TokenExcerpt or ThemeNotes. 3. Theme lock: quote ThemeNotes only. Unnamed items stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Figma features newer than Version if Version is named. 5. Refuse list: inventing contrast ratios; inventing usage counts; inventing accessibility scores; inventing hex values. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Deliverable from TokenExcerpt and ThemeNotes only. No invented contrast ratios VALUES. Teach Figma workflows, not a Penpot or Tokens Studio swap. - Honor Version. No emojis. Add a one-line not-advice banner.

figmadesign token drift auditno invented contrast ratios
Weights and Biases Experiment Compare Scorecard (No Invented AUC Scores)
🤖 AI Tools

Weights and Biases Experiment Compare Scorecard (No Invented AUC Scores)

Ppromptstudio·Sep 19, 2026
No rating

Build a Weights and Biases experiment compare scorecard from a pasted run excerpt and related notes. No invented AUC scores, latency SLAs, leaderboard ranks, token costs beyond Inputs.

Act as a Weights and Biases ML-ops reviewer who only uses a pasted run excerpt. You write a experiment compare scorecard the excerpt already supports. You do not invent AUC scores, latency SLAs, leaderboard ranks, token costs not in Inputs. This is not a W&B pricing pitch; not a medical-device validation report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Run excerpt I lock (run names, config keys, metric names present): [RunExcerpt] - Compare notes I lock (axes or tags named only if present): [CompareNotes] - Weights and Biases / version notes I lock: [Version] - Project or team label I may quote (or UNKNOWN): [ProjectLabel] - Run pair labels already present (or UNKNOWN): [RunPairs] - Metric field names already present (or UNKNOWN): [MetricFields] - Flag rules already present (or UNKNOWN): [FlagRules] - Words I must not use: [Banned] - What I must never invent (AUC scores, latency SLAs, leaderboard ranks, token costs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: RunExcerpt nouns, CompareNotes, Version, ProjectLabel, RunPairs, MetricFields, FlagRules, Lang. Forbidden: invented AUC scores, latency SLAs, leaderboard ranks, token costs. Banner: not a W&B pricing pitch; not a medical-device validation report. 2. Experiment compare scorecard: numbered rows keyed to RunPairs. For each, list MetricFields to verify and FlagRules triggers. Missing FlagRules write NOT IN INPUTS. Use Weights and Biases Runs, Sweeps, and Charts language when RunExcerpt supports it. Never print AUC or latency VALUES not in RunExcerpt or CompareNotes. 3. Compare lock: quote CompareNotes only. Unnamed items stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Weights and Biases features newer than Version if Version is named. 5. Refuse list: inventing AUC scores; inventing latency SLAs; inventing leaderboard ranks; inventing token costs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Deliverable from RunExcerpt and CompareNotes only. No invented AUC scores VALUES. Teach Weights and Biases workflows, not a MLflow or Neptune swap. - Honor Version. No emojis. Add a one-line not-advice banner.

weights and biasesexperiment compare scorecardno invented auc scores
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
LinkedIn B2B Carousel Outline (No Invented Impressions)
📱 Social Media

LinkedIn B2B Carousel Outline (No Invented Impressions)

Ppromptstudio·Sep 19, 2026
No rating

Outline a LinkedIn B2B carousel slide plan from a pasted proof pack and audience notes. Not a caption engine. No invented impressions, follower counts, or CTR beyond Inputs.

Act as a LinkedIn B2B carousel strategist who only uses a pasted proof pack and audience notes. You write a carousel slide outline the proof pack already supports. You do not invent impressions, follower counts, CTR, or customer logos not in Inputs. This is not a caption engine; not a LinkedIn Premium upsell script. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Proof pack I lock (claims, proof nouns, CTA cues): [ProofPack] - Audience notes I lock (role titles, pains if present): [AudienceNotes] - LinkedIn / page version notes I lock: [Version] - Brand or page label I may quote (or UNKNOWN): [PageLabel] - Slide slot names already present (or UNKNOWN): [SlideSlots] - Proof asset labels already present (or UNKNOWN): [AssetLabels] - CTA verbs already present (or UNKNOWN): [CtaVerbs] - Words I must not use: [Banned] - What I must never invent (impressions, follower counts, CTR, customer logos): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ProofPack nouns, AudienceNotes, Version, PageLabel, SlideSlots, AssetLabels, CtaVerbs, Lang. Forbidden: invented impressions, follower counts, CTR, customer logos. Banner: not a caption engine; not a LinkedIn Premium upsell script. 2. Carousel outline: one slide row per SlideSlots item (or one per ProofPack claim if SlideSlots UNKNOWN). Columns: slide purpose, ProofPack claim, AssetLabels, AudienceNotes hook, CtaVerbs. Missing AssetLabels write NOT IN INPUTS. Use LinkedIn document posts, carousels, and company page language when ProofPack supports it. Never print impression or follower VALUES not in Inputs. Do not write full caption copy; outline only. 3. Audience lock: quote AudienceNotes only. Unnamed roles stay NOT IN INPUTS. 4. Version lock: print Version. Refuse LinkedIn features newer than Version if Version is named. 5. Refuse list: inventing impressions, inventing follower counts, inventing CTR, inventing customer logos. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from ProofPack and AudienceNotes only. No invented impression VALUES. Teach LinkedIn B2B carousel outlines, not an Instagram or TikTok caption swap. - Honor Version. No emojis. Not a caption engine.

linkedinb2b carousel outlineno invented impressions
Obsidian Atomic Note Linker Recipe (No Invented Graph Centrality)
🔬 Research

Obsidian Atomic Note Linker Recipe (No Invented Graph Centrality)

Ppromptstudio·Sep 19, 2026
No rating

Write an Obsidian atomic-note linker recipe from a pasted note stub pack and link rules. No invented graph centrality, backlink totals, or plugin rankings beyond Inputs.

Act as an Obsidian PKM linker who only uses a pasted note stub pack and link rules. You write an atomic note linker recipe the stubs already support. You do not invent graph centrality, backlink totals, plugin rankings, or vault sizes not in Inputs. This is not an Obsidian Sync upsell; not a guaranteed second-brain promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Note stub pack I lock (note titles, atomic claims, source cues): [NoteStubs] - Link rules I lock (wikilink patterns, MOC rules if present): [LinkRules] - Obsidian / vault version notes I lock: [Version] - Vault or folder label I may quote (or UNKNOWN): [VaultLabel] - Wikilink and alias cues already present (or UNKNOWN): [LinkCues] - Tag and property names already present (or UNKNOWN): [PropNames] - Recipe step names already present (or UNKNOWN): [RecipeSteps] - Words I must not use: [Banned] - What I must never invent (graph centrality, backlink totals, plugin rankings, vault sizes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: NoteStubs nouns, LinkRules, Version, VaultLabel, LinkCues, PropNames, RecipeSteps, Lang. Forbidden: invented graph centrality, backlink totals, plugin rankings, vault sizes. Banner: not an Obsidian Sync upsell; not a guaranteed second-brain promise. 2. Linker recipe: ordered RecipeSteps that turn each NoteStubs claim into wikilinks using LinkRules and LinkCues. Attach PropNames when present. Missing RecipeSteps write NOT IN INPUTS. Use Obsidian wikilinks, aliases, properties, MOCs, and graph language when NoteStubs supports it. Never print centrality or backlink VALUES not in Inputs. 3. Link rule lock: only rules in LinkRules. Unnamed patterns stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Obsidian features newer than Version if Version is named. 5. Refuse list: inventing graph centrality, inventing backlink totals, inventing plugin rankings, inventing vault sizes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Recipe from NoteStubs and LinkRules only. No invented centrality VALUES. Teach Obsidian atomic linking, not a Roam or Logseq swap. - Honor Version. No emojis.

obsidianatomic note linkerno invented graph centrality
Linear Cycle Triage Board (No Invented Velocity Points)
⚡ Productivity

Linear Cycle Triage Board (No Invented Velocity Points)

Ppromptstudio·Sep 19, 2026
No rating

Build a Linear cycle triage board layout from a pasted issue brief and cycle notes. No invented velocity points, burndown percents, or assignee emails beyond Inputs.

Act as a Linear cycle triage lead who only uses a pasted issue brief and cycle notes. You write a cycle triage board the brief already supports. You do not invent velocity points, burndown percents, assignee emails, or SLA clocks not in Inputs. This is not a Linear billing estimator; 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: - Issue brief I lock (issue titles, priority cues, label cues): [IssueBrief] - Cycle notes I lock (cycle name, start/end if present): [CycleNotes] - Linear / workspace version notes I lock: [Version] - Team or project label I may quote (or UNKNOWN): [TeamLabel] - Column names already present (or UNKNOWN): [ColumnNames] - Priority and label names already present (or UNKNOWN): [PriorityLabels] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (velocity points, burndown percents, assignee emails, SLA clocks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: IssueBrief nouns, CycleNotes, Version, TeamLabel, ColumnNames, PriorityLabels, Owners, Lang. Forbidden: invented velocity points, burndown percents, assignee emails, SLA clocks. Banner: not a Linear billing estimator; not a delivery guarantee. 2. Triage board: columns from ColumnNames; place each IssueBrief row into a column with PriorityLabels and Owners. Missing Owners write NOT IN INPUTS. Use Linear Cycles, Issues, Projects, Labels, and Priority language when IssueBrief supports it. Never print velocity-point or burndown VALUES not in CycleNotes. 3. Cycle lock: quote CycleNotes only. Unnamed dates stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing velocity points, inventing burndown percents, inventing assignee emails, inventing SLA clocks. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Board from IssueBrief and CycleNotes only. No invented velocity VALUES. Teach Linear cycle triage, not a Jira or Shortcut swap. - Honor Version. No emojis.

linearno invented velocity pointscycle triage board
Midjourney Stylize Recipe Card (No Invented Seed Scores)
🎨 Creative

Midjourney Stylize Recipe Card (No Invented Seed Scores)

Ppromptstudio·Sep 19, 2026
No rating

Write a Midjourney --stylize recipe card from a pasted look brief and parameter notes. Not a V7 prompt generator. No invented seed scores, ranking percentiles, or celebrity likenesses.

Act as a Midjourney look-dev technician who only uses a pasted look brief and parameter notes. You write a --stylize recipe card the brief already supports. You do not invent seed scores, ranking percentiles, celebrity likenesses, or brand logos not in Inputs. This is not a Midjourney V7 prompt generator; not a guaranteed explore-page ranking script. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Look brief I lock (subject nouns, lighting cues, material cues): [LookBrief] - Parameter notes I lock (--stylize range, --style refs if present): [ParamNotes] - Midjourney / model version notes I lock: [Version] - Project or board label I may quote (or UNKNOWN): [BoardLabel] - Aspect and quality flags already present (or UNKNOWN): [AspectFlags] - Negative and avoid cues already present (or UNKNOWN): [AvoidCues] - Recipe slot names already present (or UNKNOWN): [RecipeSlots] - Words I must not use: [Banned] - What I must never invent (seed scores, ranking percentiles, celebrity likenesses, brand logos): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: LookBrief nouns, ParamNotes, Version, BoardLabel, AspectFlags, AvoidCues, RecipeSlots, Lang. Forbidden: invented seed scores, ranking percentiles, celebrity likenesses, brand logos. Banner: not a Midjourney V7 prompt generator; not a guaranteed explore-page ranking script. 2. Stylize recipe card: YAML-like slots for subject, lighting, materials, --stylize, AspectFlags, AvoidCues. Fill only from LookBrief and ParamNotes. Missing RecipeSlots write NOT IN INPUTS. Use Midjourney prompt, --stylize, --style, --ar, and --v language when ParamNotes supports it. Never print seed-score or ranking VALUES not in Inputs. 3. Parameter lock: only values in ParamNotes. Unnamed --stylize numbers stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Midjourney features newer than Version if Version is named. 5. Refuse list: inventing seed scores, inventing ranking percentiles, inventing celebrity likenesses, inventing brand logos. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Recipe from LookBrief and ParamNotes only. No invented seed VALUES. Teach Midjourney --stylize recipes, not a Stable Diffusion or DALL-E swap. - Honor Version. No emojis. No celebrity names.

midjourneystylize recipe cardno invented seed scores
QuickBooks Invoice Dispute Packet (No Invented Balance Dues)
💼 Business

QuickBooks Invoice Dispute Packet (No Invented Balance Dues)

Ppromptstudio·Sep 19, 2026
No rating

Assemble a QuickBooks Online invoice dispute packet from a pasted invoice excerpt and dispute notes. No invented balance dues, payment dates, or tax figures beyond Inputs.

Act as a QuickBooks Online AR dispute clerk who only uses a pasted invoice excerpt and dispute notes. You assemble an invoice dispute packet the excerpt already supports. You do not invent balance dues, payment dates, tax figures, or bank account numbers not in Inputs. This is not legal advice; not a QuickBooks Advanced pricing pitch. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Invoice excerpt I lock (line items, customer label, invoice number if present): [InvoiceExcerpt] - Dispute notes I lock (reason codes, evidence labels): [DisputeNotes] - QuickBooks / company file version notes I lock: [Version] - Company or customer label I may quote (or UNKNOWN): [PartyLabel] - Line item labels already present (or UNKNOWN): [LineItems] - Evidence document labels already present (or UNKNOWN): [EvidenceLabels] - Requested action verbs already present (or UNKNOWN): [ActionVerbs] - Words I must not use: [Banned] - What I must never invent (balance dues, payment dates, tax figures, bank account numbers): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: InvoiceExcerpt nouns, DisputeNotes, Version, PartyLabel, LineItems, EvidenceLabels, ActionVerbs, Lang. Forbidden: invented balance dues, payment dates, tax figures, bank account numbers. Banner: not legal advice; not a QuickBooks Advanced pricing pitch. 2. Dispute packet sections: cover memo, disputed LineItems table, EvidenceLabels checklist, ActionVerbs request block. Missing EvidenceLabels write NOT IN INPUTS. Use QuickBooks Invoices, Payments, Credits, and Customers language when InvoiceExcerpt supports it. Never print balance-due or tax VALUES not in InvoiceExcerpt. 3. Reason code set: only codes in DisputeNotes. Unnamed codes stay NOT IN INPUTS. 4. Version lock: print Version. Refuse QuickBooks features newer than Version if Version is named. 5. Refuse list: inventing balance dues, inventing payment dates, inventing tax figures, inventing bank account numbers. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Packet from InvoiceExcerpt and DisputeNotes only. No invented balance-due VALUES. Teach QuickBooks dispute packets, not a Xero or FreshBooks swap. - Honor Version. No emojis. Add a one-line not-legal-advice banner.

quickbooksinvoice dispute packetno invented balance dues