explaingit

coleam00/helpline

27PythonAudience · developerComplexity · 3/5ActiveSetup · moderate

TLDR

A pretend B2B helpdesk monorepo that serves as a worked example of an AI Layer (CLAUDE.md hierarchy, hooks, skills, subagent, MCP, plugin) for making Claude Code productive in large codebases.

Mindmap

mindmap
  root((helpline))
    Inputs
      Codebase
      Session events
      Agent prompts
    Outputs
      CLAUDE.md updates
      Skill bundles
      MCP search results
      Validator report
    Use Cases
      Study an AI Layer
      Install the plugin
      Template your own layer
    Tech Stack
      Python
      uv
      pytest
      pyright
      MCP
      Claude Code

Things people build with this

USE CASE 1

Study a realistic multi-service codebase to see how a CLAUDE.md hierarchy, hooks, skills, and an MCP fit together.

USE CASE 2

Install the helpline-ai-layer Claude Code plugin to add a self-improving Stop hook, explorer subagent, and codebase-search MCP to another repo.

USE CASE 3

Diff commit 1 against commit 2 to see exactly what an AI Layer adds to a codebase.

USE CASE 4

Copy the shape of the per-service CLAUDE.md files and domain-scoped skills as templates for your own monorepo.

Tech stack

PythonuvpytestpyrightMCPClaude Code

Getting it running

Difficulty · moderate Time to first run · 30min

Needs uv and the dev extras installed, plus Claude Code if you want to actually use the plugin and hooks against the repo.

License is not stated in the available content.

In plain English

Helpline is not a real product, even though it is written as if it were. The README is upfront about this: Helpline is a demonstration codebase that goes with a YouTube video called 'The AI Layer: How to Make Claude Code Work in Large Codebases.' The pretend product is a B2B helpdesk and customer-support platform, built as a monorepo with five services (api, auth, billing, notifications, search) and two shared internal packages (core, db). It is meant to be the kind of mid-sized, multi-service codebase where an AI coding assistant either earns its keep or quietly makes a mess. The point of the repo is to show what the author calls an 'AI Layer.' This is their term for the set of configuration files, hooks, skills, and tooling you put around a codebase so an AI agent like Claude Code can work productively inside it. The README links to an Anthropic blog post that describes the same idea at a high level and says that Helpline is the practical version: each component from that article actually built, validated, and committed in this repo. The AI Layer here has several named parts. There is a hierarchy of CLAUDE.md files, one at the root and one per service or package. There are session hooks: one that orients the agent at start, and one that reflects on what happened at the end and proposes edits to those CLAUDE.md files. There are skills scoped to specific paths in the repo, such as billing-money-rules and api-add-route. There is a read-only 'explorer' subagent that maps a subsystem without changing files, a Language Server setup using pyright, and a custom MCP server called codebase-search that offers structured queries. The git history is laid out so that commit 1 is Helpline without the AI Layer and commit 2 adds the whole thing. The README also explains how to take what you learn here back to your own codebase. The portable parts are bundled as a Claude Code plugin called helpline-ai-layer, which you can install with two plugin commands. The non-portable parts (the actual CLAUDE.md files and the domain-specific skills) are intended as templates whose shape you copy and whose content you replace. To run the project itself you clone it, run uv sync --extra dev, then uv run pytest, plus a separate validator script that checks every AI Layer component end to end.

Copy-paste prompts

Prompt 1
Walk me through the helpline-ai-layer plugin and tell me which pieces I should install in my own Node monorepo and which I should rebuild as templates.
Prompt 2
Read AI-LAYER.md and the .claude folder in this repo, then build a comparable AI Layer for my codebase with a CLAUDE.md hierarchy, hooks, an explorer subagent, and an MCP search server.
Prompt 3
Compare commit 1 and commit 2 of helpline and summarise every file the AI Layer adds, grouped by component (hooks, skills, MCP, subagent, plugin).
Prompt 4
Show me how the self-improving Stop hook in helpline reflects on a session and proposes CLAUDE.md edits, then port it to a repo that uses a flat CLAUDE.md instead of a hierarchy.
Prompt 5
Run uv sync extra dev and uv run pytest on a clean clone of helpline, then run the validator script and explain any AI Layer check that fails.
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.