content/skills/learning-skills/learn/SKILL.md
Multi-angle concept anatomy skill for a single concept or term. Breaks one idea into eight cuts, finds the shared deep structure, and compresses it into an org-mode insight note. Use when the user wants to deeply understand one concept, term, or idea from multiple perspectives, asks for 概念解剖 / concept anatomy / learn concept, or wants more than a plain-language paraphrase. Prefer this over `plain` when the goal is deep structure rather than simplification. Do not use it for quick rewrites, code walkthroughs, or multiple unrelated terms at once.
npx skillsauth add bahayonghang/my-claude-code-settings learnInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
你是概念解剖师。目标是把一个概念看透,不是把它写得玄。
一次只处理一个概念。若用户给了多个不相干概念,先让用户选一个,或分别处理。若用户只是想“说人话”地解释现有内容,应该更偏向 plain。
先把概念钉住:
八个方向各切一刀。每刀 2-4 句,只留筋骨,不带水分。
技术或科学概念也照样切,但不要硬塞诗性。哪一刀材料少,就写得更克制、更朴素。
最后把整个分析压成三个结果:
概念 = ...+ - | / \ < > * = _ . , : ; ! ' " 和空格,不用 Unicode 绘图字符。references/template.org。Get-Date -Format "yyyyMMddTHHmmss" 与 Get-Date -Format "yyyy-MM-dd ddd HH:mm"date +%Y%m%dT%H%M%S 与 date "+%Y-%m-%d %a %H:%M"New-Item -ItemType Directory -Force ~/Documents/notes | Out-Nullmkdir -p ~/Documents/notes~/Documents/notes/{timestamp}--概念解剖-{概念名}__concept.org。*bold*,代码用 ~code~ 或 =code=。development
Use only when the user explicitly asks for swarm, subagents, parallel agents, dynamic workflow, multi-agent orchestration, 多智能体编排, or when the task truly needs coordinated research plus implementation plus review plus verification packets. Do not use for ordinary code review, planning-only work, single-line bugfixes, routine audits, or migrations unless orchestration is requested or at least two independent workflow dimensions are present.
development
Run a code quality review focused on maintainability, structure, abstraction quality, file growth, branching complexity, boundary cleanliness, and refactoring opportunities. Use when the user asks for code quality review, code review, maintainability review, architecture quality review, PR code quality feedback, 代码质量审查, 代码质量 review, 可维护性审查, 架构质量审查, or review comments about code structure. Do not use for pure security review, formatting-only review, performance profiling, or implementation tasks unless the user also asks for a code quality review.
development
Plan-first brainstorming workflow that turns an idea into an approved Markdown implementation plan by default. Use when the user wants to brainstorm, design, scope, or plan a feature/spec before implementation. Spark explores project context, asks only blocking questions, writes the plan under the project root's .plannings/YYYY-MM-DD-feature-slug.md path, self-reviews it, and waits for user approval. Create an HTML or visual plan/spec only when the user explicitly asks for HTML, browser-viewable, or visual output; save the paired .html beside the Markdown plan.
development
Run a code quality review focused on maintainability, structure, abstraction quality, file growth, branching complexity, boundary cleanliness, and refactoring opportunities. Use when the user asks for code quality review, code review, maintainability review, architecture quality review, PR code quality feedback, 代码质量审查, 代码质量 review, 可维护性审查, 架构质量审查, or review comments about code structure. Do not use for pure security review, formatting-only review, performance profiling, or implementation tasks unless the user also asks for a code quality review.