An extensible hub of AI development skills, packaged as a Claude Code plugin -- currently Magento 2 (architecture, linting, performance, security) and Govard dev-environment orchestration for Magento and Laravel, with more tech stacks added over time.
Every skill follows the open Agent Skills standard (a
SKILL.md file with name/description frontmatter), which Claude Code,
OpenCode, Codex CLI, and GitHub Copilot all understand — see
Installation for how to wire this repo's skills/ folder into
each one, since they don't all scan the same directory name.
Every skill lives under skills/<name>/SKILL.md — this is the layout Claude Code's
plugin loader requires, and it's the single source of truth (no other copy exists
anywhere else in the repo).
dev-skills-hub/
├── README.md # This file (Global documentation and guide)
├── .claude-plugin/
│ ├── plugin.json # Claude Code plugin manifest
│ └── marketplace.json # Self-listing marketplace (source: "./")
│
└── skills/
├── 📦 CORE STANDARDS & ARCHITECTURES (Foundation patterns)
│ └── magento2-dev-core/ # Magento 2 core guidelines (DI, Repositories, Security)
│
├── 🛠️ QUALITY ASSURANCE & AUDITING (Linting and static analysis)
│ ├── magento2-linter/ # PHPCS, PHPStan static checking rules
│ ├── magento2-performance-audit/ # Web vitals, infrastructure and DB profiling
│ └── magento2-security-scan/ # Static vulnerability code scanning
│
├── 🎨 FRONTEND & BACKEND FRAMEWORKS (Domain-specific code)
│ ├── magento2-hyva-dev/ # Alpine.js, Tailwind CSS, CSP payment pages
│ ├── magento2-frontend-dev/ # Luma Knockout.js, LESS, RequireJS
│ └── magento2-backend-dev/ # REST, GraphQL resolvers, Cron, Queues
│
└── 🔧 DEV ENVIRONMENT & CLI TOOLS (Toolchain orchestration)
├── govard-toolbox/ # Base container orchestrator toolbox
├── govard-magento/ # Magento-specific dev env commands
└── govard-laravel/ # Laravel-specific dev env commands
You can easily expand this hub with any new programming language, framework, or utility domain (e.g., React, Python, Docker, CI/CD, AWS, etc.).
Create skills/[domain]-[tool/stack]-[purpose]/ using kebab-case
(e.g., skills/react-nextjs-tailwind/, skills/docker-ops-deployment/).
Every skill folder must contain a SKILL.md file at its root with valid YAML frontmatter:
---
name: your-skill-name
description: |
Describe exactly when the AI Agent should trigger this skill.
Make it descriptive and comprehensive so agents easily understand context.
compatibility: claude, codex, opencode, copilot
depends: [any-dependencies-if-applicable]
metadata:
audience: developers
workflow: your-workflow
---
# Your Skill Title
## Capabilities
Describe what this skill enables the agent to do.
## Best Practice Patterns
Provide code templates, standards, and typical commands.
## Verification
Step-by-step commands to verify output works properly.
compatibility,depends, andmetadataare custom conventions for cross-tool sharing — Claude Code's plugin schema ignores them (onlynameanddescriptionare required), so they're safe to keep.
Add your new skill to the directory tree above and the compatibility matrix below.
Content-format compatible with all four out of the box — actually loading a skill still requires it to sit in the directory name that tool scans (see Installation).
| Skill | Claude Code | Codex CLI | OpenCode | GitHub Copilot |
|---|---|---|---|---|
| Core & Standards | ||||
| magento2-dev-core | ✅ | ✅ | ✅ | ✅ |
| Linting & Auditing | ||||
| magento2-linter | ✅ | ✅ | ✅ | ✅ |
| magento2-performance-audit | ✅ | ✅ | ✅ | ✅ |
| magento2-security-scan | ✅ | ✅ | ✅ | ✅ |
| Frameworks | ||||
| magento2-hyva-dev | ✅ | ✅ | ✅ | ✅ |
| magento2-frontend-dev | ✅ | ✅ | ✅ | ✅ |
| magento2-backend-dev | ✅ | ✅ | ✅ | ✅ |
| Toolchains | ||||
| govard-toolbox | ✅ | ✅ | ✅ | ✅ |
| govard-magento | ✅ | ✅ | ✅ | ✅ |
| govard-laravel | ✅ | ✅ | ✅ | ✅ |
Every tool recognizes the same SKILL.md file, but each one scans its own
directory name — none of them can be pointed at an arbitrary folder like this
repo's bare skills/, so pick the option(s) below for the tools you use.
/plugin marketplace add ddtcorex/dev-skills-hub
/plugin install dev-skills-hub@dev-skills-hub
Updates: /plugin marketplace update dev-skills-hub.
Each tool scans its own directory name, so install.sh clones this repo once
into ~/.dev-skills-hub and links each skill into every tool's expected path:
curl -fsSL https://raw.githubusercontent.com/ddtcorex/dev-skills-hub/master/install.sh | bashRun interactively, it asks for scope (project = current directory, personal
= your home directory, available in every project) and which tools to target.
Re-running the exact same command later is the update — it re-pulls the
cache and re-links. Common flags for non-interactive/CI use:
curl -fsSL .../install.sh | bash -s -- -y --scope project --target claude,codex \
--skills magento2-dev-core,govard-toolbox --mode copy
curl -fsSL .../install.sh | bash -s -- -y --uninstall| Tool | Scans (project scope) | Scans (personal scope) |
|---|---|---|
| Claude Code | .claude/skills/ |
~/.claude/skills/ |
| OpenCode | .opencode/skills/ (also checks .claude/skills/, .agents/skills/) |
~/.config/opencode/skills/ |
| Codex CLI | .agents/skills/ only |
~/.agents/skills/ |
| GitHub Copilot / VS Code | .github/skills/ (also checks .claude/skills/, .agents/skills/, or a custom chat.agentSkillsLocations path) |
~/.copilot/skills/ |
install.sh creates each tool's own dedicated path (symlinked to the
~/.dev-skills-hub cache by default, or real copies with --mode copy) rather than
relying on the secondary paths some tools also check, so ls in your project
shows exactly which tools have a copy.
GitHub Copilot's older "Skillsets" feature (for Copilot Extensions — API tool integrations) is unrelated to the Agent Skills folders above; don't confuse the two when searching Copilot's docs.
Let's continuously expand this hub to automate more of our engineering workflows! 🚀