Repo Page Template

template-repo-page Template

template deprecated

Project

Repo Page Template

Every repo gets a repo page note. This is the entry point for any agent starting work in the repo. Tagged repo-page,active. Links to its parent project page.

Template

Section Order

Purpose — what and why (stable)
Value — why it matters, with evidence (grows over time)
Usage — how to use it (updated with releases)
Status — what's true right now (updated frequently)
Architecture — how it's built (changes with redesigns)
Plans — which plans produced this code (append-only)
Issues — what's broken or needed (table of issue notes)
Case Studies — evidence of value (grows over time)

Naming Convention

Slug: repo-[repo-slug] (e.g., repo-woodpecker-mcp, repo-forgejo-sdk)
Tags: repo-page,active
Project: the project this repo belongs to

Why Repos Need Pages

Project pages are too high-level to capture repo-specific context. A project like Claude Config has 4+ repos, each with different purposes, usage patterns, and value propositions. Agents starting work in a repo need repo-level context, not project-level context. Repo pages also accumulate case studies that justify the repo's existence — if a repo can't demonstrate value, it's a candidate for archival.

Relationship to Project Pages

Project pages link to repos via the Repos table (names and roles)
Repo pages link back to the project and provide deep context
Project pages are the index; repo pages are the detail