Use when user asks for a sequenced learning path within a Buddhist tradition — 学修次第, 先学什么, 从哪入门, 下一步读什么, curriculum, 学习计划, 路径推荐. Differs from /compare-masters (parallel opinion) and /master-debate (adversarial dialectic) by being 纵向 / 时序: stage-by-stage plan keyed on tradition × level (L0-L3) → foundation → intermediate → advanced + blind spots. Trigger is planning intent — "禅宗对比" goes to /compare-masters; "禅宗从哪开始学" goes here.
npx skills add https://github.com/xr843/Master-skill --skill master-curriculum
> 本路径依据历史佛教文献生成,仅供学习参考。如需正式修行指导,请亲近善知识。
| 用户说 | 加载 reference |
|--------|---------------|
| 禅宗 / 禅 / 见性 | references/chan.md |
| 净土 / 念佛 / 弥陀 | references/jingtu.md |
| 天台 / 止观 | references/tiantai.md |
| 华严 / 一真法界 | references/huayan.md |
| 唯识 / 法相 / 瑜伽行 | references/weishi.md |
| 三论 / 中观 / 般若 | references/sanlun-zhongguan.md |
| 格鲁 / 应成 / 道次第 | references/gelug-madhyamaka.md |
| 上座部 / 内观 / vipassana | references/theravada-vipassana.md |
从用户输入抽取关键词,匹配每份 reference 顶部的 ## 触发关键词 列表,取最高分。若用户说"什么传统都行 / 综合理论",按 keyword density 给一份默认推荐而非平均加载。
若全部 reference 关键词分数均为 0(典型例:噶举 / 米拉日巴 / 真言宗 / 黄檗 / 等暂未提供路径的传统),不要用任何 reference。明确告诉用户本传统尚无 curriculum 路径,并建议改用对应单 master skill(如 /master-milarepa)或先 /compare-masters 横向了解后再选定方向。禁止套用错误传统的路径。
> 本路径依据历史佛教文献生成,仅供学习参考。如需正式修行指导,请亲近善知识。
## 你的学修路径:<传统> · 从 L<n> 开始
### 一、根基(入门,建议 N 周)
- **主用经/论**:《<经名>》【<cbeta_id 或 sc_uid>】
- **推荐 master**:`/master-<slug>` — <此阶段教什么>
- **目标**:能用自己的话讲清 <3 个核心概念>
### 二、深入(进阶,M 周)
- 主用经/论 + 配合 master + 关键议题
### 三、精研(专修,长期)
- 主用经/论 + 配合 master + 验收标准
### 四、可能的盲点
(本传统初学者最易踩 2-3 个陷阱 + 各祖师对此的提醒)
### 延伸
- 交叉对比 → `/compare-masters`
- 了解争议 → `/master-debate`
meta.json.sources。CI 通过 scripts/validate-curriculum-sources.py 强制。/master-<slug> 必须指向已存在的 prebuilt/master-<slug>/。/compare-masters 和 /master-debate 的边界compare-masters = 横向并列(多家看一题,单轮)master-debate = 多轮交锋(看分歧)master-curriculum = 纵向时序(按月按季规划学什么)次第 / 先学 / 路径 / 计划 / 入门 → curriculum;不与 compare/debate 重叠。Control Cursor AI code editor via CLI. Open files, folders, diffs, and manage extensions.
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns. This skill should be used when the user asks about 'architecture decision', 'ADR', 'design pattern selection', 'technology choice', or needs to evaluate architectural trade-offs. Keywords: architecture, ADR, patterns, trade-offs, technical debt, quality attributes, decision record.
Facilitates deliberate skill development during AI-assisted coding. Offers interactive learning exercises after architectural work (new files, schema changes, refactors). Use when completing features, making design decisions, or when user asks to understand code better. Triggers on "learning exercise", "help me understand", "teach me", "why does this work", or after creating new files/modules. Do NOT use for urgent debugging, quick fixes, or when user says "just ship it".
Organize project files and folders for maintainability and scalability. Use when structuring new projects, refactoring folder structure, or establishing conventions. Handles project structure, naming conventions, and file organization best practices.
Automatically trigger review agents after task completion. Use when strategic-planner finishes planning tasks (calls plan-consultant) or when main agent completes coding tasks in /implement workflow (calls code-reviewer). Triggers on phrases like "plan complete", "implementation done", "coding finished", "ready for review".
Provides a structured workflow for planning and executing code reviews like a senior engineer. Use when asked to review code, PRs, or plan a code review task.
Recall project-first and global-supplement ChatCrystal memories before substantive implementation, refactoring, migration, configuration, investigation, or optimization work. Use when the task is non-trivial, has repository or project context, and prior fixes, decisions, pitfalls, or reusable patterns may change the approach.
Take xr843/master-curriculum from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.