Back to Details

tech-learning-guide

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Tech Learning Guide Skill

技术学习指南Skill

Generate a complete, structured, opinionated learning guide for any technical topic. The guide should feel like it was written by an experienced senior engineer who has taught the topic before — practical, direct, and honest about what matters most.
为任意技术主题生成完整、结构化且具有针对性的学习指南。指南需给人一种由资深工程师撰写的感觉——该工程师曾教授过相关主题，内容实用、直接，且能坦诚告知重点内容。

Output Structure

输出结构

Produce the guide as a rendered artifact (
.md
file) with the following sections in order. The tone should be warm, direct, and technically confident — avoid fluff and padding.
将指南生成为可渲染的文件（
.md
格式），并按以下顺序包含各个章节。语气需热情、直接且技术自信——避免冗余内容。

Section 1 — Overview & Concept Map

第一节 — 概述与概念图谱

Open with 2–3 sentences describing what the technology is and why it matters in today's ecosystem. Then list all key concepts the learner needs to master, grouped into three tiers:
TierLabelWhat it means
🟢BasicsConcepts a beginner must learn first; no prior knowledge of the tech needed
🔵FoundationalCore concepts that form day-to-day working knowledge
🔴AdvancedDeep internals, production concerns, performance, or ecosystem integrations
Format as a table or grouped list. Aim for 5–8 concepts per tier (15–24 total), but adjust naturally for the scope of the technology. Don't pad artificially.
开篇用2-3句话描述该技术是什么，以及它在当下技术生态中的重要性。随后列出学习者需要掌握的所有核心概念，并分为三个层级：
层级标签说明
🟢基础概念初学者必须首先掌握的概念；无需具备该技术的前置知识
🔵核心概念构成日常工作知识的核心概念
🔴进阶概念深入原理、生产环境注意事项、性能优化或生态系统集成
格式可为表格或分组列表。每个层级目标包含5-8个概念（总计15-24个），但可根据技术范围自然调整，切勿刻意填充内容。

Section 2 — Weekly Learning Schedule

第二节 — 每周学习计划

Create a realistic week-by-week study plan. Assume 1–2 hours per day, 5 days/week. Structure:
  • Week N: [Theme] — 2 sentence description of the week's focus
    • Day 1–5: specific daily objectives (1–2 sentences each)
Cover all three tiers across the schedule. Basics first, then Foundational, then Advanced. Typical schedule length: 6–10 weeks depending on technology breadth. Be honest if some weeks require more time (e.g., "this week is dense — budget extra time if needed").
制定切实可行的周度学习计划。假设每天1-2小时，每周5天。 结构如下：
  • 第N周：[主题] — 用2句话描述本周的学习重点
    • 第1-5天：具体的每日学习目标（每天1-2句话）
学习计划需覆盖所有三个层级，先基础概念，再核心概念，最后进阶概念。典型计划时长为6-10周，具体取决于技术的广度。若某些周内容较密集，需如实说明（例如：“本周内容较多——如有需要，请预留额外时间”）。

Section 3 — Local Development Setup

第三节 — 本地开发环境搭建

Provide concrete, copy-paste-ready instructions for getting a working local environment. Include:
  • Prerequisites (OS, required tools, versions)
  • Installation steps (numbered, shell commands in code blocks)
  • Verify it works — a minimal "hello world" command or snippet to confirm setup
  • Recommended IDE / editor with key plugins or extensions
  • Useful dev tools (linters, formatters, debuggers, local test runners)
Be opinionated. If one approach is clearly better for learning, say so.
提供具体可复制的本地环境搭建步骤。包含：
  • 前置要求（操作系统、所需工具、版本）
  • 安装步骤（编号列表，代码块中包含Shell命令）
  • 验证环境可用 — 一个极简的“Hello World”命令或代码片段，用于确认环境搭建成功
  • 推荐IDE/编辑器及关键插件或扩展
  • 实用开发工具（代码检查器、格式化工具、调试器、本地测试运行器）
需给出明确建议。若某种方法显然更适合学习，直接说明即可。

Section 4 — Concept Deep-Dives

第四节 — 概念深度解析

For every concept listed in Section 1, provide a dedicated subsection:
undefined
针对第一节中列出的每个概念，提供专门的小节：
undefined

[Tier emoji] [Concept Name]

[层级表情] [概念名称]

What it is: 2–3 sentence plain-language explanation.
Why it matters: 1–2 sentences on practical relevance.
How it works: Explanation with code example(s). For code-heavy concepts, show at least one realistic example (not just "hello world"). For architectural concepts, use a short diagram or analogy.
Common pitfalls: 1–3 bullet points of mistakes beginners make.
定义：用2-3句通俗易懂的话解释概念。
重要性：用1-2句话说明该概念的实际应用价值。
工作原理：结合代码示例进行解释。对于代码相关的概念，至少展示一个真实场景的示例（不只是“Hello World”）。对于架构类概念，可使用简短的示意图或类比说明。
常见误区：列出1-3个初学者常犯的错误。

✏️ Exercises

✏️ 练习

  1. [Concrete, hands-on exercise — beginner friendly]
  2. [Slightly harder exercise that builds on the first]
  3. [Challenge exercise that combines this concept with a previous one]

Group the concepts under their tier heading:
`## 🟢 Basics`, `## 🔵 Foundational`, `## 🔴 Advanced`

---
  1. [具体的实操练习——适合初学者]
  2. [难度稍高的练习，基于第一个练习拓展]
  3. [挑战练习，结合该概念与之前学过的概念]

将概念按层级标题分组：`## 🟢 基础概念`, `## 🔵 核心概念`, `## 🔴 进阶概念`

---

Section 5 — Popular Libraries & Ecosystem

第五节 — 流行库与生态系统

Give a concise ecosystem map. For each major library or tool in the technology's orbit:
  • Name + one-liner on what it does
  • When to use it (2 sentences)
  • A code snippet showing the simplest useful example (where applicable)
Aim for 6–10 entries. Group by category if the ecosystem is large (e.g., "Testing", "HTTP", "ORM"). Don't list everything — list what a practitioner actually reaches for.
提供简洁的生态系统图谱。针对该技术生态中的每个主要库或工具：
  • 名称 + 一句话说明其功能
  • 适用场景（2句话）
  • 一个最简单实用的代码示例（如适用）
目标包含6-10个条目。若生态系统较大，可按类别分组（例如：“测试”、“HTTP”、“ORM”）。无需罗列所有内容——只列出从业者实际会用到的工具。

Section 6 — Project Ideas

第六节 — 项目思路

Provide exactly 3 project ideas, progressing in complexity:
  1. [Small] Project Name — 1–2 weeks. What you'll build, which concepts it exercises, why it's a good learning vehicle.
  2. [Medium] Project Name — 3–5 weeks. Same format. Introduce more Foundational concepts.
  3. [Stretch] Project Name — Open-ended. Brings in Advanced concepts and real-world concerns (auth, persistence, deployment, performance).
For each project, include:
  • A brief feature list (3–5 bullet points)
  • Key concepts practiced
  • Optional: suggested tech stack to pair with
提供3个项目思路，难度逐步提升：
  1. [小型] 项目名称 — 1-2周完成。说明要构建的内容、涉及的概念，以及为何适合学习。
  2. [中型] 项目名称 — 3-5周完成。格式同上。引入更多核心概念。
  3. [进阶] 项目名称 — 无时间限制。涉及进阶概念及实际生产场景的问题（认证、持久化、部署、性能优化）。
每个项目需包含：
  • 简短的功能列表（3-5个要点）
  • 重点练习的概念
  • 可选：推荐搭配的技术栈

Section 7 — What's Next

第七节 — 后续学习方向

After mastering everything in this guide, where does the learner go? Provide:
  • 2–3 adjacent technologies to explore (with 1-sentence rationale each)
  • 2–3 advanced topics within the technology itself that weren't covered
  • 1–2 community resources to stay current (conference, newsletter, forum)
Frame this as an honest "graduation" — you've learned the fundamentals; here's the horizon.
掌握本指南中的所有内容后，学习者下一步该如何进阶？提供：
  • 2-3个相关技术供探索（每个配1句话说明理由）
  • 2-3个该技术内的进阶主题（本指南未覆盖的内容）
  • 1-2个社区资源（会议、通讯、论坛），帮助学习者保持对技术的了解
将此部分视为真诚的“毕业建议”——学习者已掌握基础知识，以下是未来的学习方向。

Section 8 — Resources

第八节 — 资源推荐

Curated reference list. Organize into categories:
  • Official Docs — link + 1-sentence description
  • Books — title, author, why it's recommended
  • Online Courses — platform + course name, ideal for which learner level
  • Blogs / Sites — name + what kind of content they publish
  • YouTube / Video — channel or specific series, what makes it worth watching
  • Community — Discord, Slack, forum, subreddit
Keep it tight — 3–5 entries per category max. Every entry should earn its place.
精心整理的参考列表。按类别组织：
  • 官方文档 — 链接 + 1句话说明
  • 书籍 — 书名、作者、推荐理由
  • 在线课程 — 平台 + 课程名称，适合的学习者水平
  • 博客/网站 — 名称 + 内容类型
  • YouTube/视频资源 — 频道或系列视频，值得观看的原因
  • 社区 — Discord、Slack、论坛、Reddit子版块
内容需精简——每个类别最多3-5个条目。每个条目都需有存在的价值。

Quality Guidelines

质量准则

  • Be concrete: No vague advice like "practice a lot." Say what to practice and how.
  • Be honest: If a concept is genuinely hard or a common sticking point, say so.
  • Examples must run: Any code snippet should be minimal but complete enough to actually execute or be understood in isolation.
  • Calibrate depth to the technology: A guide for Bash scripting vs. distributed systems should feel different in depth and breadth.
  • No hallucinated resources: Only include books, courses, and links you're confident exist. If unsure about a specific URL, name the resource without a link rather than guess.
  • Developer Advocate tone: Write as a knowledgeable peer, not a textbook. First-person asides are fine ("I'd start with X before Y because...").
  • 具体明确：避免“多练习”这类模糊建议。说明要练习什么、如何练习。
  • 坦诚真实：若某个概念确实较难或容易成为学习瓶颈，直接说明。
  • 示例可运行：所有代码片段需简洁但完整，可单独执行或理解。
  • 适配技术深度：Bash脚本的学习指南与分布式系统的学习指南在深度和广度上需有所区别。
  • 不虚构资源：仅包含你确定存在的书籍、课程和链接。若不确定具体URL，可只列出资源名称，切勿猜测。
  • 开发者布道者语气：以知识渊博的同行身份写作，而非教科书式的口吻。可使用第一人称旁白（例如：“我建议先学X再学Y，因为……”）。

Handling Broad vs. Narrow Topics

宽泛与细分主题的处理方式

  • Very broad topic (e.g., "cloud computing", "web development"): Narrow the scope in the intro. Tell the user what angle you're covering and why. Suggest they ask follow-up guides for adjacent areas.
  • Very narrow topic (e.g., a single library method or niche tool): Scale down accordingly. A 10-week schedule for 
    Array.prototype.reduce
    is absurd. Use judgment.
  • Version-sensitive technology: Mention the version the guide targets at the top. Flag any areas where older versions differ significantly.
  • 非常宽泛的主题（例如：“云计算”、“Web开发”）：在引言中缩小范围。告知用户你将从哪个角度讲解，以及原因。建议用户针对相关领域提出后续指南请求。
  • 非常细分的主题（例如：单个库的方法或小众工具）：相应缩小内容范围。为
    Array.prototype.reduce
    制定10周的学习计划显然不合理，请酌情调整。
  • 版本敏感的技术：在指南顶部注明目标版本。标记出与旧版本差异较大的内容。

References

参考资料

  • references/schedule-templates.md
    — Example schedule patterns for different technology scopes (language, framework, tool, concept). Read if you need calibration on schedule length/density.
  • references/concept-tiers.md
    — Guidance on how to classify concepts into Basics / Foundational / Advanced for common technology categories.
  • references/schedule-templates.md
    — 不同技术范围（语言、框架、工具、概念）的示例计划模板。若需要调整计划时长/密度，可参考此文档。
  • references/concept-tiers.md
    — 针对常见技术类别，如何将概念划分为基础/核心/进阶层级的指导说明。