Specimen file: deliverable

A dossier your agent can read before it edits.

This sample shows the shape of a FreshContext markdown pack. A paid pack is customized to the buyer's repo, installed dependency versions, and the specific API area where an AI coding agent keeps drifting into stale docs.

Outputmarkdown context patch

UseAGENTS.md, CLAUDE.md, or Cursor rules

Scopeone repo or dependency cluster

Price$5 FreshContext Pack

Sample markdown

The artifact is small on purpose.

The goal is to give the coding agent a version-aware note it can obey before it writes files, then force a verification loop before it claims success.

FRESHCONTEXT-PACK.mdsample repo

# FreshContext Pack - sample repo

## Purpose
Keep AI coding agents from using stale tutorials, deprecated APIs, or old framework defaults when editing this project.

## Dependency cluster
- Framework: Next.js app
- Styling: Tailwind CSS
- AI/API layer: OpenAI-compatible SDK usage
- Payments: Stripe Checkout

## Agent rules
1. Before editing code that touches a dependency, inspect the installed version from package.json and lockfile.
2. Open the official docs for that dependency and prefer current examples over blog snippets.
3. If a generated answer uses a deprecated symbol, stop and replace it before writing files.
4. After edits, run the repo's real verification command and report the exact exit code.

## Deprecation traps to check
- Do not assume old package examples are valid for the installed major version.
- Do not assume AI SDK examples from older tutorials match current client patterns.
- Watch for framework upgrade guides that changed defaults, config files, or import paths.
- Watch for examples that work in a minimal demo but fail in this repo's runtime.

## Current-doc links to pin
- Official framework docs for the installed major version
- Official SDK migration or quickstart page
- Official payment checkout/session reference
- Official styling upgrade/configuration page

## Verification checklist
- npm run lint
- npm run typecheck, if present
- npm test, if present
- One manual smoke path for the edited feature

## Prompt to use before agent edits
Read package.json and the lockfile first. Identify touched dependencies and their installed versions. Then check official docs for those versions. Do not write code until you list the version-sensitive rules that matter for this task.

Paid pack adds

The buyer version gets real repo facts.

A real delivery fills in installed versions, official docs URLs, known traps, and the exact verification command the agent must report back.

AVersion facts

Dependencies, package manager, framework version, and runtime constraints pulled from the buyer's repo or manifests.

BDoc anchors

Official current docs and migration pages pinned beside the patterns the agent should stop copying.

CVerify loop

Commands and smoke checks the coding agent must run, with exact exit-code reporting before any success claim.