Linkedln POSTs:

———LINKEDIN———

You are writing a LinkedIn post for a professional Fintec Payment / POS audience.

Context:

• Target audience: Payment, Fintech, POS Architects
• Publication style or reference tone: Analysis
• Goal of the piece: eplain
• Tone constraints: Linkedln

1. Write a post that sounds credible, specific, and human.
2. Express gratitude without generic thank-you filler.
3. Include a useful reflection, lesson, or signal about what comes next.
4. Avoid inflated self-congratulation, jargon, or vague celebration language.
5. Provide hook options with distinct tones, such as reflective, factual, or forward-looking.
6. Apply the writing and reasoning rules from:
   • anti-ai-writing-style.md
   • anti_sycophancy_prompt.md
   • writing-style-for-ai-topics.md
   • linkedin_rules.md If the files conflict, prioritize them in this order:
   1. Technical correctness and anti-sycophancy
   2. Preserving my original message
   3. Natural, human-sounding writing style
   4. LinkedIn formatting and readability

Output format:

• Final LinkedIn post

Quality bar:

• Specific over vague.
• Professional but human.
• Make the post feel like a real update, not corporate filler.
• Always add professional & reader-proff references, check /POS-ARCHITECTURE-BOOK.

here is the draft:

You are writing a LinkedIn post for a professional Fintec Payment / POS audience.

Context:

• Target audience: Payment, Fintech, POS Architects
• Publication style or reference tone: Analysis
• Goal of the piece: eplain
• Tone constraints: Linkedln

1. Write a post that sounds credible, specific, and human.
2. Express gratitude without generic thank-you filler.
3. Include a useful reflection, lesson, or signal about what comes next.
4. Avoid inflated self-congratulation, jargon, or vague celebration language.
5. Provide hook options with distinct tones, such as reflective, factual, or forward-looking.
6. Apply the writing and reasoning rules from:
   • anti-ai-writing-style.md
   • anti_sycophancy_prompt.md
   • writing-style-for-ai-topics.md
   • linkedin_rules.md If the files conflict, prioritize them in this order:
   1. Technical correctness and anti-sycophancy
   2. Preserving my original message
   3. Natural, human-sounding writing style
   4. LinkedIn formatting and readability

Output format:

• 3 hook options
• Final LinkedIn post
• 2 CTA or closing variants
• Short note on which version to use when

Missing information policy: Ask up to 2 concise questions only if the milestone itself is unclear. Otherwise proceed with assumptions.

Quality bar:

• Specific over vague.
• Professional but human.
• Make the post feel like a real update, not corporate filler.
• Always add professional & reader-proff references, check /POS-ARCHITECTURE-BOOK.

here is the draft:

You are a strong LinkedIn writer.

Turn one core idea into a short LinkedIn post series.

Context:

• Core idea or lesson: [idea]
• Audience: [audience]
• Personal, company, or role context: [context]
• Desired tone: [tone]
• CTA or discussion goal: [cta]

Instructions:

1. Create 5 posts that feel related but not repetitive.
2. Give each post a distinct angle such as story, lesson, example, opinion, or practical takeaway.
3. Keep the tone professional and readable.
4. Avoid cliches, empty inspiration, and exaggerated wins.
5. Offer hook options for each post.

Output format:

• Series strategy
• Post 1 to Post 5 with hook options

Missing information policy: Ask up to 2 concise questions only if the core idea or audience is unclear.

Quality bar:

• Distinct post angles.
• Useful content, not filler.
• Native-to-platform tone.

——— WRITE ———

You are writing a LinkedIn post for a professional audience.

Write a milestone post using the context below.

Context:

• Milestone: [milestone]
• Why it matters: [importance]
• Who deserves credit: [credit]
• Brand or founder voice: [voice]
• Desired CTA or close: [cta]
• Anything to avoid saying: [constraints]

Instructions:

1. Write a post that sounds credible, specific, and human.
2. Express gratitude without generic thank-you filler.
3. Include a useful reflection, lesson, or signal about what comes next.
4. Avoid inflated self-congratulation, jargon, or vague celebration language.
5. Provide hook options with distinct tones, such as reflective, factual, or forward-looking.
6. Apply the writing and reasoning rules from:
   • anti-ai-writing-style.md
   • anti_sycophancy_prompt.md
   • writing-style-for-ai-topics.md
   • linkedin_rules.md If the files conflict, prioritize them in this order:
   1. Technical correctness and anti-sycophancy
   2. Preserving my original message
   3. Natural, human-sounding writing style
   4. LinkedIn formatting and readability

Output format:

• 3 hook options
• Final LinkedIn post
• 2 CTA or closing variants
• Short note on which version to use when

Missing information policy: Ask up to 2 concise questions only if the milestone itself is unclear. Otherwise proceed with assumptions.

Quality bar:

• Specific over vague.
• Professional but human.
• Make the post feel like a real update, not corporate filler.

—–> example

You are writing a LinkedIn post for a professional audience.

Write a milestone post using the context below.

Context:

• Milestone: New CorebaseIT post live — “What a Fraud-Detection Paper Gets Right (and Wrong) About Payment System Design” — a payments/POS read of Almazroi & Ayub’s 2023 IEEE Access fraud paper
• Why it matters: Most fraud pitches lead with accuracy. The useful part of that literature (and of vendor claims) is the constraint list — imbalance, cost asymmetry, sequences, drift, latency — plus knowing which metrics to discard. Aimed at POS architects and fintech risk engineers who evaluate models and vendors for a living
• Who deserves credit: [optional — leave blank, or name a reviewer / colleague who pushed back on the metric claims; skip if solo]
• Brand or founder voice: Vincent Bevia / CorebaseIT — dry, operational, skeptical of headline metrics; POS architect writing for practitioners, not hype
• Desired CTA or close: Link to the full post in the first comment; invite debate on one concrete question — e.g. “If a vendor leads with accuracy, what’s the first follow-up question you ask?”
• Anything to avoid saying: Don’t claim the paper is “debunked” or that deep learning “never works”; don’t pitch CorebaseIT as a fraud product; don’t overstate production fraud rates; don’t lead with “98% accuracy is fake” as clickbait; no “thrilled to announce” / “game-changing” language

Instructions:

1. Write a post that sounds credible, specific, and human.
2. Express gratitude without generic thank-you filler.
3. Include a useful reflection, lesson, or signal about what comes next.
4. Avoid inflated self-congratulation, jargon, or vague celebration language.
5. Provide hook options with distinct tones, such as reflective, factual, or forward-looking.

Output format:

• 3 hook options
• Final LinkedIn post
• 2 CTA or closing variants
• Short note on which version to use when

Missing information policy: Ask up to 2 concise questions only if the milestone itself is unclear. Otherwise proceed with assumptions.

Quality bar:

• Specific over vague.
• Professional but human.
• Make the post feel like a real update, not corporate filler.

Output should go to folder: 30july_thrusday

For Communications

Act as a Senior Staff Communications Systems Engineer with deep expertise in digital communications, DSP, MATLAB, C/C++, FPGA, ASIC, DSP processors, and hardware/software system design.

Review the raw content below and turn it into a polished LinkedIn post.

Your tasks:

1. Proofread the content for grammar, spelling, syntax, clarity, and flow.
2. Verify the technical accuracy and credibility of the claims.
3. Preserve the original idea, message, and tone as much as possible.
4. Apply the writing and reasoning rules from:
   • anti-ai-writing-style.md
   • anti_sycophancy_prompt.md
   • writing-style-for-ai-topics.md
   • linkedin_rules.md If the files conflict, prioritize them in this order:
   1. Technical correctness and anti-sycophancy
   2. Preserving my original message
   3. Natural, human-sounding writing style
   4. LinkedIn formatting and readability
5. Avoid making the post sound generic, overly polished, promotional, or obviously AI-written.
6. Add credible references only where they genuinely support the main claims.
7. If references are useful, place them in a short “References / further reading” section or suggest them for the first comment.
8. Keep the final post natural, professional, concise, and suitable for LinkedIn.
9. Format the final post so I can save it in the /ready_to_post folder.
10. Blog URLs in the first comment must use https://corebaseit.com/corebaseit_posts/slug/ — not /posts/ (404 on the live site).

Before writing the final version, briefly list:

• Claims that need verification.
• Wording that sounds too generic or AI-like.
• References that should be added, if any. [PASTE RAW CONTENT HERE]

For POS - Payments

one of my favorites:

Act as a seasoned technical writer with deep expertise in POS, EMV, PCI, fintech, and network architecture.

Review the raw content below and turn it into a polished LinkedIn post.

Your tasks:

1. Proofread the content for grammar, spelling, syntax, clarity, and flow.
2. Verify the technical accuracy and credibility of the claims.
3. Preserve the original idea, message, and tone as much as possible.
4. Apply the writing and reasoning rules from:
   • anti-ai-writing-style.md
   • anti_sycophancy_prompt.md
   • writing-style-for-ai-topics.md
   • linkedin_rules.md If the files conflict, prioritize them in this order:
   1. Technical correctness and anti-sycophancy
   2. Preserving my original message
   3. Natural, human-sounding writing style
   4. LinkedIn formatting and readability
5. Avoid making the post sound generic, overly polished, promotional, or obviously AI-written.
6. Add credible references only where they genuinely support the main claims.
7. If references are useful, place them in a short “References / further reading” section or suggest them for the first comment.
8. Keep the final post natural, professional, concise, and suitable for LinkedIn.
9. Format the final post so I can save it in the /ready_to_post folder.
10. Blog URLs in the first comment must use https://corebaseit.com/corebaseit_posts/slug/ — not /posts/ (404 on the live site).

Before writing the final version, briefly list:

• Claims that need verification.
• Wording that sounds too generic or AI-like.
• References that should be added, if any. [PASTE RAW CONTENT HERE]

for AI

Act as a seasoned technical and AI Engineer editor with strong expertise in AI, Data Analysis, LLMs, Agentic AI, reasoning models, and logical analysis.

Review the raw content below and turn it into a polished LinkedIn post.

Your tasks:

1. Proofread the content for grammar, spelling, syntax, clarity, and flow.
2. Verify the technical accuracy and credibility of the claims.
3. Preserve the original idea, message, and tone as much as possible.
4. Apply the writing and reasoning rules from:
   • anti-ai-writing-style.md
   • linkedin_rules.md
   • anti_sycophancy_prompt.md
   • writing-style-for-ai-topics.md If the files conflict, prioritize them in this order:
   1. Technical correctness and anti-sycophancy
   2. Preserving my original message
   3. Natural, human-sounding writing style
   4. LinkedIn formatting and readability
5. Avoid making the post sound generic, overly polished, promotional, or obviously AI-written.
6. Add credible references only where they genuinely support the main claims.
7. If references are useful, place them in a short “References / further reading” section or suggest them for the first comment.
8. Keep the final post natural, professional, concise, and suitable for LinkedIn.
9. Format the final post so I can save it in the /ready_to_post folder.
10. Blog URLs in the first comment must use https://corebaseit.com/corebaseit_posts/slug/ — not /posts/ (404 on the live site).

Before writing the final version, briefly list:

• Claims that need verification.
• Wording that sounds too generic or AI-like.
• References that should be added, if any.

Raw content: [PASTE RAW CONTENT HERE]

Hybrid –> For POS - Payments & AI

one of my favorites:

Act as a seasoned technical writer with deep expertise in POS, EMV, PCI, fintech, AI, Data Analysis, LLMs, Agentic AI, reasoning models, and logical analysis.

Review the raw content below and turn it into a polished LinkedIn post.

Your tasks:

1. Proofread the content for grammar, spelling, syntax, clarity, and flow.
2. Verify the technical accuracy and credibility of the claims.
3. Preserve the original idea, message, and tone as much as possible.
4. Apply the writing and reasoning rules from:
   • anti-ai-writing-style.md
   • anti_sycophancy_prompt.md
   • writing-style-for-ai-topics.md
   • linkedin_rules.md If the files conflict, prioritize them in this order:
   1. Technical correctness and anti-sycophancy
   2. Preserving my original message
   3. Natural, human-sounding writing style
   4. LinkedIn formatting and readability
5. Avoid making the post sound generic, overly polished, promotional, or obviously AI-written.
6. Add credible references only where they genuinely support the main claims.
7. If references are useful, place them in a short “References / further reading” section or suggest them for the first comment.
8. Keep the final post natural, professional, concise, and suitable for LinkedIn.
9. Format the final post so I can save it in the /ready_to_post folder.
10. Blog URLs in the first comment must use https://corebaseit.com/corebaseit_posts/slug/ — not /posts/ (404 on the live site).

Before writing the final version, briefly list:

• Claims that need verification.
• Wording that sounds too generic or AI-like.
• References that should be added, if any. [PASTE RAW CONTENT HERE]

Act as a seasoned technical writer with deep expertise in AI, Software Engineering, social skills, human behaviour and Network Architecture with an eye for detail and clarity, thoroughly proofread the authenticity and correctness of the content, add references to provide validity, correct any grammatical, syntactical, or typographical errors. Please utilize the anti-ai-writing-style.md, anti_sycophancy_prompt.md. and rules linkedln_rules, to write a POST for Linkedln here in the raw content:

Act as a seasoned technical writer with deep expertise in AI, Software Engineering, social skills, human behaviour, and Network Architecture, with an eye for detail and clarity. Let’s find references, analyze them, and write a nice LinkedIn post on the following theme. Please utilize the anti-ai-writing-style.md and anti_sycophancy_prompt.md and rules linkedln_rules. Here is the theme I want to focus on:

example -> ARQC, TC, and AAC are EMV cryptogram types

For notebooklm:

Act as a seasoned technical writer with deep expertise in AI, Software Engineering, social skills, human behaviour, and Network Architecture with an eye for detail and clarity, please write a nice post on the information we have here. Please utilize the anti-ai-writing-style.md and anti_sycophancy_prompt.md file from references. Include references and also the notes…

here in the raw content:

General - Overall

Act as an experienced technical writer and editor with deep expertise in AI, software engineering, network architecture, social skills, and human behaviour.

I already have a draft post. Your task is to turn it into a polished post that sounds like me: my tone, my flow, my style, and my way of explaining technical ideas.

Please do the following:

1. Review the draft for factual accuracy.
2. Identify claims that need verification, nuance, or stronger support.
3. Correct anything that is inaccurate, exaggerated, unclear, or misleading.
4. Add credible references where they strengthen the post.
5. Preserve my original intent, but rewrite the text so it feels authentic to my voice.
6. Improve grammar, syntax, punctuation, spelling, and readability.
7. Apply the writing and reasoning rules from:
   • anti-ai-writing-style.md
   • anti_sycophancy_prompt.md
   • writing-style-for-ai-topics.md
   • linkedin_rules.md If the files conflict, prioritize them in this order:
   1. Technical correctness and anti-sycophancy
   2. Preserving my original message
   3. Natural, human-sounding writing style
   4. LinkedIn formatting and readability
8. Avoid generic AI-writing patterns, corporate filler, exaggerated claims, and repetitive sentence structures.
9. Keep the tone technical, thoughtful, practical, direct, and human.
10. Make the final output ready to publish as a LinkedIn post.

Important:

• Do not simply polish the text.
• Challenge weak claims.
• Flag anything that cannot be verified.
• Prefer precise language over broad statements.
• Where a claim is uncertain, rewrite it with appropriate nuance.
• Keep the final post in my voice, not in a generic editorial voice.

Here is the draft post:

Act as a seasoned technical writer and editor with deep expertise in AI, software engineering, network architecture, social skills, and human behaviour.

Transform the next Corebaseit POST into a polished Linkedln post without lossing context, as it will be used as references.

Requirements:

• Correct grammar, syntax, punctuation, spelling, and typos.
• Improve clarity, structure, flow, and readability.
• Preserve my original meaning, technical intent, and voice.
• Apply the writing and reasoning rules from:
  • anti-ai-writing-style.md
  • anti_sycophancy_prompt.md
  • writing-style-for-ai-topics.md
  • linkedin_rules.md If the files conflict, prioritize them in this order:
  1. Technical correctness and anti-sycophancy
  2. Preserving my original message
  3. Natural, human-sounding writing style
  4. LinkedIn formatting and readability
• Avoid generic AI-writing patterns, corporate filler, exaggerated claims, and repetitive sentence structures.
• Keep the tone technical, thoughtful, practical, and human.
• Add or refine headings where helpful.
• Save the final Markdown file under /future_considering_posting.

Corebaseit content:

Act as a seasoned technical writer and editor with deep expertise in AI, software engineering, network architecture, social skills, and human behaviour.

Transform the raw content below into a polished Linkedln post.

Requirements:

• Correct grammar, syntax, punctuation, spelling, and typos.
• Improve clarity, structure, flow, and readability.
• Preserve my original meaning, technical intent, and voice.
• Apply the writing and reasoning rules from:
  • anti-ai-writing-style.md
  • anti_sycophancy_prompt.md
  • writing-style-for-ai-topics.md
  • linkedin_rules.md If the files conflict, prioritize them in this order:
  1. Technical correctness and anti-sycophancy
  2. Preserving my original message
  3. Natural, human-sounding writing style
  4. LinkedIn formatting and readability
• Avoid generic AI-writing patterns, corporate filler, exaggerated claims, and repetitive sentence structures.
• Keep the tone technical, thoughtful, practical, and human.
• Add or refine headings where helpful.
• Save the final Markdown file under /future_considering_posting.

Raw content:

[PASTE RAW CONTENT HERE]

-----