PHPackages jardis/dev-skills - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. jardis/dev-skills ActiveComposer-plugin[Utility & Helpers](/categories/utility) jardis/dev-skills ================= Composer plugin that installs Jardis Skills and aggregates AGENTS.md for AI-assisted development (Claude Code, Cursor, Continue, Aider) v1.0.0(1w ago)0102MITPHPPHP >=8.3CI passing Since Jun 1Pushed 1w agoCompare [ Source](https://github.com/jardisTools/dev-skills)[ Packagist](https://packagist.org/packages/jardis/dev-skills)[ RSS](/packages/jardis-dev-skills/feed)WikiDiscussions main Synced 1w ago READMEChangelog (1)Dependencies (5)Versions (3)Used By (2) jardis/dev-skills ================= [](#jardisdev-skills) Composer plugin that automatically supplies your AI agent (Claude Code, Cursor, Continue, Aider, ...) with all rules and APIs for the Jardis packages in use — one command, no configuration. Part of the **[Jardis Business Platform](https://jardis.io)** — DDD ecosystem with integrated AI support. --- What does the plugin do? ------------------------ [](#what-does-the-plugin-do) After `composer install` or `composer update`, the plugin scans your `vendor/` directory for `jardis*` packages, copies their skill definitions (`vendor//.claude/skills//`) into your project (`.claude/skills//`), and aggregates all `AGENTS.md` files from Jardis packages into a single `AGENTS.md` in the project root. Result: Claude Code, Cursor & Co. automatically know the rules, patterns, and APIs of the packages you have pulled in via Composer. Additionally, the plugin ships **9 cross-package skills** of its own: architecture, pattern, and testing rules; the `schema-authoring` guide for the Jardis Designer; and five `platform-*` guides for working on Designer-generated code — `platform-implementation` (fachlogik on top of generated code, including the layout of generated PHP classes), `platform-usage` (wiring generated Commands/Queries into an HTTP / CLI / queue transport), `platform-versioning` (ClassVersion resolution and the versioning model), `platform-workflow` (the FlowDesigner Workflow-Engine API), and `platform-cookbook` (Phase-3 recipes, troubleshooting, and event transport). Which of these get copied into your project is controlled via `composer.json` — see [Configuring bundled skills](#configuring-bundled-skills). **No bundled skills are installed by default**; you opt in explicitly. --- Installation ------------ [](#installation) ``` composer require --dev jardis/dev-skills ``` After installation you will see a line such as: ``` Jardis Skills installed: skills, AGENTS.md aggregated. See https://docs.jardis.io/en/skills ``` From that point on, your project contains: ``` your-project/ ├── .claude/ │ └── skills/ │ ├── adapter-cache/ ← from vendor/jardisadapter/cache/ │ ├── support-repository/ ← from vendor/jardissupport/repository/ │ ├── rules-architecture/ ← from jardis/dev-skills itself │ ├── rules-testing/ ← from jardis/dev-skills itself │ └── ... └── AGENTS.md ← aggregated content of all jardis/*-AGENTS.md ``` Requirements: PHP >= 8.3, Composer >= 2. --- Which skills are installed? --------------------------- [](#which-skills-are-installed) The plugin **detects** skills exclusively by directory name prefix. These prefixes are reserved for Jardis: PrefixSource`adapter-*``jardisadapter/*` (HTTP, Cache, Messaging, Mailer, ...)`core-*``jardiscore/*` (Foundation, Kernel)`support-*``jardissupport/*` (Repository, Validation, Workflow, ...)`tools-*``jardistools/*` (DbSchema). The bundled `tools-definition` skill was retired — Designer YAML vocabulary lives in `tools-builder-engine` (Builder repo).`schema-*`Plugin itself — `schema-authoring` for the Designer input format`platform-*`Plugin itself — `platform-implementation` (working on generated code), `platform-usage` (wiring Commands/Queries into a transport), `platform-versioning` (ClassVersion resolution + versioning model), `platform-workflow` (FlowDesigner Workflow-Engine API), `platform-cookbook` (Phase-3 recipes, troubleshooting, event transport)`rules-*`Plugin itself — `rules-architecture`, `rules-patterns`, `rules-testing`**Custom skills with a different prefix** (`my-*`, `internal-*`, ...) are left untouched by the plugin — neither during install nor during uninstall. --- Configuring bundled skills -------------------------- [](#configuring-bundled-skills) The 9 bundled skills (`schema-authoring`, `platform-implementation`, `platform-usage`, `platform-versioning`, `platform-workflow`, `platform-cookbook`, `rules-architecture`, `rules-patterns`, `rules-testing`) are **opt-in**. Controlled via `composer.json`: ``` { "extra": { "jardis/dev-skills": { "bundled-skills": true } } } ``` **Accepted values:** ValueEffectKey absent or `false`No bundled skills (default)`true`All 9 bundled skills`["rules-*", "schema-authoring"]`Whitelist shortcut — only matching skills`{ "include": [...], "exclude": [...] }`Apply include first, then exclude**Examples:** ``` "bundled-skills": ["rules-*"] ``` Installs `rules-architecture`, `rules-patterns`, `rules-testing`. ``` "bundled-skills": { "include": ["rules-*"], "exclude": ["rules-patterns"] } ``` Installs `rules-architecture` and `rules-testing`, **not** `rules-patterns`. ``` "bundled-skills": { "exclude": ["rules-patterns"] } ``` Installs all bundled skills except `rules-patterns` (missing `include` = all). **Pattern syntax:** Shell globs via `fnmatch()` — `*` matches anything, `?` matches one character. No regex. **Sync behavior:** The config is the source of truth. If you narrow `bundled-skills` (e.g. from `true` to `["rules-*"]`), the next `composer install` removes the deselected bundled skills from `.claude/skills/`, **even if you modified them locally**. Vendor skills and custom skills without a Jardis prefix (`my-*`, `internal-*`) are left untouched. **Invalid config** (e.g. `bundled-skills: 42`): console warning, falls back to the default (no bundled skills). No abort. > **Upgrade notes:** > > - **Bundle grown to 9 skills (2026-06-01).** Three `platform-*` guides were added for working on Designer-generated code: `platform-versioning` (ClassVersion resolution + versioning model), `platform-workflow` (FlowDesigner Workflow-Engine API), and `platform-cookbook` (Phase-3 recipes, troubleshooting, event transport). They are opt-in like the rest; a `["platform-*"]` whitelist now installs all five platform skills. > - **Bundle slimmed to 6 skills (v4, 2026-05-23).** `tools-definition` was retired from the dev-skills bundle. Its Schema-YAML coverage was already in `schema-authoring`; the Aggregate / Source / FieldMap / Lists / Flow vocabulary moved to `tools-builder-engine` in the Builder repo (Persona E — Builder dev, outside this bundle). Consumers with `"bundled-skills"` configs that referenced `tools-definition` or `tools-*` should drop the entry; no other action needed. See `docs/PRD-skill-overhaul.md` §V4. > - The earlier bundled-skills reshape (v1–v3) removed three `plan-*` skills (`plan-requirements`, `plan-ddd-modeling`, `plan-data-discovery`), added `schema-authoring` as their focused replacement, and merged `tools-builder` into `platform-implementation` §1. > - **New (v3):** `platform-usage` covers the thin layer between the generated Domain entry points and HTTP / CLI / queue / worker code — call chain, bootstrap lifetime, DomainResponse → transport mapping. Pair with `platform-implementation` when shipping a service. > - `schema-authoring` ships a companion `examples/` directory with a full MeterDevice `Schema.yaml` so the AI can refer to a complete working artefact instead of reconstructing one from the spec. > - Before this version all bundled skills were always installed. Set `"bundled-skills": true` to restore the always-install behavior, or choose a subset config that fits your project. --- Conflicts --------- [](#conflicts) ### Skill directories [](#skill-directories) If a skill directory under `.claude/skills//` already exists during install (e.g. because you maintained it yourself or an older version came from a Jardis package), the plugin moves the existing directory to `.claude/skills/.backup/` and installs the new version. The console shows a warning with the backup path. ``` jardis/dev-skills: existing skill "adapter-cache" moved to .claude/skills/adapter-cache.backup ``` The backup is **not** deleted automatically — you decide whether you need it. Existing `*.backup` directories are **never** treated as skills: the plugin skips them during discovery and never backs them up again, so repeated installs cannot pile up `…​.backup.backup` directories. ### AGENTS.md [](#agentsmd) The plugin manages a **managed block** in `AGENTS.md` between the markers `\` and ``. Everything outside these markers belongs to you and is left untouched. If an aggregated source package ships its **own** managed block in its `AGENTS.md` (e.g. a Jardis package that itself consumes this plugin), those markers are **stripped** during aggregation — only the package's content outside its markers is embedded. The result therefore always has exactly one BEGIN/END pair, never nested markers. - **File does not exist yet:** The plugin creates `AGENTS.md`; content is the managed block only. - **File exists without markers** (your own `AGENTS.md`): The plugin backs up the original once to `AGENTS.md.backup`, carries your content into the new file, and appends the managed block at the bottom. Console: ``` jardis/dev-skills: existing AGENTS.md moved to /path/AGENTS.md.backup ``` The backup is **not** deleted automatically. - **File exists with markers** (re-run): The managed block is replaced in place; your content above and below remains unchanged — including its position. No backup, no warning. - **Duplicate / nested markers** (more than one BEGIN and/or END, e.g. left behind by an older plugin version that appended instead of replacing): The plugin **self-heals**. The whole region from the first BEGIN to the last END is treated as the managed block and collapsed into a single fresh block; your content outside the markers stays untouched. A notice is printed so the cause stays visible: ``` jardis/dev-skills: korrupte AGENTS.md repariert (mehrfacher managed block zusammengeführt). ``` - **Corrupt markers** (only HEADER, only FOOTER, or the first BEGIN sitting after the last END): Install aborts with `InstallFailedException` — these cases are not unambiguously healable. Fix the file manually and run `composer install` again. --- Uninstallation -------------- [](#uninstallation) ``` composer remove jardis/dev-skills ``` During uninstall the plugin removes: - All skill directories with a Jardis prefix (`adapter-*`, `core-*`, `support-*`, `tools-*`, `schema-*`, `platform-*`, `rules-*`) - The managed block between the markers from `AGENTS.md`. Further behavior depends on what else is in the file: - Only the managed block in the file → the entire file is deleted. - Managed block plus your own content → only the block is removed; your content and the file are kept. - Corrupt markers (only HEADER or only FOOTER) → file is left untouched, console shows a warning. **Left untouched:** - Skills with the legacy `plan-*` prefix from earlier versions of this plugin (the bundled `plan-*` skills were retired; if a `plan-*` directory still exists in your project it is now treated as a custom skill) - Skills without a Jardis prefix (your own) - `.backup` directories from earlier conflicts (including `AGENTS.md.backup`) - An `AGENTS.md` without markers (no Jardis aggregation → no reason to touch it) --- Shipping your own Jardis-compatible skills (for package maintainers) -------------------------------------------------------------------- [](#shipping-your-own-jardis-compatible-skills-for-package-maintainers) If you are building a Composer package that should ship a skill to the plugin, two things are sufficient: 1. **Package name with a `jardis` prefix** (e.g. `jardisadapter/foo`, `jardissupport/bar`) — the plugin only scans `vendor/jardis*/`. 2. **Skill file** at `/.claude/skills//SKILL.md`. Recommended prefix per the table above (`adapter-*`, `support-*`, ...) — otherwise the plugin will not ignore the skill, but the uninstall behavior will not apply. 3. **Optional:** `/AGENTS.md` in the package root. Content is aggregated into the project `AGENTS.md` during install. No further configuration needed — no `extra:` block in `composer.json` required. --- Troubleshooting --------------- [](#troubleshooting) **Skills do not end up in the project**The plugin triggers on `post-install-cmd` / `post-update-cmd`. If you call `composer require jardis/dev-skills` inside another Composer script, these events do not fire. Solution: run a separate `composer install` in the project root. **My `AGENTS.md` is not removed during uninstall**This is intentional: if the file does not contain the managed block marker `\`, the plugin assumes you have manually taken over or rewritten it. You can only delete it yourself. **Vendor package has a skill but it is not copied**Check: is the package name under `vendor/jardis*/`? The plugin scans exclusively this glob pattern (`vendor/jardis*/*/.claude/skills/*/SKILL.md`). Packages without a `jardis` prefix are ignored. **Custom skill was moved to `.backup/`**This happens when your skill uses one of the Jardis prefixes and the plugin copies a same-named skill from a vendor package. Renaming (e.g. `adapter-cache` → `my-cache`) resolves this permanently. --- Development (plugin maintainers) -------------------------------- [](#development-plugin-maintainers) Docker-based via `make`: ``` make install # composer install make phpunit # Tests make phpstan # Static analysis level 8 make phpcs # PSR-12 make start / make stop # Container lifecycle ``` Architecture: Closure-Orchestrator pattern (`src/SkillInstaller.php`, `src/SkillUninstaller.php`), handlers as `__invoke()` closures under `src/Handler/`, value objects under `src/Data/`. Composer events via `Composer\Plugin\PluginInterface` + `Composer\EventDispatcher\EventSubscriberInterface` in `src/Plugin.php`. More details: --- License ------- [](#license) MIT — see [LICENSE.md](LICENSE.md). ### Health Score 43 — FairBetter than 89% of packages Maintenance98 Actively maintained with recent releases Popularity7 Limited adoption so far Community10 Small or concentrated contributor base Maturity49 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Unknown Total 1 Last Release 8d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/e07a1b668e9e01ee6d1b85de7b3be1c2513f68aae9494b2011d1592104d5daa0?d=identicon)[jardis](/maintainers/jardis) --- Top Contributors [![Headgent](https://avatars.githubusercontent.com/u/245725954?v=4)](https://github.com/Headgent "Headgent (1 commits)") --- Tags dddcomposer-pluginskillsclaude-codeHeadgentjardisai-assistedagents.md ### Code Quality TestsPHPUnit Static AnalysisPHPStan Code StylePHP\_CodeSniffer Type Coverage Yes ### Embed Badge ![Health badge](/badges/jardis-dev-skills/health.svg) ``` [![Health](https://phpackages.com/badges/jardis-dev-skills/health.svg)](https://phpackages.com/packages/jardis-dev-skills) ``` ### Alternatives [symfony/runtime Enables decoupling PHP applications from global state 74694.9M933](/packages/symfony-runtime)[vaimo/composer-patches Applies a patch from a local or remote file to any package that is part of a given composer project. Patches can be defined both on project and on package level. Optional support for patch versioning, sequencing, custom patch applier configuration and patch command for testing/troubleshooting added patches. 3014.5M22](/packages/vaimo-composer-patches)[drupal/core-composer-scaffold A flexible Composer project scaffold builder. 5344.1M525](/packages/drupal-core-composer-scaffold)[mnsami/composer-custom-directory-installer A composer plugin, to help install packages of different types in custom paths. 1465.3M59](/packages/mnsami-composer-custom-directory-installer)[drupal/core-project-message Adds a message after Composer installation. 2124.0M192](/packages/drupal-core-project-message)[llm/skills AI skills discovery and management system for LLM agents 212.8k3](/packages/llm-skills) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)