Skip to content

dnunez24/config

v0.2.0MIT

House dev tool configuration: skills, format-on-edit hooks, and Markdown/Biome language servers.

GitHub

web-config plugin

Complementary to the config init CLI, not an alternative: the CLI writes config files into a repository; this plugin changes how an agent behaves while working in one. Neither installs the other.

Install

# Oh My Pi
omp plugin marketplace add dnunez24/web-config
omp plugin install web-config@dnunez24

# Claude Code
/plugin marketplace add dnunez24/web-config
/plugin install web-config@dnunez24

# Codex
codex plugin marketplace add dnunez24/web-config --sparse .agents/plugins
# then: /plugins in the CLI, install web-config, and run /hooks to review and
# trust the bundled hooks -- Codex skips plugin hooks until you trust them.

Oh My Pi needs /reload-plugins for skills and commands, but a session restart for newly installed hooks and extension modules.

What's in here

  • skills/use-shared-config, skills/contribute-shared-config -- Agent Skills, portable across all three hosts.
  • hooks/hooks.json -- PostToolUse format-and-report and Stop typecheck, read natively by Claude Code and Codex.
  • hooks/post/omp-format-changed.ts -- the same format-and-report behavior for Oh My Pi, loaded via omp.extensions in plugin/package.json (Oh My Pi does not read hooks.json).
  • .lsp.json / omp/lsp.json -- Markdown (rumdl), TypeScript/JavaScript (tsc --lsp --stdio, TypeScript 7's native Language Server Protocol (LSP) server), prose linting for Markdown and TS/JS (vale-ls, scoped to match .vale.ini) on both hosts, and, for Claude Code only, Biome. typescript@7.0.2 contains no tsserver, so the third-party typescript-language-server cannot run against it -- but tsc itself now speaks LSP directly (typescript-go), which both configs use instead. The Stop hook still runs a full tsc typecheck as a backstop. Both hosts require rumdl on PATH or resolvable via node_modules/.bin, and vale/vale-ls on PATH -- neither host installs any of them.