# Axhub Prototype Context

> Use when an annotated prototype URL exposes PRD, directory, annotation, or source context that an AI Agent needs for review, implementation planning, production work, source handoff, or optional review-report submission.

- Skill: `lintendo/axhub-prototype-context` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add lintendo/axhub-prototype-context`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lintendo/axhub-prototype-context/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: lintendo (https://skillmd.com/u/lintendo)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lintendo/axhub-prototype-context

---


# Annotated Prototype Context

Read the published context from an annotated prototype so an AI Agent can understand its pages, PRD, annotations, and available source before continuing with review or production work. Treat the page as read-only unless the user asks to submit a review report back to Axhub Make.

## Workflow

1. Open the requested annotated prototype URL with Playwright, Browser, Chrome, or an equivalent tool that can evaluate page JavaScript.
2. Wait until the app renders, then poll briefly for `window.__AXHUB_ANNOTATION_SOURCE__`.
3. Evaluate and return that value. Do not modify the object or write anything back to `window`.
4. If the value is missing, report the URL, page title, relevant console errors, and that the annotated prototype context snapshot was not published.
5. If the user asks to submit a review report back to Axhub Make, read `references/review-report-submission.md`.

Minimal page evaluation:

```js
await page.waitForFunction(() => window.__AXHUB_ANNOTATION_SOURCE__, { timeout: 10000 });
const source = await page.evaluate(() => window.__AXHUB_ANNOTATION_SOURCE__);
```

## What To Report

- Directory / PRD outline from `source.directory`.
- Markdown or PRD entries from directory nodes with `type: "markdown"`.
- Annotation count and the important node fields: `id`, `title`, `pageId`, `locator`, `annotationText`, `aiPrompt`, `color`, and `controls`.
- Source handoff from `source.source` when present. Report `root` and `manifest`; when source is needed, read the manifest and relevant files via `root`.
- Mention whether images are attached by checking `images.length`; do not download images unless the user asks.

## Data Shape

```ts
type AnnotationSourceRuntimeSnapshot = {
  directory: AnnotationDirectory | null;
  nodes: AnnotationNode[];
  source?: {
    root?: string;
    manifest?: string;
  };
};
```

- `directory.nodes` is the prototype tree. Node types are `folder`, `route`, `link`, and `markdown`.
- `nodes` is the full annotation list, independent of current page, selected state, and color filter.
- Each annotation node includes `id`, `index`, optional `title`, optional `pageId`, `locator`, `aiPrompt`, `annotationText`, `hasMarkdown`, `color`, `images`, optional `controls`, `createdAt`, and `updatedAt`.
- `source` is only a source-code discovery reference. In HTML published with source included, `manifest` points to `source/manifest.json`; resolve its paths relative to `source.root`.