Skip to main content

Documentation Index

Fetch the complete documentation index at: https://labs.prompthon.io/llms.txt

Use this file to discover all available pages before exploring further.

This document holds the internal structure and reference notes that support Prompthon Agentic Labs. It is intentionally separate from the top-level README so the front door can stay lightweight.

Current status

  • The top-level lab lanes are now scaffolded in the repository.
  • Imported reference material is kept outside the published docs surface.
  • Audience guides and contributor templates are in place for future content work.
  • The first public lab article wave is drafted.
  • Public contributor guidance now covers articles, radar notes, source projects, and curated reference notes.

What this lab covers

  • Agent system fundamentals and terminology
  • Reusable agent patterns and workflow mechanisms
  • Systems concerns such as context, protocols, evaluation, and reliability
  • Ecosystem comparisons across global and Chinese agent tooling
  • Story-led case studies for major agent product categories
  • Fast-moving radar and publication extensions

Repository structure

PathPurpose
foundations/Core concepts, terminology, and mental models
patterns/Reusable agent design patterns and mechanisms
systems/Production-minded systems topics such as evaluation and interoperability
ecosystem/Topic-first comparisons of tools, models, and platforms
case-studies/Story-led examples for major agent archetypes
radar/Fast-moving market and protocol tracking
reading-paths/Audience-first entry points into the lab
publications/Metadata and structure for external reading extensions
contributor-kit/Templates and editorial scaffolding for contributions
local reference archiveImported source material and planning documents kept outside the published docs surface
Lane-local example projects live only where code is natural in v1:
  • patterns/examples/
  • systems/examples/
  • ecosystem/examples/
  • case-studies/examples/
Curated contributor-facing source maps live in contributor-kit/reference-notes/.

Editorial direction

  • Path-first, not chapter-first
  • Story-led pages that move from problem to architecture to tradeoffs
  • Topic-first ecosystem coverage with explicit global and Chinese lanes
  • Repo-native content outside references/, with source-aware adaptation

Reference base and reuse boundary

Reference material should be used for curation and planning, not as publishable copy or citation scaffolding. Tutorial-oriented repositories should not be carried forward as public citations. Prefer official product documentation, framework repositories, protocol specifications, and runnable solution repositories when a page needs external sources. If content is later adapted from any upstream material, attribution and license constraints must be reviewed before publication.