By yandy-r
Yandy's Claude Infrastructure toolkit — consulting / systems-integration workflows. Phase 0 scaffolding.
Assemble a signed evidence bundle for the active customer from an evidence stub plus supplemental execution metadata.
Ad-hoc cross-customer isolation check for a path or text blob using the customer-guard detection library.
Scaffold a new yci customer profile from _template.yaml.
Produce a dual-branded Method of Procedure deliverable for the active customer from a reviewed change input.
Produce a dual-branded network change review deliverable (blast radius, rollback plan, pre/post checks, evidence stub) for the active customer.
Produce a typed blast-radius label (tenants, services, devices, dependencies, downstream consumers, RTO band, confidence, coverage gaps) for a proposed change against the active customer's inventory. Use when the user runs /yci:blast-radius, asks "what breaks if I change X", needs impact analysis before a CAB submission, or needs the structured JSON label consumed by yci:network-change-review, yci:mop, yci:evidence-bundle, and the change-window-gate hook. Reads the active customer profile's inventory.adapter (file minimum; netbox stub).
Ad-hoc cross-customer isolation check. Runs the customer-isolation detection library against a single path or text blob and reports allow/deny with the same catalogued errors as the PreToolUse hook. Useful for validating pastes and test fixtures before running a tool that would otherwise trigger the guard.
Load, switch, and scaffold yci customer profiles. Use when the user runs /yci:switch, /yci:whoami, or /yci:init — or asks to see/change/create the active customer context. Resolves the active customer via the 4-tier precedence chain ($YCI_CUSTOMER > .yci-customer dotfile > MRU > refuse) and persists state to <data-root>/state.json. All downstream yci skills depend on this one — it is the load-bearing primitive for customer isolation.
Assemble a signed, compliance-adaptive evidence bundle for the active customer from an evidence stub plus supplemental execution metadata. Use when the user runs /yci:evidence, needs a handoff-ready evidence pack, or wants to package approvals, diffs, pre/post state, operator identity, and tenant scope under the active compliance adapter.
Proof-of-life skill for the yci plugin — confirms the skill pipeline resolves end-to-end. Prints a one-line greeting from yci. Phase 0; replaced by yci:whoami when the customer-profile machinery lands.
Matches all tools
Hooks run on every tool call, not just specific ones
Uses power tools
Uses Bash, Write, or Edit tools
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.
Yandy's Claude Infrastructure (yci) plugin for Claude Code — customer profiles, compliance adapters, customer-isolation PreToolUse hook, change-window enforcement, blast-radius analysis, network-change review, and evidence-bundle packaging for consulting and systems-integration engagements.
Provenance:
yciwas originally developed inyandy-r/claude-pluginsalongsideycc. It was extracted into this sibling repo in 2026-04 so the customer-guard PreToolUse hook no longer fires in the ycc dev workspace. Git history for every yci-owned path survives the move (git log -- yci/shows the full trail). Seedocs/prps/prds/yci.prd.mdfor the product rationale.
yci:customer-profile — load / switch / init the active customer profile (engagement-scoped identity, inventory adapter, compliance adapter, change-window adapter, safety posture).yci:customer-guard — PreToolUse hook that fail-closes on cross-customer path / identifier collisions. Catalogued deny reasons; dry-run and fail-open env knobs for development.yci:hello — Phase-0 proof-of-life skill (will be replaced by yci:whoami once the customer-profile machinery lands end-to-end).yci/skills/_shared/.yci:blast-radius, yci:evidence-bundle, yci:network-change-review, yci:change-window-gate hook — see PRD §6 for the phased rollout.# Add the marketplace
/plugin marketplace add yandy-r/claude-infra-plugins
# Install the plugin
/plugin install yci@yci
Or enable in ~/.claude/settings.json:
{
"enabledPlugins": {
"yci@yci": true
}
}
yci/.claude-plugin/plugin.json.claude-infra-plugins/
├── .claude-plugin/
│ └── marketplace.json # single plugin entry (yci)
├── yci/
│ ├── .claude-plugin/
│ │ └── plugin.json # name: "yci"
│ ├── CONTRIBUTING.md # yci-specific policy (non-goals, adapter pattern)
│ ├── hooks/
│ │ └── customer-guard/ # PreToolUse hook
│ ├── skills/
│ │ ├── _shared/ # cross-skill helpers (customer-isolation, adapters, schema)
│ │ ├── customer-profile/ # load / switch / init profiles
│ │ ├── customer-guard/ # guard-check operator skill
│ │ └── hello/ # Phase-0 proof-of-life
│ ├── agents/ # (Phase 1+)
│ ├── commands/ # (Phase 1+)
│ └── docs/
│ ├── profiles.md
│ └── profiles/_internal.yaml.example
├── docs/
│ └── prps/
│ ├── prds/yci.prd.md # product requirements document
│ ├── reports/ # implementation reports (archived)
│ └── plans/ # implementation plans (archived)
└── scripts/
├── validate.sh # single entrypoint; CI runs this on push/PR
├── install-shellcheck.sh
└── lib/shellcheck-resolve.sh
# One-time: install pinned shellcheck (matches .tool-versions)
./scripts/install-shellcheck.sh
# Validate the bundle
./scripts/validate.sh
CI runs ./scripts/validate.sh on every push and pull request via .github/workflows/validate.yml.
Before proposing a new skill, command, or agent, read the Scope & Guardrails policy in CONTRIBUTING.md and the yci-specific non-goals and compliance-adapter rules in yci/CONTRIBUTING.md.
yandy-r/claude-plugins — sibling repo shipping the ycc development-workflow plugin.npx claudepluginhub yandy-r/claude-infra-plugins --plugin yciUnified planning pipeline: feature research, shared context creation, parallel plan generation, and validation. Orchestrates parallel research and analysis agents for comprehensive implementation planning.
Execute parallel implementation plans by deploying implementor agents in dependency-resolved batches. Step 3 of the planning workflow, requires parallel-plan.md from plan-workflow plugin.
Git commit and documentation workflow manager. Analyzes changes, determines commit strategy (direct vs agents), writes conventional commit messages, coordinates documentation updates, creates pull requests, and converts deep-research output into structured GitHub issues.
Orchestrate multiple specialized agents to accomplish complex tasks efficiently through intelligent task decomposition, parallel execution, and result synthesis.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development
Claude harness - A harness for solo developers (Vibecoders) to handle full-cycle contract development.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques