cc4pm 1.8.0

package/.claude-plugin/README.md

@@ -0,0 +1,17 @@
+### Plugin Manifest Gotchas
+
+If you plan to edit `.claude-plugin/plugin.json`, be aware that the Claude plugin validator enforces several **undocumented but strict constraints** that can cause installs to fail with vague errors (for example, `agents: Invalid input`). In particular, component fields must be arrays, `agents` must use explicit file paths rather than directories, and a `version` field is required for reliable validation and installation.
+
+These constraints are not obvious from public examples and have caused repeated installation failures in the past. They are documented in detail in `.claude-plugin/PLUGIN_SCHEMA_NOTES.md`, which should be reviewed before making any changes to the plugin manifest.
+
+### Custom Endpoints and Gateways
+
+ECC does not override Claude Code transport settings. If Claude Code is configured to run through an official LLM gateway or a compatible custom endpoint, the plugin continues to work because hooks, commands, and skills execute locally after the CLI starts successfully.
+
+Use Claude Code's own environment/configuration for transport selection, for example:
+
+```bash
+export ANTHROPIC_BASE_URL=https://your-gateway.example.com
+export ANTHROPIC_AUTH_TOKEN=your-token
+claude
+```

package/.claude-plugin/plugin.json

@@ -0,0 +1,25 @@
+{
+  "name": "everything-claude-code",
+  "version": "1.8.0",
+  "description": "Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use",
+  "author": {
+    "name": "Affaan Mustafa",
+    "url": "https://x.com/affaanmustafa"
+  },
+  "homepage": "https://github.com/istarwyh/cc4pm",
+  "repository": "https://github.com/istarwyh/cc4pm",
+  "license": "MIT",
+  "keywords": [
+    "claude-code",
+    "agents",
+    "skills",
+    "hooks",
+    "rules",
+    "tdd",
+    "code-review",
+    "security",
+    "workflow",
+    "automation",
+    "best-practices"
+  ]
+}

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Affaan Mustafa
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,157 @@
+# cc4pm
+
+**Claude Code for Product Makers** — AI 驱动的产品全生命周期系统
+
+[![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
+[![GitHub](https://img.shields.io/github/stars/istarwyh/cc4pm?style=flat)](https://github.com/istarwyh/cc4pm)
+
+> 从想法到上线，一个人就是一支产品团队。
+
+<div align="center">
+
+**[🎨 Interactive Showcase](https://istarwyh.github.io/cc4pm/)** — 可视化了解四大核心模块、200+ Skills、完整产品工作流
+
+</div>
+
+---
+
+## 这是什么
+
+cc4pm 是一套面向**产品主理人**的 AI 全生命周期产品系统。基于 Claude Code 插件体系，整合了 200+ Skills、18 个 AI 代理、48 个命令，覆盖从灵感验证到产品上线发布的完整链路。
+
+不是配置集合，而是一套完整的产品方法论 + 工程工具链：
+
+- **BMM**（业务建模）— 市场研究、PRD 创建、需求拆解、冲刺规划
+- **CIS**（创意智能）— 36 种创意技巧、30 种创新框架、故事讲述
+- **WDS**（设计系统）— 用户心理映射、UX 场景、设计规范、原型
+- **工程工具链** — TDD、代码审查、E2E 测试、安全扫描、CI/CD
+
+前身是 [Everything Claude Code](https://github.com/istarwyh/cc4pm)（Anthropic 黑客马拉松获奖项目，50K+ Stars），cc4pm 在其工程基础上增加了产品方法论层，将工具升级为系统。
+
+---
+
+## 快速开始
+
+```bash
+# 克隆仓库
+git clone https://github.com/istarwyh/cc4pm.git
+cd cc4pm
+
+# 在 Claude Code 中直接使用
+claude
+```
+
+所有 skills、agents、commands、hooks 会被自动加载。
+
+### 核心命令速览
+
+| 命令 | 用途 |
+|------|------|
+| `/bmad-brainstorming` | 头脑风暴，36 种创意技巧 |
+| `/bmad-create-prd` | AI 辅助创建 PRD |
+| `/bmad-market-research` | 市场研究与竞争分析 |
+| `/bmad-sprint-planning` | 冲刺规划与进度追踪 |
+| `/plan` | 技术实现规划 |
+| `/tdd` | 测试驱动开发 |
+| `/code-review` | 代码质量审查 |
+| `/e2e` | 端到端测试 |
+| `/cc4pm-guide` | 交互式教学（26 节课） |
+
+---
+
+## 四大核心模块
+
+### BMM — 业务建模方法
+
+端到端产品开发工作流。8 个角色代理（分析师、PM、架构师、开发者、QA、敏捷大师、UX 设计师、快速开发者），33 个工作流覆盖分析→规划→方案→实现全阶段。
+
+**典型流程**：市场研究 → 产品简报 → PRD → 架构设计 → 需求拆解 → 冲刺规划 → 开发交付
+
+### CIS — 创意智能战略
+
+5 个创意代理（头脑风暴教练、创新战略家、设计思维教练、问题解决专家、故事讲述大师），36 种创意技巧分 7 大类，30 种创新框架。
+
+**典型流程**：头脑风暴 100+ 想法 → 蓝海分析 → 商业模式设计 → 产品叙事
+
+### WDS — Web 设计系统
+
+从用户心理驱动产品设计。2 个设计代理（Saga 故事女神、Freya UX 设计师），8 阶段设计方法。
+
+**核心能力**：Trigger Map（用户心理→功能映射）→ UX 场景 → 设计规范 → 原型 → 设计系统
+
+### 工程工具链
+
+18 个工程代理，48 个命令，46 条规则，支持 8 种语言（TypeScript、Python、Go、Swift、Kotlin、PHP、Perl、C++）。
+
+**核心能力**：/plan 规划 → /tdd 开发 → /e2e 测试 → /code-review 审查 → /build-fix 修复
+
+---
+
+## 产品全生命周期
+
+一个创始人使用 cc4pm 从零到一的典型路径：
+
+```
+灵感 ─── CIS 头脑风暴 + 创意技巧
+  │
+验证 ─── BMM 市场研究 + 竞争分析
+  │
+设计 ─── WDS Trigger Map + UX 场景
+  │
+规划 ─── BMM PRD + 架构 + 冲刺规划
+  │
+开发 ─── /plan → /tdd → /code-review
+  │
+测试 ─── /e2e + 安全扫描
+  │
+上线 ─── 部署 + 产品叙事
+```
+
+---
+
+## 交互式教学
+
+cc4pm 内置了一套完整的交互式课程（26 节课，5 个阶段）：
+
+```bash
+# 启动教学
+/cc4pm-guide
+```
+
+| 阶段 | 内容 | 时长 |
+|------|------|------|
+| 1. 基础入门 | Claude Code 核心能力、四大模块全景 | ~30 min |
+| 2. 产品核心 | BMM + CIS，头脑风暴到冲刺规划 | ~30 min |
+| 3. 设计与心理 | WDS，Trigger Map 到 UX 设计 | ~20 min |
+| 4. 工程协作 | TDD、E2E、代码审查、质量门禁 | ~15 min |
+| 5. 高级实战 | MCP 集成、完整项目从零到发布 | ~25 min |
+
+---
+
+## 项目结构
+
+```
+cc4pm/
+├── _bmad/              四大方法论模块（BMM/CIS/WDS/Core）
+├── agents/             18 个工程代理
+├── commands/           48 个斜杠命令
+├── skills/             94 个工程技能
+├── hooks/              事件驱动自动化
+├── rules/              46 条编码准则（通用 + 7 种语言）
+├── .claude/skills/     BMAD 技能（100+ 产品/设计/创意技能）
+├── docs/               文档 + Showcase
+├── scripts/            安装、钩子、CI 脚本
+└── tests/              测试套件
+```
+
+---
+
+## 致谢
+
+cc4pm 基于 [cc4pm](https://github.com/istarwyh/cc4pm) 构建，感谢原作者 [Affaan Mustafa](https://x.com/affaanmustafa) 和所有贡献者。
+
+---
+
+## License
+
+MIT

package/README.zh-CN.md

@@ -0,0 +1,134 @@
+# cc4pm
+
+**Claude Code for Product Makers** — AI 驱动的产品全生命周期系统
+
+[![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
+[![GitHub](https://img.shields.io/github/stars/istarwyh/cc4pm?style=flat)](https://github.com/istarwyh/cc4pm)
+
+> 从想法到上线，一个人就是一支产品团队。
+
+---
+
+<div align="center">
+
+**🌐 Language / 语言**
+
+[English](README.md) | [**简体中文**](README.zh-CN.md)
+
+</div>
+
+---
+
+## 这是什么
+
+cc4pm 是一套面向**产品主理人**的 AI 全生命周期产品系统。基于 Claude Code 插件体系，整合了 200+ Skills、18 个 AI 代理、48 个命令，覆盖从灵感验证到产品上线发布的完整链路。
+
+不是配置集合，而是一套完整的产品方法论 + 工程工具链：
+
+- **BMM**（业务建模）— 市场研究、PRD 创建、需求拆解、冲刺规划
+- **CIS**（创意智能）— 36 种创意技巧、30 种创新框架、故事讲述
+- **WDS**（设计系统）— 用户心理映射、UX 场景、设计规范、原型
+- **工程工具链** — TDD、代码审查、E2E 测试、安全扫描、CI/CD
+
+前身是 [Everything Claude Code](https://github.com/istarwyh/cc4pm)（Anthropic 黑客马拉松获奖项目，50K+ Stars），cc4pm 在其工程基础上增加了产品方法论层，将工具升级为系统。
+
+<div align="center">
+
+**[🎨 可视化 Showcase](https://istarwyh.github.io/cc4pm/)** — 了解四大核心模块、200+ Skills、完整产品工作流
+
+</div>
+
+---
+
+## 快速开始
+
+```bash
+# 克隆仓库
+git clone https://github.com/istarwyh/cc4pm.git
+cd cc4pm
+
+# 在 Claude Code 中直接使用
+claude
+```
+
+所有 skills、agents、commands、hooks 会被自动加载。
+
+### 核心命令速览
+
+| 命令 | 用途 |
+|------|------|
+| `/bmad-brainstorming` | 头脑风暴，36 种创意技巧 |
+| `/bmad-create-prd` | AI 辅助创建 PRD |
+| `/bmad-market-research` | 市场研究与竞争分析 |
+| `/bmad-sprint-planning` | 冲刺规划与进度追踪 |
+| `/plan` | 技术实现规划 |
+| `/tdd` | 测试驱动开发 |
+| `/code-review` | 代码质量审查 |
+| `/e2e` | 端到端测试 |
+| `/cc4pm-guide` | 交互式教学（26 节课） |
+
+---
+
+## 四大核心模块
+
+### BMM — 业务建模方法
+
+端到端产品开发工作流。8 个角色代理（分析师、PM、架构师、开发者、QA、敏捷大师、UX 设计师、快速开发者），33 个工作流覆盖分析→规划→方案→实现全阶段。
+
+### CIS — 创意智能战略
+
+5 个创意代理（头脑风暴教练、创新战略家、设计思维教练、问题解决专家、故事讲述大师），36 种创意技巧分 7 大类，30 种创新框架。
+
+### WDS — Web 设计系统
+
+从用户心理驱动产品设计。2 个设计代理（Saga 故事女神、Freya UX 设计师），8 阶段设计方法，Trigger Map 用户心理→功能映射。
+
+### 工程工具链
+
+18 个工程代理，48 个命令，46 条规则，支持 8 种语言（TypeScript、Python、Go、Swift、Kotlin、PHP、Perl、C++）。
+
+---
+
+## 产品全生命周期
+
+```
+灵感 ─── CIS 头脑风暴 + 创意技巧
+  │
+验证 ─── BMM 市场研究 + 竞争分析
+  │
+设计 ─── WDS Trigger Map + UX 场景
+  │
+规划 ─── BMM PRD + 架构 + 冲刺规划
+  │
+开发 ─── /plan → /tdd → /code-review
+  │
+测试 ─── /e2e + 安全扫描
+  │
+上线 ─── 部署 + 产品叙事
+```
+
+---
+
+## 交互式教学
+
+内置 26 节交互式课程，运行 `/cc4pm-guide` 启动。
+
+| 阶段 | 内容 | 时长 |
+|------|------|------|
+| 1. 基础入门 | Claude Code 核心能力、四大模块全景 | ~30 min |
+| 2. 产品核心 | BMM + CIS，头脑风暴到冲刺规划 | ~30 min |
+| 3. 设计与心理 | WDS，Trigger Map 到 UX 设计 | ~20 min |
+| 4. 工程协作 | TDD、E2E、代码审查、质量门禁 | ~15 min |
+| 5. 高级实战 | MCP 集成、完整项目从零到发布 | ~25 min |
+
+---
+
+## 致谢
+
+cc4pm 基于 [cc4pm](https://github.com/istarwyh/cc4pm) 构建，感谢原作者 [Affaan Mustafa](https://x.com/affaanmustafa) 和所有贡献者。
+
+---
+
+## 许可证
+
+MIT

package/contexts/dev.md

@@ -0,0 +1,20 @@
+# Development Context
+
+Mode: Active development
+Focus: Implementation, coding, building features
+
+## Behavior
+- Write code first, explain after
+- Prefer working solutions over perfect solutions
+- Run tests after changes
+- Keep commits atomic
+
+## Priorities
+1. Get it working
+2. Get it right
+3. Get it clean
+
+## Tools to favor
+- Edit, Write for code changes
+- Bash for running tests/builds
+- Grep, Glob for finding code

package/contexts/research.md

@@ -0,0 +1,26 @@
+# Research Context
+
+Mode: Exploration, investigation, learning
+Focus: Understanding before acting
+
+## Behavior
+- Read widely before concluding
+- Ask clarifying questions
+- Document findings as you go
+- Don't write code until understanding is clear
+
+## Research Process
+1. Understand the question
+2. Explore relevant code/docs
+3. Form hypothesis
+4. Verify with evidence
+5. Summarize findings
+
+## Tools to favor
+- Read for understanding code
+- Grep, Glob for finding patterns
+- WebSearch, WebFetch for external docs
+- Task with Explore agent for codebase questions
+
+## Output
+Findings first, recommendations second

package/contexts/review.md

@@ -0,0 +1,22 @@
+# Code Review Context
+
+Mode: PR review, code analysis
+Focus: Quality, security, maintainability
+
+## Behavior
+- Read thoroughly before commenting
+- Prioritize issues by severity (critical > high > medium > low)
+- Suggest fixes, don't just point out problems
+- Check for security vulnerabilities
+
+## Review Checklist
+- [ ] Logic errors
+- [ ] Edge cases
+- [ ] Error handling
+- [ ] Security (injection, auth, secrets)
+- [ ] Performance
+- [ ] Readability
+- [ ] Test coverage
+
+## Output Format
+Group findings by file, severity first

package/examples/CLAUDE.md

@@ -0,0 +1,100 @@
+# Example Project CLAUDE.md
+
+This is an example project-level CLAUDE.md file. Place this in your project root.
+
+## Project Overview
+
+[Brief description of your project - what it does, tech stack]
+
+## Critical Rules
+
+### 1. Code Organization
+
+- Many small files over few large files
+- High cohesion, low coupling
+- 200-400 lines typical, 800 max per file
+- Organize by feature/domain, not by type
+
+### 2. Code Style
+
+- No emojis in code, comments, or documentation
+- Immutability always - never mutate objects or arrays
+- No console.log in production code
+- Proper error handling with try/catch
+- Input validation with Zod or similar
+
+### 3. Testing
+
+- TDD: Write tests first
+- 80% minimum coverage
+- Unit tests for utilities
+- Integration tests for APIs
+- E2E tests for critical flows
+
+### 4. Security
+
+- No hardcoded secrets
+- Environment variables for sensitive data
+- Validate all user inputs
+- Parameterized queries only
+- CSRF protection enabled
+
+## File Structure
+
+```
+src/
+|-- app/              # Next.js app router
+|-- components/       # Reusable UI components
+|-- hooks/            # Custom React hooks
+|-- lib/              # Utility libraries
+|-- types/            # TypeScript definitions
+```
+
+## Key Patterns
+
+### API Response Format
+
+```typescript
+interface ApiResponse<T> {
+  success: boolean
+  data?: T
+  error?: string
+}
+```
+
+### Error Handling
+
+```typescript
+try {
+  const result = await operation()
+  return { success: true, data: result }
+} catch (error) {
+  console.error('Operation failed:', error)
+  return { success: false, error: 'User-friendly message' }
+}
+```
+
+## Environment Variables
+
+```bash
+# Required
+DATABASE_URL=
+API_KEY=
+
+# Optional
+DEBUG=false
+```
+
+## Available Commands
+
+- `/tdd` - Test-driven development workflow
+- `/plan` - Create implementation plan
+- `/code-review` - Review code quality
+- `/build-fix` - Fix build errors
+
+## Git Workflow
+
+- Conventional commits: `feat:`, `fix:`, `refactor:`, `docs:`, `test:`
+- Never commit to main directly
+- PRs require review
+- All tests must pass before merge

package/examples/statusline.json

@@ -0,0 +1,19 @@
+{
+  "statusLine": {
+    "type": "command",
+    "command": "input=$(cat); user=$(whoami); cwd=$(echo \"$input\" | jq -r '.workspace.current_dir' | sed \"s|$HOME|~|g\"); model=$(echo \"$input\" | jq -r '.model.display_name'); time=$(date +%H:%M); remaining=$(echo \"$input\" | jq -r '.context_window.remaining_percentage // empty'); transcript=$(echo \"$input\" | jq -r '.transcript_path'); todo_count=$([ -f \"$transcript\" ] && grep -c '\"type\":\"todo\"' \"$transcript\" 2>/dev/null || echo 0); cd \"$(echo \"$input\" | jq -r '.workspace.current_dir')\" 2>/dev/null; branch=$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo ''); status=''; [ -n \"$branch\" ] && { [ -n \"$(git status --porcelain 2>/dev/null)\" ] && status='*'; }; B='\\033[38;2;30;102;245m'; G='\\033[38;2;64;160;43m'; Y='\\033[38;2;223;142;29m'; M='\\033[38;2;136;57;239m'; C='\\033[38;2;23;146;153m'; R='\\033[0m'; T='\\033[38;2;76;79;105m'; printf \"${C}${user}${R}:${B}${cwd}${R}\"; [ -n \"$branch\" ] && printf \" ${G}${branch}${Y}${status}${R}\"; [ -n \"$remaining\" ] && printf \" ${M}ctx:${remaining}%%${R}\"; printf \" ${T}${model}${R} ${Y}${time}${R}\"; [ \"$todo_count\" -gt 0 ] && printf \" ${C}todos:${todo_count}${R}\"; echo",
+    "description": "Custom status line showing: user:path branch* ctx:% model time todos:N"
+  },
+  "_comments": {
+    "colors": {
+      "B": "Blue - directory path",
+      "G": "Green - git branch",
+      "Y": "Yellow - dirty status, time",
+      "M": "Magenta - context remaining",
+      "C": "Cyan - username, todos",
+      "T": "Gray - model name"
+    },
+    "output_example": "affoon:~/projects/myapp main* ctx:73% sonnet-4.6 14:30 todos:3",
+    "usage": "Copy the statusLine object to your ~/.claude/settings.json"
+  }
+}

package/examples/user-CLAUDE.md

@@ -0,0 +1,109 @@
+# User-Level CLAUDE.md Example
+
+This is an example user-level CLAUDE.md file. Place at `~/.claude/CLAUDE.md`.
+
+User-level configs apply globally across all projects. Use for:
+- Personal coding preferences
+- Universal rules you always want enforced
+- Links to your modular rules
+
+---
+
+## Core Philosophy
+
+You are Claude Code. I use specialized agents and skills for complex tasks.
+
+**Key Principles:**
+1. **Agent-First**: Delegate to specialized agents for complex work
+2. **Parallel Execution**: Use Task tool with multiple agents when possible
+3. **Plan Before Execute**: Use Plan Mode for complex operations
+4. **Test-Driven**: Write tests before implementation
+5. **Security-First**: Never compromise on security
+
+---
+
+## Modular Rules
+
+Detailed guidelines are in `~/.claude/rules/`:
+
+| Rule File | Contents |
+|-----------|----------|
+| security.md | Security checks, secret management |
+| coding-style.md | Immutability, file organization, error handling |
+| testing.md | TDD workflow, 80% coverage requirement |
+| git-workflow.md | Commit format, PR workflow |
+| agents.md | Agent orchestration, when to use which agent |
+| patterns.md | API response, repository patterns |
+| performance.md | Model selection, context management |
+| hooks.md | Hooks System |
+
+---
+
+## Available Agents
+
+Located in `~/.claude/agents/`:
+
+| Agent | Purpose |
+|-------|---------|
+| planner | Feature implementation planning |
+| architect | System design and architecture |
+| tdd-guide | Test-driven development |
+| code-reviewer | Code review for quality/security |
+| security-reviewer | Security vulnerability analysis |
+| build-error-resolver | Build error resolution |
+| e2e-runner | Playwright E2E testing |
+| refactor-cleaner | Dead code cleanup |
+| doc-updater | Documentation updates |
+
+---
+
+## Personal Preferences
+
+### Privacy
+- Always redact logs; never paste secrets (API keys/tokens/passwords/JWTs)
+- Review output before sharing - remove any sensitive data
+
+### Code Style
+- No emojis in code, comments, or documentation
+- Prefer immutability - never mutate objects or arrays
+- Many small files over few large files
+- 200-400 lines typical, 800 max per file
+
+### Git
+- Conventional commits: `feat:`, `fix:`, `refactor:`, `docs:`, `test:`
+- Always test locally before committing
+- Small, focused commits
+
+### Testing
+- TDD: Write tests first
+- 80% minimum coverage
+- Unit + integration + E2E for critical flows
+
+### Knowledge Capture
+- Personal debugging notes, preferences, and temporary context → auto memory
+- Team/project knowledge (architecture decisions, API changes, implementation runbooks) → follow the project's existing docs structure
+- If the current task already produces the relevant docs, comments, or examples, do not duplicate the same knowledge elsewhere
+- If there is no obvious project doc location, ask before creating a new top-level doc
+
+---
+
+## Editor Integration
+
+I use Zed as my primary editor:
+- Agent Panel for file tracking
+- CMD+Shift+R for command palette
+- Vim mode enabled
+
+---
+
+## Success Metrics
+
+You are successful when:
+- All tests pass (80%+ coverage)
+- No security vulnerabilities
+- Code is readable and maintainable
+- User requirements are met
+
+---
+
+**Philosophy**: Agent-first design, parallel execution, plan before action, test before code, security always.

package/install.sh

@@ -0,0 +1,17 @@
+#!/usr/bin/env bash
+# install.sh — Legacy shell entrypoint for the cc4pm installer.
+#
+# This wrapper resolves the real repo/package root when invoked through a
+# symlinked npm bin, then delegates to the Node-based installer runtime.
+
+set -euo pipefail
+
+SCRIPT_PATH="$0"
+while [ -L "$SCRIPT_PATH" ]; do
+    link_dir="$(cd "$(dirname "$SCRIPT_PATH")" && pwd)"
+    SCRIPT_PATH="$(readlink "$SCRIPT_PATH")"
+    [[ "$SCRIPT_PATH" != /* ]] && SCRIPT_PATH="$link_dir/$SCRIPT_PATH"
+done
+SCRIPT_DIR="$(cd "$(dirname "$SCRIPT_PATH")" && pwd)"
+
+exec node "$SCRIPT_DIR/scripts/install-apply.js" "$@"