Kopyala, yapıştır, işini bitir

Transform the person in the photo I uploaded into a vertical poster illustration. Keep their facial features, skin tone, hair and apparent age exactly as they are. The person must stay recognizable.

SCENE: A fictional coastal city inspired by Florida, at sunset. Sky graduating from deep purple to orange and pink. Palm trees, art deco hotels, pink and blue neon signage, yachts in a marina, a helicopter passing low in the distance. Neon reflections on wet asphalt.

SUBJECT: Turned three quarters toward the camera, slight low angle, relaxed and confident stance. Wearing [OUTFIT: e.g. a light linen jacket over a white t-shirt]. Leaning against a sports car parked in the foreground.

LIGHTING: Warm sunset light rimming one side of the face, pink neon fill from the opposite side. High contrast, cinematic.

STYLE: Saturated digital illustration, bold outlines, subtle canvas texture, game cover composition. Leave empty space at the top and bottom for text, with a soft vignette along the bottom edge.

TECHNICAL: Vertical 3:4 aspect ratio, poster quality, sharp detail, 4K.

RULES: Do not alter, beautify, slim down or replace the face. Do not add any real brand logo, game logo, brand name or readable text. No extra fingers, no malformed hands.

CITY: [ENTER CITY OR COUNTRY HERE]

Create a premium vertical travel-art illustration representing the location above.

First, determine the most visually iconic and immediately recognizable landmarks, architecture, transportation, landscape and cultural visual elements associated with this location.

Then compose them into ONE cohesive handcrafted layered paper-cut cityscape.

The image must look like a sophisticated physical papercut diorama made from 6-10 stacked sheets of colored paper.

STYLE:
high-end editorial papercut illustration,
layered cut paper,
stacked paper sheets,
physical paper thickness,
visible cut edges,
subtle contact shadows,
handcrafted paper texture,
vintage travel poster,
premium tourism editorial artwork,
graphic but dimensional,
clean geometric silhouettes,
rich architectural detail.

The artwork should NOT look like:
a photograph,
digital painting,
ordinary flat vector art,
CGI,
3D software rendering,
plastic,
clay,
origami,
cartoon,
anime,
isometric illustration,
or a generic AI cityscape.

Create genuine physical depth through overlapping paper layers, cut-outs, recessed elements and soft shadows.

COMPOSITION:

4:5 vertical poster.

At the top, place the location name in large uppercase letters:

"[CITY]"

Use widely spaced elegant sans-serif lettering.
The letters themselves should appear slightly raised from the paper background.
Subtle shadows underneath the letters.

Below the title, construct a detailed panoramic miniature of the location.

Use 3-6 highly recognizable local landmarks.
Do not simply place landmarks next to each other.
Integrate them naturally into the same landscape.

Include appropriate local elements such as:
architecture,
bridges,
waterfront,
roads,
public transportation,
trees,
plants,
hills,
mountains,
coastal elements,
historic buildings,
modern skyline,
local neighborhoods.

Only use elements that make geographical sense for this location.

Create three strong depth layers:

BACKGROUND:
warm ivory paper sky,
distant skyline,
mountains or landscape silhouettes when appropriate.

MIDDLE GROUND:
major city architecture and iconic landmarks.

FOREGROUND:
dark botanical shapes,
roads,
bridges,
water,
transportation or architectural details.

Use overlapping paper pieces to create strong depth.

COLOR SYSTEM:

warm ivory background,
deep navy,
dark teal,
muted blue,
dusty turquoise,
sage green,
terracotta,
muted coral,
mustard yellow,
sand.

Use a limited cohesive palette.
Avoid neon colors.
Avoid pure white.
Avoid excessive saturation.

LIGHT:
soft directional studio light,
subtle shadows between every major paper layer,
natural paper depth,
no dramatic photographic lighting.

MATERIAL:
matte colored paper,
slightly fibrous handmade paper,
clean precision-cut edges,
tiny handmade imperfections,
subtle variations in paper texture.

The final image should resemble an expensive handcrafted collectible travel poster photographed in a studio.

IMPORTANT:
The city must be instantly recognizable from its landmarks and visual identity.

Do not invent fictional landmarks.
Do not duplicate the same building.
Do not create random skyscrapers unless they genuinely belong to the location.

TEXT RULE:
The ONLY written text in the image is the city name.
No additional words, numbers, logos, signs or captions.

OUTPUT:
4:5 vertical composition.
Centered balanced composition.
Premium editorial travel-poster aesthetic.
Extremely detailed layered paper craftsmanship.

Place a title into the empty space at the top of the poster image I uploaded, without disturbing the existing composition.

TEXT TO RENDER: [YOUR NAME]
SECOND LINE, SMALLER: [CITY or TAGLINE]

TYPOGRAPHY: Very heavy, tightly spaced, geometric block letters. Slight three dimensional extrusion with a thin white outline. Colour: cream white with a warm orange drop shadow.

PLACEMENT: Top centre, inside safe margins, never bleeding off the edges. The letters must not cover the person's face.

RULES: Render only the text I provided, nothing else. Reproduce Turkish characters exactly as written, including ç ğ ı İ ö ş ü. Do not imitate the logo, wordmark or typeface of any real brand.

Create a miniature diorama sitting on a desk.

SUBJECT: [PROFESSION or BRAND: e.g. a coffee shop, a software team, a dental clinic] modelled as a tiny scale set.

DETAILS: Include five small objects that describe that line of work: [OBJECT 1], [OBJECT 2], [OBJECT 3]. Human figures should read as 2 cm miniatures, posed naturally while working.

STYLE: Soft clay and resin texture, tilt shift macro photography feel, shallow depth of field, background gently blurred. Warm neutral palette, pastel tones.

LIGHTING: Soft window light from the side, long and soft shadows.

TECHNICAL: Square 1:1 aspect ratio, macro lens look, high detail.

RULES: Do not add text, logos, brand names or any readable lettering.

Present the person in the photo I uploaded as a collectible action figure in blister packaging. Keep the facial features so the figure stays recognizable.

PACKAGING: Cardboard backing panel with a clear moulded plastic bubble. The figure stands upright inside. Three accessories sit in small side compartments: [ACCESSORY 1], [ACCESSORY 2], [ACCESSORY 3].

FIGURE: Slightly stylised plastic toy texture, visible articulation joints, matte surface, natural pose.

BACKING PANEL: Flat [COLOUR] background with simple geometric shapes. Leave an empty banner strip across the top.

STYLE: Product photography. Studio lighting, soft reflections, neutral grey backdrop, gentle contact shadow.

TECHNICAL: Vertical 3:4 aspect ratio, sharp detail.

RULES: Do not imitate the logo, typeface or packaging design of any real toy brand. Do not put readable text on the box.

Produce a professional portrait from the photo I uploaded. Keep the face, skin tone, apparent age, body weight and hair exactly as they are. Do not beautify, slim or smooth the skin. Only fix the lighting and the background.

FRAMING: Chest up, camera at eye level, slight three quarter angle. Eyes to camera. A calm, trustworthy expression with a faint smile.

WARDROBE: [OUTFIT: e.g. navy blazer over a white shirt]. Wrinkles pressed out, collar sitting straight.

LIGHTING: Soft key light from upper left, gentle fill from the opposite side, subtle rim light behind. Small catchlights in the eyes.

BACKGROUND: Neutral grey or a softly blurred office. The subject must separate cleanly from it.

TECHNICAL: Square 1:1 aspect ratio, 85mm portrait lens look, shallow depth of field, natural skin texture preserved.

RULES: Do not change the face. Do not add text, logos or watermarks.

Turn the product photo I uploaded into a professional studio shot. Keep the product's shape, colour, texture, label and proportions exactly as they are. Do not change any wording or detail printed on the product.

SET: [SURFACE: e.g. a light beige micro textured surface]. Background in the same tone, fading slightly lighter toward the top.

LIGHTING: Large soft box from the upper left, white bounce card opposite. A soft contact shadow under the product. Controlled reflections on glossy surfaces.

COMPOSITION: Product centred, equal breathing room top and bottom. Optionally place [PROP] beside it, never overlapping the product.

TECHNICAL: Square 1:1 aspect ratio, commercial product photography quality, tack sharp focus, accurate colour.

RULES: Do not rewrite or invent packaging copy. Do not add new logos, price tags or badges.

Create a single key visual for an advertising campaign.

BRAND: [BRAND]. Industry: [INDUSTRY]. Emotion to convey: [EMOTION: e.g. trust, speed, relief].

SCENE: [WHO] [WHERE] [DOING WHAT]. The story must land in one glance, so a viewer senses what the brand promises without reading anything.

LIGHTING: [LIGHT: e.g. low sunrise side light], cinematic contrast, subtle film grain.

COLOUR PALETTE: [THREE COLOURS]. Do not stray outside these three.

COMPOSITION: Leave the right third empty for copy. Place the main subject on the left third.

TECHNICAL: Horizontal 16:9 aspect ratio, 35mm lens look, advertising photography quality.

RULES: Do not render text, logos or watermarks in the image. Copy will be added later.

Create a sticker set from the person in the photo I uploaded. Keep the facial features and hair recognizable.

SET: Six expressions in this order: laughing, surprised, thumbs up, thinking, clapping, winking.

STYLE: Clean vector cartoon, bold outer outline, flat colours, no shading. Exaggerated but friendly proportions, large eyes.

LAYOUT: Each expression in its own cell with equal spacing, all on a white background. Three columns by two rows.

TECHNICAL: Square 1:1 aspect ratio, clean edges, white cut margin around each sticker.

RULES: Do not add text, emoji, logos or watermarks.

You are an experienced SEO content editor. Write a 1,500 word blog post about "[TOPIC]", targeting the keyword "[TARGET KEYWORD]".

OUTPUT LANGUAGE: Turkish. Use correct Turkish spelling and diacritics throughout.

Rules:
Place the keyword in the title and within the first 100 words.
Use H2 and H3 subheadings.
Give a concrete example in every section.
End with a four question FAQ block.
Tone: knowledgeable but warm, short sentences.
Avoid filler transitions. Phrases such as "sonuc olarak", "gunumuz dunyasinda", "bu baglamda" are banned.

Deliver: a 155 character meta description, then the full article.

You are an SEO strategist. Build a topic cluster plan for "[MAIN TOPIC]", aimed at [TARGET AUDIENCE] searching in Turkish.

OUTPUT LANGUAGE: Turkish. Keywords must be written the way Turkish users actually type them.

Deliver:
1. One pillar page: title, target keyword, and the six subtopics it will cover.
2. Twelve supporting articles. For each: title, target keyword, search intent (informational, comparison, transactional), estimated difficulty (low, medium, high) and a one sentence angle.
3. An internal linking map: which article links to which, and with what anchor text.
4. Publishing order: which four articles should ship first and why.

Never assign the same keyword to two articles. Present it as a table.

Rewrite the text below so it reads as if a person wrote it, while keeping the meaning and the facts intact.

TEXT:
[TEXT]

OUTPUT LANGUAGE: Turkish, matching the language of the source text.

Rules:
Vary sentence length. Never place three long sentences in a row.
Remove formulaic connectors: sonuc olarak, dolayisiyla, ote yandan, bu baglamda, kisacasi.
Stop stacking adjectives. At most one adjective per sentence.
Replace abstract claims with concrete examples.
Drop in a short sentence now and then. Address the reader directly now and then.
Do not add exaggerated claims, do not alter any data, do not invent new facts.

Deliver only the rewritten text. Do not list your changes.

Write a frequently asked questions block for a web page.

Page topic: [TOPIC]
Audience: [AUDIENCE]
Already covered on the page: [EXISTING HEADINGS]

OUTPUT LANGUAGE: Turkish.

Deliver:
1. Six questions, each phrased the way people actually type them into Google, none repeating what the page already answers.
2. Each answer 40 to 60 words, opening with a direct response in the first sentence.
3. No pricing, no guarantees, no promises of a certain outcome.
4. The same questions as FAQPage JSON-LD, minified onto a single line.

Output the visible FAQ text first, then the code block.

You are an SEO editor. Write search result copy for the page below.

Page topic: [TOPIC]
Target keyword: [KEYWORD]
Brand: [BRAND]
The page's core promise: [PROMISE]

OUTPUT LANGUAGE: Turkish.

Deliver:
Five title options, each 50 to 60 characters, keyword near the front.
Five meta descriptions, each 150 to 160 characters, ending with a clear call to action.
Print the character count under every option.
No hype, no all caps shouting. Use numbers and concrete benefits.

Finish with one sentence explaining which pair you would pick and why.

You are a content strategist. Run a gap analysis on the data below.

Our pages: [YOUR TITLES]
Competitor 1 pages: [TITLES]
Competitor 2 pages: [TITLES]
Industry: [INDUSTRY]

OUTPUT LANGUAGE: Turkish.

Deliver:
1. Topics competitors cover that we do not, grouped by search intent.
2. Topics we cover but handle weakly, and exactly what is missing.
3. Five topics nobody covers that the audience is clearly asking about.
4. For each idea, an estimated value (high, medium, low) with the reasoning.

Do not estimate traffic or rankings you cannot derive from the data I gave you. Where you are unsure, say so plainly.

You are a content editor. Break the article below into assets for different channels.

ARTICLE:
[ARTICLE TEXT]

OUTPUT LANGUAGE: Turkish.

Produce:
1. A LinkedIn post, 180 words, with a hook in the first two lines.
2. An Instagram carousel outline, eight slides, at most 20 words per slide.
3. A six post thread for X.
4. A newsletter intro, 120 words, leading to the full article.
5. A Reels script, 45 seconds, with hook, body and close.

Every asset must rest on facts actually present in the article. Do not invent claims. Do not copy sentences verbatim; rewrite for each channel.

You are a social media strategist. Build a two week Instagram content calendar for "[BRAND or INDUSTRY]".

Target audience: [TARGET AUDIENCE]

OUTPUT LANGUAGE: Turkish, including hooks, captions and hashtags.

For each day give: content format (Reels, carousel, story), topic headline, a three second opening hook, a caption draft (two to three sentences plus a call to action) and five hashtags.

Mix: 40 percent educational value, 30 percent engagement (question or poll), 20 percent social proof, 10 percent selling.

Present it as a table.

You are a short form video writer. Write a 30 to 45 second Reels script about "[TOPIC]".

Audience: [AUDIENCE]. Brand: [BRAND]. Goal: [SAVES, SHARES or CLICKS].

OUTPUT LANGUAGE: Turkish for all spoken lines and on screen text.

Format as a table: time range, what is on screen, what is said, on screen caption.

Rules:
The first two seconds must stop the scroll. Give three alternative hooks.
Spoken lines must sound like everyday speech. Keep sentences short.
On screen captions: six words maximum.
Close with a clear call to action and a line that loops back to the opening.
Also add six hashtags and two cover text options.

Write a LinkedIn post.

Who I am: [ROLE and INDUSTRY]
What I want to share: [EXPERIENCE, FINDING or MISTAKE]
What the reader should take away: [LESSON]

OUTPUT LANGUAGE: Turkish.

Rules:
The first line stands alone and creates curiosity. Leave the second line blank.
Total 150 to 220 words. Paragraphs of at most two lines.
Include a concrete number or a concrete incident. No generic advice.
Do not boast, do not sell. End with a single answerable question.
No emoji. No hashtags.

Also give three alternative opening lines.

Draft an Instagram carousel.

Topic: [TOPIC]. Audience: [AUDIENCE]. Goal: [GOAL].

OUTPUT LANGUAGE: Turkish.

Produce ten slides. For each slide give:
Slide number
Headline, six words maximum
Body copy, 25 words maximum
Visual note: what to illustrate or which photo to place

Structure: slide 1 hook, slide 2 sharpen the problem, slides 3 to 8 the solution steps, slide 9 summary, slide 10 call to action.

Also write the caption, 120 words, plus eight hashtags. Invent nothing; leave anything you cannot verify in square brackets.

You are a YouTube scriptwriter. Write an 8 to 10 minute video script about "[VIDEO TOPIC]".

Channel audience: [TARGET AUDIENCE]

OUTPUT LANGUAGE: Turkish.

Structure: a curiosity hook in the first 15 seconds (give three alternatives), the promise of the intro, three to five main sections (each with a concrete example or demo suggestion), transition lines between sections, a natural moment for the subscribe reminder, and a closing bridge to the next video.

Also deliver: five video title options (50 to 60 characters, curiosity plus benefit) and a draft description.

You are a community manager. Build a reply kit for comments arriving on the [BRAND] account.

Brand tone: [TONE: e.g. warm, plain, unpretentious]
Recurring themes: [THEME 1], [THEME 2], [THEME 3]

OUTPUT LANGUAGE: Turkish.

Produce:
1. Five short replies to positive comments, each worded differently so they do not read as copy paste.
2. Three replies to people asking about price: move the conversation to DM without quoting a figure.
3. Three replies to complaints: acknowledge the problem first, then offer a concrete next step. Never get defensive.
4. Two calm replies to irrelevant or provocative comments.
5. Three rules for when not to reply at all.

Every reply at most two sentences. Promise nothing, guarantee nothing.

You write openings for short videos and social posts. Topic: [TOPIC]. Audience: [AUDIENCE].

OUTPUT LANGUAGE: Turkish.

Produce 20 opening lines, split across these patterns:
Four that invert the expectation
Four built on fear of missing out
Four built on a concrete number
Four phrased as a question
Four framed as a personal confession or mistake

Rules:
Twelve words maximum per line.
Do not invent statistics. If a number is needed, leave it in square brackets.
No exaggerated promises, no clickbait.

Finish by naming the three most likely to hold this audience, with your reasoning.

You are a conversion focused ecommerce copywriter. Write a product page description for: [PRODUCT NAME and THREE FEATURES].

OUTPUT LANGUAGE: Turkish.

Structure:
1. Name the customer's problem in one sentence.
2. Position the product as the answer.
3. Five bullet benefits, each translating a feature into what it does for the buyer.
4. A social proof line.
5. A risk reducer (returns or warranty) and a call to action.

Tone: reassuring, never hyped. 150 to 200 words. Work the product name in naturally twice so the page ranks.

Do not invent reviews, figures or awards. If I have not supplied one, leave that sentence in square brackets.

You are a B2B sales specialist. Write a three email cold outreach sequence selling [SERVICE or PRODUCT] to [TARGET COMPANY TYPE] companies.

OUTPUT LANGUAGE: Turkish.

Email 1: A personalised opening referencing something concrete about the company, a one sentence value proposition, and a micro call to action (not a 15 minute meeting, more like a quick question). 90 words maximum.
Email 2, three days later: A comparable customer example with a number.
Email 3, seven days later: A polite close that leaves the door open.

Give three subject lines per email, 45 characters maximum, no clickbait.

Do not invent the case study. If I have not given you a real one, leave a placeholder in square brackets.

You are a direct response copywriter. Write a long form sales page for [PRODUCT or SERVICE].

Audience: [AUDIENCE]. Price range: [PRICE]. Main objection: [OBJECTION]. Difference from competitors: [DIFFERENCE].

OUTPUT LANGUAGE: Turkish.

Sections:
1. Headline and subheadline. Give five headline alternatives.
2. Problem section, in the audience's own words.
3. Solution section: how the product works, in three steps.
4. Benefit list: six items, written as outcomes rather than features.
5. Who it suits and who it does not.
6. Social proof placement (placeholder).
7. Price presentation and what is included.
8. Objection handling: five objections with answers.
9. FAQ: six questions.
10. Close and call to action.

Rules: no fake reviews, no invented figures, no discount that does not exist, no guarantee you cannot back. Where you lack data, leave square brackets.

You are a sales coach. Build an objection handling script for selling [PRODUCT or SERVICE].

Audience: [AUDIENCE]. Average price: [PRICE]. Competitors: [COMPETITORS].

OUTPUT LANGUAGE: Turkish.

For every objection produce:
What the customer actually means
One clarifying question to ask
A two sentence response
The next question that moves the conversation forward

Objections: too expensive, let me think about it, a competitor is cheaper, I already have one, I am not sure it will work, I am not the decision maker, I will get back to you.

No pressure, no fear tactics, no manufactured urgency. Keep the answers honest and short.

Write a WhatsApp message sequence for a business that sells over chat.

Business: [BUSINESS]. Product: [PRODUCT]. Audience: [AUDIENCE]. Tone: [TONE].

OUTPUT LANGUAGE: Turkish.

Produce:
1. A greeting for someone arriving from an ad: two sentences, asking what they need.
2. Four qualifying questions, written to be asked one at a time.
3. A product pitch message: short, bulleted, 60 words maximum.
4. The reply to give when someone asks the price.
5. A follow up 24 hours after silence.
6. A final follow up three days later.
7. A thank you and delivery details message after the order.

Every message must fit on one phone screen. It must not read like a bot. No shouting in capitals, no strings of exclamation marks.

You are a performance marketer. Write [PLATFORM: Meta, Google, LinkedIn] ad copy for [PRODUCT or SERVICE].

Audience: [AUDIENCE]. Core benefit: [BENEFIT]. Price: [PRICE]. Restricted topic: [IF ANY].

OUTPUT LANGUAGE: Turkish.

Produce five angles, and for each angle three headlines and two primary texts.

Angles: problem led, outcome led, comparison, story, objection breaking.

Rules:
Headlines 40 characters maximum, primary texts 125 words maximum.
No unverifiable figures, no fake testimonials, no discount that does not exist.
If the category is health, finance or legal, never promise a guaranteed result.

Finish by naming the three variants to launch the test with, and why.

Draft a service proposal.

Client: [CLIENT and INDUSTRY]. Need: [NEED]. My solution: [SOLUTION]. Timeline: [TIMELINE]. Budget range: [BUDGET].

OUTPUT LANGUAGE: Turkish.

Sections:
1. Situation summary: restate what the client told you in your own words, proving you understood.
2. Goal: what will be different when the project ends, stated measurably.
3. Scope: what will be done, itemised.
4. Out of scope: what will not be done, itemised.
5. Timeline: phases and delivery dates.
6. Investment: price and payment schedule.
7. What we need from you and what you can expect from us.
8. Next step: one clear action.

Tone: professional, unadorned. Do not guarantee outcomes; commit to measurement and reporting instead.

Turn the meeting notes below into a clean output.

NOTES:
[RAW NOTES]

OUTPUT LANGUAGE: Turkish.

Produce:
1. A one paragraph summary, 80 words maximum.
2. A list of decisions made.
3. An action table: task, owner, due date, dependency.
4. Open questions and who needs to answer them.
5. A proposed agenda for the next meeting.

Rules: never invent a name, a date or a decision that is not in the notes. If an owner is unclear, write "belirsiz". If no date was given, leave it blank and list the missing details at the end.

Draft a reply to the email below.

INCOMING EMAIL:
[EMAIL TEXT]

My situation: [WHAT HAPPENED, WHAT I CAN DO, WHAT I CANNOT DO]
Relationship: [CUSTOMER, MANAGER, SUPPLIER, COLLEAGUE]

OUTPUT LANGUAGE: Turkish.

Produce three versions:
1. Short and formal
2. Warm and explanatory
3. Boundary setting but relationship preserving, for when I need to say no

Each version 120 words maximum, with a subject line. Do not promise anything I did not say I could do, do not invent dates. Finish with one sentence recommending a version and why.

You are a spreadsheet expert. Write the formula that does the following.

Program: [EXCEL or GOOGLE SHEETS]
Data layout: [WHAT IS IN WHICH COLUMN, e.g. column A dates, column B product, column C amount]
Desired result: [WHAT TO CALCULATE]
Edge cases: [BLANK CELLS, ERRORS, DUPLICATE ROWS and so on]

OUTPUT LANGUAGE: Turkish for all explanations.

Deliver:
1. The complete formula, ready to copy.
2. A piece by piece explanation of what it does.
3. The most common mistake with it and how to check for it.
4. A simpler alternative, if one exists.

If I am on a Turkish language Excel, also give the Turkish function names.

Draft a presentation.

Topic: [TOPIC]. Audience: [WHO]. Length: [MINUTES]. What I want them to do afterwards: [ACTION].

OUTPUT LANGUAGE: Turkish.

Produce ten slides. For each slide:
Slide title
At most three bullets to appear on the slide
Speaker notes, 60 to 80 words
A visual suggestion

Flow: situation, problem, cost of the problem, solution, how it works, evidence, objections, plan, cost, next step.

Never put a paragraph on a slide. If a figure is needed, ask me for the source rather than inventing one.

You are a process consultant. Review the repetitive work in my business and find the automation opportunities.

Business: [BUSINESS and INDUSTRY]. Team: [HOW MANY PEOPLE, WHICH ROLES].
Daily and weekly tasks: [LIST THE TASKS]
Tools we use: [TOOLS]

OUTPUT LANGUAGE: Turkish.

Deliver a table: task name, hours per week, how much of it can be automated, with which tool, setup difficulty (low, medium, high), and the risk.

Then:
1. The three tasks to tackle in the first three months, and why those.
2. Tasks that should not be automated, and why.
3. For every proposal, where human review must stay in the loop.

Base your time estimates on the information I gave you. Where it is missing, ask.

You are an experienced startup advisor. Analyse this business idea without mercy: [BUSINESS IDEA].

OUTPUT LANGUAGE: Turkish.

In order:
1. Target customer, and whether this truly solves a burning problem.
2. Market size estimate, using TAM, SAM and SOM logic, specific to Turkey.
3. The three strongest competitors and their weak points.
4. Revenue model alternatives.
5. A plan to test this within 30 days on a zero budget, concrete down to a landing page and ten customer interviews.
6. Why this idea might fail: the three most likely reasons.

Do not paint a rosy picture. State the weaknesses plainly.

You are a productivity coach. Help me plan this week.

To do list: [LIST]
Fixed appointments: [MEETINGS and TIMES]
Weekly working hours: [HOURS]
Must be finished this week: [ONE TO THREE ITEMS]
Hours when my energy is highest: [TIME RANGE]

OUTPUT LANGUAGE: Turkish.

Deliver:
1. Group the tasks by impact and urgency, with a time estimate on each.
2. A day by day plan, placing deep work blocks in my high energy hours.
3. Calculate whether the total exceeds my working hours, and if it does, tell me what to cut.
4. Three things I should say no to this week.
5. Three check in questions to ask myself on Friday.

Be realistic. Do not pack the day wall to wall; leave gaps.

You are a senior recruiter. Rewrite my CV against the job posting I am applying to.

CURRENT CV:
[CV TEXT]

JOB POSTING:
[POSTING TEXT]

OUTPUT LANGUAGE: Turkish, unless the posting itself is in English, in which case match the posting.

Do this:
1. A three line summary at the top: who I am, what I do, what I bring.
2. At most four bullets per role, each starting with an action verb and containing an outcome.
3. Weave in keywords from the posting, but only where they genuinely match work I actually did.
4. Flag every place a number is missing and tell me which figure to go find.
5. Finish with the three weakest points of my CV against this posting and how to strengthen them.

Rules: never write work I did not do, never inflate a title, never invent a number. No decorative adjectives.

Write a cover letter for a job application.

Who I am: [EXPERIENCE SUMMARY]
The posting: [POSTING TEXT]
Something concrete I know about the company: [COMPANY NOTE]
My strongest piece of evidence: [PROJECT or RESULT]

OUTPUT LANGUAGE: Turkish, unless the posting is in English.

Structure:
Paragraph 1: why this company, anchored to a concrete detail. No generic praise.
Paragraph 2: the most critical need in the posting, and my matching evidence.
Paragraph 3: a second piece of evidence and how I work.
Paragraph 4: a short close asking for an interview.

250 words maximum. No boilerplate phrases. Do not boast; tell the story instead. If I have no evidence, do not fabricate one; ask me what to add.

Run a mock interview with me. Stay in role and never ask the next question before I have answered.

Position: [POSITION]. Company type: [COMPANY]. My level: [JUNIOR, MID, SENIOR].
CV summary: [SUMMARY]

OUTPUT LANGUAGE: Turkish.

Rules:
Ask one question at a time and wait for my answer.
After each answer, tell me what I did well, what I left out, and what a stronger version of my answer would sound like.
Ask eight questions in total: two introductory, three technical, two behavioural, one hard question (salary expectation or an employment gap).
Score my answers against the STAR structure.

At the end: a score out of ten, my strongest and weakest area, and the three topics to study before the real interview.

Ask the first question now.

Overhaul my LinkedIn profile.

Current headline: [HEADLINE]
About section: [TEXT]
Experience: [ROLES]
My goal: [FIND A JOB, FIND CLIENTS, BUILD A REPUTATION]
Who I want to find me: [AUDIENCE]

OUTPUT LANGUAGE: Turkish.

Deliver:
1. Five headline options, 220 characters maximum, making clear what I do and who it helps.
2. An About section: a hook in the first two lines, four paragraphs total, closing with an invitation to get in touch.
3. Three outcome focused bullets per role.
4. Fifteen keywords to be findable for, and where to place each one.
5. Five profile sections that are missing and should be added.

No hype, no invented titles. If I have not given you a number, leave a placeholder.

Help me prepare for a salary conversation.

Position: [POSITION]. Experience: [YEARS]. City: [CITY]. Current salary: [AMOUNT]. Target: [AMOUNT].
What I delivered in the last 12 months: [CONCRETE WORK and RESULTS]

OUTPUT LANGUAGE: Turkish.

Deliver:
1. A value file: six bullets translating my work into the employer's language.
2. My opening line: how to state the number, one paragraph.
3. Range strategy: which number to name, and what my walk away floor should be.
4. Six likely pushbacks with a response to each: no budget, let us see performance first, the company is struggling, everyone here earns the same, you lack seniority, let us talk later.
5. Five things worth asking for beyond salary.
6. A closing line and a follow up email draft.

Do not invent market salary data. Work from what I gave you and ask if something is missing.

You are an instructional designer. Build a [DURATION] week learning plan for "[TOPIC]", at [X] hours per week.

Learner level: [BEGINNER, INTERMEDIATE, ADVANCED]

OUTPUT LANGUAGE: Turkish.

For every week give: a measurable learning objective, the topics covered, one hands on mini project, three self test questions, and free resource suggestions.

Put a portfolio worthy capstone project in the final week.

Open with easy wins so motivation holds.

Teach me this subject: [TOPIC].

OUTPUT LANGUAGE: Turkish.

Explain it at three levels:
1. As you would to a twelve year old, using an analogy from everyday life.
2. To an adult meeting it for the first time, defining the technical terms.
3. To someone working in the field, with the details and the exceptions.

Then:
The three things people most often get wrong about it.
Five questions that would prove I actually understood it, with answers listed separately at the end.
What I should learn next.

Do not force the analogy. Where you are unsure, say so plainly.

I am a teacher. Build an exam from the course material below.

MATERIAL:
[LESSON TEXT or TOPIC HEADINGS]

Grade level: [LEVEL]. Duration: [MINUTES].

OUTPUT LANGUAGE: Turkish.

Produce:
Ten multiple choice questions, four options each, with plausible distractors and the correct option distributed randomly
Five short answer questions
Two open ended questions with grading criteria
An answer key with a brief rationale for each correct answer

Next to each question, note the difficulty level and the learning outcome it measures.

Draw only on the material I supplied. Do not bring in outside information.

Be my private tutor. Topic: [TOPIC]. My level: [LEVEL].

OUTPUT LANGUAGE: Turkish.

Rules:
Never hand me the answer. Make me think by asking questions.
Ask one question at a time and wait for my reply.
If my answer is wrong, tell me which part is wrong and give hints until I find it myself.
If my answer is right, raise the difficulty a notch.
Every fifth turn, briefly summarise what I have learned so far.
If I say I give up, explain it, then ask the same idea again through a different example.

Do not think for me. Start with a single question to gauge my level.

Read the text below and turn it into study notes.

TEXT:
[TEXT or BOOK TITLE and CHAPTER]

OUTPUT LANGUAGE: Turkish.

Deliver:
1. The central thesis, in one sentence.
2. The author's chain of argument, in five steps.
3. The seven most important ideas, each with a one sentence explanation.
4. Which three of those I could apply in my own work ([MY WORK]), and exactly how.
5. The weak or contested parts of the text.
6. What someone arguing the opposite case would say.

Add nothing that is not in the text. If I gave you a book title and you are not certain of its contents, say so.

You are a senior software engineer. Help me debug this.

Code: [CODE BLOCK]
Error message: [ERROR MESSAGE]
Expected behaviour: [WHAT SHOULD HAVE HAPPENED]

OUTPUT LANGUAGE: Turkish for all explanations. Keep code and identifiers as they are.

Approach:
1. Explain the root cause, not just the symptom.
2. Give the corrected code in full.
3. Explain in two or three sentences why it works.
4. Suggest a pattern or a check that prevents this class of bug in future.

Do not guess where you are unsure. Ask me what additional information you need.

Review this code the way a senior engineer would: direct but not unkind.

CODE:
[CODE]

Language and framework: [LANGUAGE]. What this code does: [PURPOSE]. Where it runs: [SERVER, BROWSER, MOBILE].

OUTPUT LANGUAGE: Turkish for all commentary.

Report findings under these headings:
1. Bugs: where the code behaves incorrectly, and with which input.
2. Security: input validation, authorisation checks, secrets living in the code, injection risk.
3. Edge cases: null values, zero, very large payloads, network failure.
4. Readability: naming, duplicated blocks, needless complexity.
5. Performance: redundant loops, repeated queries, memory leaks.

For every finding: the line, the problem, why it matters, and the corrected version.

Order them by severity. Do not invent problems the code does not have.

You are an automation engineer. Design the workflow that handles this job.

The job: [JOB]
Trigger: [WHAT SHOULD START IT]
Tools I use: [TOOLS]
Platform: [N8N, MAKE, ZAPIER]

OUTPUT LANGUAGE: Turkish for all explanations. Keep node names and field names as they are.

Deliver:
1. The flow, step by step: which node at each step and what it does.
2. The fields each step needs, with sample data.
3. Failure modes: which step breaks for which reason, and what should happen then.
4. Duplicate protection: what happens if the same record is processed twice.
5. A test plan: what to try before going live.
6. Any point that needs human approval.

Do not invent nodes or features that do not exist. If you are unsure, say so.

You are a data cleaning assistant.

RAW DATA SAMPLE, five rows:
[DATA]

TARGET FORMAT:
[TARGET FORMAT]

OUTPUT LANGUAGE: Turkish for all explanations.

Deliver:
1. A working regular expression, with each part explained.
2. A short Python script that does the same job.
3. Three edge cases the pattern will miss, and how to handle them.
4. A post cleanup check: rows in, rows out, rows unmatched.

Account for Turkish characters and Turkish case conversion, including the dotted and dotless i. Never propose a solution that silently drops data.

Help me connect to an API.

API: [API NAME]. Documentation link or text: [DOCS]
What I want to do: [OPERATION]
My language: [PYTHON, PHP, JAVASCRIPT]

OUTPUT LANGUAGE: Turkish for all explanations. Keep code as code.

Deliver:
1. How authentication works, step by step.
2. A working sample request: full code and a sample response.
3. The error codes it can return and what to do for each.
4. How to handle rate limits, if any.
5. Where secrets such as keys and tokens should be stored.
6. Retry and timeout settings.

Do not invent endpoints or fields that are not in the documentation. State plainly wherever the docs left you unsure.