core-ai
CLAUDE.md0 starsChanged 8 months agoMITView on GitHub
Monorepo containing Helius developer tools distributed as independent packages: The reference files in helius-skills/helius/references/ and helius-plugin/skills/build/references/ must be kept in sync. These are the canonical Helius API reference docs used by Claude to route and compose tool calls. The DFlow skill (helius-skills/helius-dflow/, helius-plugin/skills/dflow/, and helius-cursor/skills/dflow/) has its own reference files that must also be kept in sync. The Phantom skill (helius-skills/helius-phantom/, helius-plugin/skills/phantom/, and helius-cursor/skills/phantom/) has its own reference files that must also be kept in sync. The OKX skill (helius-skills/helius-okx/,…
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- helius-cli/CLAUDE.mdCLAUDE.md
- helius-mcp/CLAUDE.mdCLAUDE.md
- helius-dflowSkill
- helius-okxSkill
- helius-phantomSkill
- heliusSkill
- svmSkill
The file
We split this CLAUDE.md into the rules it gives an agent
9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
When updating any reference file, update it in helius-skills/ first, then copy the change to both helius-plugin/ and helius-cursor/.
- Very specific: line 28
When updating DFlow reference files, update in helius-skills/helius-dflow/references/ first, then copy to both …
- Very specific: line 38
When updating Phantom reference files, update in helius-skills/helius-phantom/references/ first, then copy to both …
- Very specific: line 48
When updating OKX reference files, update in helius-skills/helius-okx/references/ first, then copy to both …
- Very specific: line 57
When updating SVM reference files, update in helius-skills/svm/references/ first, then copy to both helius-plugin/skills/svm/references/ …
- Very specific: line 76
All skill content flows from helius-skills/ to four destinations:
- Distinctive: line 89
If you change the router surface, routed tool descriptions, action-routing guidance, or summary-first response behavior, update all of …
- Distinctive: line 101
Do not leave router/runtime changes documented in only one layer.
- Very specific: line 111
When making content changes to SKILL.md (e.g., adding rules, updating routing logic, new pitfalls), apply the change to helius-plugin/, …
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Core AI
Monorepo containing Helius developer tools distributed as independent packages:
helius-mcp/— MCP server (npm:helius-mcp) — AI-assistant agnostichelius-skills/— Standalone Claude Code skill (installed viainstall.sh)helius-plugin/— Claude Code plugin (all-in-one: bundles skill + auto-starts MCP)helius-cursor/— Cursor plugin (all-in-one: bundles skill + auto-starts MCP)helius-cli/— CLI for account setup (npm:helius-cli)
Shared Content: Reference Files
The reference files in helius-skills/helius/references/ and helius-plugin/skills/build/references/ must be kept in sync. These are the canonical Helius API reference docs used by Claude to route and compose tool calls.
- Canonical source:
helius-skills/helius/references/ - Copies:
helius-plugin/skills/build/references/,helius-cursor/skills/build/references/ - When updating any reference file, update it in
helius-skills/first, then copy the change to bothhelius-plugin/andhelius-cursor/. - CI will fail if these directories diverge.
DFlow Skill References
The DFlow skill (helius-skills/helius-dflow/, helius-plugin/skills/dflow/, and helius-cursor/skills/dflow/) has its own reference files that must also be kept in sync.
- Canonical source:
helius-skills/helius-dflow/references/ - Copies:
helius-plugin/skills/dflow/references/,helius-cursor/skills/dflow/references/ - The DFlow skill contains 12 reference files: 7 Helius copies (prefixed with
helius-), 4 DFlow-specific files, and 1 integration-patterns file. - The Helius copies have modified cross-references (e.g.,
references/helius-laserstream.mdinstead ofreferences/laserstream.md) to work alongside DFlow files in the same directory. - When updating DFlow reference files, update in
helius-skills/helius-dflow/references/first, then copy to bothhelius-plugin/skills/dflow/references/andhelius-cursor/skills/dflow/references/.
Phantom Skill References
The Phantom skill (helius-skills/helius-phantom/, helius-plugin/skills/phantom/, and helius-cursor/skills/phantom/) has its own reference files that must also be kept in sync.
- Canonical source:
helius-skills/helius-phantom/references/ - Copies:
helius-plugin/skills/phantom/references/,helius-cursor/skills/phantom/references/ - The Phantom skill contains 16 reference files: 7 Helius copies (prefixed with
helius-), 8 Phantom-specific files (react-sdk, browser-sdk, react-native-sdk, transactions, token-gating, nft-minting, payments, frontend-security), and 1 integration-patterns file. - The Helius copies have modified cross-references (e.g., LaserStream and Webhooks point to
docs.helius.devinstead of local references, since those are excluded from the frontend skill). - When updating Phantom reference files, update in
helius-skills/helius-phantom/references/first, then copy to bothhelius-plugin/skills/phantom/references/andhelius-cursor/skills/phantom/references/.
OKX Skill References
The OKX skill (helius-skills/helius-okx/, helius-plugin/skills/okx/, and helius-cursor/skills/okx/) has its own reference files that must also be kept in sync.
- Canonical source:
helius-skills/helius-okx/references/ - Copies:
helius-plugin/skills/okx/references/,helius-cursor/skills/okx/references/ - The OKX skill contains 13 reference files: 7 Helius copies (prefixed with
helius-), 5 OKX-specific files (swap, token-discovery, market-data, signals-trenches, gateway), and 1 integration-patterns file. - The Helius copies have modified cross-references (e.g.,
references/helius-laserstream.mdinstead ofreferences/laserstream.md) to work alongside OKX files in the same directory. - When updating OKX reference files, update in
helius-skills/helius-okx/references/first, then copy to bothhelius-plugin/skills/okx/references/andhelius-cursor/skills/okx/references/.
SVM Skill References
The SVM skill (helius-skills/svm/, helius-plugin/skills/svm/, and helius-cursor/skills/svm/) has its own reference files that must also be kept in sync.
- Canonical source:
helius-skills/svm/references/ - Copies:
helius-plugin/skills/svm/references/,helius-cursor/skills/svm/references/ - The SVM skill contains 10 reference files: compilation, programs, execution, accounts, transactions, consensus, validators, data, development, tokens.
- When updating SVM reference files, update in
helius-skills/svm/references/first, then copy to bothhelius-plugin/skills/svm/references/andhelius-cursor/skills/svm/references/.
Skill Versioning
Skill versions are managed via versions.json at the repo root (single source of truth). The compiler reads this file and injects versions into all SKILL.md copies and prompt variants.
- To bump a version: edit
versions.json, then runnpx tsx scripts/compile-skills.ts - The compiler updates: canonical
helius-skills/*/SKILL.md, plugin/cursor copies, Codex SKILL.md, and all prompt variants (openai/claude/full) - Versions follow semver (
major.minor.patch)
Generated Output
The following directories are generated by npx tsx scripts/compile-skills.ts from canonical sources in helius-skills/. Do not edit them directly.
.agents/skills/— Codex-native skills + prompt variantshelius-mcp/system-prompts/— npm-shipped prompt copies
Sync Paths from Canonical Source
All skill content flows from helius-skills/ to four destinations:
helius-skills/→helius-plugin/skills/(manual copy — Claude Code plugin)helius-skills/→helius-cursor/skills/(manual copy — Cursor plugin)helius-skills/→.agents/skills/(compiler-generated)helius-skills/→helius-mcp/system-prompts/(compiler-generated)
CI validates all sync paths. After modifying any SKILL.md or reference file in helius-skills/, run npx tsx scripts/compile-skills.ts to regenerate output.
Router Surface Maintenance
The Helius MCP public surface is a coordinated contract: 10 public tools total, shared action routing, and summary-first responses with expandResult.
If you change the router surface, routed tool descriptions, action-routing guidance, or summary-first response behavior, update all of these in the same pass:
AGENTS.mdREADME.mdhelius-mcp/README.mdhelius-plugin/README.mdhelius-cursor/README.md- canonical
helius-skills/*/SKILL.md - manual plugin/cursor
SKILL.mdcopies - generated
.agents/skills/output - generated
helius-mcp/system-prompts/output
Do not leave router/runtime changes documented in only one layer.
SKILL.md Files
The SKILL.md files in each package are intentionally not identical — they share most content but differ in:
- Skill name (
heliusvsbuild,helius-dflowvsdflow,helius-okxvsokx,helius-phantomvsphantom,svmvssvm) - Metadata/frontmatter
- MCP prerequisite messaging (manual install vs plugin auto-start, Cursor vs Claude Code restart instructions)
When making content changes to SKILL.md (e.g., adding rules, updating routing logic, new pitfalls), apply the change to helius-plugin/, helius-cursor/, and helius-skills/ manually.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

