Skip to content

OpenHeartDevelopers/pycemrg-context

Repository files navigation

pycemrg-context

Suite-level context for AI agents (Claude Code) when consumers compose projects from the pycemrg library suite.

What this is for

When a user is building a project that needs pycemrg functionality ("extract atrial myocardium, then mesh it"), this repo lets Claude:

  1. Recommend which pycemrg libraries and functions to use
  2. Output the right install instructions per library (pip or git clone)
  3. Flag steps that aren't in the suite — distinguishing project-specific glue from things that look like missing suite capabilities

This is a consumer-side tool. It does not handle contribution back to the suite; that goes through normal GitHub Issues/PRs in the individual library repos.

Setup

macOS / Linux

git clone <url> ~/dev/pycemrg-context
cd ~/dev/pycemrg-context
./install.sh

The install script symlinks command files into ~/.claude/commands/ and skills into ~/.claude/skills/. Because they're symlinks, a git pull is picked up automatically; re-run only if files were added or removed.

Windows (PowerShell)

git clone <url> $HOME\dev\pycemrg-context
cd $HOME\dev\pycemrg-context
.\install.ps1

install.ps1 copies the same files into %USERPROFILE%\.claude (no symlinks, so no Developer Mode or admin needed). Because they're copies, re-run install.ps1 after every git pull to refresh the installed files.

If PowerShell blocks the script, allow it for the current process only: Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

Usage

In any Claude Code session, run:

/pycemrg-build

Then describe what you want to build. Claude will:

  1. Decompose the task into steps
  2. Ask you to confirm the decomposition
  3. Route to the relevant library source files
  4. Produce a build plan tagging each step as SUITE / PROJECT / GAP
  5. Output consolidated install instructions

Repo contents

File Purpose Maintained by
LIBRARY_REGISTRY.md One row per library: name, distribution, install Hand (you)
PYCEMRG_SUITE.md One-paragraph + capabilities per library CI (future) / hand
source/*.md Per-library API reference for consumers CI on push to main
commands/pycemrg-build.md The consumer slash command Hand
commands/export-api.md Prompt run by CI to generate source files Hand
pycemrg-docs/ Skill: scaffold/refresh a library's MkDocs site Hand

Adding a library to the suite

  1. Add a row to LIBRARY_REGISTRY.md
  2. Add a section to PYCEMRG_SUITE.md (until CI generates this)
  3. Set up the export-api CI workflow in the new library's repo (see docs/CI_SETUP.md — to be written when first CI workflow lands)
  4. Source file appears under source/ on the library's next push to main

Relationship to library CLAUDE.md files

Scope Location
Personal practices, manifest ~/.claude/CLAUDE.md
Suite-level consumer routing This repo
Library-specific commands + gotchas {library}/CLAUDE.md
Full per-library API reference source/{library}.md (this repo, CI-generated)

About

Suite-level context for AI agents (like Claude Code) when working across the pycemrg library ecosystem.

Resources

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors