# Overview (/web/guides)



Use these guides when you want the working sequence between product surfaces,
not just route-by-route descriptions.

<Cards>
  <Card title="Project Workflow" href="/web/guides/project-workflow" description="Connect GitHub, confirm App coverage, sync repos, open a workspace, and choose the right next surface." />

  <Card title="Connection Scope and Overrides" href="/web/guides/connection-scope-and-overrides" description="Decide when an integration should be global, project-scoped, or explicitly excluded in one repo." />

  <Card title="GitHub App Coverage" href="/web/guides/github-app-coverage" description="Understand OAuth vs App coverage, why repos can be visible but not triggerable, and how to verify the right install." />

  <Card title="Choose the Right Routing Surface" href="/web/guides/choose-routing-surface" description="Decide when to use Triggers, Assignments, or Automations instead of overbuilding the workflow." />

  <Card title="GitHub Mention Routing" href="/web/guides/github-mention-routing" description="Learn the exact difference between @mogplex and @mogplex/<agent-slug>, plus how mention routing works in Triggers and Automations." />

  <Card title="Legacy Routes" href="/web/guides/legacy-routes" description="Map older route names like /flows, /library, and /primitives onto the current Mogplex surfaces." />
</Cards>

## Start here if... [#start-here-if]

* you are setting up a repo for the first time:
  [Project Workflow](/web/guides/project-workflow)
* you can see repos, but trigger-backed surfaces still look empty:
  [GitHub App Coverage](/web/guides/github-app-coverage)
* one repo should have different tool access than the rest of your account:
  [Connection Scope and Overrides](/web/guides/connection-scope-and-overrides)
* you are not sure whether the job belongs in Triggers, Assignments, or
  Automations:
  [Choose the Right Routing Surface](/web/guides/choose-routing-surface)
* mention routing is not behaving the way you expected:
  [GitHub Mention Routing](/web/guides/github-mention-routing)
* older bookmarks or route names are confusing:
  [Legacy Routes](/web/guides/legacy-routes)

## Use the guides differently from the route docs [#use-the-guides-differently-from-the-route-docs]

The route docs explain what each page is for.

These guides explain:

* which page to start from
* what prerequisite state must already exist
* what common failure mode to check next
* how to move between setup, routing, and runtime inspection without guessing

If you already know the surface you need, go back to the route docs.

If you know the problem but not the next page, start here.