# CHUDCS2 (/docs)

Architecture, setup, features and development notes for the Linux overlay.

CHUDCS2 is a C++20 Linux application that reads Counter-Strike 2 state, renders a transparent OpenGL and Dear ImGui overlay, and includes a C++ unit-test harness.

<Cards>
  <Card
    title="Install and run"
    href="/docs/installation"
    description="Install Arch Linux dependencies, build the binary and launch the live overlay."
  />
  <Card
    title="Architecture"
    href="/docs/concepts/architecture"
    description="Follow game data from ingestion through frame preparation, rendering and input."
  />
  <Card
    title="Feature list"
    href="/docs/concepts/features"
    description="See the visual overlay, grenade tools, input helpers and diagnostics in the current tree."
  />
  <Card
    title="Develop"
    href="/docs/guides/development"
    description="Use the repository layout, build targets and workflow for code changes."
  />
</Cards>

## Where to start [#where-to-start]

- New users: [Installation](/docs/installation), then [Quick start](/docs/quick-start).
- Code changes: [Architecture](/docs/concepts/architecture), [Project layout](/docs/reference/project-layout), and [Development](/docs/guides/development).
- Test changes: [Testing](/docs/guides/testing) and [Packet layout](/docs/reference/shared-memory).
- Feature workflows: [Keybinds](/docs/guides/keybinds), [Web radar](/docs/guides/web-radar), and [Grenade authoring](/docs/guides/grenade-authoring).
- Profiles and appearance: [Manage profiles](/docs/guides/profiles), [Visual settings](/docs/guides/visual-settings), and [Focus and shortcuts](/docs/guides/focus-and-shortcuts).
- Runtime tuning: [Configuration](/docs/concepts/configuration), [Launch options](/docs/reference/launch-options), and [Display scaling](/docs/guides/display-scaling).
- Performance: [Performance tuning](/docs/guides/performance) and [Collect diagnostics](/docs/guides/diagnostics).
- Failures: [Troubleshooting](/docs/guides/troubleshooting).

## Repository conventions [#repository-conventions]

The executable expects `assets/`, `offsets.json`, and configuration data beside the binary. Build output is normally written to `build/`. The docs in this site describe the source tree as it exists in the repository, including the optional `AimAssist` module.