Use when the user wants to switch the active topic, list their topics, or see a cross-topic overview. 触发:「切换到 X」「切到 X」「列出专题」「我有哪些专题」「switch」「换个专题」「当前在学啥」。
Scanned 8/31/2026
Install to Claude Code
npx -y skills add guoqiaoZhou/study-with-claude-code --skill switch --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Switch?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/guoqiaozhou-switch)More formats (shields.io, HTML) on the badges page.
---
name: swcc-switch
description: Use when the user wants to switch the active topic, list their topics, or see a cross-topic overview. 触发:「切换到 X」「切到 X」「列出专题」「我有哪些专题」「switch」「换个专题」「当前在学啥」。
argument-hint: "[topic]"
user-invocable: true
---
# swcc · switch — 多专题切换 + 总览
切换当前默认专题,或在无参数时列出所有专题的总览供选择。
> 开始前先读数据契约:`${CLAUDE_PLUGIN_ROOT}/skills/_shared/data-contract.md`(第九节 config、第十三节到期判定)。
参数:`$ARGUMENTS` —— 可选 topic(目标专题的名称或 slug)。
---
## 核心原则
1. **唯一写入 = `config.json` 的 `activeTopic`。** 不碰任何专题的 tree / progress / system——总览部分全是只读。
2. **不存在就别乱写。** 目标专题不存在时,列出可选项让用户重选,绝不新建或瞎指。
3. **总览要给决策信息。** 列专题时带掌握比例 + 今日到期数,让用户一眼看出该去哪。
---
## 流程
### 1. 读取专题表
- 读 `config.json` 的 `topics[]` 与当前 `activeTopic`。config 不存在/缺失 → 按数据契约第九节兜底扫 `topics/`;一个都没有 → 提示先 `/swcc-plan <topic>`,停止。
### 2. 分支:带参 or 无参
| 情况 | 行为 |
|---|---|
| **带 topic 参数** | 把参数规整为 slug,在 `topics[]` + 磁盘 `topics/<slug>/` 里匹配。匹配到 → 设 `activeTopic` = 该 slug,写回 `config.json`,确认。匹配不到 → 列出现有专题让用户重选,**不写**。 |
| **无参数** | 渲染总览(下方),让用户选一个 → 设 `activeTopic` 写回。 |
### 3. 总览渲染(只读)
对每个专题,读其 `progress.json` 算:已掌握/总数比例、今日到期数(数据契约第十三节)、上次复习日(`stats.lastReviewDate`)。
```
📚 我的复习专题
━━━━━━━━━━━━━━━━━━━━
▶ <topic-A> 🟢 <a>/<total> 掌握 🔔 今日到期 <n> 上次 <date> ← 当前
<topic-B> 🟢 <a>/<total> 掌握 🔔 今日到期 <n> 上次 <date>
切换:/swcc-switch <topic>
```
### 4. 切换后确认
```
✅ 已切换到 <topic>(activeTopic)
下一步:/swcc-go 开始复习,或 /swcc-daily 看今天到期。
```
---
## 质量基准
- 只改了 `config.json` 的 `activeTopic` 一个字段,其余文件未动。
- 目标不存在时未误写、给了可选项。
- 总览的比例/到期数与各 progress.json 一致。
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.