←Leaderboard/Software Engineering/Gentleman-Skills
Last commit on February 2, 2026·Created on January 16, 2026

Gentleman-Programming/Gentleman-Skills

“Gives AI assistants the structural memory of a senior engineer.”
Combined rank
#474
across all skills
In Software Engineering
#44
category rank
Stars
657
+0.3% in last 7d
Forks
97
+1.0% in last 7d
Watchers
11
0.0% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

Gentleman-Skills is a collection of ready-to-use skill definitions for AI coding assistants. Each skill embeds framework-specific patterns — from Angular standalone components and Spring Boot constructor injection to React Native project structure and Elixir anti-patterns — so the assistant generates code that respects a team’s architecture and coding standards. It serves fullstack developers, platform teams, and architects who want to standardize AI-generated code without rewriting instructions every session.

WHO IT'S FOR
AI Agent Power Users
loading skill packs for AI assistants
Developer Platform / DevEx Teams
maintaining internal skill library for dev
Full-Stack Developers
generating framework code with AI skills
Engineering Leads / Architects
enforcing architectural patterns through AI skills
Repository contents

24 skill files

Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill collection

Follow the documented setup, then try a first task.

I’m using

Claude Code curated bundle

Installs: Complete curated skills bundle; the listed skillPaths are a bounded selection of positively documented paths, not the complete bundle inventory. · Claude Code

Before you start
  • Git must be available for the documented clone command.

Platform: macOS/Linux

Run from: The directory in which the Gentleman-Skills repository folder should be created

  1. In a terminal, clone the repository from the working directory.

    git clone https://github.com/Gentleman-Programming/Gentleman-Skills.git
  2. In the same terminal working directory, copy the complete curated bundle into Claude Code's skills directory.

    cp -r Gentleman-Skills/curated/* ~/.claude/skills/
README.md ↗ · Checked Sep 29, 2026

Give it something to do.

Suggested first task

Refactor a TypeScript model safely

Uses typescript

  • Path to an existing TypeScript file
  • Any compatibility constraints that must be preserved
Use the typescript skill to review and refactor the TypeScript file at <FILE_PATH>. Replace direct string unions with const-derived types where applicable, extract inline nested object types into flat named interfaces, and replace any uses of `any` with `unknown`, a type guard, or an appropriate generic. Keep behavior unchanged and briefly explain each change. <FILE_PATH> is a placeholder for the TypeScript file to inspect.
curated/typescript/SKILL.md ↗ · Checked Sep 29, 2026
Suggested first task

Create a production-oriented Angular login form

Uses angular-forms

  • Path to an existing Angular project
  • Desired component name or target component file
Use the angular-forms skill to draft a small production-oriented Reactive Forms login component for the Angular project at <PROJECT_PATH>. Include required and email validation for the email field, a minimum length of 8 for the password, `fb.nonNullable.group()` for typed non-nullable values, `getRawValue()` on valid submission, and a disabled submit button while the form is invalid. <PROJECT_PATH> is a placeholder for the existing Angular project directory; adapt names to its conventions.
curated/angular/forms/SKILL.md ↗ · Checked Sep 29, 2026
Suggested first task

Draft a conventional pull-request description

Uses github-pr

  • Summary of the changes and why they were made
  • Testing performed or still needed
  • Optional issue number
Use the github-pr skill to draft—but do not publish—a pull-request title and Markdown description from <CHANGE_SUMMARY>. Use a conventional-commit title and include Summary, Changes, and Testing sections. Include `Closes #<ISSUE_NUMBER>` only if an issue number is provided. <CHANGE_SUMMARY> is a placeholder for the change details, and <ISSUE_NUMBER> is an optional placeholder.
curated/github-pr/SKILL.md ↗ · Checked Sep 29, 2026