AI Prompts Library

Turn my messy week notes into a status report my {MANAGER / CLIENT / TEAM} will actually read.
Report cadence: {WEEKLY / BIWEEKLY}. Their priority right now: {WHAT THEY CARE ABOUT MOST}.
Format:
1. HEADLINE: one sentence — the week's most important truth (progress or problem, whichever is
bigger). Managers often read only this; make it carry the week.
2. SHIPPED/DONE: 3–5 items max, outcome-phrased ("Launched X — early signups: 43") not
activity-phrased ("worked on X"). Group small stuff as one line.
3. IN PROGRESS: what's moving, each with a % or next milestone + date. No vague "ongoing".
4. BLOCKED/NEEDS DECISION: the section that makes reports valuable — each blocker with: what's
stuck, who/what unblocks it, and the specific ask ("Need your yes/no on X by Thursday or the
timeline slips a week"). Never bury an ask in prose.
4. NEXT WEEK: top 3 priorities, so misalignment surfaces NOW instead of next Friday.
Rules: under 200 words total, no adjectives doing the work of numbers, bad news stated plainly in the first half — buried bad news destroys trust when found.
MY NOTES: {PASTE}

Build my 30-60-90 day plan. New role: {TITLE} at {COMPANY TYPE/SIZE}. What I know about their
situation: {ANY CONTEXT — why they hired, team state, known problems}. What success looks like per my manager (if known): {PASTE OR SKIP}.
Structure:
DAYS 1–30 — LEARN: the 10 questions to answer about how things really work (decision-making,
unwritten rules, who influences what); the 5 relationships to build first and what to ask each
person; the map of current processes BEFORE suggesting changes. Include the classic trap to avoid: proposing fixes before earning context.
DAYS 31–60 — CONTRIBUTE: pick my early win — criteria: visible, achievable solo or with light
help, matters to my manager, low political risk. Give 3 candidate types for my role. Start owning routine responsibilities fully.
DAYS 61–90 — LEAD: propose one improvement backed by what I observed (not what worked at my last job); take on something nobody owns; set 6-month goals with my manager.
Finish with: the 5 questions to ask my manager in week 1, and a simple weekly self-check (3
questions).

Rewrite my project description for my {PORTFOLIO / GITHUB README / CV}. Reviewers spend 30 seconds — make them count.
MY PROJECT (rough description): {WHAT IT IS, WHAT IT DOES, TECH USED, ANYTHING HARD ABOUT IT}
Produce:
1. ONE-LINER: what it does + for whom + the impressive bit, in under 20 words. No "simple" or
"basic" — never undersell in the first line.
2. FULL DESCRIPTION (100–140 words): the problem it solves → the interesting decision or trade-off
I made (this signals seniority more than any tech list) → one concrete challenge and how I solved it → outcome (users, performance, or what I learned that changed how I build).
3. TECH LIST: ordered by relevance to the jobs I want ({TARGET ROLE}), not alphabetically.
4. THE QUESTION IT PLANTS: a good project description makes interviewers ask about it. What
question does mine invite, and my 60-second answer.
Rule: specifics beat adjectives. "Handles 10k concurrent users" beats "highly scalable".

Decode this job posting for me. Read it like a skeptical insider, not an applicant.
1. THE REAL JOB: ignoring the wishlist, what will this person spend 80% of their time doing? (The first 3 responsibilities and any repeated theme reveal it.)
2. THE REAL REQUIREMENTS: which listed requirements are hard gates vs. nice-to-haves I can apply without? (Rule of thumb: the top 3 + anything repeated = real.)
3. RED FLAGS: translate the euphemisms — "fast-paced environment", "wear many hats", "like a
family", salary missing, 15 responsibilities for a junior title. Rate overall risk: low medium / high.
4. WHAT THEY'RE STRUGGLING WITH: job ads are complaints in disguise. What problem forced them to open this role?
5. MY ANGLE: given the decoded reality, the 2 things my application should emphasize.
6. INTERVIEW QUESTIONS: 4 sharp questions I should ask THEM, each designed to verify a specific suspicion from above.
JOB POSTING: {PASTE}

Help me explain a gap in my career without apologizing for it. The gap: {WHEN + HOW LONG}. What actually happened: {HONEST REASON — burnout, caregiving, failed business, health, travel, job hunting}. What I did during it (even small things): {ANYTHING — courses, freelance, volunteering, recovery, parenting}. 
Deliver:
1. CV LINE: one honest, neutral line for the CV (e.g. "Career break — family caregiving; completed X during this time"). No euphemisms that invite suspicion.
2. INTERVIEW ANSWER (60 seconds): structure = brief factual reason → what I learned or did → pivot to why I'm ready and motivated NOW. Confident tone; no oversharing, no defensiveness, ends looking forward.
3. THE FOLLOW-UP TRAP: the probing question an interviewer might ask next, and my calm answer.
4. REFRAME CHECK: rewrite anything in my story that sounds like an apology into a statement of
fact.
Rule: never lie, never invent activities — dishonesty in interviews compounds.

You are a LinkedIn ghostwriter for professionals. Rewrite my profile to attract recruiters for
{TARGET ROLE} positions.
Deliver:
1. HEADLINE (max 220 chars): not just a job title — value + specialty + keyword. Give 3 options:
professional, bold, and keyword-heavy.
2. ABOUT section (max 2,000 chars): first 2 lines must hook (they show before "see more").
Structure: hook -> what I do and for whom -> 3 proof points from my background -> personality line -> call to action. Write in first person, no buzzwords ("passionate", "results-driven" are banned).
3. EXPERIENCE bullets: rewrite the 3 roles I paste, max 4 bullets each, achievement-first.
MY CURRENT PROFILE / CV:
{PASTE}

PROMPT TEXT:
Act as the hiring manager for a {JOB TITLE} position at a {COMPANY TYPE, e.g. mid-size SaaS
company}. Based on my CV below:
1. Write the 12 questions you would most likely ask me — mix of behavioral, technical, and "explain
this gap/choice on your CV" questions specific to MY history.
2. For each, draft a strong 60–90 second answer using ONLY facts from my CV, structured as STAR
(Situation, Task, Action, Result). Where my CV lacks a needed detail, insert {FILL: what happened?} so I know what to add.
3. Finish with the 3 questions I should ask THEM, tailored to this role.
MY CV:
{PASTE CV}

ROLE: You are an expert CV writer and document designer specializing in tech internship applications in Europe (especially Germany). Produce a single-page, ATS-friendly, recruiter-optimized CV in .docx format following the exact specifications below.

🎯 OUTPUT REQUIREMENTS

Format: Single .docx file (A4 paper size, 210 × 297 mm)
Length: Strictly ONE page
Font: Calibri throughout
Margins: Narrow — approximately 1.5 cm top/bottom, 1.6 cm left/right
Language: English (unless told otherwise)
Tone: Professional, confident, achievement-focused, no fluff


🎨 VISUAL DESIGN SPECIFICATION
Color palette (use exactly these hex codes):

Primary accent (NAVY): #1F3A5F — used for name, section headings, company names, links, bullet markers
Body text (DARK): #1A1A1A
Meta/secondary text (GREY): #555555 — used for dates, locations, subtitles

Header layout (centered):

Full name in large NAVY bold caps with wide letter-spacing (~20pt size)
Title line in DARK text directly below — format: [Target Role] | [Degree Program]
Contact line in small GREY text: City, Country • Phone • email@example.com (email in NAVY, underlined)
Links line in small NAVY underlined: github.com/username • portfolio-site.com • other-link.com
A solid NAVY horizontal rule (1.5pt thick) underneath the header to separate it from the body

Section headings:

ALL CAPS, NAVY color, bold, ~11pt with extra letter-spacing
A thin NAVY underline rule beneath each heading
Sections in this exact order: Summary → Professional Experience → Selected Projects → Education → Technical Skills → Languages & Training

Role/job header style (within each section):

Line 1: **Job Title**  •  [Company in NAVY]                              [Dates in italic GREY, right-aligned]
Line 2 (optional subtitle): One italic GREY sentence describing the company/context
Bullets follow

Bullets:

Use a small NAVY square bullet ▪
Each bullet starts with a bold action verb (Developing, Built, Engineered, Implemented, Trained, etc.)
Keep tight line spacing (1.15–1.25) and minimal vertical gap between bullets

Skills section:

Use a 2-column label/value format (not bullets)
Left column: bold NAVY category labels (e.g., "Languages", "ML / Data")
Right column: comma-separated values, with • separators between sub-groups


🧱 STRUCTURE (in this exact order)

Header block (name, title, contact, links, rule)
Summary paragraph — 4–5 lines justified text, no heading needed (or use "PROFESSIONAL SUMMARY"). Mention: current academic status, key skills, current role/highlight, side projects, and what role you're seeking + when.
PROFESSIONAL EXPERIENCE — 1–3 roles, 2–4 bullets each, strongest verbs first
SELECTED PROJECTS — 2–4 projects, 2 bullets each, link the live URL
EDUCATION — Degree, university, dates, focus areas, relevant coursework
TECHNICAL SKILLS — 4–6 rows in label/value format
LANGUAGES & TRAINING — Languages with proficiency levels + certifications combined


✍️ WRITING RULES

Strong action verbs only — start each bullet with: Developing, Engineering, Built, Implemented, Designed, Trained, Founded, Launched, Modeled, Iterating, Documented, etc.
Quantify when possible — but never invent numbers
Be specific with tools — e.g., "Python pipeline with Trimesh and scikit-learn" not "ML pipeline"
Bold key technologies inline within bullets (e.g., **Python**, **scikit-learn**)
No clichés — avoid "passionate", "team player", "go-getter", "results-driven"
No personal pronouns — start with verbs, not "I"
Keep bullets ≤ 2 lines when printed
Dates format: MM/YYYY – MM/YYYY or MM/YYYY – Present


🚫 DO NOT

Add photos, age, marital status, or nationality (unless explicitly required by the user)
Use icons unless requested
Use multiple fonts or decorative graphics
Exceed one page
Include references or "References available upon request"
Use light grey text that won't print well
Use tables with visible borders for the skills section (use invisible alignment)  

<<< YOUR INFO >>>

FULL NAME: [Your full name]
TARGET ROLE: [e.g., "Machine Learning & Data Science Student"]
DEGREE LINE: [e.g., "B.Sc. Information Technology"]
LOCATION: [City, Country]
PHONE: [+xx xxx xxx xxx]
EMAIL: [your.email@example.com]
LINKS: [github.com/yourhandle, portfolio-url.com, etc.]

SUMMARY GOAL:
- Current status: [e.g., "4th-semester B.Sc. student at your universtiy name"]
- Strongest credential: [e.g., "Currently developing ML pipelines for a Fraunhofer-spin-off MedTech project"]
- Notable projects: [e.g., "project name"]
- Target role + start date: [e.g., "Seeking ML/Data Science internship starting Winter Semester 2026/27"]

PROFESSIONAL EXPERIENCE:
[For each role, provide:]
- Job Title:
- Company:
- Dates:
- Location:
- Company subtitle (one line):
- 3–4 achievement bullets (what you did, what tools, what impact):

PROJECTS:
[For each project, provide:]
- Project name:
- Role/type (e.g., "Solo Project", "Founder"):
- URL:
- Dates:
- 2 bullets describing what you built and the tech stack:

EDUCATION:
- Degree:
- Institution:
- Dates + current semester:
- Focus areas:
- Relevant coursework:

TECHNICAL SKILLS (group into 4–6 categories):
- Languages: [e.g., Python, Java, SQL]
- ML / Data:
- 3D / Web:
- Tools:
- (Add or rename categories as needed)

LANGUAGES:
- [Language] ([Level], [Description]) — e.g., English (B2, Full Professional)
- [Language] ([Level]) ...

TRAINING / CERTIFICATES:
- [Certificate name] — [Institution] ([Dates]); [optional notes]

<<< END OF YOUR INFO >>>