agentic-devkit

A model-agnostic toolkit of AI-agent plugins for product teams. One global clone generates scoped AI context (skills, conduct, hooks, permissions) for Claude Code, Cursor, and Codex across all your projects. Edit a skill once; every project picks it up.

Quick Start

Install the toolkit once per machine. devkit-install clones it to ~/.claude/agentic-devkit (the global clone, DEVKIT_HOME), symlinks the universal core skills + the devkit stack-router into ~/.claude/skills/, installs the core subagents, and adds a daily auto-update hook.

git clone https://github.com/Blaryxoff/agentic-devkit.git ~/.claude/agentic-devkit
~/.claude/agentic-devkit/bin/devkit-install

Per project, declare the stack in .devkit/toolkit.json and (for Cursor/Codex, or to emit Claude stack subagents/MCP) run the adapter from the global clone:

cd my-project
~/.claude/agentic-devkit/bin/devkit-resolve --init          # write .devkit/toolkit.json

~/.claude/agentic-devkit/bin/devkit-install --cursor         # .cursor/ rules + skills + hooks
~/.claude/agentic-devkit/bin/devkit-install --codex          # .codex/ resolved skills + AGENTS.md
~/.claude/agentic-devkit/bin/devkit-install --claude         # .claude/ stack subagents, hooks, .mcp.json

For Claude Code, the core skills + devkit router are already global after devkit-install; the per-project --claude run is only needed when a stack ships subagents, hooks, or MCP servers.

CLI Usage

• List resolved plugin names.

~/.claude/agentic-devkit/bin/devkit-resolve

• Create .devkit/toolkit.json interactively.

~/.claude/agentic-devkit/bin/devkit-resolve --init

• Validate config and show resolved set.

~/.claude/agentic-devkit/bin/devkit-resolve --validate

• List resolved plugin directories.

~/.claude/agentic-devkit/bin/devkit-resolve --dirs

• Generate tool-specific config.

~/.claude/agentic-devkit/bin/devkit-resolve --adapter=...

Supported adapters: claude, cursor, codex.

Available Plugins

Plugin	Layer	Description	Dependencies
devkit-core	core	Cross-stack shared standards: workflow, git, spec/test-case process, review conventions	(always enabled)
devkit-frontend	stack	Tool-agnostic frontend architecture and generic CSS standards	core
devkit-laravel	framework	Laravel conventions: architecture, PHP, security, Inertia integration	core
devkit-nuxt	framework	Nuxt conventions: SSR, data-fetching, TypeScript, BEM/SCSS workflows	core, frontend, vue
devkit-vue	framework	Vue component, composable, and state organization conventions	core, frontend
devkit-inertia	framework	Inertia.js transport, page props contracts, and form/navigation behavior	core
devkit-tailwind	styling	Tailwind CSS utility conventions and tokenization rules	core
devkit-css	styling	Modern CSS intelligence layer from css.dev	core

Example Stacks

Laravel + Vue + Tailwind

{
  "version": 1,
  "enabled": [
    "devkit-laravel",
    "devkit-vue",
    "devkit-inertia",
    "devkit-tailwind"
  ]
}

Resolves: core -> frontend -> vue -> inertia -> laravel -> tailwind

Nuxt

{
  "version": 1,
  "enabled": [
    "devkit-nuxt"
  ]
}

Resolves: core -> frontend -> vue -> nuxt

Laravel API only

{
  "version": 1,
  "enabled": [
    "devkit-laravel"
  ]
}

Resolves: core -> laravel

How It Works

1. Configure enabled plugins in .devkit/toolkit.json (or run ~/.claude/agentic-devkit/bin/devkit-resolve --init).
2. Resolver auto-includes devkit-core and transitive dependencies, validates the graph, and sorts by layer.
3. Adapter generation emits tool-specific files for the resolved set only.

Adapter	Generated files
claude	.claude/settings.json (hooks), .claude/agents/*.md (stack subagents), .mcp.json — core skills + router are global
cursor	.cursor/skills/devkit-*--*/, compact conduct-index rules, MCP config, and hooks
codex	.codex/skills/devkit-*--*/ for non-core plugins and compact conduct indexes in AGENTS.md

Generated text (conduct paths in .mdc / AGENTS.md) references the global clone at ~/.claude/agentic-devkit, so output is identical regardless of where the project lives on disk. Disabled plugins do not enter generated AI context.

devkit-install keeps only devkit-core skills globally for Codex and Cursor and removes stale global non-core links. Their project adapters link only resolved non-core skills, including transitive dependencies; plugins such as devkit-css stay absent unless explicitly enabled. Generated AGENTS.md / .mdc rules point to one conduct index per plugin and require scope-driven loading instead of listing the full conduct corpus. Re-run the adapter after changing .devkit/toolkit.json, then start a new agent session to refresh its skill catalog.

The global install also merges a native Codex PreToolUse coder gate into ~/.codex/hooks.json. On the first apply_patch edit in a session it blocks once and instructs Codex to load devkit-coder, which pulls in the core and active-stack conduct before the edit is retried. Review and trust the hook with /hooks after installation or changes.

Claude Code Setup

Core skills and the devkit stack-router are installed globally by devkit-install (symlinked into ~/.claude/skills/), so Claude Code auto-discovers them in every project. Core skills auto-match natively; the devkit router reads .devkit/toolkit.json and loads the matching stack skill + conduct on demand from the global clone.

Run the per-project Claude adapter only when a stack ships subagents, hooks, or MCP servers:

~/.claude/agentic-devkit/bin/devkit-install --claude --project=.

This emits .claude/agents/*.md (stack subagents), .claude/settings.json (plugin hooks), and .mcp.json — all referencing the global clone. Re-run only when the enabled-plugin set or infra files change; skill/conduct edits propagate live through the clone (kept current by the daily auto-update hook).

Repository Layout

plugins/              Convention-based plugin discovery (plugins/*/plugin.json)
  core/
  frontend/
  laravel/
  nuxt/
  vue/
  inertia/
  tailwind/
  css/
bin/
  devkit-install      Global installer: core skills + router + subagents + auto-update hook
  devkit-update       Timestamp-guarded `git pull --ff-only` for the global clone
  devkit-resolve      CLI: init/resolve/validate/adapter generation
adapters/
  _lib/resolve.sh     Shared resolution logic
  _lib/hooks.sh       Shared hook merge/translation helpers
  claude/generate
  cursor/generate
  codex/generate
schemas/              JSON schemas for toolkit and plugin manifests
examples/             Starter .devkit/toolkit.json presets
howto/                Developer guides (Russian)

Extending the Toolkit

Add a plugin

1. Create plugins/<name>/plugin.json.
2. Add skills at plugins/<name>/skills/<skill>/SKILL.md.
3. Add conduct docs at plugins/<name>/conduct/*.md (if applicable).
4. Verify in a consuming project with ~/.claude/agentic-devkit/bin/devkit-resolve --validate.

Add a skill

Add SKILL.md under plugins/<plugin>/skills/<skill-name>/. Adapters pick it up on next generation.

Add an adapter

See adapters/README.md.

Requirements

• jq
• python3
• bash 3.2+