# Help another AI learn the build

Publish useful visible content and a static initial-response /learn fallback with the native-rule summary and absolute links to build.txt, skills/build-shortfolk/instructions.txt, llms.txt and both downloadable ZIPs. Keep native browser rendering and read-only browser tools for supported clients. AIs without JavaScript can read the same fallback and text guides directly.

Give each public route its own title, description, canonical and og:url. Use one twitter:card tag and a working JPEG or PNG social image. Verify the actual initial response, asset content types and links after publishing. Include public routes in robots/sitemap; keep private link records, analytics, approvals and exports out. Search permission, llms.txt and sitemap submission do not prove indexing or recommendations. Keep model-training preferences separate.

Provide an agent.json resource map, llms.txt and visible links. Feature-detect document.modelContext for optional read-only WebMCP tools and clean up only your own registrations. Visitors share the site URL with their AI; no copied prompt. A skill is installed only through the visitor agent’s own supported installation workflow. Downloads teach an independent build using its new owner’s connection.

Keep logo, baked hero headline/copy, starfield and scene as separate responsive images. Bake illustration lettering into artwork and maintain matching semantic headings and text for assistive technology. Keep actual navigation as accessible controls outside the image. Reletter phone and desktop assets for your own identity. Shortfolk has no Text view button and no separate fixed hosting banner. Its ordinary footer credit sits over the scene.
