claude

dev-core

The always-on engineering rules, core skills, and the tier and domain specialist agents. Requires the repo-docs plugin for repo grounding.

0 on GitHubby Personal AI Setupv0.23.5MITupdated yesterdaydevelopment
/

Plugin dev-core from marketplace ai-setup in josippapez/ai-setup. Commands read from the repo's manifest — today.

This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.

What it installs

Skills (11)

  • accessibility

    Use whenever accessibility or a11y work comes up, and for any WCAG question — even when WCAG is never named. Two halves: scan a running page for real violations with the bundled axe-core harness driven through the chrome-devtools MCP, and look up authoritative WCAG 2.2 / 2.1 text with the bundled wc

  • agent-browser

    Fetch facts from the live web and drive a real browser. Use for ANY question whose answer is not already in this repo or in a file you read: library APIs, current versions, changelogs, config keys, CLI flags, specs, error messages, pricing, docs of any kind. Also for interacting with websites: navig

  • agent-orchestration

    Route tasks to the right subagent or Claude model tier based on task type, scope, and cost. The main agent stays orchestrator and prompt-loop owner throughout.

  • code-structure

    Decide where operational logic belongs: actions own domain rules (the why and when), a shared service layer owns reusable mechanics (the how).

  • computer-use

    Drive the real desktop with mouse, keyboard, and screenshots: native app UI, OS dialogs, browser chrome outside the page, and seeing what is actually on screen. Use whenever the thing you need has no API and no DOM behind it.

  • exhaustive-code-review

    Review that finishes instead of stopping. Freeze the review surface in a ledger, fan out one subagent per review lane over the whole surface, and require a verdict for every unit so a later re-run cannot surface issues that were sitting there the whole time.

  • find-improvements

    Research a project for what makes it slow, flaky, costly or painful to work with, then fix the problems one at a time, each with evidence: where the friction shows up, a measurement before and after, a test that fails on the old code, and a check where the code really runs. Ends with the fixes made

  • opensrc

    Read a library actual installed source. Resolves a local cached path with `npx opensrc path <pkg>`, then grep or read it.

  • pr-standard

    The bar a pull request has to clear to merge with no review comments, and the procedure for scoring a PR against it. Covers the PR-level properties (one reason to exist, size, tests that fail on base, description, dependencies, commits, CI) that the always-on rules do not; the hunk-level half is the

  • self-improve

    Turn a correction or a failure from this session into a skill: update the skill that should have caught it, or write a new one. Covers finding the owning file, writing the description so the skill actually triggers, and mirroring the change to the other adapters.

  • tanstack-docs-cli

    Find current TanStack documentation with the TanStack docs CLI.

Subagents (13)

  • dockerfile-specialist

    Audits and hardens Dockerfiles and container builds — minimal/secure base images, digest pinning, layer hygiene, and reproducible, scannable builds. Use for Dockerfile audits, image hardening, and compose validation.

  • docs-maintainer

    Maintains the repository's owning documentation and guidance (rules and skills) so it stays aligned with code and workflow changes. Use for docs-sync triggered by behavior, workflow, or config changes.

  • figma-layout-token-analyst

    Analyzes Figma designs via the Figma MCP, reports layout structure and intent, and maps design values to existing design tokens — flagging token gaps. Read-only design analysis; use before building UI from a Figma reference.

  • free-tier-explorer

    Low-cost agent for exploration, research, summarization, and low-priority background context-gathering.

  • frontend-specialist

    Implements and refactors frontend UI with design-system reuse, accessibility, i18n, and testability as defaults. Use for component work, UI features, and frontend refactors.

  • high-tier-coder

    Opus coding agent, used only when the approach is still undecided, the change is security- or safety-critical, mid-tier-coder already failed, or the user asks for it. Size or file count alone does not qualify; use mid-tier-coder for that.

  • infrastructure-specialist

    Maintains build, CI, and deployment configuration with reliability- and security-focused defaults — deterministic, auditable, least-privilege. Use for CI pipelines, build config, and deploy settings (containers → dockerfile-specialist).

  • low-tier-fast

    Fast, cheap agent for small explicit edits, renames, lint and type fixes, docs and config tweaks, test runs, and one-off lookups.

  • mid-tier-coder

    The default coding agent. Use for implementation work of any size once the approach is clear, including multi-file features, refactors, plugins, and conversions.

  • self-improve-specialist

    Implements requested changes to repeatable agent behavior by updating rules and skills in a consistent single-source-first flow. Use for non-trivial behavior, workflow, or guidance changes that must stay consistent across adapters.

  • test-specialist

    Adds and stabilizes targeted tests with deterministic scope and clear failure diagnostics. Use for test creation, refactoring, and flaky-test stabilization.

  • top-tier-reasoner

    Top-tier reasoning agent for architecture, complex design, deep debugging, ambiguity resolution, and safety- or security-critical decisions. Returns a concise recommendation with trade-offs and risks.

  • wcag-a11y-aa-specialist

    Audits and remediates accessibility issues to WCAG 2.2 A/AA standards for web and mobile UI.

MCP servers (4)

  • interactive

    runs: npx -y @rawwee/interactive-mcp -t 1200 --disable-tools message_complete_notification,intensive_chat

  • context7

    runs: npx -y @upstash/context7-mcp

  • chrome-devtools

    runs: npx -y chrome-devtools-mcp@latest --autoConnect

  • computer-use

    runs: npx -y computer-use-mcp

Hooks (9)

  • SessionStart

    diff -q "${CLAUDE_PLUGIN_ROOT}/package.json" "${CLAUDE_PLUGIN_DATA}/.installed-package.json" >/dev/null 2>&1 || (cd "${CLAUDE_PLUGIN_DATA}" && cp "${CLAUDE_PLUGIN_ROOT}/package.json" . && npm install

  • SessionStart

    node "${CLAUDE_PLUGIN_ROOT}/hooks/link-rules.cjs" 0

  • SessionStart

    node "${CLAUDE_PLUGIN_ROOT}/hooks/link-rules.cjs" 1

  • SessionStart

    node "${CLAUDE_PLUGIN_ROOT}/hooks/link-rules.cjs" 2

  • SubagentStart

    node "${CLAUDE_PLUGIN_ROOT}/hooks/link-rules.cjs" 0 SubagentStart

  • SubagentStart

    node "${CLAUDE_PLUGIN_ROOT}/hooks/link-rules.cjs" 1 SubagentStart

  • SubagentStart

    node "${CLAUDE_PLUGIN_ROOT}/hooks/link-rules.cjs" 2 SubagentStart

  • UserPromptSubmit

    node "${CLAUDE_PLUGIN_ROOT}/hooks/inject-rules-digest.cjs"

  • Stop

    node "${CLAUDE_PLUGIN_ROOT}/hooks/recheck-stop.cjs"

View source on GitHub

More from josippapez/ai-setup

All 12 plugins →

Vendored web design, motion, and 3D skills from MengTo/Skills, GreenSock, Emil Kowalski, ibelick, and Vercel's web interface guidelines. Skills only; no rules, hooks, or MCP servers.

40 skills

0

repo-docs

claude

Local semantic doc search, installed-package lookup and JS/TS file-impact tools for one repository. dev-core requires it.

2 commands · 1 MCP server · hooks

0

Always-on rules for how output reads: short and plain in anything a person sees, and only what was asked for in anything that leaves the machine.

1 skill · hooks

0

feedback

claude

Local feedback inbox MCP for the AI setup: collect_feedback records bugs, pain points, ambiguities, and ideas; read_feedback lists them so they can be acted on later. Stored as JSONL inside the plugin.

1 MCP server · hooks

0

verified

claude

Stop-hook correctness gate: scores an answer's factual claims against what the session actually ran, blocks on anything unbacked, and records verdicts to a replay ledger so pattern changes are scored before they ship.

1 command · hooks

0

One skill, building-blocks: explains what is going on, what was built, or the answer to a question in plain words, for someone who was not in the session. For end-of-session handoffs that are actually readable.

1 skill

0

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

nextjs

claude

Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.

6 skills

vercel/next.js 143,495

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

Taste Skill

claudecodex

tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.

1 skill

Leonxlnx/taste-skill 114,391

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Maintain dev-core?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins12 plugins