By vdhanaraj
House conventions standard plus skills to scaffold (bootstrap), reconcile/upgrade (sync), and orient projects against it, with a session-start drift check.
Stand up a NEW repo against the house conventions standard — scaffold the doc skeleton, a verbatim version-stamped CONVENTIONS.md, the project stubs, the vendored config defaults, _local, and the AGENTS.md/CLAUDE.md pointer. One-time. For an EXISTING repo (reconcile drift, pull upstream upgrades) use the sync skill instead. Never clobbers existing files.
Read-only orientation + drift classifier for the current repo. Reads ARCHITECTURE.md then CONVENTIONS.md to ground the session, then reports where the repo stands relative to the standard and whether every gap is accounted for — version drift, undocumented divergence (the repo departs from the standard but ARCHITECTURE.md doesn't say why), and brownfield repos not yet on the standard. Cheap and offline by default; never writes files. Use at session start, after a session-start drift notice, or to prime context. Full content diffing is `orient --deep`; applying changes is the sync skill.
Reconcile an EXISTING repo against the house conventions standard and pull upstream upgrades. Compares the project's vendored artifacts (CONVENTIONS.md + .conventions/*.base.*) against the version-stamped canonical, surfaces diffs, and resolves them in either direction — never silently overwrites. Use to check/upgrade a project's conventions, after a "newer version available" notice, or when conventions drift. For a brand-new repo use bootstrap instead.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
The canonical home for the house conventions standard, plus the skills and hook that let Claude and Codex apply it to a project and keep it current over time.
This repo is three things at once:
CONVENTIONS.md, version-stamped, the single
canonical copy. Everything else references it; nothing duplicates it.conventions plugin — three skills + a session-start hook (below).conventions-source and check
it for newer versions.| Skill | When | What it does |
|---|---|---|
conventions:bootstrap | new repo | Scaffold the doc skeleton + a verbatim CONVENTIONS.md + templates/ stubs + vendored config defaults + _local/ + AGENTS.md/CLAUDE.md. One-time. |
conventions:sync | existing repo | Reconcile drift and pull upstream upgrades for the tracked artifacts (CONVENTIONS.md + .conventions/*.base.*). Bidirectional, never silently overwrites. |
conventions:orient | every session | Read-only: read ARCHITECTURE.md → CONVENTIONS.md, run the cheap version check, surface anything stale. Never touches files. |
hooks/session-start.sh runs when you open a repo. It does a cheap, offline, deterministic
version compare (project's vendored conventions-version vs the installed standard) and:
ARCHITECTURE.md + CONVENTIONS.md so the session
starts grounded, and points you at conventions:sync.bootstrap writes a pin into the project's own CONVENTIONS.md frontmatter:
---
conventions-version: 1 # the version this copy is
conventions-source: [email protected]:platform/conventions.git # or a local path
---
conventions-version is compared as an integer; conventions-source tells sync where
upstream lives (a local clone for personal use, an internal git remote at work). The standard
repo is tagged vN to match the stamp.
Install the plugin from the repo-local marketplace (no raw symlinking):
.claude-plugin/marketplace.json.codex-plugin/plugin.json /
.agents/plugins/marketplace.jsonInstalling the plugin wires the skills (conventions:*) and the session-start hook on both
tools. For a team, host this repo internally and register it as a shared marketplace.
The full design and the decisions behind it live in _local/PROPOSAL.md (gitignored kickoff
scratch). The durable subset migrates into this README and CONVENTIONS.md.
Effectively none. The engine is git + the agent + a few lines of POSIX sh. Config defaults
are vendored files, not packages. A scaffolded app will pull its own UI/runtime deps — that's
app-level and separate from this plugin's (dependency-free) surface.
npx claudepluginhub vdhanaraj/conventions --plugin conventionsPermanent coding companion for Claude Code — survives any update. MCP-based terminal pet with ASCII art, stats, reactions, and personality.
Intelligent prompt optimization: injects the right context at the right moment so Claude lands a better first output. Clarifies vague prompts with research-based questions, plus targeted nudges for approach selection, plan readability, workflow routing, background execution, subagent routing, output readability, user-decision questions, and plan-mode assessment
Semantic search for Claude Code conversations. Remember past discussions, decisions, and patterns.