/learn — Self-improving Claude Code skills

Expert guidance on Swift Concurrency best practices, patterns, and implementation. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or...

A personal JavaScript learning repo with exercises based on the MDN “Test your skills” modules

Here you can find the readme.md file for my profile and learn more about me, my skills, my projects and my contact information.

Transform a youtube video / youtube playlist in a SKILL.md file, allowing Claude Code to learn new skills/workflows from video content

Reference implementation of the System Skill Pattern for building Claude Skills that remember, learn, and improve over time. CLI + SKILL.md + Database demonstrated via a Pomodoro timer.

This project is an attempt to make a website that has computer science high schoolers take a questionnaire to assess their specific computer science career field of interest and recommend free...

In this challenge, I'm committed to honing my Java programming skills by writing solutions from scratch without referring to any online sources or relying on assistance from chat bots. I believe...

|

Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.

|

Formik form handling with validation patterns. Use when building forms, implementing validation, or handling form submission.

Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.

Codebase orientation. Use FIRST when exploring code, finding files, or understanding project structure.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not...

Next.js 15 critical performance fixes. Use when writing React components, data fetching, Server Actions, or optimizing bundle size.

GraphQL queries, mutations, and code generation patterns. Use when creating GraphQL operations, working with Apollo Client, or generating types.

Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.

Execute tasks from a feature spec one at a time, updating living documentation as you go. Use after /interview to implement the planned feature.

Facilitate productive team retrospectives with structured formats and actionable improvement outcomes