> ## 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.

# Start Here

<div className="not-prose my-4 rounded-md border border-gray-200 bg-gray-50 p-2 text-sm dark:border-gray-800 dark:bg-gray-900/40">
  <div className="mb-2 px-1 text-xs font-semibold uppercase tracking-wide text-gray-500 dark:text-gray-400">Need help?</div>

  <div className="flex flex-wrap gap-2">
    <a className="inline-flex items-center gap-2 rounded-md border border-gray-200 bg-white px-3 py-1.5 font-medium text-gray-700 no-underline shadow-sm hover:border-gray-300 hover:bg-gray-50 dark:border-gray-800 dark:bg-gray-950/60 dark:text-gray-200 dark:hover:bg-gray-900" href="https://discord.gg/sDE2HhGTg4" target="_blank" rel="noreferrer">
      <Icon icon="discord" iconType="brands" size={14} />

      <span>Ask in Discord</span>
    </a>

    <a className="inline-flex items-center gap-2 rounded-md border border-gray-200 bg-white px-3 py-1.5 font-medium text-gray-700 no-underline shadow-sm hover:border-gray-300 hover:bg-gray-50 dark:border-gray-800 dark:bg-gray-950/60 dark:text-gray-200 dark:hover:bg-gray-900" href="https://github.com/Prompthon-IO/agent-systems-handbook/issues/new/choose" target="_blank" rel="noreferrer">
      <Icon icon="github" iconType="brands" size={14} />

      <span>Open a GitHub issue</span>
    </a>

    <a className="inline-flex items-center gap-2 rounded-md border border-gray-200 bg-white px-3 py-1.5 font-medium text-gray-700 no-underline shadow-sm hover:border-gray-300 hover:bg-gray-50 dark:border-gray-800 dark:bg-gray-950/60 dark:text-gray-200 dark:hover:bg-gray-900" href="https://github.com/Prompthon-IO/agent-systems-handbook/blob/main/SUPPORT.md" target="_blank" rel="noreferrer">
      <Icon icon="life-ring" size={14} />

      <span>Support guide</span>
    </a>
  </div>
</div>

Everyone is welcome to contribute. You do not need to decide whether you are a
learner, curator, builder, writer, or future maintainer before you start. Start
from the signal in front of you and choose the smallest public artifact that
would make the project clearer for the next reader.

I should contribute when:

* I feel confused by a concept and can name the missing beginner context.
* I find a broken setup step, outdated detail, bug, or missing feature.
* I notice a new AI signal, tool behavior, source project, or practitioner
  workflow that the handbook should track.
* I can turn an AI-assisted investigation into a clearer explanation, issue,
  prompt, example, or package.
* I want to practice public project work by asking a better question, opening an
  issue, improving a page, or recording useful Discord activity.

## What you can contribute

<CardGroup cols={2}>
  <Card title="Lab Article" icon="book-open" href="/contributor-kit/article-guidelines">
    An evergreen handbook page for a concept, pattern, system, or case study.
  </Card>

  <Card title="Case Study Project" icon="code" href="/contributor-kit/source-project-guidelines">
    A repo-owned example, starter, or case-study project that helps readers
    practice with real structure.
  </Card>

  <Card title="Skill Package" icon="wand-magic-sparkles" href="/contributor-kit/skill-package-guidelines">
    A local-agent workflow package with clear instructions, helper files, and
    enough documentation to review or run it.
  </Card>

  <Card title="Discord Activity Record" icon="discord" iconType="brands" href="/contributor-kit/discord-activity-record">
    Participate in Discord discussions and record useful questions, decisions,
    and follow-up work for the project.
  </Card>
</CardGroup>

## Fresh start path

1. Pick the contribution direction that matches your signal or question.
2. Open the matching card above and read the page for that contribution type.
3. Ask AI to help you clarify the signal, compare it with the guidance, and
   shape the next artifact.
4. If the shape is still unclear, ask in Discord `#handbook-contributors` with
   the signal, context, and the draft direction AI helped you form.
5. Continue from the specific guidance page once the contribution type is clear.

## Community links

* [Discord](https://discord.gg/sDE2HhGTg4): ask early contributor questions and
  route unclear ideas.
* [Contributor Kit](/contributor-kit): use this after you know what kind of
  contribution you are making.

## Why signal-driven contribution matters

Prompthon Agentic Labs encourages learners to treat curiosity, confusion,
friction, and new AI signals as the beginning of contribution. Static materials
are useful, but the strongest learning trigger is often a signal: a new
observation from AI Signals, a broken setup step, a missing explanation, a
feature idea, or a question that keeps coming back.

AI assistants can help you investigate the signal, name the problem, test your
understanding, compare possible fixes, and shape the next artifact. But AI does
not take initiative by itself. It does not decide what is worth improving.
Humans do. That is why this community values learners who actively notice
signals and turn them into GitHub issues, bug reports, feature requests, small
fixes, prompts, source notes, or draft handbook improvements.