# A Paste-Ready Prompt Is Now a Quickstart Artifact For a task the developer will hand to a coding agent, the artifact that shortens time to first result is a prompt they can paste, so a quickstart that ships only a code block is incomplete. Tessa Mero, one month into directing developer advocacy at Checkmarx, describes her own habit in a HackerNoon interview published 2026-09-25 [¶32]: skip the long explanation, go to the sample, copy, paste, run, experiment. Then she names the shift. > [!quote] [¶32] > These days, “Copy Prompt” is becoming the new “Copy Code”. The mechanism is the same one behind every quickstart artifact. Mero's threshold is a few minutes: a developer who can't get started inside that window is likely gone [¶20], and quickstart docs, short demo videos, written tutorials, and sample apps all exist to hit that one number. When the developer's workflow runs through an agent or chat assistant, their first action is a prompt. A code sample then costs a translation step (read the code, work out what to ask for), while a prompt block is the first action itself. In [¶33] she lists the prompt beside demo, sample app, and snippet as the things a developer can try. The prompt inherits the code sample's obligations: tested, versioned, dated, and labeled with the model it was tested on, because its output drifts as models change. The claim holds where the audience works through a coding agent and the task is one agents do well: scaffolding, config generation, migration, boilerplate. It breaks where the code itself is the lesson (a security fix the reader must understand, an API contract), where output varies enough across models to mislead, or where the audience doesn't use agents. The evidence is one practitioner's observation, not a measurement: Mero says three times she is new to the role [¶10, ¶17, ¶24], the "few minutes" bound is her estimate, and she doesn't say what a good prompt block contains. That gap is the work: the vault already holds a governance model for prompts docs teams run internally, and this claim puts the same asset class in front of the reader. <!-- atomicity: 1 idea ✓ --> ## Why This Matters When you write or review a quickstart, put a prompt block next to the code block for any step a reader would hand to an agent: the prompt text, the expected output, the model and date it was tested on, and a line saying output drifts. Then time a new user through both paths and keep whichever one gets to a working result first. ## Links - [[3. Resources/Permanent Notes/Time-to-Hello-World Is the Critical Developer Experience Metric]] — extends: the set of artifacts that move that metric now includes a prompt block, not only code samples and sample apps. - [[3. Resources/Permanent Notes/DevRel Artifacts Must Match How Developers Consume Information]] — evidence-for: Mero's "Copy Prompt" line is a practitioner sighting of the artifact shift that note predicts. - [[3. Resources/Permanent Notes/Documentation Prompts Are Documentation Assets Governed Like Code]] — applies-in: that note governs prompts a docs team runs internally, this one puts the same class of asset in front of the reader with the same review and versioning duties. - [[3. Resources/Permanent Notes/Prompt Rules Decay With Model Versions Date Every Never]] — constrains: a published prompt block needs the model and date it was tested on, because the output that made it a quickstart artifact changes with model versions. - [[3. Resources/MOCs/Documentation & Technical Writing MOC]] — applies-in: a quickstart component rule for the docs practice section. ## Source - [[3. Resources/Readwise/Articles/Is Dev Rel Marketing, Engineering, or Product The Answer Is Yes, Says Checkmarx's Tessa Mero|Is Dev Rel Marketing, Engineering, or Product? "The Answer Is Yes," Says Checkmarx's Tessa Mero]] - https://hackernoon.com/is-dev-rel-marketing-engineering-or-product-the-answer-is-yes-says-checkmarxs-tessa-mero