smart-claude-code-plugins

Toggle "learning mode" — a co-coding mode where the user hand-writes the code themselves instead of you writing it. Trigger on /smart:learning, or whenever the user wants to enable or disable hands-on participation in coding: phrases like "learning mode", "let me write the code", "I want to participate in coding", "co-code with me", "参与编码", "hands-on mode", "turn learning mode off". This is a plain on/off switch — no ratios, no config. When on, every piece of code you would write goes to the console instead, labeled New file / New code / Modify / Delete for the user to type in, and you review what they land, one task at a time. Enabling injects the rules into `.claude/CLAUDE.local.md` (which Claude Code auto-loads every session) so they persist; the presence of that block is the entire state — nothing is stored in `.smart/settings.json`. Use this skill for any request about turning the user's own involvement in writing code on or off.

Use when the user wants to capture, review, or close the open loops Claude surfaced during the current conversation — the insights, suggested next steps, and follow-up questions Claude raised while chasing something else, which get buried as the conversation branches. Persists them to `.smart/notebook.md` as a running list of unfollowed leads. Trigger on `/smart:notebook`, or when the user says "notebook", "记录本", "做题本", "open loops", "what did we not follow up on", "别丢", "被掩埋", "未跟进", "现在有哪些没跟进的". A companion `Stop` hook already auto-captures marked blocks (★ Insight, 建议下一步) after every reply; this skill adds the free-form leads the hook cannot parse and manages their open/closed status. This is NOT `todo` (either/or decisions under a pinned mainline) and NOT `distill` (reusable knowledge Q/A archive) — notebook tracks unclosed leads so a question chased into another question never gets lost.

Use when the user asks to distill, summarize, archive, persist, or save the current session/conversation into a knowledge base; mentions /smart:distill, distill, knowledge base, session topics, Q&A archive, current CC output, or "write this chat to disk"; or provides a scope/target directory for session knowledge capture. Applies only to current conversation context, not source files.

This skill should be used when the user wants to capture, anchor, or reconcile the decisions and options Claude surfaced during the current conversation into a persistent `.smart/todo-list.md` — a mainline-plus-branches todo. Trigger on `/smart:todo`, or when the user says "todo", "todolist", "待办", "主线", "pull me back", "拉回主线", "别跑偏", "I'm lost in branches", "现在该做什么", or wants to stop the conversation's ever-branching decisions from burying the original goal. It pins one Mainline (the fundamental goal) that branch churn can never overwrite, parks divergent decisions as reconciled branches (merging duplicates instead of rewriting), and re-surfaces the mainline every run to pull the user back. Reads the current conversation's surfaced decisions — not source-file TODOs or the native task list.

Personal local config for Claude Code sessions. Trigger on /smart:local, or when the user says "create CLAUDE.local.md", "setup local memory", "local preferences", "git-ignore my local claude file", or wants a per-project personal memory file that is never committed. Bootstraps a git-ignored `.claude/CLAUDE.local.md` in the current project, seeded with the personal preferences below, and ensures it is git-ignored. The personal preferences also apply on their own: always reply in Simplified Chinese, store Plan Mode files under `.claude/plans/`.

This skill should be used when the user says "analyze","optimize plugins", "disable unused plugins", "save context", "reduce context usage", "which plugins do I need", "clean up plugins", "focus context", "trim plugins", or wants to detect the project type and disable irrelevant plugins to save context window space. Invoked explicitly via /smart:optimize-tokens.

This skill should be used when the user wants to commit staged or unstaged changes (e.g. "commit", "save my work", "done", "make a commit"). Performs only the commit operation — no CI checks, no version bump, no push.

This skill should be used when the user wants to create a pull request (e.g. "create PR", "open PR", "open a pull request", "submit PR", "merge request"), or wants the full check+commit+push+PR pipeline. Includes push and version bump — no need to push first.

This skill should be used when the user says "bump version", "update version", "release", "new version", "version bump", "prepare release", "increment version", or when preparing a release. Also triggers proactively in the push pipeline on any branch. Supports plugin.json, package.json (including monorepo), pyproject.toml, and app.json (Expo/React Native).

Auto-detect project CI configuration, extract and run corresponding check commands locally (generic, no fixed directory structure dependency)

This skill should be used when the user says "help", "what can you do", "list skills", "list hooks", "list agents", "show commands", "how to use", or wants an overview of the smart plugin's capabilities.

This skill should be used when the user says "hud", "statusline", "install statusline", "setup statusline", "configure statusline", "reset statusline", "restore statusline", or wants to install or restore the smart plugin's statusline.

Use when the user wants to push code to remote (e.g. "push", "push to origin"), or wants the full commit+push pipeline. Not for creating PRs — use smart:pr instead. Includes automatic version bump before push.

This skill should be used when the user says "sendshot", "install sendshot", "setup sendshot", "send screenshot to ec2", "upload clipboard image", "send clipboard to remote", or wants to install the cross-platform sendshot shell function that uploads a clipboard image to a remote host.

This skill should be used whenever you are about to author, edit, or scale a Workflow script (the Workflow tool / multi-agent orchestration), or when the user says a workflow "burns too many tokens", "is too expensive", asks to "tier models", "use haiku/sonnet/opus per task", "make the workflow cheaper", "reduce workflow cost", "model layering / 模型分层", or wants fan-out / pipeline agents to run cost-efficiently. Apply it BEFORE writing agent() calls so each subagent runs on the right model tier and the script prunes work before spawning. Use it even when the user only says "write a workflow for X" — cost-tiering should be the default, not an afterthought.