Isolate Dependency Process Boundary banner
jasonkneen jasonkneen

Isolate Dependency Process Boundary

Development community

Description

--- name: isolate-dependency-process-boundary description: Use a GPL-incompatible-but-needed dependency by running it in a separate process the app talks to over IPC, so it is never linked into the GPL-3.0-or-later desktop work — the "isolate it behind a process boundary" path that the compat gate, the compliance-paths router, and the vendoring convention all name but none spell out --- # Isolate a GPL-incompatible dependency behind a process boundary The desktop app ships **GPL-3.0-or-later**

Installation

Installs to ~/.claude/skills/jasonkneen-agent-farm-cli-isolate-dependency-process-boundary/SKILL.md

Terminal
mkdir -p ~/.claude/skills/jasonkneen-agent-farm-cli-isolate-dependency-process-boundary && curl -fsSL https://raw.githubusercontent.com/jasonkneen/Agent-Farm-CLI/HEAD/skills/isolate-dependency-process-boundary.md -o ~/.claude/skills/jasonkneen-agent-farm-cli-isolate-dependency-process-boundary/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

Full documentation available on GitHub

View Source Repository