authoring-skills
Use when creating new skills, improving existing skills, or when the user requests help with skill authoring. Creates optimized Claude Code skills (SKILL.md files) following official best practices for descript...
Browse published AI skills maintained by jkappers. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
20Repository stars across indexed skills
0Repository forks
17Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Use when creating new skills, improving existing skills, or when the user requests help with skill authoring. Creates optimized Claude Code skills (SKILL.md files) following official best practices for descript...
Standards for writing CLAUDE.md and modular rules files (.claude/rules/) that maximize LLM execution efficiency. Use when creating or editing project instructions, defining conventions, or optimizing agent beha...
Creates INVEST-compliant user stories with acceptance criteria. Use when capturing requirements, defining backlog items, or breaking down features.
Code quality standards for writing and reviewing. Use when writing new code, reviewing PRs, refactoring, or making architectural decisions.
Invoke this skill first when authoring any AI agent instructions. Foundational principles for writing LLM instructions (skills, CLAUDE.md, rules, commands). Covers token economics, imperative language, formatti...
Use when working with .svelte files, SvelteKit projects, or Svelte reactivity. Covers component structure, stores, routing, Svelte 5 runes, and testing patterns.
Use when working with .rb files, Ruby gems, or implementing Ruby features. Covers Ruby idioms, naming conventions, enumerable patterns, service objects, error handling, and RSpec testing.
Use when working with .cs files, .NET projects, implementing C# features, advising on C#/.NET architecture and patterns, or answering questions about C#/.NET development. Covers async patterns, dependency injec...
Regulatory guidance for U.S. mortgage servicing software. Use when working with loan data models, payment processing, loss mitigation workflows, compliance timelines, or questions about RESPA, TILA, FCRA, GSE r...
Creates actionable bug reports with reproduction steps. Use when documenting bugs, creating defect tickets, or improving existing bug reports.
Creates risk-based test plans and strategies. Use when planning testing, defining test scope, or documenting QA approach.
Creates feature specifications capturing requirements and acceptance criteria. Use when writing specs, documenting features, or defining requirements.
Conventional Commits standards for git messages. Use when creating commits, writing commit messages, or reviewing commit history.
Use when working with Rails projects, ActiveRecord models, controllers, routes, or Rails-specific patterns. Covers naming conventions, models, migrations, service objects, and testing with RSpec.
Architectural planning and ADR creation. Use when evaluating feasibility, making technology choices, or defining system integration.
Use when writing unit tests, integration tests, or setting up test projects in C#. Covers xUnit patterns, Moq mocking, Bogus test data generation, and Alba integration testing.
Regulatory guidance for Canadian mortgage servicing software. Use when working with Canadian loan data models, payment processing, default management, insured vs uninsured mortgages, or questions about FCAC, OS...
Create optimized, secure multi-stage Dockerfiles for React applications (Vite, CRA, Next.js static). Use when (1) creating a new Dockerfile for a React project, (2) containerizing a React/Vite application, (3)...
Create optimized, secure multi-stage Dockerfiles for .NET Core and ASP.NET Core applications. Use when (1) creating a new Dockerfile for a .NET project, (2) containerizing a .NET application, (3) optimizing an...
Conventional Commits v1.0.0 standards for git messages. Use when (1) creating git commits, (2) writing or drafting commit messages, (3) reviewing commit message format, (4) explaining commit conventions, or (5)...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.