Productive— faster every day
For your professionTeachersStudentsManagersMarketingDevelopersFreelancersParents

Prompt library · AI · 18 prompts

Prompts from the guide

From pencil sketch to computer: what you can actually turn into vectors, CAD, and 3D today

18 prompts from this guide. Fill in whatever sits in [square brackets] — your own context, the document text or the name of your tool. That context is exactly what separates a generic answer from a usable one.

Read the full guide →

First prompt: checking whether the photo is usable

I'm attaching a photo of a hand-drawn floor plan sketch that I want to vectorize
and bring into CAD. Assess it as input for vectorization, not as a drawing.

Go through this in order:
1. Contrast between the line and the paper — is the drawing dark enough, or is
   there a risk that vectorization will lose the line?
2. Shadows and uneven lighting — where exactly in the photo is this a problem?
3. Perspective — is the photo square-on, or is the paper trapezoidal? Estimate
   how much.
4. Distracting elements — paper grid, notes, hatching, fingers in frame,
   a stapler.
5. Is at least one dimension in the drawing legible, one I could calibrate the
   scale against? If so, state it.

End with a clear verdict: either “usable, go ahead” or “retake it,” with
a specific instruction on what to do differently. Don't try to flatter the
photo — I need the truth before I build anything on top of it.

Second prompt: cleaning up the photo before vectorization

Prepare the attached photo of a hand-drawn sketch for vectorization. The goal
isn't a pretty picture — it's the cleanest possible black-and-white line
drawing.

Do this:
1. Level the horizon and correct the perspective so the paper's edges are
   vertical and horizontal.
2. Crop to the paper, with a minimal margin.
3. Increase contrast and exposure so the paper is pure white and the line is as
   dark as possible. Target look: a scanned document, not a photo.
4. Suppress noise and paper texture.
5. Keep the resolution — don't downscale.

After each edit, tell me what you did and why. At the end, show the result and
flag any spots where the line got lost or blended into the background while
you were boosting contrast.

Prompt: batch-vectorizing a folder of sketches

I have a folder at [folder path] full of photos of hand-drawn floor plan
sketches, JPG format. I want to batch-convert them into vector SVGs using
Inkscape, which I have installed.

Steps:
1. First, tell me how many files you found and what resolution they're at.
   Don't change anything yet.
2. Propose an Inkscape command that traces the bitmap using a brightness
   threshold, and explain each parameter in one sentence.
3. Run it on ONE file that I choose first, and show me the result. Never
   overwrite the originals — save outputs into a subfolder called vectors.
4. Once I confirm the result looks right, process the rest as a batch.
5. At the end, give me a table: file, number of resulting paths, output size,
   and flag any where the path count looks suspiciously high — that usually
   means noise got vectorized too.

Don't touch anything outside this folder.

Prompt: assessing and cleaning up the resulting curves

I'm attaching the result of vectorizing a hand-drawn floor plan sketch (SVG)
alongside the original photo. Compare them and tell me what needs fixing
before I use this as reference material in CAD.

Focus on:
1. Missing line segments — places where the outline didn't close.
2. Doubled outlines — vectorization often turns one line into two, because it
   traces both of its edges. Where did that happen?
3. Leftover noise: small paths that aren't part of the drawing.
4. Text and dimensions — did they get vectorized as curves? Those are better
   deleted and retyped later as real text.
5. Redundant points on curves that could be simplified.

For each point, tell me whether I should fix it in a graphic editor or later
while tracing in CAD. Don't rewrite the file for me — I want a list first.

Prompt: calculating and checking the scale

I'm calibrating the scale of a vectorized floor plan sketch. Help me
calculate this, and more importantly, verify it.

Data:
- Reference dimension measured on-site with a tape measure: [e.g. inside
  length of the south wall = 4.20 m]
- That same dimension measured in the vector editor: [e.g. 847 px]
- Control dimension measured on-site: [e.g. width of the door opening = 0.80 m]
- That same control dimension in the vector: [e.g. 158 px]

Do this:
1. Calculate the scale from the reference dimension — how many meters
   correspond to one unit in the file, and what factor should I scale the
   drawing by so that 1 unit = 1 mm.
2. Apply that scale to the control dimension and tell me what length that
   would produce.
3. Compare it to the measured value and calculate the deviation in
   millimeters and in percent.
4. Assess: up to what deviation is this reference material usable for a
   layout study, and beyond what point does it need to be retaken or
   re-measured? Explain your reasoning.

Show me the intermediate calculations so I can double-check them myself.

Prompt: a checklist of dimensions to verify on-site

I'm attaching a floor plan sketch [description: 3-bedroom apartment, a
prefab-panel building, I'm measuring for a kitchen redesign].

Build me a checklist of dimensions I need to measure with a tape measure
on-site to turn this sketch into usable reference material. Rank them by
importance, and for each one, note:
- exactly what to measure and from where to where,
- why that dimension matters,
- how much inaccuracy is still fine, and at what point it becomes a problem.

Don't forget the things people commonly forget: ceiling heights, sill
heights, the position and height of water, drain, gas, and electrical
connections, door swing direction, radiator placement, clearance around open
cabinet doors, and out-of-square corners.

I want the output as a table I can print and take with me, with a blank
column for the measured value.

Prompt: preparing the export and a checklist

I have a vectorized and calibrated floor plan sketch in SVG (1 unit = 1 mm),
and I need to get it into [name of CAD program] as reference material for
tracing.

Prepare me a process and a checklist:
1. Which export format do you recommend for this goal and why — and what's
   the second-best option if the first one fails?
2. What to watch for with units, so the drawing comes in at the right size.
3. How to clean up the file before export: what to delete, what to merge,
   what to convert.
4. What to do right after opening it in CAD — how do I verify the scale is
   correct, and how do I lock the reference layer.
5. The three most common problems with this kind of transfer and how to
   recognize them.

Keep it short and in steps — I want to use this as a checklist card, not
read it like an article.

Prompt: checking the file after import

I've opened the vectorized reference material in CAD and I want to make sure
it's usable. Walk me through checking it.

Give me a list of checks to run, ranked by importance, and for each one note
what result is fine and what result means there's a problem:
- checking the scale against a known dimension,
- checking squareness where corners should be square,
- checking that the drawing is complete and nothing got lost,
- checking the element count (a sign of curves having broken apart),
- checking the position relative to the coordinate origin.

For each check, write one sentence on what to do if it fails.

The SketchUp route

I'm attaching an apartment floor plan (calibrated, dimensions in meters) and
I want a simple 3D massing model from it for communicating with a client, not
a rendering.

Specs:
- Ceiling height: [2.6 m]
- Exterior wall thickness: [0.45 m], interior partitions: [0.1 m]
- Windows: sill height [0.9 m], head height [2.2 m], widths per the floor plan
- Door openings: height [2.0 m]
- Don't worry about materials, plain white is fine.

Here's the process I want:
1. First, tell me how you read the rooms and dimensions off the floor plan —
   a list of rooms with their areas. Stop there and let me confirm it.
2. Only build the model after I confirm.
3. At the end, tell me what you had to guess, because it couldn't be read
   off the reference material.

That last part matters most to me — I need to know what not to trust in the
model.

The Blender route

I'm working in Blender and I have a calibrated floor plan imported as
reference material (curves, 1 unit = 1 meter).

I want to build a simple massing model from it:
1. First describe the process you'll use — what objects will result and how
   they'll be named.
2. Extrude the walls to a height of [2.6 m], exterior ones at a thickness of
   [0.45 m].
3. Cut openings for windows and doors per the reference material, sill height
   [0.9 m].
4. Put each room into its own collection, named after the room.
5. Set the camera to an isometric top-down view and render a preview.

Don't touch anything outside the scene I have open, and ask before running
anything that deletes or overwrites existing objects.

Prompt: a structured summary of the current state from photos

I'm attaching [number] photos of the kitchen we're going to remodel. Build me
a structured summary of the current state from them.

Break it into sections:
1. Structure and surfaces — flooring, walls, ceiling, windows, doors, sills.
2. Utilities and connections — what's visible: radiators, switches, outlets,
   drains, gas, range hood, boiler. Note anything that can only be guessed at
   too.
3. Fixtures — what's in the space and whether it's staying or going.
4. Issues and risks — anything in the photos that looks like a complication
   for the remodel.

Rules:
- DO NOT estimate dimensions. Wherever a dimension would be needed, write
  “needs to be measured on-site” instead, and briefly say why.
- Where you're not sure what you're looking at, say so openly instead of
  guessing.

At the end, add a list of questions I should ask the owner.

Design variations from a photo — and how to label them honestly

I'm attaching a photo of the current kitchen. Create three moodboard
variations for the client — I care about color, materials, and atmosphere,
not the layout design.

Variations:
A) [light Scandinavian, oak and white]
B) [dark, matte fronts, stone]
C) [traditional, wood, framed cabinet doors]

For each variation, I want:
- a visual based on the attached photo (keep the layout, window, and space
  proportions unchanged),
- legible text in the bottom-right corner of the image reading “Illustrative
  visualization — not binding, does not reflect actual dimensions,”
- a short caption below the image: materials, surfaces, colors, and what to
  ask the supplier about.

Don't invent brand names or specific products you can't back up.

Prompt: what kind of PDF is this, and what can I get out of it

I'm attaching a PDF with construction documentation. Before I start working
with it, I need to know what I'm dealing with.

Determine and tell me:
1. Is the PDF's content vector (real lines and text), or is it a scan or
   a photo embedded in the PDF? How did you tell?
2. Can text be searched in the document? If so, list the labels, title
   block, and legend for me.
3. What drawings does the document contain, on which pages, and at what
   scale according to the title block.
4. What dimensions in the document are legible, and which ones you're not
   sure about.
5. Based on that, recommend a process: can geometry be pulled out directly,
   or does it need to go through vectorization like an image?

For points 2 and 4, distinguish clearly between what you actually read and
what you inferred. Don't make up numbers that aren't visible.

Prompt: transcribing and comparing against reality

I pulled these values from the documentation: [paste the transcribed
dimensions and areas]. On-site, I measured this: [paste the measured
values].

Compare the two:
1. A table: value from the documentation, measured value, difference in cm
   and in %.
2. Flag differences that fall within normal construction tolerance, and
   those that mean something has changed since the documentation was made.
3. For larger differences, propose an explanation — an added layer of
   finish, a new partition, a different measuring convention (clear versus
   structural dimensions), a transcription error.
4. Tell me which dimensions I should re-measure, because the difference
   could be a measurement error.

Don't explain away the differences. If something doesn't match, I want to
see it.

Phase 8: A presentation board for the client or contractor

Put together a client presentation board, A3 landscape, output as PDF.

Materials: [floor plan, 3 photos of the current state, 3 moodboard variations,
dimension table].

Structure:
1. Header: project name, address, date, my name.
2. Left third: floor plan with the scale and a north arrow marked.
3. Center: photos of the current state with short captions.
4. Right third: three material variations, each with a caption.
5. Footer across the full width, small but legible type: “Study and reference
   material for discussion. This is not construction documentation. Verify
   dimensions on-site before manufacturing.”

Stick to two typefaces, one accent color, and a calm layout. Don't stretch
anything to fill the page just to avoid empty space. Once it's done, show me
a preview and tell me what's weakest about the layout.

Phase 8: A presentation board for the client or contractor

Write a scope brief for a carpenter for a kitchen counter. Materials: [floor
plan, condition summary, measured dimensions, moodboard].

Structure of the text:
1. What's being done and in what space — two sentences.
2. Measured dimensions in a table, noting which ones were verified with
   a tape measure and which come from reference material.
3. Known constraints and risks — a soil stack, an uneven wall, a low sill,
   utility connection locations.
4. What I want to achieve and what's the priority for me.
5. Questions I need answered in the quote.

Write it plainly, no marketing language. Never state a dimension I don't
have in the materials — write “to be measured” instead.

Security and data

I'm about to install a community MCP server [link to the project] so Claude
can control [program]. Before I do, walk through it with me.

I want to know:
1. What the server actually does technically — what permissions it needs,
   which folders it can reach, whether it can run code inside the
   application.
2. How well-maintained the project is: last activity, who's behind it, open
   issues.
3. Which specific steps in the installation instructions make a permanent
   change to my system, and how to undo them.
4. What I should back up before running it on my data for the first time.
5. The smallest reasonable test I can run to confirm it works, without
   risking my files.

Where you don't have information, say so. Don't repeat marketing claims from
the project's description as fact.

Pro tip

Turn our process into a one-page working card I can use for every job.

Include:
1. What to do on-site — photographing the sketch, the minimum dimensions to
   measure.
2. What to do at home — the order of steps from photo to DXF, one sentence
   per step on what "done" looks like.
3. Checkpoints where I stop and verify something, and exactly what I'm
   verifying.
4. What never goes out without a caption.

Format: numbered steps, no explanations, fits on one A4 page. Make it
printable and checkable off.

All prompts