From maxim
Enforce the NK universe **junction read-only rule**: when Maxim detects that a target file path resolves through a filesystem junction or symlink (typically `.mxm-system\` or `.claude\` inside a sister project), it must refuse all write, delete, and git commit operations through that path. Reading is allowed.
npx claudepluginhub drnabeelkhan/maxim --plugin mxm-pack-l3-4-govtechThis skill uses the workspace's default tool permissions.
Enforce the NK universe **junction read-only rule**: when Maxim detects that a target file path resolves through a filesystem junction or symlink (typically `.mxm-system\` or `.claude\` inside a sister project), it must refuse all write, delete, and git commit operations through that path. Reading is allowed.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Enforce the NK universe junction read-only rule: when Maxim detects that a target file path resolves through a filesystem junction or symlink (typically .mxm-system\ or .claude\ inside a sister project), it must refuse all write, delete, and git commit operations through that path. Reading is allowed.
Without this guard, an agent could accidentally write to the maxim source repo while operating in another project (e.g., mxm-simplification) — corrupting cross-project state and violating the data flow rule.
.mxm-system\and.claude\inside mxm-simplification\ are junctions. ✅ Reading through junctions is ALLOWED ❌ Writing through junctions is FORBIDDEN ❌ Deleting through junctions is FORBIDDEN ❌ Git commits through junctions are FORBIDDEN
This applies to ANY junction created by bootstrap/link-local-project.ps1 or any user-created junction pointing back at the maxim repo.
For any write target path P:
P upward to find any junction or symlink ancestor.E:\Projects\Maxim\maxim\ or symlink-equivalent): apply READ-ONLY rule.PowerShell:
$item = Get-Item -Path "<target-path>"
if ($item.LinkType -in @("Junction", "SymbolicLink")) {
$resolved = $item.Target
# Compare $resolved to current project root
}
Bash:
real_target=$(readlink -f "<target-path>")
project_root=$(pwd)
if [[ "$real_target" != "$project_root"* ]]; then
echo "BLOCK: write resolves outside project root via junction"
fi
When a forbidden write is detected:
🔒 JUNCTION READ-ONLY VIOLATION
Target path: <target-path>
Resolves to: <real-resolved-path>
Junction at: <junction-ancestor>
Reason: <real-resolved-path> is outside the current project root
This operation is FORBIDDEN by the NK universe junction rule.
Allowed:
✅ Read this file through the junction
❌ Write / Edit / Delete / Commit through the junction
To make this change:
1. Open the source repo directly:
cd <real-resolved-path-without-junction>
2. Make the change there.
3. Commit there.
4. Pull updates here through the junction.
.mxm-skills/junction-guard.log:
{"timestamp":"2026-04-16T11:00:00Z","tool":"Write","target":"<path>","resolved":"<real>","blocked":true,"agent":"<calling-agent>"}
/mxm-junction-bypass (NOT IMPLEMENTED — would require CSO approval).Junction Guard Verdict: ALLOW | BLOCK
Target: [path]
Resolves to: [real-path or "same project"]
Crosses junction: YES | NO
Action: [proceed | refuse]
Logged to: .mxm-skills/junction-guard.log
security-analyst (potential agent misconfiguration)None. This is a structural safety enforcer, not a behavioral skill.
PROJECT_STRUCTURE_NK.md (Junction Rule section)CLAUDE.d/session-memory.md (Junction Read-Only Enforcement section)bootstrap/link-local-project.ps1 (creates the junctions this guard protects)Copyright (c) 2026 iSystematic Inc. Maxim product. BSL 1.1.