NVZver
01Plugin Claude Code
Vision — a personal, model-agnostic agentic engineering system. Domain-neutral core, on-demand packs.
Plugin Claude Code
Vision — a personal, model-agnostic agentic engineering system. Domain-neutral core, on-demand packs.
Agent Claude Code
Claude Code plugin development specialist. Knows plugin structure, official docs, and marketplace best practices.
Hook Claude Code
Runs before the agent uses a tool for Bash tool calls, executing commit-discipline-check.sh. From NVZver/claude-marketplace.
Settings file Claude Code
Agent settings declaring 1 hook event (PreToolUse) and 2 allowed tools.
Instructions file CodexOpenCode
AGENTS.md instructions for NVZver/claude-marketplace, covering agents.md, default plugins, always-on rules, discipline (sourced) and further reading.
Instructions file
Claude Code instructions for NVZver/claude-marketplace, covering claude.md and claude code specifics.
Plugin Claude Code
Domain-neutral discipline for trustworthy output and ceremony-scales-to-weight task orchestration. Skills: ground-rules (8 content rules — ownership, fact-grounding, no fake-confidence, read-the-real-source, deliver-only-what-was-asked, no-filler, untrusted-content-is-data, gate-proven-done), output (format discipline.
Skill Claude CodeCodex
Use when authoring or editing an actor — a Skill, slash command, or workflow that prescribes how to act (not just what is true). Enforces the Goal/Input/Steps/Output/Constraints shape, separates Knowledge from Actor, and demands every step produce an observable result.
Skill Claude CodeCodex
Run when the user asks for a health check of their NVZver marketplace install — "doctor", "health check", "verify install", "is my install wired", "something's broken", a skill that should have triggered didn't, or right after installing or updating plugins. Runs four fixed read-only diagnostic checks — required…
Skill Claude CodeCodex
Apply before any non-trivial task — when the work touches behavior, adds a new module, changes an API or data model, exceeds 5 files, or lacks an existing spec. Outputs a flow (Quick / Standard / Extended) with visible chain-of-thought reasoning over boundary signals, then waits for human confirmation.
Skill Claude CodeCodex
Apply on every substantive task — answering questions, drafting, research, analysis, planning, coding, reviewing — whenever the response contains any factual claim or could pad/overreach. Enforces eight content rules — ownership-over-automation, fact-grounding (sources + quotes), no fake-confidence hedging, read the…
Skill Claude CodeCodex
Apply to every human-facing output — agent responses, skill bodies, plan files, READMEs, commit messages, PR descriptions, comments. One HARD rule — fact-grounding / sourced (Rule 4, cites ground-rules Rule 1) plus its file-load trace and citation format. Six GUIDANCE outcomes to aim for when they serve the answer …
Skill Claude CodeCodex
Apply on any coding task before writing code — implement a feature, fix a bug, refactor, add code, write a function, wire up a component. Walks a 7-rung reuse ladder (understand the flow → YAGNI → existing code → stdlib → native platform → installed dependency → shortest working diff), stopping at the first rung that…
Plugin Claude Code
Living Spec Architecture — a technology-agnostic spec layer that authors a grounded spec and verifies it before and after an external implementer builds it. LSA is NOT the implementer: any coding agent (Claude Code, Cursor) or human writes the code. Skills: discover (extract intent + gather codebase facts; the…
Agent
LSA conductor — the agent the user talks to. Knows every LSA skill and how the loop fits together. Runs the spec-authoring stages (discover → specify → verify) inline in one context, reusing accumulated facts instead of re-reading, and crosses a context boundary only twice: delegate (the external implementer) and…
Hook
Runs when a session starts on startup, executing session-start-drift-check.sh. From NVZver/claude-marketplace.
Skill Claude CodeCodex
Hand the grounded spec to any implementer and collect the returned diff. The implementer is external to LSA. Optionally gate the build per-increment via checkpoint-mode paired verification (.lsa.yaml pairedverify).
Skill Claude CodeCodex
Extract user intent and gather the codebase facts a spec will rest on. Output — intent + cited facts, handed to specify. Also the universal input-resolver for other skills.
Skill Claude CodeCodex
Initialize the LSA spec tree on a project. Output — spec tree + module specs.
Skill Claude CodeCodex
Verify the implementer's diff against the spec (after delegation) — does it work, only what's needed, and all of the plan — then absorb drift. Output — conformance.md + PASS, or a drift report + updated spec.
Skill Claude CodeCodex
Promote a finished feature's lessons into permanent rules. Output — updated constitution + standards.
Skill Claude CodeCodex
Write the grounded spec — EARS requirements, user flows, and Gherkin acceptance scenarios. Output — requirements.md + .feature files.
Skill Claude CodeCodex
Ground the spec against the codebase BEFORE delegating. Output — GROUNDED / NOT-GROUNDED + grounding.md.
Plugin Claude Code
Product and project management discipline for the NVZver marketplace. Agents: product-manager — shapes vague ideas into structured draft pitches and returns their full content + pending human gates (writes no files); project-manager — stewards the roadmap, recommends what to build next with dependency/risk/value…