developer-stack-skills

AI agent SKILL.md files for full-stack developers — Java, Python, React, Angular, Testing, and Project Conventions.

Compatible with Claude, Cline, Roocode, GitHub Copilot, and Cursor.

Install

npm install developer-stack-skills

Global install:

npm install -g developer-stack-skills

Version in this README: 3.0.0

Interactive npm install can auto-run post-install configuration, but recent npm versions hide lifecycle script output by default. Treat configuration as explicit step after installation unless you install with --foreground-scripts.

• npm install developer-stack-skills Installs skills into <project>/.ai-skills/developer-stack-skills Default mode prompt prefers copy
• npm install -g developer-stack-skills Installs skills into ~/.ai-skills/developer-stack-skills Default mode prompt prefers symlink Post-install configure step: developer-stack-skills configure

Why global install still asks for project directory:

• Global install has two separate outputs:
  1. Skill files go into shared user-level folder: ~/.ai-skills/developer-stack-skills
  2. Agent config files still get written into one specific project
• Installer asks for Project directory so it knows where to update CLAUDE.md, .clinerules, .roo/config.yml, .cursor/rules/developer-stack-skills.mdc, and .github/copilot-instructions.md
• Global package install does not mean "enable skills for every repo automatically"
• It means "store one shared copy of skills globally, then link chosen project to those skills"

Post-install configure command:

developer-stack-skills configure

Shortcut:

developer-stack-skills
developer-stack-skills install

To force npm to show install-time prompts/logs:

npm install developer-stack-skills --foreground-scripts
npm install -g developer-stack-skills --foreground-scripts

Remove installed skills and agent config:

developer-stack-skills uninstall

Show version:

developer-stack-skills version

Show help:

developer-stack-skills help

Start MCP server (stdio):

developer-stack-skills serve

Or run from local package without global install:

npx developer-stack-skills configure
npx developer-stack-skills serve

Installer will:

1. Detect OS automatically
2. Ask which agent to configure: all, claude, cursor, cline, roocode, or copilot
3. Ask whether to copy files or create symlink
4. Ask which project directory to install into when needed
5. Install all skill folders into project or global skill directory
6. Update agent-specific config files in that project
7. Log package version, package install type (source, local, or global), install scope, OS, source directory, install directory, and each generated config path

Project-level install dir:

<project>/.ai-skills/developer-stack-skills/

Global install dir:

~/.ai-skills/developer-stack-skills/

postinstall skips auto-config in non-interactive environments and in source checkout of this repo. npm also hides lifecycle script output by default unless --foreground-scripts is set. In those cases, run developer-stack-skills configure after installation.

Non-interactive install:

developer-stack-skills install --agent all --mode symlink --dir . --yes
developer-stack-skills uninstall --agent all --dir . --dry-run --yes

Example log output:

[developer-stack-skills] installing version 3.0.0
[developer-stack-skills] package install type: global
[developer-stack-skills] skill install scope: global
[developer-stack-skills] os: windows
[developer-stack-skills] package dir: C:\Users\<you>\AppData\Roaming\npm\node_modules\developer-stack-skills
[developer-stack-skills] project dir: D:\Projects\my-app
[developer-stack-skills] install dir: C:\Users\<you>\.ai-skills\developer-stack-skills
[developer-stack-skills] skill installed: java-spring -> C:\Users\<you>\.ai-skills\developer-stack-skills\java-spring
[developer-stack-skills] cline config updated: D:\Projects\my-app\.clinerules
[developer-stack-skills] install complete

Flags:

• --agent <all|claude|cursor|cline|roocode|copilot>
• --mode <copy|symlink>
• --dir <project-directory>
• --dry-run
• --yes

Commands:

• configure
• install
• uninstall
• serve
• version
• help

MCP Server

Skills are exposed as MCP tools via stdio transport.

developer-stack-skills serve

Add to MCP client config:

{
  "mcpServers": {
    "developer-stack-skills": {
      "command": "developer-stack-skills",
      "args": ["serve"]
    }
  }
}

Or without global install:

{
  "mcpServers": {
    "developer-stack-skills": {
      "command": "npx",
      "args": ["developer-stack-skills", "serve"]
    }
  }
}

Available tools:

| Tool | Description | |---|---| | list_available_skills | List all skills with descriptions and file patterns | | get_skill | Load full SKILL.md for a stack (java-spring, python-backend, frontend, testing, project-conventions) | | get_conventions | Load project-wide conventions (shortcut for get_skill with project-conventions) | | detect_stack | Given a file path, return which skill applies and a ready-to-use get_skill call |

Claude Code Commands

Five slash commands are installed into your project:

| Command | Description | |---|---| | /implement-feature [description] | Detect stack, plan, implement with tests | | /write-tests [target] | Write tests following stack conventions | | /review-pr | Review branch changes against conventions | | /check-deps | Audit dependencies for outdated versions and vulnerabilities | | /add-endpoint [description] | Add REST endpoint following stack and REST conventions |

Hooks

Two Claude Code hooks fire automatically:

| Hook | File | Fires When | |---|---|---| | pre-write | hooks/pre-write.js | Before any file write — injects stack reminder based on file extension | | pre-bash | hooks/pre-bash.js | Before bash commands — warns to verify latest stable version on package installs |

The pre-write hook covers: Java, Kotlin, Python, Angular TypeScript, generic TypeScript/JSX, .env files, and .sql migrations.

The pre-bash hook detects: pip install, uv add, npm install, yarn add, pnpm add, bun add, poetry add, and npx pkg@latest.

Installed Files

Skill files get copied or linked here:

<project>/.ai-skills/developer-stack-skills/

Or for global package installs:

~/.ai-skills/developer-stack-skills/

Agent configs get created or updated here:

• Claude: CLAUDE.md
• Cursor: .cursor/rules/developer-stack-skills.mdc
• Cline: .clinerules
• Roocode: .roo/config.yml
• GitHub Copilot: .github/copilot-instructions.md

Notes:

• copy makes project-local copies of skill folders
• symlink keeps installed skills linked to package source
• Running installer again refreshes installed skill folders and rewrites managed config sections

FAQ

Why does npm install -g developer-stack-skills still ask for Project directory?

Because installer does two different things:

1. It installs skill folders
2. It updates agent config files for a specific project

With global package install, skill folders go to:

~/.ai-skills/developer-stack-skills/

But agent configs still must be written into a real project, for example:

D:\Projects\my-app\CLAUDE.md
D:\Projects\my-app\.clinerules
D:\Projects\my-app\.roo\config.yml

So Project directory prompt is still required. Global install means shared skill storage, not machine-wide auto-enable for every repository.

What is difference between npm install -g developer-stack-skills and npm install developer-stack-skills?

npm install -g developer-stack-skills

• Package installs into global npm directory
• CLI command developer-stack-skills works anywhere
• Skills install into ~/.ai-skills/developer-stack-skills/
• Default install mode is symlink
• Best when you want one shared install reused across many projects

npm install developer-stack-skills

• Package installs into current project's node_modules
• CLI usually runs through npx developer-stack-skills or npm scripts
• Skills install into <project>/.ai-skills/developer-stack-skills/
• Default install mode is copy
• Best when each project should keep its own isolated skill copy

Same in both cases:

• Installer still updates agent config files per project
• Skills are not auto-enabled for every repository on machine

Skills Included

| Skill | File | Use When | |---|---|---| | java-spring | java-spring/SKILL.md | Spring Boot, JPA, REST APIs, JUnit | | python-backend | python-backend/SKILL.md | FastAPI, SQLAlchemy, Pydantic, pytest | | frontend | frontend/SKILL.md | React, Angular, TypeScript, TanStack Query | | testing | testing/SKILL.md | Unit, integration, E2E across all stacks | | project-conventions | project-conventions/SKILL.md | Git, ADRs, naming, PR standards, README |

Stack

• Java: Java 25, Spring Boot 4 / Spring Framework 7, JPA/Hibernate, JUnit 5, Mockito
• Python: Python 3.14+, FastAPI, Pydantic v2, SQLAlchemy 2.x, pytest
• Frontend: React 19+, Angular 21+, TypeScript 5+, TanStack Query, Vitest
• Testing: JUnit 5, pytest, Vitest, Testing Library, Playwright, Testcontainers
• Conventions: Conventional Commits, ADRs, Git Flow or Trunk-Based Development

License

MIT