plugins/writing-and-docs/skills/learning-guide/SKILL.md
Guide technical learning through hands-on projects and clear explanations. Use when exploring new technologies, creating learning paths, building practice projects, or understanding new concepts like Go, Terraform, Kubernetes, or AWS.
npx skillsauth add arosenkranz/claude-code-config learning-guideInstall 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.
Structured approach to learning new technologies through hands-on practice.
When learning a new technology:
Week 1: Foundations
Day 1-2: Syntax and Types
- Variables, functions, control flow
- Project: CLI calculator
Day 3-4: Data Structures
- Slices, maps, structs
- Project: Contact book CLI
Day 5-7: Packages and Testing
- Creating modules
- Writing tests
- Project: URL shortener library
Week 2: Concurrency
Day 1-2: Goroutines and Channels
- Project: Concurrent web scraper
Day 3-4: Sync Package
- Mutexes, WaitGroups
- Project: Rate-limited API client
Day 5-7: Real Application
- Project: Simple HTTP server with graceful shutdown
Week 1: Core Concepts
Day 1-2: HCL Basics
- Resources, variables, outputs
- Project: Create S3 bucket + IAM policy
Day 3-4: State Management
- Remote state, locking
- Project: Multi-file infrastructure
Day 5-7: Modules
- Creating reusable modules
- Project: VPC module with subnets
Week 2: Real Infrastructure
Day 1-3: Complete Application
- Project: Deploy containerized app to ECS
Day 4-5: Environments
- Workspaces or directory structure
- Project: Dev/Staging/Prod setup
Day 6-7: CI/CD Integration
- Project: GitHub Actions for terraform plan/apply
Week 1: Local Development
Day 1-2: Concepts
- Pods, Services, Deployments
- Project: Deploy nginx with minikube
Day 3-4: Configuration
- ConfigMaps, Secrets, Volumes
- Project: Stateful application with persistence
Day 5-7: Networking
- Services, Ingress
- Project: Multi-service application
Week 2: Production Patterns
Day 1-2: Scaling
- HPA, Resource limits
- Project: Auto-scaling deployment
Day 3-4: Observability
- Logs, metrics, health checks
- Project: Add monitoring to application
Day 5-7: Helm
- Charts and values
- Project: Create Helm chart for your app
| Project | Technologies | Time | |---------|-------------|------| | Personal CLI tool | Go or Python | 2-4 hrs | | Static site generator | Any language | 4-6 hrs | | API wrapper library | TypeScript | 3-5 hrs | | Docker dev environment | Docker Compose | 2-3 hrs |
| Project | Technologies | Time | |---------|-------------|------| | REST API with DB | Go/Python + PostgreSQL | 8-12 hrs | | CI/CD pipeline | GitHub Actions | 4-6 hrs | | Infrastructure module | Terraform + AWS | 6-8 hrs | | Monitoring stack | Prometheus + Grafana | 4-6 hrs |
| Project | Technologies | Time | |---------|-------------|------| | Microservices app | K8s + multiple services | 20+ hrs | | Custom Terraform provider | Go + Terraform SDK | 15+ hrs | | Full GitOps setup | ArgoCD + Helm | 10-15 hrs | | Observability platform | OTEL + various backends | 15+ hrs |
Your homelab is perfect for practicing:
| Technology | Homelab Application | |------------|---------------------| | Docker | Deploy new services | | Terraform | Manage cloud resources | | Kubernetes | Run k3s cluster | | Go | Build automation tools | | Monitoring | Set up observability |
# [Date] - [Technology] - [Topic]
## What I Learned
- Key concept 1
- Key concept 2
## What I Built
- Description of project/exercise
## Challenges
- Problem I encountered
- How I solved it
## Next Steps
- [ ] What to learn next
- [ ] Project to try
Rate yourself 1-5 on each technology:
Track progress monthly to see growth.
tools
Lightweight orchestrator for spec-before-plan workflow. Use when starting a feature with ambiguous requirements. Walks SPEC.md → PLAN.md → execute, delegating to /superpowers:writing-plans and /superpowers:executing-plans. Invoke when asked to "spec this out", "spec-first", "spec and plan for X", or when feature requirements are vague.
tools
Problem Statement Co-Authoring Skill
development
Structure and maintain professional brag documents with clear templates for accomplishments, projects, and growth tracking. Use when documenting achievements, creating brag document entries, formatting accomplishments, or tracking career progress.
development
Analyze technical documentation for clarity, conciseness, and effectiveness using Google Technical Writing principles. Use when reviewing documentation, checking writing quality, improving docs, or providing writing feedback.