Prompt Archaeology: how prompts evolve into useful tools

You can get “an answer” with a single sentence, but you get a reliable artifact by iterating: adding constraints, structure, audience, and quality checks. Explore five layers and watch the output tighten.

Layers

Prompt quality 20%

This meter updates as you explore each version.

V1 — Vague request

Low specificity Generic output risk

Prompt

Write a portfolio project description.

Output

I built a project that demonstrates my skills. I used different technologies and learned a lot in the process. The project shows my ability to solve problems and work hard. I am proud of the result and plan to keep improving it.

Lesson: the model fills the gaps with safe, generic language when goals and context are missing.

V2 — Add constraints

Constraints added More concrete

Prompt

Write a project description in 3–4 sentences. Include: problem, approach, tools used, and a measurable outcome. Keep it recruiter-friendly.

Output

I built a web portfolio to present my work clearly to recruiters and teammates. I designed five pages with consistent navigation and implemented a JavaScript-based style toggle that switches between two full layouts. I used HTML, CSS, and JavaScript with clean structure and version control throughout development. The result is a fast, readable site that communicates projects, skills, and service in under two minutes of browsing.

Lesson: constraints force the output into a useful shape and reduce “resume-fluff.”

V3 — Add structure

Scannable format Better hierarchy

Prompt

Write a project entry with headings: Overview, What I built, Technical highlights, Impact. Use bullet points under highlights. Keep it concise.

Output

Overview A personal portfolio site designed for quick recruiter scanning and a strong first impression. What I built Five distinct pages with consistent navigation, plus a style toggle that switches between two complete layouts. Technical highlights - Single HTML file per page; shared components via consistent markup patterns - Two independent CSS designs (layout change, not just color changes) - JavaScript toggler with persistent state across pages Impact A professional site that communicates skills and projects quickly and cleanly without external libraries.

Lesson: structure turns a blob of text into something a human can skim.

V4 — Add audience and tone

Audience specified Tone tuned

Prompt

Same as V3, but write for a recruiter and a future teammate. Tone: confident, precise, no hype. Use active voice and avoid vague words like “things” and “stuff.”

Output

Overview A recruiter-friendly portfolio site that presents my work clearly and reflects how I collaborate and communicate. What I built A five-page site built with HTML/CSS/JavaScript, featuring a style toggle that switches between two full layouts while keeping identical HTML. Technical highlights - Layout-first redesign: two CSS files with different grid systems and navigation placement - Clean, consistent file organization and naming conventions - JavaScript toggle with local persistence to keep the experience consistent across pages Impact A polished site that communicates skills quickly, demonstrates attention to detail, and showcases front-end fundamentals without templates.

Lesson: specifying audience and tone reduces filler and improves trust.

V5 — Quality assurance pass

Self-check added Higher reliability

Prompt

Rewrite V4 output with a QA pass: remove redundancy, tighten phrasing, ensure each section adds new information, and keep the entire entry under 120 words.

Output

Overview A recruiter-ready portfolio site that’s fast to skim and easy to navigate. What I built A five-page HTML/CSS/JS site with a style toggle that swaps between two complete layouts while preserving identical HTML. Technical highlights - Two independent CSS designs with different layout systems - Consistent structure and naming for maintainable pages - Persistent style selection with JavaScript Impact Demonstrates front-end fundamentals, attention to detail, and clear communication—without templates or libraries.

Lesson: adding a QA instruction is the fastest way to improve clarity and reduce repetition.

Final prompt used (required)

This textarea contains the exact prompt used to produce this GenAI page. It scrolls if needed.

Tip: Keep this prompt accurate; it documents your process.