claude-skills: 66 Domain-Specific Plugins That Turn Claude Code Into a Full-Stack Pair Programmer

General-purpose Claude Code is great at "explain this function" but flat when you ask for a NestJS interceptor wired to a specific auth pattern, or for a React Server Component that lines up with your existing data layer. You end up re-stating the same context every session. Jeffallan/claude-skills packages 66 stack-specific skills plus a /common-ground protocol that loads references on demand, so Claude only sees the slice it needs for the current task.

Why This Skill Matters

The repo ships 66 skills across 12 categories (languages, backend/frontend frameworks, infrastructure, APIs, testing, DevOps, security, data/ML, and platform specialists), plus 9 workflow commands and 371 reference files. The interesting piece is the routing: when you ask for "JWT auth in my NestJS API," it activates the NestJS Expert skill and loads only references/authentication.md, not the entire skill library. That keeps context windows lean and answers stack-specific instead of generic.

It also exposes /common-ground, a context-engineering protocol for syncing Claude with your project's conventions before any work begins. Pair that with the workflow commands for epic / Jira / Confluence integration and you get a Claude that behaves like a teammate who already read your docs.

Installation

The repo publishes a marketplace plugin. Install it once and use it from any Claude Code session.

# Add the marketplace
/plugin marketplace add jeffallan/claude-skills

# Install the skill package
/plugin install fullstack-dev-skills@jeffallan

Verify it appears in your installed plugins:

/plugin → Installed
  - fullstack-dev-skills (jeffallan)

For local development (modifying a skill in place without re-publishing), follow the path in docs/local_skill_development.md. Workflow commands that touch Jira or Confluence require an Atlassian MCP server to be configured separately.

Real Workflow: Build a JWT Auth Layer in a NestJS API

You are working on an existing NestJS service and need to add JWT auth without breaking the current login route. Generic Claude Code will produce a generic interceptor.

Step 1. Run /common-ground to sync the skill with your project. It scans package.json, the existing src/ tree, and your test runner, then commits a short shared context the rest of the session will reuse:

/common-ground
→ Detected: NestJS 10, TypeORM 0.3, Jest 29, JWT via @nestjs/jwt
→ Existing module: AuthModule (LocalStrategy only)
→ Will activate: NestJS Expert + references/authentication.md

Step 2. Ask for the implementation in plain language:

Implement JWT authentication in my NestJS API using the existing AuthModule.
Add a JwtStrategy, a guard for protected routes, and a /auth/login endpoint
that issues tokens on valid credentials.

Step 3. The NestJS Expert skill activates. Expected output:

• A JwtStrategy extending PassportStrategy(Strategy) with secretOrKey sourced from ConfigService.
• An AuthGuard('jwt') applied via @UseGuards on a sample protected controller.
• A /auth/login POST handler using @nestjs/jwt's signAsync.
• A Jest test under test/auth.e2e-spec.ts that logs in with a seed user and asserts a 200 with a token.

Step 4. Run the test, commit, and move on. The next time you ask a NestJS question in the same project, /common-ground is already in effect and the references stay loaded.

Real Workflow: Debug a Failing Test Without Re-Explaining the Stack

A Jest test in your React app is failing after a refactor. The error mentions a stale closure over a context provider, but you do not want to spend the next prompt re-stating the React version, the test runner, and the component tree.

Step 1. Trigger the bug-investigation workflow explicitly:

The test src/components/UserMenu.test.tsx is failing with
"act() wrapping" warnings. Walk through Debugging Wizard → Framework Expert →
Test Master → Code Reviewer and propose a fix.

Step 2. The plugin sequences four skills in order. Each one contributes a slice:

• Debugging Wizard reads the error trace and the relevant test file, then names the likely cause (here: useEffect cleanup missing when the context provider unmounts).
• Framework Expert (React) loads references/server-components.md and references/testing.md, narrows it to a React 18 + Testing Library gotcha.
• Test Master proposes the exact test rewrite, with await waitFor and a properly returned cleanup function from render.
• Code Reviewer flags one extra thing: the original component was missing a key prop on the provider, which is the upstream cause.

Step 3. Apply the fix, rerun the test, and confirm the warning is gone. The full investigation took one prompt because the four skills together carried the context you would otherwise have re-typed.

• Run /common-ground once at the start of each session on a new project; it pays back within the first non-trivial prompt.
• Trust the routing: when the plugin activates only one reference file, that is by design — keeping context lean is the point.
• For multi-skill flows (Feature Forge → Architecture Designer → Fullstack Guardian → Test Master → DevOps Engineer), state the feature in one prompt and let the sequence run end to end.
• If you only need one category (say, "all the testing skills"), ask for that explicitly; the plugin will narrow the activation.

When Not to Use This

If you are doing exploratory work on a codebase the plugin has never seen, the first prompt still costs you the /common-ground setup. For one-off questions on a throwaway script, skip the plugin and ask plain Claude Code — you do not gain much from loading NestJS-specific references to fix a five-line shell script.

See the leaderboard for more full-stack skill bundles.