Skip to content

Getting started with Claude Code

What to request, what to install and what to click, from the day you join to the day your first change is live on www.leahydocumentation.com.

This page is for a new team member who will help maintain this documentation site. Where to start is the page that routes you here and sets the time it takes; How this site works explains what GitHub, Claude and Cloudflare each do and why the site is built this way. This page is the sequence you follow to start working: the two accounts to request, the one-time connection between them, and your first change through to the published site. What lives where is the companion to it: what sits on your computer, what sits on your Claude account, and which of the two actually holds the access.

Set aside about half an hour of your own time. Most of the calendar time is waiting on two invitations, and they can be requested on the same day.

What you need, and who grants it

Five things have to be in place. Two of them are seats that someone else has to grant, so ask for both before you start.

What you need What it gives you Who grants it
A Claude seat in the Leahy Consulting organization on claude.ai Claude Code, in the desktop app and at claude.ai/code, billed to the firm rather than to you An Owner or Admin of the claude.ai organization
The Claude desktop app on your Mac or PC The Code tab, where you run sessions You — it's a download, with no license key to enter
Membership of the Leahy-Consulting organization on GitHub, with Write access to the Documentation repository Permission to read the site's files, push a branch and merge a pull request An Owner of the GitHub organization
The Claude GitHub App authorized for your GitHub account Lets a Claude session clone the repository and push branches on your behalf You, sometimes with an Owner's approval
A cloud environment The machine your sessions run on, in Anthropic's cloud rather than on your laptop Created for you the first time you connect

The Claude seat and the GitHub membership are granted by two different companies, and neither knows about the other:

ANTHROPIC · CLAUDE.AI Leahy Consulting organization grants your Claude seat, which carries Claude Code administered by a claude.ai Owner or Admin GITHUB Leahy-Consulting organization grants membership and Write access to the Documentation repository administered by a GitHub organization Owner You connect the two, once by authorizing the Claude GitHub App A cloud session on the site Leahy-Consulting/Documentation
Two front doors, kept by two different companies. A Claude seat gives no GitHub access, and GitHub membership gives no Claude seat.

For account managers

The links in each step below go straight to the page where the access is granted. The two that need an administrator are the Claude seat, granted under Organization settings → Members on claude.ai, and GitHub organization membership at github.com/orgs/Leahy-Consulting/people.

The screens on this page are drawn rather than photographed, so they show the controls that matter without going stale every time a button moves. Claude and GitHub both change wording occasionally; if a label reads a little differently on your screen, the position and the purpose still hold.

Step 1 — A Claude seat in the Leahy Consulting organization

Claude Code is part of a Claude seat, and the seat has to sit inside the firm's claude.ai organization. A personal Pro subscription will run Claude Code, but it won't carry the organization's settings, shared sessions or billing, so ask for a seat on the firm's plan instead.

Send your work email address to an Owner or Admin of the claude.ai organization and ask for a Claude seat with Claude Code. They do this in Organization settings → Members:

claude.ai — Organization settings LEAHY CONSULTING Members Organization and access Billing Claude Code Connectors Members Add member 1 Premium seats 6 of 8 used · Standard seats 3 of 5 used NAME ROLE TIER Tom Lanham [email protected] Owner Premium ▾ Anthony Feria [email protected] Admin Premium ▾ New teammate invitation sent — waiting to be accepted Member Premium ▾ 2
The Members page on claude.ai, where a seat is granted and its tier is set.
  1. Add member — the administrator enters your work email address and sends the invitation. Several people can be added at once from the same button.
  2. Tier — the dropdown assigns the seat. Claude Code comes with a Team seat either way; a Premium seat carries a larger usage allowance, which is what a long documentation session actually consumes. Ask for Premium if one is free.

You will get an email invitation. Accept it, sign in at claude.ai, and check the account switcher in the bottom left corner: it should name Leahy Consulting, not Personal. If it says Personal, switch to the organization before you start any documentation work.

For account managers. Seats are granted and reassigned under Organization settings → Members, reached from the account switcher on claude.ai. Anthropic's own instructions are in Manage members on Team and Enterprise plans and Purchase and manage seats on Team plans. Organization-wide Claude Code settings sit separately at claude.ai/admin-settings/claude-code.

Step 2 — Install the desktop app and sign in

Claude Code runs in the Code tab of the Claude desktop app. Download it, install it, launch it and sign in with the work email address that now holds your seat:

The reference for everything the app can do is the Claude Code desktop documentation.

Claude Chat Cowork Code 1 + New session SESSIONS A/P reconciling guide Fix physical inventory path Leahy Consulting [email protected] 2 What should Claude work on? Local ▾ Choose a folder ▾ ➤ Nothing is configured yet — the next three steps set the environment and the repository this session works in.
The Code tab on a fresh install: a session list on the left, and a prompt box that isn't pointed at anything yet.
  1. Code — the app has three tabs. Chat is ordinary Claude, Cowork is for longer non-code work, and Code is the one that edits this site. Everything on this page happens in Code.
  2. Account — confirm the switcher at the bottom of the sidebar shows Leahy Consulting.

On Windows, the Code tab needs Git for Windows installed before it will open; install it and restart the app. On a Mac there is nothing else to install.

Step 3 — A GitHub account in the Leahy-Consulting organization

The site's files live in the Leahy-Consulting/Documentation repository on GitHub. You need your own GitHub account, and that account needs to be a member of the organization with Write access to the repository. Write is what allows a branch to be pushed and a pull request to be merged; Read is not enough.

If you don't have a GitHub account yet, create a free one at github.com/signup, using your work email address so an Owner can find you. Then send your GitHub username to an Owner of the organization.

github.com/orgs/Leahy-Consulting/people Leahy-Consulting Overview Repositories People Teams Settings Find a member… Invite member 1 tlanham Tom Lanham Owner aferia Anthony Feria Owner your-username invitation pending Member · Write access 2
The People page of the GitHub organization, where membership is invited and repository access is set.
  1. Invite member — the Owner enters your username or work email and sends the invitation. The Member role is the right one; Owner is not needed to write documentation.
  2. Write access to Documentation — membership alone doesn't grant access to a repository. The Owner adds you to a team that has Write on Documentation, or grants it directly on the repository in Settings → Collaborators and teams.

Accept the invitation from the email GitHub sends, or from your organization memberships, which lists anything still pending. Then open github.com/Leahy-Consulting/Documentation and confirm you can see the repository while signed in. If the page 404s, the invitation hasn't been accepted or the access hasn't been granted yet.

The organization may require two-factor authentication before it will let you in. Turn it on at GitHub → Settings → Password and authentication. An authenticator app takes a minute, and GitHub will prompt you for a set of recovery codes worth keeping.

For account managers. Invitations are sent from github.com/orgs/Leahy-Consulting/people. Teams are at github.com/orgs/Leahy-Consulting/teams, and per-repository access at Documentation → Settings → Collaborators and teams. GitHub's own instructions: Inviting users to join your organization.

Step 4 — Connect Claude to GitHub, once

Claude needs your permission to reach the repository on your behalf. This is a one-time authorization of the Claude GitHub App, and it is done from your own account: no administrator can do it for you.

Start it either from the desktop app, where picking Cloud as the environment prompts you, or in a browser at claude.ai/code, which prompts on first use. You can also go straight to the app's own page, github.com/apps/claude, and click Install. All three land on the same GitHub page:

github.com/apps/claude — Install & Authorize Install Claude Claude would like permission to read and write code, branches and pull requests. INSTALL ON your-username (your personal account) Leahy-Consulting 1 REPOSITORY ACCESS All repositories Only select repositories Leahy-Consulting/Documentation 2 Install & Authorize 3 Not an Owner of Leahy-Consulting? GitHub records a request instead, and an Owner approves it in the organization's third-party access settings.
The one-time GitHub authorization. Installing on the organization, rather than on your personal account, is what puts the Documentation repository in reach.
  1. Install on Leahy-Consulting — choose the organization. Installing only on your personal account leaves the firm's repositories out of reach.
  2. Only select repositories → Documentation — narrow it to the repository you actually work in. You can add more later.
  3. Install & Authorize — GitHub asks you to confirm, and returns you to Claude.

If you are not an Owner of the GitHub organization, GitHub turns this into a request for approval rather than an installation. An Owner approves it under the organization's third-party access settings at github.com/organizations/Leahy-Consulting/settings/installations. You can see and adjust your own authorization afterwards at github.com/settings/installations.

You do this once, and not once per machine. The authorization is attached to your Claude account rather than to the computer you performed it on, so the next device you sign in from, whether a second laptop, a browser or the phone app, finds the repository already in the selector. The same fact runs the other way: deleting Claude off a laptop revokes nothing. What lives where sets out the three places the setup is held and how to take access away when you need to.

The App narrows the webhooks, not the access

Choosing Only select repositories controls which repositories Claude receives GitHub events for. It does not fence off the rest of GitHub: a session can reach any repository your GitHub account can see, which is why Step 3 grants membership deliberately rather than broadly. What lives where sets out what a session's reach actually depends on.

Step 5 — Run your sessions in the cloud

A Claude Code session can run on your own machine or on a machine Anthropic provides. We use the cloud for documentation work:

Cloud session Local session
Where the files are Cloned fresh from GitHub each session A working copy on your laptop
What you install Nothing Git, Python, MkDocs and the theme
If you close the laptop The session keeps running It stops
Where you can watch it The desktop app, claude.ai/code or the Claude phone app The app on that machine
What everyone gets The same environment Whatever that machine happens to have

What lives where compares the same pair for reach, which is the comparison that matters when someone asks what Claude had access to.

There is a concrete reason behind the preference. The site's pages are generated by MkDocs, so a change to anything under hub-src/docs/ has to be rebuilt before it publishes. In a cloud session Claude installs what the build needs and runs it. Locally, that toolchain becomes your problem.

The first time you connect, Claude creates a cloud environment called Default with Trusted network access, which reaches the common package registries and nothing else. That is the right environment for this site; there is nothing to configure.

Claude — Code — new session What should Claude work on? Cloud ▴ Local — this machine Cloud — Default · Trusted network ✓ SSH connection… + Add cloud environment 1 Pick Cloud, and leave the Default environment as it is. Nothing here needs configuring for this site.
The environment dropdown. Choose Cloud once and the app remembers it for the next session.

A cloud session stops after a spell of inactivity and its machine is reclaimed. Nothing is lost: reopen the session and it comes back with the conversation intact on a fresh machine.

A running session can be watched from anywhere you are signed in: the desktop app, claude.ai/code, or the Claude app for iPhone and iPad or Android. A session follows your Claude account rather than the machine it started on, which is the subject of What lives where. The full reference for cloud sessions is Claude Code on the web, and the environment settings are documented under cloud environments.

Step 6 — Start a session on the Documentation repository

Click + New session in the sidebar, or press Cmd+N on a Mac or Ctrl+N on Windows. Then set four things in the prompt area before you type anything:

Correct the menu path in the physical inventory guide: it should read Inventory Management → Trx → Physical Inventory Count Entry. Cloud ▾ 1 Leahy-Consulting/Documentation ▾ 2 + main ▾ 3 Opus 5 ▾ Accept edits ▾ 4 Press Enter to start. The session clones the repository, and from here on you steer it in plain English.
The prompt area of a new session, set for documentation work: cloud environment, the Documentation repository, branched from main.
  1. Environment: Cloud — as set in Step 5.
  2. Repository: Leahy-Consulting/Documentation — the repository selector sits under the prompt box. The + beside it adds a second repository, which documentation work almost never needs.
  3. Branch: main — start from main so you are editing the site as it stands today. Claude makes its own branch for the change; you don't create one by hand. Pick a different branch only when you are continuing work that is already in flight.
  4. Permission mode — Accept edits lets Claude make its changes and push a branch without stopping at each file, and it is the sensible default here: nothing it writes reaches the live site until a person merges it. Switch to Plan for a large job, such as restructuring a section, when you want to approve the approach before any file changes.

The model sits at the end of that row, and the effort setting sits inside the model picker. Both are Step 7. Neither is locked in when the session starts, so if you would rather begin typing, the defaults are sound.

Check the repository selector every time

The selector remembers whatever you used last. Sending a documentation request into a different repository wastes the session, and the first thing you'll notice is Claude reporting that it can't find the page.

Step 7 — Choose the model and the effort

Two settings sit next to the send button and decide how Claude approaches the work. Both can be changed in the middle of a session. The change takes effect on your next message, and nothing in the conversation is lost.

THE MODEL PICKER, BESIDE THE SEND BUTTON Opus 5 ▴ the usage ring Opus 5 complex reasoning and multi-step work ✓ Sonnet 5 everyday edits, quicker, lighter on usage Haiku 4.5 short, simple, mechanical jobs Fable 5 the largest jobs, where the seat allows it EFFORT low medium high xhigh max high is the default — leave it there CLICK THE RING TO SEE WHERE YOU STAND 61% THIS SESSION Context window 38% — Claude compacts it for you YOUR PLAN ALLOWANCE Five-hour window 24% This week 61% — resets Thursday
The model picker with the effort slider beside it, and the usage ring that answers "how much have I used?" in one click.

The model

Several Claude models are available, and they differ in how much reasoning they bring and how much of your allowance they consume:

Model What it is for
Opus 5 Complex reasoning and multi-step work. Use this for documentation work for now.
Sonnet 5 Everyday edits. Quicker to answer and lighter on your allowance, with less depth on a tangled job
Haiku 4.5 Short, simple, mechanical jobs where speed is the point
Fable 5 The largest jobs — work you would otherwise split across several sittings. It investigates before acting and checks itself more. Available where the organization's plan reaches it

Opus 5 is the recommendation for now. Documentation work is judgment work: deciding which of six pages a rename touches, whether two source documents contradict each other, whether a paragraph reads like us. That is what the strongest reasoning model is for, and the cost of a wrong page is a customer reading it.

Treat that as a recommendation with a date on it. Anthropic releases new models several times a year, and each one shifts the balance. The picker always lists what your seat can reach, so when a name you don't recognize appears, ask; this page will be updated rather than left to go stale.

To change it mid-session, open the picker beside the send button and choose another model, or type /model sonnet in the prompt box. Either way the switch applies from your next message, and the conversation carries over intact. In a cloud session, type the name as an argument, /model sonnet, rather than expecting a picker to open.

Effort

Effort is how much thinking Claude does before it acts. At a low level it answers more directly; at a high level it works the problem out first, considers alternatives and checks itself. Five levels are available on Opus 5 and Sonnet 5: low, medium, high, xhigh and max.

Leave it on high. That is the default, and it is the balance point: deep enough for real work without spending reasoning on a two-line fix. Move it only for a specific reason:

Level When it earns the change
low or medium A batch of mechanical edits: renaming a module across pages, reformatting a table, fixing a repeated link
high Everything else, including writing and rewriting pages. The default
xhigh A genuinely hard one-off: reconciling two source documents that disagree, or restructuring a section and its navigation together
max Rarely. It reasons deepest but can overthink a straightforward job, and it lasts only for the current session

Set it from the slider inside the model picker, or with /effort followed by a level. The level in force shows next to the model name in the session header, so you can tell at a glance.

One deep answer without changing the setting

Put the word ultrathink anywhere in your prompt and Claude reasons harder on that turn only. Useful when one question in an otherwise ordinary session deserves more thought.

What this uses, and how to keep track

Everything Claude does is counted in tokens. A token is a small piece of text, roughly three-quarters of a word, so a page of documentation is about 700 of them. Everything Claude reads counts: your prompt, the files it opens, the output of the commands it runs. So does everything it writes, including the thinking it does along the way.

Your seat carries an allowance, not a bill. Usage draws against two windows, a rolling five-hour one and a weekly one, and the allowance is shared with Claude chat and Cowork. Its size depends on whether your seat is Standard or Premium. Cloud sessions draw on the same allowance as local ones, and the cloud machine itself costs nothing extra. If you exhaust a window, Claude says so and tells you when it resets.

Four things move the needle, in roughly this order:

  • How long the session has been open. The whole conversation goes to Claude with every message, so a session left open all day draws on your allowance even for a one-line question. Starting a new session for unrelated work is the single most effective habit, and it costs nothing.
  • The model. Opus 5 consumes more than Sonnet 5 for the same job; Haiku 4.5 consumes least.
  • The effort level. Thinking is counted like everything else Claude writes, so xhigh and max cost more than high, and low costs less.
  • The size of the job. A batch of 30 documents through doc-intake is a different order of work from correcting a menu path.

Three ways to see where you stand, in order of convenience:

How What it shows
Click the usage ring beside the model picker The context window for this session, and your plan usage for the current period
Type /usage Plan usage bars plus a breakdown of what consumed them, with d and w to switch between the last day and the last week
Type /context What is occupying the context window right now

The /usage figures are computed from this machine's own session history, so they are close rather than exact, and they don't include what you used on another device. Administrators have the authoritative view: the Claude Code analytics dashboard and the spend report in organization analytics.

Running out is not a problem to hide

Hitting a limit means the work was substantial, not that something went wrong. Tell an Owner or Admin: seats can be moved to a Premium tier, and usage credits can be turned on for the organization so work continues past the allowance.

Step 8 — Write the prompt, and use a skill with /

Sessions are conversations. Describe the change in plain English, name the page or the product if you know it, and say what the reader should end up with. Claude finds the files.

Correct the menu path in the physical inventory guide: it should read Inventory Management → Trx → Physical Inventory Count Entry. Check whether any other page repeats the old path.

Some jobs are procedures rather than one-off requests, and those are written down in the repository as skills: instructions Claude loads when it needs them. Two live in this repository, so everyone who opens a session on it gets both:

  • doc-intake — the pipeline that turns a batch of source documents into published pages: duplicate check, archiving the original, writing the page, re-annotating screenshots, recording the decision in DOCUMENT-MAP.md and rebuilding the hub.
  • leahy-prose — the house voice and terminology guide. Claude loads this one on its own whenever it writes anything a customer will read.

Neither is left to memory. The repository carries a CLAUDE.md that loads at the start of every session and names both skills, and a hook that reminds Claude of the style guide whenever an edit lands on a page under hub-src/docs/. A local session asks you to trust the workspace the first time you open it, because a repository can define hooks; accept it for this one. Cloud sessions pick both up from the clone with nothing to confirm.

Type / in the prompt box to see what's available, or click the + button and choose Slash commands:

TYPING A SLASH OPENS THE LIST /doc | /doc-intake Process new source documents into published pages /leahy-prose The house voice and terminology guide /code-review Review the changes on this branch 1 Arrow keys to move, Enter to choose DRAG THE FILES IN, THEN DESCRIBE THE BATCH ap-white-papers.zip ✕ /doc-intake Two new A/P white papers — check them against the library, then publish what's new under Macola® guides → Accounts payable. ➤ Enter sends it. Claude extracts the archive, works through the intake procedure and reports what it found.
Invoking a skill: type /, choose it, drag the documents in and describe the batch. The skill supplies the procedure, and your sentence supplies the specifics.

Handing the documents over

Give the files to Claude in the session. Drag them into the prompt box, say what they are, and let Claude do the handling: extracting a zip, naming each file in the site's lowercase-hyphenated convention, filing the original under source-documents/originals/, writing the pages, recording each decision in DOCUMENT-MAP.md, rebuilding the hub and committing the lot. Nothing about the batch has to be tidy before you hand it over, and nothing has to be renamed or placed by hand.

For a large batch, zip it and hand over the one archive. That keeps the batch together for the duplicate check, which compares every candidate against the library and against the rest of the batch.

Attachments aren't offered on every surface, and the + button beside the prompt is absent in cloud sessions. If the prompt box won't take the files, two routes end up in the same place:

Situation What to do
The folder or archive is already on your machine Run that one session with Environment: Local and name the path: "the batch is in ~/Downloads/ap-batch.zip". Claude reads it straight off the disk, which is the least fuss for a large batch.
You are working in a browser Download the files, then Add file → Upload files with Create a new branch for this commit, and name that branch in your prompt

A cloud session's network reaches the package registries and little else, so it cannot pull a batch out of Google Drive or a file share by itself. Download the files first, or use a local session, where the Google Drive connector is available from the + button.

You don't have to type /doc-intake at all. Say "here are three new fact sheets to add" and Claude recognizes the job and loads the skill itself. The slash is for when you want to be certain which procedure it follows.

Step 9 — Review what Claude changed

When Claude finishes, a diff indicator appears in the session showing lines added and removed, such as +128 −14. Click it. The file list is on the left, the changes on the right.

Changes +128 −14 Review code Create PR 3 FILES CHANGED hub-src/docs/macola-guides/ accounts-payable/reconcile.md hub-src/mkdocs.yml macola-guides/accounts- payable/reconcile/index.html sitemap.xml DOCUMENT-MAP.md The built pages and the sitemap change too — that is the rebuild, and it belongs in the change. 1 − Open the **Inventory → Trx → Count Entry** screen and + Open the **Inventory Management → Trx → Physical + Inventory Count Entry** screen and key in the counts recorded on the tags, one warehouse at a time. Your comment on this line "This path is Progression only — say so, and give the ES path too." 2 Comments queue up and go to Claude with your next message, so it knows which line you meant without you describing where it is.
The diff view. Every changed file is listed, including the rebuilt pages, and a comment can be pinned to the line it is about.
  1. The built output is part of the change. Editing hub-src/docs/… is only half of a page change; the site Cloudflare publishes is the built HTML at the repository root. If a change touches only hub-src/ and no built pages, the rebuild hasn't run and the live site won't move. Ask Claude to rebuild the hub.
  2. Comment on the line, not in a paragraph. Click a line, type the correction, press Enter. Send several at once with Cmd+Enter on a Mac or Ctrl+Enter on Windows, and Claude picks them up with your next message.
  3. Create PR opens a pull request when you want one. Step 10 covers both routes to the live site.

Two questions are yours to answer, and Claude can't answer them for you: is it true, and does it read like us? Formatting, links, house voice and the rebuild are Claude's job to get right before you look. Menu paths, version differences and the question of whether a customer would recognize the advice are yours.

Step 10 — Get the change into main

main is the branch Cloudflare publishes. Anything merged into it is live about a minute later.

A pull request is optional, and the short route suits a small, obviously safe change. Nothing in the tools requires one, so when the diff is a typo, a corrected menu path or a single paragraph and it looks right, tell Claude to commit it to main.

Commit this to main.

That is the whole step. Claude commits, pushes, and Cloudflare publishes about a minute later. Nothing is lost by skipping the pull request: every commit carries its author, date and message, and any commit can be reverted, including one merged months ago. The whole record is the commit history of main.

Everything else earns a pull request. It is a second pair of eyes rather than a gate you have to pass:

When to open one Why
A new page, or a section you rewrote from a source document Someone else reads it before a customer does
You are new to the site and would rather have a colleague look first The diff is easier to talk about on GitHub than over a screen share
A change that touches several pages at once The pull request shows all of it in one place
Anything you are unsure about Merging can wait; the branch keeps until you decide

To open one, click Create PR in the diff view, or say "open a pull request for this". Asking Claude works even when the app's own button asks you to install the GitHub command-line tool first. Give it a title that says what changed rather than which files moved, and let Claude write the description from the diff.

Either way, the session stays live afterwards: paste a reviewer's comment or a failing check into the chat and Claude works on it in the same conversation.

Step 11 — Reviewing and merging a pull request

Skip this step until someone asks you to review one, or until you open one yourself.

If you are the second reader, the work is on GitHub. Open the pull request from the repository's Pull requests tab and read the Files changed tab.

github.com/Leahy-Consulting/Documentation/pull/128 Add the A/P reconciliation guide #128 Open Conversation Commits Checks Files changed 5 1 Review changes Comment Approve Request changes Submit review 2 ✓ Cloudflare Pages — preview build ready Open the preview to read the page as a reader will see it. This branch has no conflicts with the base branch. Merge pull request ▾ merge · squash · rebase 3 After the merge, nobody publishes anything. Cloudflare picks up the new files and rebuilds www.leahydocumentation.com worldwide in about a minute. Open the page and read it once on the live site — that is the last step.
The reviewer's side: read the diff, approve or ask for revisions, then merge. Publishing takes care of itself.
  1. Files changed — read the diff, not the summary. Comment on any line by hovering it and clicking the +.
  2. Review changes → Approve, or Request changes with what needs to differ. Choose Request changes when something is wrong on the page, not when you would have phrased it differently.
  3. Merge pull request — the plain merge keeps the history as a list of reviewed merges, which is what the repository's history already reads like. Delete the branch when GitHub offers; the commits stay in main.

What to look for, in the order that catches the most:

  • Is it true? Menu paths, status codes, version differences, account numbers. This is the only thing a reviewer can catch that nothing else will.
  • Does it read like us? Professional, cordial, concrete. Promotional adjectives standing in for facts are the usual slip.
  • Can a reader find it? A new page needs its entry in the navigation (hub-src/mkdocs.yml) and in the index of the section it belongs to.
  • Did the rebuild run? Built pages at the repository root should change alongside the Markdown source.
  • Is the record kept? A page written from a source document needs its row in DOCUMENT-MAP.md and the original archived under source-documents/originals/.

A minute after the merge, open the page on www.leahydocumentation.com and read it once as a reader will see it. That is the last step, and it catches the things a diff hides.

If GitHub reports a conflict instead of a clean merge, nothing is broken and nothing has published. Two branches changed the same lines, most often the navigation list, because every new page adds a line to it. Say so in the session and Claude resolves it, and the resolution shows up in the pull request like any other change. When branches collide sets out what Claude settles on its own and what a person has to decide.

When something goes wrong

What you see What it means What to do
No repositories in the selector The GitHub connection is missing, or your account can't see the repository Redo Step 4, then confirm you can open the repository on github.com while signed in
Only a GitHub sign-in button at claude.ai/code The Claude GitHub App was never authorized Step 4
"Not available for the selected organization" Claude Code on the web isn't enabled for the claude.ai organization Ask an Owner to check claude.ai/admin-settings/claude-code
The session is marked expired The machine was reclaimed after a quiet spell Reopen the session; the conversation comes back
Claude can't push, or the merge button is greyed out Read access without Write Ask a GitHub Owner to grant Write on Documentation
The page looks right in the diff but the live site hasn't changed The hub wasn't rebuilt, so only the source changed Ask Claude to rebuild the hub and push again
A change published that shouldn't have Every commit is reversible Ask Claude to revert the commit; Cloudflare republishes the previous version
A session won't start at all Usually a capacity or service problem, not your setup Check status.claude.com, then try again in a minute
A second computer had the repository already, without asking you to authorize GitHub Expected. The connection belongs to your Claude account, not to a machine Nothing to fix — What lives where explains what is held where

If none of that fits, the app's own Help → Get Support menu reaches Anthropic, and our team is on the numbers at the bottom of this page.

Habits worth keeping

  • Start each session from the current main, so you are editing today's site.
  • One change at a time, small enough to read in a few minutes.
  • Read the page on the live site after it publishes.
  • If you do open a pull request, merge it within a few days. A branch that sits for a month is editing last month's site.
  • Say what you are working on, especially before restructuring a section. A conflict that planning prevents never needs resolving.

What lives where covers what your computer, your Claude account and GitHub each hold. How this site works covers what the three systems do and why. Current value and roadmap covers what the firm intends to do with all of it, and why the pages that matter most have to come from the people who know the answers. And CONTRIBUTING.md in the repository has the exact steps behind adding a product, a guide, a release-notes set or an annotated screenshot.

Every link on this page

Keep this section bookmarked; it is the whole guide in one screen.

Getting access

Purpose Link Who uses it
Grant or reassign a Claude seat Organization settings → Members on claude.ai claude.ai Owner or Admin
Anthropic's instructions for seats and members Manage members · Manage seats claude.ai Owner or Admin
Organization-wide Claude Code settings claude.ai/admin-settings/claude-code claude.ai Owner
Invite a GitHub organization member github.com/orgs/Leahy-Consulting/people GitHub Owner
Teams, and who is in them github.com/orgs/Leahy-Consulting/teams GitHub Owner
Write access to this repository Documentation → Settings → Collaborators and teams GitHub Owner
Approve the Claude GitHub App for the organization Third-party access → GitHub Apps GitHub Owner
Create a GitHub account github.com/signup You
Accept a pending organization invitation github.com/settings/organizations You
Turn on two-factor authentication github.com/settings/security You
Authorize, review or revoke the Claude GitHub App github.com/apps/claude · your installations You

Working

Purpose Link
Claude desktop app macOS · Windows · Windows ARM64 · Linux
Git for Windows, needed by the Code tab on Windows git-scm.com/downloads/win
Claude Code in a browser claude.ai/code
Claude on your phone, to watch a running session iPhone and iPad · Android
The repository Leahy-Consulting/Documentation
Upload source documents to a new branch Add file → Upload files
Open pull requests Pull requests
What changed, and when Commit history of main
The published site www.leahydocumentation.com
Service status, when a session won't start status.claude.com
Your organization's Claude Code adoption and spend Claude Code analytics

Reading

Purpose Link
Where to start, and how long each page takes Where to start
Finding your way around the published site Using this site
What the firm intends to build this site into Current value and roadmap
What is held on your computer, on your Claude account and on GitHub — and how to revoke it What lives where
How this site works — the three systems, and why How this site works
What goes where when adding content CONTRIBUTING.md
The house voice and terminology guide leahy-prose
The document intake procedure doc-intake
What became of each source document DOCUMENT-MAP.md · the reader-facing library
The desktop app, in full Claude Code desktop documentation
Cloud sessions and environments Claude Code on the web · Cloud environments
Skills, and how they load Skills
Models, aliases and effort levels Model configuration · Choosing a model and effort level
What draws on your allowance, and how to reduce it Manage costs
What a Standard and a Premium seat include Claude Code on Team and Enterprise plans
The session that wrote this page session transcript on claude.ai

This page as its own example

This page was written the way it tells you to work. A cloud session on Leahy-Consulting/Documentation, started from the Code tab, drafted the prose against the house style guide, drew every screen on it as inline SVG, added the navigation entry, ran ./tools/build-hub.sh, and committed the result to main: the same eleven steps, in the same order, with a person reading each draft and sending corrections back into the session.

The transcript is open for anyone who wants to see what that conversation actually looks like, including the wrong turns: the session that produced this page. Sign in with your Leahy Consulting account to open it.

Support & contact

Our team is glad to walk through any of this: the first session, a pull request you're unsure about, or a page that isn't publishing.