skills CLAUDE.md

CLAUDE.md — repo conventions for Claude Code

This file briefs Claude Code when working inside this repo (adding new skills, editing existing ones, fixing docs). It's not for end-users — they install via the methods in docs/install.md.

What this repo is

~22 Agent Skills that wrap the Longbridge Securities platform — quotes, charts, fundamentals, valuation, news, watchlist, account analytics, etc. Multilingual triggers (Simplified Chinese / Traditional Chinese / English). The default style is prompt-only (SKILL.md tells the LLM what longbridge ... command to run); scripts/ and commands/ subfolders are allowed but should be opt-in for clear runtime needs (DOCX generation, chart helpers, slash commands), not as a wrapper-by-default.

Layout

longbridge-skills/
├── .claude-plugin/marketplace.json    # plugin marketplace entry
├── skills/                            # ~22 skill folders
│   ├── <slug>/
│   │   ├── SKILL.md                   # required
│   │   ├── references/                # optional — on-demand detail loaded by the LLM
│   │   ├── scripts/                   # optional — Python helpers (e.g. DOCX, charts) when there's a clear runtime need
│   │   └── commands/                  # optional — Claude Code slash commands (`/<command>`)
│   └── ...
├── docs/
│   ├── architecture.md                # multilingual + CLI/MCP routing design
│   └── install.md                     # install / verify / FAQ
├── CLAUDE.md                          # this file
├── README.md
├── LICENSE                            # MIT
└── .gitignore

Conventions for adding or editing a skill

1. Slug + directory

• Directory name must match ^[a-z0-9]+(-[a-z0-9]+)*$ (lowercase ASCII + hyphens).
• It MUST equal the name: value in the SKILL.md frontmatter.
• Existing skills are namespaced longbridge-* (e.g. longbridge-quote). The single base skill is just longbridge.
• Slugs are immutable once published. Never rename or delete a published skill's slug. Installers (npx skills update) match by slug, so a rename does not upgrade the old install — it orphans it on every user's machine (stale + competing for the same triggers) while the new name is never picked up by update. Reorganize by adding/editing content under the existing slug. If a new slug is genuinely unavoidable, it is a breaking change: note it in the release notes and direct users to the full reinstall (scripts/update.sh), the only thing that clears orphaned slugs.