AI Prompt Library - Page 4

You are a Python automation expert. Write a script that organises files in the folder [PATH]: [RULES, e.g. move files into subfolders by type (images, PDFs, documents), rename photos by date taken, delete nothing]. Requirements: a dry-run mode that only prints what would happen, a log of every action, safe handling of duplicate file names, and support for both Windows and Linux paths using pathlib. Explain how to run it and how to schedule it to run automatically on my operating system.

Tip: Always run in dry-run mode first and check the output before letting the script move real files.

Act as a Python developer who scrapes responsibly. I want to collect [DATA, e.g. public product names and prices] from [WEBSITE TYPE] for [PURPOSE, e.g. personal price comparison, research]. First tell me what to check before scraping: the site's terms of use, robots.txt, whether an official API exists, and personal data concerns. Then write a script using requests and BeautifulSoup (or Playwright if the page needs JavaScript) that respects rate limits with delays, sets a clear user agent, handles errors and saves results to CSV. Do not include any method to bypass logins, CAPTCHAs or blocks.

Tip: If the site offers an API or a data export, use that instead. Only collect public data you are allowed to use.

You are an automation engineer. Write a Python script that every morning reads [DATA SOURCE, e.g. a CSV, Google Sheet, MySQL table], calculates [SUMMARY, e.g. yesterday's orders and revenue in PKR], builds a clean HTML email with a small table, and sends it to [RECIPIENTS] using SMTP. Keep email credentials in environment variables or a .env file, not in the code. Include error handling and logging, and explain how to schedule it with cron on Linux or Task Scheduler on Windows.

Tip: For Gmail, use an app password rather than your main password. Send test emails to yourself first.

Act as a bot developer. Build a Telegram bot in [Python or Node.js] for [BUSINESS, e.g. a bakery taking pre-orders, a tuition centre sharing timetables]. Features: /start welcome message, a menu with buttons, answering [COMMON QUESTIONS], collecting an order or enquiry and forwarding it to the owner's chat, and storing enquiries in a simple database. Explain how to create the bot token with BotFather, keep the token secret, run it locally, and host it cheaply. Keep the code well organised and commented.

Tip: Start with the basic features, test with friends, then add more commands one by one.

Act as a hiring manager at a software company in [CITY, e.g. Lahore, Karachi, Islamabad] who reviews junior developer CVs. I want a job as a [ROLE, e.g. MERN developer, Laravel developer, Flutter developer, data analyst]. My current skills: [LIST]. Suggest 5 portfolio projects that would stand out, avoiding overused ones like basic to-do apps or weather apps. For each: the problem it solves, key features, tech stack, what skill it proves to an employer, and an estimated build time. Rank them by impact on my job search.

Tip: Build two or three projects well rather than five badly. Deploy them online and link them in your CV.

You are a product-minded senior developer mentoring me. My project idea: [IDEA]. Tech stack: [STACK]. I can spend [HOURS] per week. Turn this into a plan: a short problem statement, a list of MVP features vs later features, a simple database schema, main screens or pages, a weekly milestone plan, a testing plan, and a deployment plan using free or low-cost hosting. End with how I should present the project on GitHub and in my CV so employers understand its value.

Tip: Keep the MVP small enough to finish in a few weeks. Update the plan with the AI as you progress.

Act as a developer branding coach. Write a GitHub profile README for me. Details: name [NAME], role I want [ROLE], location [CITY, Pakistan] and open to [remote / onsite / freelance], skills [LIST], top 3 projects with one-line descriptions and links [LIST], what I am currently learning [TOPIC], and how to contact me [METHOD]. Keep it professional, short and scannable, in Markdown, with a clean skills section. Avoid clutter like too many badges or animated widgets. Give two versions: minimal and slightly more detailed.

Tip: Create a repository with the same name as your GitHub username and put this in its README.md.

You are an experienced freelance developer who helps others quote fairly. A client wants: [PASTE PROJECT DESCRIPTION]. My skill level: [LEVEL] and my usual rate: [HOURLY RATE IN USD OR PKR]. Break the project into tasks in a table with columns: Task, Details, Estimated hours (low and high), Risk level. Add time for communication, testing, revisions and deployment. Give a total range and suggest how to structure pricing (fixed price with milestones, or hourly). List the questions I must ask the client before sending a quote, and things to exclude clearly from scope.

Tip: Ask the client the listed questions before quoting. Add a buffer to estimates for unclear requirements.

Act as a freelancing coach who knows how buyers on Fiverr search and decide. Write a gig for my service: [SERVICE, e.g. Laravel bug fixing, WordPress website development, Flutter app UI]. My experience: [SUMMARY, only true claims]. Give: 3 gig title options, a gig description under 1,200 characters with clear benefits and what the buyer must provide, three package tiers (Basic, Standard, Premium) with deliverables and delivery time (leave prices as [PRICE] for me to decide), 5 search tags, and 5 FAQs. Do not make promises I cannot keep, such as guaranteed rankings.

Tip: Only list skills and results you can actually deliver. Look at similar gigs to decide your own pricing.

You are a top-rated Upwork freelancer helping me write a proposal. Here is the job post:

[PASTE JOB POST]

My relevant experience and portfolio links: [LIST, only real work]. Write a proposal under 180 words that: opens by addressing the client's specific problem (not with 'Dear Sir'), shows I understood the requirements, briefly suggests my approach, mentions one relevant past project, asks one smart clarifying question, and ends with a clear next step. Keep the tone confident and friendly, not desperate or generic.

Tip: Personalise every proposal. Sending the same generic text to many jobs rarely works.

Act as a business analyst for a small software house. A client wants [PROJECT, e.g. an inventory system for their shop, a booking website for a salon in Rawalpindi]. Their brief: [PASTE BRIEF]. Write a list of clarifying questions grouped by: goals and users, features, content and data, design, integrations (payments, SMS, maps), hosting and maintenance, budget and timeline. Keep questions simple enough for a non-technical client. Then give a one-page requirements summary template I can fill in after the meeting and send back for approval.

Tip: Send the questions before the meeting or use them during a call. Get written approval of the summary before starting.

You are an expert in both [SOURCE LANGUAGE] and [TARGET LANGUAGE]. Convert this code:

[PASTE CODE]

Do not do a word-for-word translation; write idiomatic [TARGET LANGUAGE] using its common libraries and conventions. Keep the same behaviour. After the code, list: differences in behaviour to watch for (integer division, null handling, string encoding, error handling), library equivalents you used, and any part that could not be translated directly.

Tip: Run the same test inputs through both versions to confirm they give identical results.

Act as a friendly coding teacher for students in Pakistan whose first language is Urdu. Explain this error message and how to fix it:

[PASTE ERROR AND CODE]

Use very simple English with short sentences. Where helpful, add the Urdu word in brackets for key ideas (for example variable, loop, condition). Explain: what the error means, why it happened in my code, the fix, and one tip to avoid it in future. Avoid jargon; if you must use a technical term, explain it.

Tip: Useful for beginners and for teachers explaining errors to students. Ask for a fully Urdu explanation if needed.

You are a TypeScript trainer. I know JavaScript well and want to learn TypeScript for [PURPOSE, e.g. React projects, Node.js APIs, job requirements]. Teach me the essentials in a practical order: basic types, interfaces vs type aliases, union types, generics, type narrowing, utility types, and typing API responses. For each, give a before (JavaScript) and after (TypeScript) example. Then convert this JavaScript file of mine to TypeScript and explain each type decision:

[PASTE FILE]

Tip: Turn on strict mode in tsconfig.json from the start; it teaches good habits early.

Act as a university lecturer teaching object-oriented programming. Explain classes, objects, constructors, encapsulation, inheritance, polymorphism, abstraction, interfaces and traits using modern PHP (8 or later). Use one running example throughout, such as a bank account system or an online shop, instead of unrelated examples. For each concept give a short explanation, code, and a common exam or interview question with a model answer. Finish with a small assignment that uses all the concepts together.

Tip: Type the code yourself instead of copying, and run it locally to see the output.

You are a software architect. Here is code that is becoming hard to extend:

[PASTE CODE]

The change I need to make often is: [e.g. adding new payment methods, new notification channels, new report formats]. Suggest which design pattern (for example Strategy, Factory, Observer, Adapter, Repository) fits best and why, and which patterns would be overkill here. Show the refactored code using the pattern in [LANGUAGE], and explain how adding a new variation would work after the change.

Tip: Patterns are tools, not goals. If the AI says the code is fine without one, that is a good answer too.

Act as a clean code reviewer focused only on readability. Review this code:

[PASTE CODE]

Suggest better names for variables, functions and classes, point out long functions or deep nesting, magic numbers, unclear conditions, and inconsistent formatting. Give your suggestions as a table: Current, Suggested, Reason. Then show the improved code with the same behaviour. Do not change logic or add features.

Tip: Use this before submitting assignments or client code. Apply your team's style guide if it differs from the suggestions.

You are an engineering manager. Our [PRODUCT TYPE] codebase has these problems: [LIST, e.g. no tests, outdated framework version, duplicated code, slow deployments, one person understands the billing module]. Team size: [N]. We still need to ship features every [PERIOD]. Create a realistic plan to reduce technical debt without stopping feature work. Include a prioritisation table (Problem, Business risk, Effort, Priority), a quarterly roadmap, how to explain the value to non-technical management, and simple metrics to track progress.

Tip: Share honest details about your team's capacity so the plan is achievable.

Act as a senior PHP consultant. I have a legacy plain PHP application with [DESCRIPTION, e.g. 60 files, mysqli queries mixed with HTML, session-based login, no framework]. It is live and used by [USERS]. Plan a gradual migration to Laravel [VERSION] with no big-bang rewrite. Cover: assessment steps, running old and new code side by side, migrating the database and authentication, which modules to move first, testing strategy, and risks. Give a phased plan with rough effort per phase and a rollback option at each step.

Tip: Share the list of main modules and how users log in. Keep the live app backed up throughout.

You are a MySQL expert and teacher. Explain how indexes work in MySQL (B-tree basics, composite indexes, the leftmost prefix rule, covering indexes) in simple words with an analogy. Then, based on my table and most common queries, recommend which indexes to add or remove:

Table: [PASTE CREATE TABLE]
Common queries: [PASTE 3-5 QUERIES]

Give the exact ALTER TABLE statements and explain how to verify the improvement with EXPLAIN.

Tip: Add indexes during low-traffic hours on large tables, as it can lock or slow the table.

Act as a data analytics trainer. Teach me SQL window functions: ROW_NUMBER, RANK, DENSE_RANK, LAG, LEAD, running totals with SUM OVER, moving averages and PARTITION BY. Use one sample table, [TABLE, e.g. monthly sales per salesperson per city], and give the CREATE and INSERT statements so I can follow along. For each function show a query, its output table, and a real business question it answers. End with 5 practice questions without answers.

Tip: Run the examples in MySQL 8, PostgreSQL or SQLite, which all support window functions.

You are a database administrator. Explain how to back up and restore a [MySQL / PostgreSQL] database of about [SIZE] from the command line. Cover: a full backup command, backing up a single table, compressing the output, restoring to a new database, and moving a database from my local XAMPP setup to a live server. Explain each flag. Include safety tips: testing restores, not typing passwords directly in commands, and checking character sets so Urdu text is not corrupted.

Tip: Practise restoring to a test database before you ever need to do it in an emergency.

Act as a backend security architect. My project: [DESCRIPTION, e.g. a Laravel API used by a Flutter mobile app and a React admin panel]. Explain the difference between session-based authentication and token-based authentication (JWT or opaque tokens) in simple terms. Compare them for my case in a table: security, logout and revocation, mobile support, scalability, complexity. Recommend one approach, explain where to store tokens safely on web and mobile, and list the common mistakes to avoid.

Tip: Mention your framework, as many have built-in solutions such as Laravel Sanctum that are safer than building your own.

You are a backend engineer focused on reliability and abuse prevention for your own services. Explain rate limiting strategies (fixed window, sliding window, token bucket) simply. Then show how to add rate limiting to my [FRAMEWORK, e.g. Express, Laravel, Django REST] API for: login attempts, OTP or SMS sending endpoints, and general API use. Include the code, the right HTTP status and headers to return, and how to handle users behind a shared IP address such as a university network.

Tip: Protect OTP and SMS endpoints first, since abuse there can cost you money quickly.

Act as a QA engineer who tests APIs. Based on these endpoints:

[PASTE ENDPOINT LIST OR OPENAPI SPEC]

Design a Postman test plan. For each endpoint give: test cases (valid request, missing fields, invalid types, unauthorised, not found), the request body, and a Postman test script in JavaScript that checks status code, response time and key fields. Show how to use environment variables for the base URL and token, and how to run the collection from the command line with Newman for CI.

Tip: Use a staging server for tests, never production data. Save the token in an environment variable, not in requests.

You are a web accessibility specialist. Review this HTML and CSS against WCAG guidelines:

[PASTE CODE]

Check: headings order, alt text, form labels, colour contrast, keyboard navigation and focus styles, ARIA use, link text, and language attributes (including pages with mixed English and Urdu text). List each issue in a table with severity, who it affects, and the fix. Then give the corrected code.

Tip: Also test yourself by navigating the page with only the Tab key, and run a Lighthouse accessibility audit.

Act as a Tailwind CSS expert. Convert this component from plain CSS to Tailwind CSS [VERSION]:

[PASTE HTML AND CSS]

Keep the same look on mobile and desktop. Use responsive prefixes, hover and focus states, and dark mode classes if the original has them. Where the class list gets very long, suggest how to extract a reusable component instead of using @apply everywhere. Point out any styles that have no direct Tailwind equivalent and how to handle them.

Tip: Compare both versions side by side in the browser to catch small differences in spacing or colour.

You are a technical SEO engineer who works with Next.js. My site: [DESCRIPTION, e.g. a blog in English and Urdu, a service business site in Multan]. Next.js version and router: [App Router / Pages Router]. Give a technical SEO checklist with code: metadata and Open Graph tags per page, dynamic sitemap and robots file, canonical URLs, structured data (JSON-LD) for my content type, hreflang for multiple languages, image optimisation and page speed. Explain which pages should be static, server rendered or client rendered, and why.

Tip: Check the results with Google Search Console and the Rich Results Test after deploying.

Act as a senior Flutter developer. Show me how to connect my Flutter app to this REST API: [ENDPOINTS AND SAMPLE JSON RESPONSES]. Include: model classes with fromJson and toJson, a service or repository class using http or dio, error handling for no internet and server errors, a loading, success and error state on screen, and storing the auth token securely. Follow a clean folder structure. Explain how to test with a slow network, since many users are on mobile data.

Tip: Paste real sample responses from your API so the model classes match exactly.

You are a mobile release manager. My Flutter app [NAME AND PURPOSE] is ready for its first release on Google Play. Give me a step-by-step checklist: app icon and splash screen, app name and package ID, versioning, signing the release build and keeping the keystore safe, reducing app size, testing a release build on real low-end Android phones, privacy policy and data safety form preparation, store listing text and screenshots, and using internal or closed testing before production. Mark the steps that cannot be changed later.

Tip: Check Google Play's current policies yourself, since requirements change. Back up your keystore in two safe places.

Act as a DevSecOps engineer. My [STACK] project currently has [SITUATION, e.g. API keys hard-coded in files, a .env committed to GitHub, passwords shared on WhatsApp]. Explain the right way to handle secrets across local development, CI, staging and production. Cover: .env files and .gitignore, example env files, CI secrets, a secrets manager option, rotating a key that has leaked, and removing a secret from Git history. Give a step-by-step clean-up plan for my current situation.

Tip: If a key was ever pushed publicly, rotate it first; removing it from history alone is not enough.

You are a site reliability engineer. My [APP/SERVER] had this problem: [SYMPTOM, e.g. site went down at 2am, random 500 errors, very slow checkout]. Here are log excerpts from around that time:

[PASTE LOGS, with IPs and personal data masked]

Analyse them: identify the most likely root cause, the timeline of events, and any warning signs before the failure. Suggest the commands (grep, awk, tail, journalctl) I can use to dig further, a fix, and monitoring or alerts that would catch it earlier next time.

Tip: Include logs from a few minutes before the problem started, not only the errors themselves.

Act as a Linux administrator. I want to run [SCRIPT/COMMAND] on my server [SCHEDULE IN PLAIN WORDS, e.g. every weekday at 9am Pakistan time]. Give the correct crontab line and explain each field. Then explain why cron jobs often work manually but fail in cron (environment variables, PATH, relative paths, permissions, timezone) and how to fix each. Show how to log output and errors to a file and how to check whether the job ran. If I use Laravel, also show the scheduler setup.

Tip: Check the server's timezone with the 'date' command first, as it is often set to UTC.

You are a JavaScript performance expert. My [browser app / Node.js server] uses more and more memory over time: [DETAILS, e.g. tab becomes slow after an hour, server restarts after a day]. Code that might be involved:

[PASTE CODE]

Explain the common causes of memory leaks (forgotten event listeners, timers, closures, growing caches, detached DOM nodes). Show me step by step how to use Chrome DevTools heap snapshots or Node.js inspection tools to find the leak, and point out anything suspicious in my code with a fix.

Tip: Take two or three heap snapshots a few minutes apart and compare them to see what keeps growing.

Act as a backend performance architect. My app: [DESCRIPTION], about [TRAFFIC] requests per day. Slow parts: [LIST, e.g. homepage product list, dashboard stats, search]. Data that changes often: [LIST]. Recommend a caching strategy covering: browser and CDN caching, application caching with Redis or Memcached, database query caching, and cache invalidation. For each slow part, say what to cache, for how long and how to invalidate it. Show code examples in [FRAMEWORK] and warn me where caching could show users stale or wrong data.

Tip: Measure response times before and after, so you know caching actually helped.

You are a supervisor for BS Computer Science and Software Engineering final year projects at a Pakistani university. Our group of [NUMBER] students is interested in [AREAS, e.g. AI, web, mobile, IoT] and has these skills: [LIST]. Suggest 5 original FYP ideas that solve real local problems. For each: problem statement, target users, main modules, tech stack, what makes it more than a basic CRUD app, and risks. Then help us write a one-page proposal for our favourite idea with objectives, scope and a timeline across [NUMBER] months. The work itself must be ours.

Tip: Discuss the ideas with your real supervisor before finalising, and check your department's proposal format.

Act as a browser extension developer. Build a Chrome extension using Manifest V3 that [FEATURE, e.g. saves highlighted text to a notes list, shows a word count of the page, blocks distracting sites during study hours]. Give the full file structure and code: manifest.json, popup HTML/CSS/JS, content script and background service worker if needed, and storage handling. Request only the minimum permissions and explain why each is needed. Explain how to load it unpacked for testing.

Tip: Load it through chrome://extensions with Developer mode on. Ask for extra features one at a time.

You are a senior developer finishing a freelance project and handing it to the client and any future developer. Based on these project details: [STACK, HOSTING, MAIN FEATURES, THIRD-PARTY SERVICES, FOLDER STRUCTURE], write a handover document covering: system overview, how to run it locally, deployment steps, where credentials are stored (without real values), backups, common admin tasks for a non-technical client, known limitations, and a maintenance checklist. Use clear headings and simple language for the client sections.

Tip: Share credentials with the client separately through a secure method, never inside the document.

Act as a QA lead. The feature is: [DESCRIBE, e.g. checkout with cash on delivery and discount codes, student registration form, file upload]. Write a test plan with test cases in a table: ID, Scenario, Steps, Test data, Expected result, Priority. Include happy paths, edge cases (empty fields, very long inputs, Urdu or special characters, slow internet, double clicks, expired sessions), negative cases and basic security checks. Mark which cases should be automated and which are better tested manually.

Tip: Share any business rules (limits, discounts, roles) so the AI can create realistic test data.

You are a Linux system administrator. I get 'Permission denied' when [ACTION, e.g. my Laravel app writes to storage, Nginx serves files, I run a script]. Output of ls -la for the relevant folder: [PASTE]. The process runs as user: [USER, if known]. Explain how Linux permissions and ownership work (read, write, execute, user, group, others) in simple words. Then give the correct, least-privilege fix for my case, and explain why using chmod 777 is a bad idea.

Tip: Avoid chmod 777 even if an online answer suggests it; it opens security holes on your server.

You are an experienced recruiter who screens hundreds of CVs a week. I will paste my current CV and a job advertisement. Rewrite my CV so it matches this role without inventing anything. Keep my real experience, but reorder sections, sharpen bullet points and use the keywords from the ad where they honestly apply. Each bullet should start with a strong action verb and show a result where possible. Keep it to [1 or 2] pages. After the rewrite, give me a short list of any requirements in the ad that my CV does not show, so I can decide whether to add them or address them in my cover letter.

Job ad:
[PASTE JOB AD]

My CV:
[PASTE CV]

Tip: Paste the full job ad, not just the title. If the gap list shows something you actually have, tell the AI and ask it to add it in.

Act as a CV coach. Below is a list of my job duties written the way most people write them ("responsible for..."). Convert each one into an achievement-focused CV bullet using the format: action verb + what I did + measurable result or impact. If I have not given a number, do not make one up; instead write the bullet with a placeholder like [X%] or [number of clients] and tell me what figure I should find. Give me two versions of each bullet: one short (under 15 words) and one detailed (under 30 words).

My role: [JOB TITLE] at [COMPANY TYPE]
Duties:
[PASTE DUTIES]

Tip: List duties one per line. Afterwards, fill in the placeholders with real figures from your records or ask your manager for them.

I am a fresh graduate in Pakistan with a [DEGREE, e.g. BS Computer Science] from [UNIVERSITY], graduating in [YEAR]. I have no formal job experience. Build me a one-page CV that highlights what I do have: final year project, internships (if any), university societies, volunteer work, freelance or tutoring work, certifications and skills. Ask me up to 8 questions first to collect the details you need. Then produce the CV in plain text with these sections: Contact, Profile (3 lines), Education, Projects, Experience/Activities, Skills, Certifications. Keep the tone confident but honest, and avoid buzzwords like "hardworking" and "team player" unless backed by an example.

Tip: Answer the AI's questions in detail, including small things like tutoring or running a society page. Paste the result into a clean Word or Google Docs template.

Write 3 different professional summaries for the top of my CV. Each should be 3-4 lines (maximum 60 words) and written without "I". Version 1: formal and corporate. Version 2: results-focused with numbers. Version 3: suited to a career changer or someone returning to work. Base them only on the details below and avoid clichés like "dynamic", "passionate" and "results-driven". End each summary with the kind of role I am targeting.

Target role: [JOB TITLE]
Years of experience: [NUMBER]
Key skills: [SKILLS]
Best achievements: [2-3 ACHIEVEMENTS]
Industry: [INDUSTRY]

Tip: Pick the version closest to your target role and edit a few words so it sounds like you. Change it slightly for each application.

Act as an Applicant Tracking System (ATS) specialist. Review my CV text below against the job description. Give me:
1. A table of the top 15 keywords and skills from the job description, showing whether each appears in my CV (Yes/No/Partly).
2. Formatting problems that often confuse ATS software (tables, columns, headers, graphics, unusual section names, dates format).
3. Suggested section headings using standard names.
4. Five specific edits that would improve my match, without keyword stuffing or adding skills I do not have.

Job description:
[PASTE JD]

CV text:
[PASTE CV AS PLAIN TEXT]

Tip: Copy your CV as plain text from the file; if the text comes out jumbled, that itself is a sign the ATS may struggle with it.

Pretend you are a hiring manager for a [JOB TITLE] role at a [COMPANY SIZE/TYPE] in [CITY/COUNTRY]. You have 30 seconds to scan my CV. Tell me honestly:
- Your first impression in 2 sentences
- Whether you would shortlist me, and why
- The 3 weakest parts of the CV
- Anything that looks like a red flag (gaps, job hopping, vague claims, spelling)
- A prioritised list of 7 fixes, from most to least important
Be direct and specific. Quote the exact lines you would change and show the improved version.

My CV:
[PASTE CV]

Tip: Run it once, make the fixes, then run it again with the new version to see if the verdict changes.

I have a gap in my employment from [MONTH YEAR] to [MONTH YEAR] because of [REASON, e.g. caring for a parent, health, preparing for CSS, relocating, layoffs]. Help me handle it honestly. Give me:
1. A one-line entry I can put on my CV for this period, if appropriate.
2. A 2-sentence mention for my cover letter.
3. A 30-second spoken answer for when an interviewer asks "What were you doing during this time?"
Keep all three truthful, calm and forward-looking, without over-explaining or sharing private details I do not need to share. Mention any skills or activities from that period: [COURSES, FREELANCE, VOLUNTEERING, NONE].

Tip: Practise the spoken answer out loud until it sounds natural. Never invent a job to cover a gap.

I have a CV in the typical Pakistani format (with photo, father's name, CNIC, date of birth, religion, marital status, and a long objective). I want to apply for jobs in the UK. Convert it into a UK-style CV: remove personal details that UK employers do not expect, replace the objective with a short profile, use reverse chronological order, express education in terms a UK employer understands (e.g. explain FSc/Intermediate and my degree briefly), and keep it to 2 pages. List every change you made and why, in a short table at the end.

My CV:
[PASTE CV]

Tip: Check whether your degree needs an equivalence statement from the relevant body and add it yourself. You can repeat this for Canada or Australia by changing the country.

I am applying for [JOB TITLE] roles in [UAE/Saudi Arabia/Qatar/Oman/Kuwait/Bahrain] from Pakistan. Reformat my CV for Gulf recruiters. Include a short profile, key skills box near the top, relevant GCC or international experience first, certifications, and a personal details section with only what Gulf employers commonly ask for (nationality, visa status, notice period, availability to relocate, driving licence if relevant). Tell me which details I should confirm locally because practices vary by employer. Keep the CV to 2 pages and provide a list of 10 keywords recruiters in this field in the Gulf would search for.

My CV:
[PASTE CV]

Tip: Fill in your visa status and notice period accurately. Only list licences and certifications you actually hold.

Write a cover letter for the job below. Structure: 1) opening line that names the role and gives one specific reason I am interested in this company, 2) a paragraph linking my two strongest achievements to the job's main requirements, 3) a short paragraph on how I would add value in the first months, 4) a confident closing with a call to action. Keep it under 300 words, plain and human, no clichés like "I am writing to express my interest". Do not claim anything that is not in my background.

Company: [COMPANY NAME]
What I know about them: [PRODUCT, NEWS, VALUES]
Job ad: [PASTE AD]
My background: [PASTE CV OR KEY POINTS]

Tip: Spend five minutes on the company website first so you can give a real reason for your interest. Read the letter aloud and remove anything that does not sound like you.

Many jobs in Pakistan ask candidates to email their CV to an HR address. Write a short application email (under 120 words) for the role of [JOB TITLE] advertised on [WHERE: Rozee.pk, LinkedIn, newspaper, company website]. Include a clear subject line with the job title and reference number [REF NO IF ANY], a 3-sentence body that states my most relevant qualification and experience, mention of the attached CV, and a polite sign-off with my phone number. Give me 2 versions: one formal, one slightly warmer. Also list 3 mistakes to avoid when sending CVs by email (e.g. file names).

My key points: [DEGREE, YEARS OF EXPERIENCE, TOP SKILL]

Tip: Name your file clearly, like Firstname-Lastname-CV.pdf, and send from a professional email address.

I am moving from [CURRENT FIELD] to [NEW FIELD]. Write a cover letter for the role of [TARGET JOB] that tackles the career change head on. Explain the reason for the change in one or two honest sentences, then show transferable skills with concrete examples from my past work, then mention what I have done to prepare (courses, projects, freelance work: [LIST]). Keep it under 280 words. Avoid sounding apologetic. After the letter, suggest 3 transferable skills I may be underselling based on my background.

My background: [SUMMARY]
Job ad: [PASTE AD]

Tip: Add a link to one small project in the new field if you have it; it does more than any sentence can.

Act as a LinkedIn profile strategist. Using my details below, write:
1. Five headline options (max 220 characters each) that include my target role, key skills and value, not just my current job title.
2. An About section of 180-250 words written in the first person, with a hook in the first two lines (these show before "see more"), my story, key achievements, skills, and a closing line inviting people to connect or message me.
3. A list of 10 skills I should add to the Skills section, ordered by importance for recruiters in my field.

Target role: [ROLE]
Current role: [ROLE]
Industry: [INDUSTRY]
Location: [CITY, e.g. Lahore/Karachi/Islamabad or remote]
Achievements: [LIST]

Tip: Pin the headline you like best and test it for two weeks; check whether profile views from recruiters go up.

Rewrite the Experience entries of my LinkedIn profile. For each role, give a 1-line description of the company or team, then 3-5 bullet points focused on achievements and skills, using keywords a recruiter searching for [TARGET ROLE] would use. LinkedIn is less formal than a CV, so the tone can be slightly conversational but still professional. Keep each role under 120 words. Flag any entries that are too thin and ask me what to add.

My experience:
[PASTE EACH ROLE WITH DATES AND DUTIES]

Tip: Update one role at a time and keep LinkedIn consistent with your CV dates and titles.

I want to connect with recruiters and hiring managers in [INDUSTRY] in [CITY/COUNTRY]. Write 5 LinkedIn connection request notes (under 300 characters each) for different situations: 1) a recruiter at a company I want to join, 2) a hiring manager who posted a job, 3) an alumnus of [MY UNIVERSITY] working at the company, 4) someone whose post I found useful, 5) a person I met at an event [EVENT NAME]. Each note should be polite, specific, not pushy, and must not ask for a job directly in the first message.

Tip: Personalise each note with one real detail about the person before sending. Send a small number of good requests daily rather than a flood.

I am a [ROLE, e.g. junior data analyst] in Pakistan and want to build visibility on LinkedIn to attract job offers. Create a 4-week posting plan with 2 posts per week. For each post give: the topic, the post type (lesson learned, project breakdown, tip list, opinion, question), a strong first line, and 3-4 bullet points of what to cover. Topics should draw on my real work: [PROJECTS, TOOLS, SKILLS]. Avoid humble-bragging and motivational clichés. Then write the first post in full (under 200 words) as an example.

Tip: Write the remaining posts in your own words using the outline, and reply to comments on your posts within a few hours.

Act as a career coach. I am looking for a [TARGET ROLE] job in [CITY/REMOTE/ABROAD]. I can spend [HOURS] hours a day on the search. Create a 30-day plan split into weeks, covering: fixing my CV and LinkedIn, building a target list of companies, applying through job portals, networking and referrals, direct outreach, skill gaps, and interview practice. Give daily tasks in a table with columns: Day, Task, Time needed, Output (e.g. "5 tailored applications sent"). Include a simple weekly review checklist. Keep it realistic for someone who may also be studying or working.

My situation: [FRESH GRADUATE / EMPLOYED / UNEMPLOYED], [FIELD]

Tip: Copy the table into a spreadsheet and tick off tasks. At the end of each week, paste your results back and ask the AI to adjust next week.

Help me build a target company list for my job search. I want to work as a [ROLE] in [CITY OR COUNTRY]. Suggest categories of employers I should consider (e.g. multinationals, local conglomerates, startups, NGOs, government bodies, banks, software houses, BPOs) and for each category explain what they usually look for and how they tend to hire. Then give me a template table with columns: Company, Category, Why I fit, Contact person, Where they post jobs, Date applied, Status. Do not list company names as facts about current hiring; I will research and fill those in myself.

Tip: Use Perplexity or a job portal to fill real company names into the table, then aim for a mix of categories.

Analyse the job advertisement below as an experienced recruiter. Tell me:
1. The 3-5 must-have requirements versus the nice-to-haves.
2. What the job will really involve day to day, in plain language.
3. Any hints about company culture, workload or seniority hidden in the wording.
4. Possible red flags (vague pay, unrealistic requirements, signs of a scam such as asking for fees).
5. Questions I should ask in the interview.
6. How well I match, given my background, as a score out of 10 with reasons.

Job ad: [PASTE AD]
My background: [SHORT SUMMARY]

Tip: Use this before spending time on a tailored application. Be wary of any job that asks you to pay a fee to apply or to get a visa.

I received this job offer or message: [PASTE MESSAGE OR DESCRIBE OFFER]. Act as a careful HR professional and help me judge whether it could be a scam. Check for common warning signs: requests for money (registration, training, medical or visa fees), pressure to decide quickly, a salary far above normal for the role, poor grammar, generic email addresses, interviews only over chat, requests for CNIC or bank details early on, and overseas offers without a clear employer. Give me a verdict (likely genuine / unclear / likely scam), the reasons, and a list of steps to verify the employer myself.

Tip: Never pay money or share your CNIC, bank or JazzCash/Easypaisa details until you have verified the employer independently.