Start here

Agent orientation path

Follow this sequence when an agent is pointed at the main URL and needs to understand the repo without human explanation.

  1. Read /agent-manifest.json for the machine-readable overview.
  2. Read /file-map.json to understand where behavior lives.
  3. Open AGENTS.md and docs/agent-playbook.md in the file system.
  4. Read /standards/ and /qa-contract/.
  5. Review /examples/ before creating a new site pattern.
  6. Run npm run qa:all before claiming the site is ready.

Core pages

Navigation map for agents

Agent Start

Entry route for agents: what this repo is, how to inspect it, and the fastest path to competence.

/agent-start/

Repo Map

Human-readable and machine-oriented map of source files, generated endpoints, docs, data, and QA evidence.

/repo-map/

Standards

Website Specification category map translated into implementation responsibilities for this starter.

/standards/

Workflows

Step-by-step workflows for adapting, validating, crawling, and handing off a serious website.

/workflows/

Examples

Pattern examples agents can reuse for local service, B2B SaaS, professional services, proof, and FAQ pages.

/examples/

Copy Lab

Conversion copy principles, good/bad examples, source boundaries, and agent workflow based on public offer/copy pattern study.

/copy-lab/

Page Pattern Fixtures

Concrete route fixtures that turn page-pattern contracts into inspectable Astro pages with metadata, schema, traceability, and QA expectations.

/fixtures/page-patterns/

Design System Fixtures

Concrete design-system fixtures for endpoint rows, QA command blocks, evidence cards, pattern tables, and status badges.

/fixtures/design-system/

QA Contract

Executable quality contract behind qa:routes, qa:seo, qa:aeo, and qa:all.

/qa-contract/

Machine-readable first

Endpoints an agent should fetch directly

EndpointPurpose
/agent-manifest.jsonTop-level machine-readable index of pages, files, standards, workflows, examples, and QA commands.
/file-map.jsonStructured map of important source files and generated endpoints.
/qa-contract.jsonMachine-readable definition of route, SEO, AEO, build, and crawl expectations.
/examples.jsonStructured example pattern catalog.
/agent-tasks.jsonStructured future-agent backlog for improving this reference before real implementation work.
/product-roadmap.jsonStructured product roadmap for executing every value multiplier to completion.
/walkthroughs.jsonStep-by-step execution walkthroughs for every roadmap value multiplier.
/contract-registry.jsonFormal registry of JSON contracts, schemas, source owners, validation evidence, and failure modes.
/site-studies.jsonStructured good/bad real-site studies with audit evidence and agent checks.
/seo-aeo-evaluation.jsonStructured SEO/AEO evaluation checks, proof commands, evidence expectations, and automation status.
/source-traceability.jsonStructured source-to-site claim ledger, artifact chain, and proof policy.
/site-type-playbooks.jsonStructured build playbooks for local service, SaaS, professional services, proof, and answer-ready resource sites.
/page-patterns.jsonStructured reusable page-pattern contracts for service, proof, resource, contact, home, and schema-backed pages.
/page-pattern-fixtures.jsonStructured route fixture inventory proving each page-pattern contract can drive an actual Astro route.
/conversion-copy.jsonStructured conversion copy system with principles, copy types, good/bad examples, source boundaries, workflow, and QA gates.
/offer-ecosystem.jsonStructured offer-ecosystem funnel contract for AI tools, communities, workshops, playbooks, pricing tiers, qualification gates, referrals, and disclaimers.
/infrastructure-decisions.jsonStructured infrastructure decision system for hosting, rendering, CMS, data, auth, media, search, analytics, forms, payments, DNS/CDN, observability, and deployment tiers.
/browser-visual-qa.jsonStructured browser visual QA contract for screenshots, viewports, layout checks, and report evidence.
/crawl-evidence.jsonStructured crawl evidence contract for Screaming Frog exports, summary reports, and readiness criteria.
/design-system-contracts.jsonStructured design-system contract for tokens, components, accessibility, anti-patterns, QA gates, and stress tests.
/aeo-geo-context.jsonStructured AEO/GEO model context contract for answer-engine prompts, citations, source boundaries, and stress tests.
/why-explanations.jsonStructured rationale contract for where explanations, tradeoffs, evidence, and failure modes are required.
/real-site-comparisons.jsonStructured real-site comparison contract for reference studies, scoring dimensions, evidence, and follow-up tasks.
/handoff-reports.jsonStructured handoff report contract for final evidence, risks, next actions, and closeout records.
/agent-index.jsonLightweight orientation index (reading order plus endpoint list) for token-constrained agents; the cheapest complete index.
/evidence/index.jsonPublished QA evidence index from the latest accepted run; every entry links a live report artifact.
/accessibility-contract.jsonWCAG 2.2 AA accessibility contract: value rules, enforcement method, manual checklist, anti-patterns.
/performance-budgets.jsonCore Web Vitals targets, asset budgets, page rules, and measurement method enforced by qa:perf.
/demo-build.jsonCanonical demo build record: fictional source chain, playbook execution, pages, claims, and QA gates.
/demo/brightline/schema.jsonMachine-readable schema facts for the fictional local-service demo with claim IDs.
/demo/logpilot/schema.jsonMachine-readable schema facts for the fictional B2B SaaS demo with claim IDs.
/llms.txtConcise LLM entry point.
/llms-full.txtLonger LLM-readable repo and site summary.
/schemamap.xmlSchema endpoint discovery map.
/sitemap.xmlIndexable route discovery.
/robots.txtCrawler and AI-use policy hints.
/schemas/agent-manifest.schema.jsonJSON Schema for /agent-manifest.json.
/schemas/file-map.schema.jsonJSON Schema for /file-map.json.
/schemas/qa-contract.schema.jsonJSON Schema for /qa-contract.json.
/schemas/examples.schema.jsonJSON Schema for /examples.json.
/schemas/agent-tasks.schema.jsonJSON Schema for /agent-tasks.json.
/schemas/product-roadmap.schema.jsonJSON Schema for /product-roadmap.json.
/schemas/walkthroughs.schema.jsonJSON Schema for /walkthroughs.json.
/schemas/contract-registry.schema.jsonJSON Schema for /contract-registry.json.
/schemas/site-studies.schema.jsonJSON Schema for /site-studies.json.
/schemas/seo-aeo-evaluation.schema.jsonJSON Schema for /seo-aeo-evaluation.json.
/schemas/source-traceability.schema.jsonJSON Schema for /source-traceability.json.
/schemas/site-type-playbooks.schema.jsonJSON Schema for /site-type-playbooks.json.
/schemas/page-patterns.schema.jsonJSON Schema for /page-patterns.json.
/schemas/page-pattern-fixtures.schema.jsonJSON Schema for /page-pattern-fixtures.json.
/schemas/conversion-copy.schema.jsonJSON Schema for /conversion-copy.json.
/schemas/offer-ecosystem.schema.jsonJSON Schema for /offer-ecosystem.json.
/schemas/infrastructure-decisions.schema.jsonJSON Schema for /infrastructure-decisions.json.
/schemas/browser-visual-qa.schema.jsonJSON Schema for /browser-visual-qa.json.
/schemas/crawl-evidence.schema.jsonJSON Schema for /crawl-evidence.json.
/schemas/design-system-contracts.schema.jsonJSON Schema for /design-system-contracts.json.
/schemas/aeo-geo-context.schema.jsonJSON Schema for /aeo-geo-context.json.
/schemas/why-explanations.schema.jsonJSON Schema for /why-explanations.json.
/schemas/real-site-comparisons.schema.jsonJSON Schema for /real-site-comparisons.json.
/schemas/handoff-reports.schema.jsonJSON Schema for /handoff-reports.json.
/schemas/demo-build.schema.jsonJSON Schema for /demo-build.json.
/schemas/performance-budgets.schema.jsonJSON Schema for /performance-budgets.json.
/schemas/accessibility-contract.schema.jsonJSON Schema for /accessibility-contract.json.
/schemas/evidence-index.schema.jsonJSON Schema for /evidence/index.json.
/schemas/agent-index.schema.jsonJSON Schema for /agent-index.json.

Primary workflow

Agent orientation

  1. Open the main URL.
  2. Read /agent-manifest.json.
  3. Read AGENTS.md and docs/agent-playbook.md.
  4. Read /file-map.json to identify source files and generated outputs.
  5. Run npm run qa:all before changing behavior.