2 Commits

Author	SHA1	Message	Date
xianren	3f81cbb955	feat(v0.6): namespace all 14 master slash commands under /master-<slug> prefix ... Slash command discoverability cleanup. Claude Code users typically have 50+ skills installed; bare-word commands like /atisha and /zhiyi got scattered across the /-completion list. v0.6 prefixes all 14 master slash commands with master- so they cluster under /m<tab> and clearly signal "this is a Master-skill master skill". Scope of rename --------------- * Slash commands: /zhiyi → /master-zhiyi, /huineng → /master-huineng, ... all 14 affected. * Directory layout: prebuilt/<slug>/ → prebuilt/master-<slug>/ for all 14 masters (git mv preserves history). * Frontmatter: each prebuilt/master-<slug>/SKILL.md updates `name:` to master-<slug>. * compare-masters and create-master meta-skills are intentionally unchanged — they're already prefixed by their nature, and /master-compare-masters would be doublespeak. Decoupling: fojin.app/chat is NOT affected ------------------------------------------ The fojin web frontend's master dropdown uses bare slug IDs (atisha, huineng, ...) and is already grouped under "法师模式" in its UI. Backend master_profiles.py keeps `id="atisha"` etc. unchanged. No fojin-side migration required. The two surfaces (Claude Code slash + fojin dropdown) are now formally decoupled by design, not coincidence. Compatibility ------------- * NPX installer accepts both forms: `npx master-skill install zhiyi` (short) and `install master-zhiyi` (full) both resolve to the same prebuilt/master-zhiyi/ source. Install destination is always ~/.claude/skills/master-<slug>/. Backward-compatible uninstall handles legacy non-prefixed installs (~/.claude/skills/zhiyi/). * The cli.mjs already used `master-${name}` for install destinations (since v0.3 NPX installer was added), so existing v0.4/v0.5 NPX users were already getting the prefix in skills/ — only the source prebuilt/ layout and slash commands change in v0.6. Files updated ------------- * 14 directories renamed (28 files moved, 0 content changes). * 14 SKILL.md frontmatter `name:` fields. * prebuilt/compare/SKILL.md: 43 slug references updated to prefixed form. * bin/cli.mjs: resolveMasterDir helper accepts both short and full; cmdInstall and cmdUninstall handle legacy paths. * .github/workflows/validate-and-test.yml: fidelity-smoke MASTERS rotation array updated to all 14 prefixed names (was 8 hardcoded 汉传 only — now properly rotates across the full set). * scripts/{validate,cite,query,test-fidelity}.py: --master arg help text examples. * README.md + README_EN.md: situational guidance table, install snippets, master cards. New v0.6 release banner. * SKILL.md (project-level) preset list with new slash names. * ETHICS.md Tier table slug references (4). * All plugin manifests bumped 0.5.0 → 0.6.0 with description noting the /master-<slug> invocation pattern. * CHANGELOG.md: [0.6.0] section with breaking-change notice and migration commands for existing NPX users. Validation ---------- * python scripts/validate.py --strict ✓ 15 masters pass * python scripts/validate-fidelity.py ✓ all valid * python scripts/test-fidelity.py --all --dry-run ✓ * pytest tests/ ✓ 31 passed, 6 skipped * node bin/cli.mjs list ✓ shows all 14 with master- prefix * node bin/cli.mjs install zhiyi ✓ resolves to prebuilt/master-zhiyi/ * node bin/cli.mjs install master-zhiyi ✓ resolves to same Migration for existing v0.4/v0.5 users -------------------------------------- npx master-skill@0.5 uninstall zhiyi huineng xuanzang ... # OR: rm -rf ~/.claude/skills/{zhiyi,huineng,...} npx master-skill@latest install --all Then start a new Claude Code session; the new slash commands are /master-zhiyi, /master-huineng, etc. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-02 20:43:36 +08:00
xianren	3dfaa6bb62	chore(community): add contributing infra, issue/PR templates, npm publish workflow ... Tier A infrastructure to convert 204★ momentum into durable community and distribution. Pairs with PR #12 (ETHICS / CHANGELOG / fidelity smoke) — merge PR #12 first, then this. **Community docs** - `CONTRIBUTING.md` — three-tier contribution flow (code vs docs vs master content), with a detailed §3 "how to contribute a new master" covering copyright tier self-check, `/create-master` vs manual path, SKILL.md frontmatter spec, voice.md Layer 0-3, fidelity.jsonl authoring. - `CODE_OF_CONDUCT.md` — Contributor Covenant 2.1 + Buddhist-project-specific rules (no doctrinal supremacy, no using the repo as a dharma platform, no impersonating clergy, no apocryphal scripture citations). - `SECURITY.md` — threat model (prompt injection, supply chain, secret leak, installer safety, religious-boundary adversarial input), SLA table, GH Security Advisory as primary channel. **Issue / PR templates** - `bug_report.yml` — area selector, master selector, repro template. - `feature_request.yml` — non-master enhancement requests. - `new_master.yml` — **MUST precede any new-master PR**; forces tier A/B/D self-judgment and citation planning before sunk cost. - `boundary_violation.yml` — P0 template for ETHICS.md §3 violations. - `config.yml` — directs users to Discussions for chatter, Security Advisory for vulnerabilities, email for urgent takedowns. - `PULL_REQUEST_TEMPLATE.md` — change-type checkboxes, self-check list, new- master fields, local-test block. **npm publish** - `.github/workflows/npm-publish.yml` — release-tag + workflow_dispatch, with dry-run mode, tag-version match check, `npm publish --provenance`. First-time publish needs NPM_TOKEN secret (user action). - `package.json` hardening: - `engines.node: >=18` - scripts: `validate`, `validate:fidelity`, `test`, `test:smoke`, `prepack` - `publishConfig` (public, npm registry) - `files` list expanded to include platform manifests + governance docs - richer `keywords`, `author`, `bugs`, `homepage` fields - expanded description mentions all 8 masters for search discoverability **README** - 贡献指南 section rewritten to point at CONTRIBUTING.md + Discussions + four issue templates, with "先开 New Master issue 征询" gate spelled out. Discussions were enabled on the repo alongside this commit via `gh api`, so the links in README/templates resolve immediately on merge. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-16 13:53:25 +08:00