---
title: "Guides"
description: "Task-shaped instructions for working with Hem in a real project."
image: "https://hem.run/social/hem.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://hem.run/llms.txt
> Use this file to discover all available pages before exploring further.

# Guides

These guides assume you already know what you want to do and need the steps to do it. They branch where real projects branch, and they link to [reference](/reference) rather than repeating option tables. If you are still learning the language, start with [the tour](/).

## Setting up

[Add Hem to a Vite project](/guides/set-up-a-project) covers installing the plugin, pointing it at your existing tsconfig, handling JSX, and deciding what to do with the generated siblings.

[Check and build from the command line](/guides/use-the-cli) covers CI gating, emitting without Vite, watch mode, formatting checks, and a minimal job you can copy.

[Test Hem modules](/guides/test-hem-code) covers `hem test`, filters and watch mode, pointing the JSX transform elsewhere, and testing against a different Effect transport.

[Set up your editor](/guides/editor-setup) covers the VS Code extension, format on save, quick fixes, and connecting other editors to the language server.

## Working in a mixed codebase

[Keep other tools off generated files](/guides/integrate-generated-files) covers formatter, linter, coverage, and watcher configuration so nothing else tries to own Hem's output.

[Enable the Effect extension](/guides/enable-effect) covers configuring the transport, what the capability probe checks, and what changes in your code once it is on.

[Migrate TypeScript to Hem](/guides/migrate-typescript) covers reading a readiness report, applying the safe subset, handling refusals, and where the automated path stops and judgment starts.

Source: https://hem.run/guides/index.mdx