tech-learning-guide

Name: tech-learning-guide
Author: sivaprasadreddy

31stars1forks

How to install tech-learning-guide?

sivaprasadreddy/learning-skill/tech-learning-guide

$npx -y skills add sivaprasadreddy/learning-skill --skill tech-learning-guide

Installs into the current project.

Summary

Generate a comprehensive, structured learning guide for any technical topic or technology. Use this skill whenever a user wants to learn a new technology, programming language, framework, tool, or concept — even if they phrase it casually (e.g., "teach me Rust", "how do I get sta

Files · 1

View on GitHub

SKILL.md

1	# Tech Learning Guide Skill
2
3	Generate a complete, structured, opinionated learning guide for any technical topic. The guide
4	should feel like it was written by an experienced senior engineer who has taught the topic before
5	— practical, direct, and honest about what matters most.
6
7	## Output Structure
8
9	Produce the guide as a rendered artifact (`.md` file) with the following sections in order.
10	The tone should be warm, direct, and technically confident — avoid fluff and padding.
11
12	---
13
14	## Section 1 — Overview & Concept Map
15
16	Open with 2–3 sentences describing what the technology is and why it matters in today's ecosystem.
17	Then list all key concepts the learner needs to master, grouped into three tiers:
18
19	\| Tier \| Label \| What it means \|
20	\|------\|------------------\|-----------------------------------------------------------------------------\|
21	\| 🟢 \| Basics \| Concepts a beginner must learn first; no prior knowledge of the tech needed \|
22	\| 🔵 \| Foundational \| Core concepts that form day-to-day working knowledge \|
23	\| 🔴 \| Advanced \| Deep internals, production concerns, performance, or ecosystem integrations \|
24
25	Format as a table or grouped list. Aim for 5–8 concepts per tier (15–24 total), but adjust
26	naturally for the scope of the technology. Don't pad artificially.
27
28	---
29
30	## Section 2 — Weekly Learning Schedule
31
32	Create a realistic week-by-week study plan. Assume 1–2 hours per day, 5 days/week.
33	Structure:
34
35	- Week N: [Theme] — 2 sentence description of the week's focus
36	- Day 1–5: specific daily objectives (1–2 sentences each)
37
38	Cover all three tiers across the schedule. Basics first, then Foundational, then Advanced.
39	Typical schedule length: 6–10 weeks depending on technology breadth. Be honest if some weeks
40	require more time (e.g., "this week is dense — budget extra time if needed").
41
42	---
43
44	## Section 3 — Local Development Setup
45
46	Provide concrete, copy-paste-ready instructions for getting a working local environment.
47	Include:
48
49	- Prerequisites (OS, required tools, versions)
50	- Installation steps (numbered, shell commands in code blocks)
51	- Verify it works — a minimal "hello world" command or snippet to confirm setup
52	- Recommended IDE / editor with key plugins or extensions
53	- Useful dev tools (linters, formatters, debuggers, local test runners)
54
55	Be opinionated. If one approach is clearly better for learning, say so.
56
57	---
58
59	## Section 4 — Concept Deep-Dives
60
61	For every concept listed in Section 1, provide a dedicated subsection:
62
63	```
64	### [Tier emoji] [Concept Name]
65
66	What it is: 2–3 sentence plain-language explanation.
67
68	Why it matters: 1–2 sentences on practical relevance.
69
70	How it works: Explanation with code example(s). For code-heavy concepts, show at least
71	one realistic example (not just "hello world"). For architectural concepts, use a short
72	diagram or analogy.
73
74	Common pitfalls: 1–3 bullet points of mistakes beginners make.
75
76	---
77	#### ✏️ Exercises
78
79	1. [Concrete, hands-on exercise — beginner friendly]
80	2. [Slightly harder exercise that builds on the first]
81	3. [Challenge exercise that combines this concept with a previous one]
82	```
83
84	Group the concepts under their tier heading:
85	`## 🟢 Basics`, `## 🔵 Foundational`, `## 🔴 Advanced`
86
87	---
88
89	## Section 5 — Popular Libraries & Ecosystem
90
91	Give a concise ecosystem map. For each major library or tool in the technology's orbit:
92
93	- Name + one-liner on what it does
94	- When to use it (2 sentences)
95	- A code snippet showing the simplest useful example (where applicable)
96
97	Aim for 6–10 entries. Group by category if the ecosystem is large (e.g., "Testing", "HTTP",
98	"ORM"). Don't list everything — list what a practitioner actually reaches for.
99
100	---
101
102	## Section 6 — Project Ideas
103
104	Provide exactly 3 project ideas, progressing in complexity:
105
106	1. [Small] Project Name — 1–2 weeks. What you'll build, which concepts it exercises,
107	why it's a good learning vehicle.
108	2. [Medium] Project Name — 3–5 weeks. Same format. Introduce more Foundational concepts.
109	3. [Stretch] Project Name — Ope

People who liked this also viewed

6 picks

Type

tech-learning-guide

31stars1forks

View on GitHub

How to install tech-learning-guide?

sivaprasadreddy/learning-skill/tech-learning-guide

$npx -y skills add sivaprasadreddy/learning-skill --skill tech-learning-guide

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Tech Learning Guide Skill
2
3	Generate a complete, structured, opinionated learning guide for any technical topic. The guide
4	should feel like it was written by an experienced senior engineer who has taught the topic before
5	— practical, direct, and honest about what matters most.
6
7	## Output Structure
8
9	Produce the guide as a rendered artifact (`.md` file) with the following sections in order.
10	The tone should be warm, direct, and technically confident — avoid fluff and padding.
11
12	---
13
14	## Section 1 — Overview & Concept Map
15
16	Open with 2–3 sentences describing what the technology is and why it matters in today's ecosystem.
17	Then list all key concepts the learner needs to master, grouped into three tiers:
18
19	\| Tier \| Label \| What it means \|
20	\|------\|------------------\|-----------------------------------------------------------------------------\|
21	\| 🟢 \| Basics \| Concepts a beginner must learn first; no prior knowledge of the tech needed \|
22	\| 🔵 \| Foundational \| Core concepts that form day-to-day working knowledge \|
23	\| 🔴 \| Advanced \| Deep internals, production concerns, performance, or ecosystem integrations \|
24
25	Format as a table or grouped list. Aim for 5–8 concepts per tier (15–24 total), but adjust
26	naturally for the scope of the technology. Don't pad artificially.
27
28	---
29
30	## Section 2 — Weekly Learning Schedule
31
32	Create a realistic week-by-week study plan. Assume 1–2 hours per day, 5 days/week.
33	Structure:
34
35	- Week N: [Theme] — 2 sentence description of the week's focus
36	- Day 1–5: specific daily objectives (1–2 sentences each)
37
38	Cover all three tiers across the schedule. Basics first, then Foundational, then Advanced.
39	Typical schedule length: 6–10 weeks depending on technology breadth. Be honest if some weeks
40	require more time (e.g., "this week is dense — budget extra time if needed").
41
42	---
43
44	## Section 3 — Local Development Setup
45
46	Provide concrete, copy-paste-ready instructions for getting a working local environment.
47	Include:
48
49	- Prerequisites (OS, required tools, versions)
50	- Installation steps (numbered, shell commands in code blocks)
51	- Verify it works — a minimal "hello world" command or snippet to confirm setup
52	- Recommended IDE / editor with key plugins or extensions
53	- Useful dev tools (linters, formatters, debuggers, local test runners)
54
55	Be opinionated. If one approach is clearly better for learning, say so.
56
57	---
58
59	## Section 4 — Concept Deep-Dives
60
61	For every concept listed in Section 1, provide a dedicated subsection:
62
63	```
64	### [Tier emoji] [Concept Name]
65
66	What it is: 2–3 sentence plain-language explanation.
67
68	Why it matters: 1–2 sentences on practical relevance.
69
70	How it works: Explanation with code example(s). For code-heavy concepts, show at least
71	one realistic example (not just "hello world"). For architectural concepts, use a short
72	diagram or analogy.
73
74	Common pitfalls: 1–3 bullet points of mistakes beginners make.
75
76	---
77	#### ✏️ Exercises
78
79	1. [Concrete, hands-on exercise — beginner friendly]
80	2. [Slightly harder exercise that builds on the first]
81	3. [Challenge exercise that combines this concept with a previous one]
82	```
83
84	Group the concepts under their tier heading:
85	`## 🟢 Basics`, `## 🔵 Foundational`, `## 🔴 Advanced`
86
87	---
88
89	## Section 5 — Popular Libraries & Ecosystem
90
91	Give a concise ecosystem map. For each major library or tool in the technology's orbit:
92
93	- Name + one-liner on what it does
94	- When to use it (2 sentences)
95	- A code snippet showing the simplest useful example (where applicable)
96
97	Aim for 6–10 entries. Group by category if the ecosystem is large (e.g., "Testing", "HTTP",
98	"ORM"). Don't list everything — list what a practitioner actually reaches for.
99
100	---
101
102	## Section 6 — Project Ideas
103
104	Provide exactly 3 project ideas, progressing in complexity:
105
106	1. [Small] Project Name — 1–2 weeks. What you'll build, which concepts it exercises,
107	why it's a good learning vehicle.
108	2. [Medium] Project Name — 3–5 weeks. Same format. Introduce more Foundational concepts.
109	3. [Stretch] Project Name — Ope

People who liked this also viewed

6 picks

Type