菜单
Installable UI plugins for WeGotWorkspace — registry, activation, ZIP install, static assets, and Flysystem/WebDAV boundaries. Use when working on plugin.json, PUT /plugins/{id}/activation, or wgw-plugins/.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Context-loading guide for the WeGotWorkspace monorepo. Covers dev layout, skill routing, and critical constraints. Use when starting work, onboarding, or unsure which skill to load.
PR and handoff review checklist — issue acceptance criteria, smells scan, policy vs CI, done-checklist verification. Use when reviewing diffs, preparing merge-ready work, or asked to code-review.
Local dev setup, Docker, Storybook proxy, HTTPS/WebDAV, and troubleshooting for the WeGotWorkspace monorepo. Use when dev servers fail, ports conflict, or live Storybook/API integration breaks.
Git workflow for this repository — branching, commits, pull requests, signed commits, and CI gates. Use when creating branches, staging, committing, opening PRs, or asked about git workflow.
Feature planning workflow for the WeGotWorkspace monorepo — research checklist, plan template, parallelization rules, and chunk handoffs. Use when scoping a feature, breaking down work, or preparing for multitask builds.
Verify GitHub issue acceptance criteria before handoff or PR — fetch issue, map criteria to checks, report pass/fail per criterion. Use when work tracks an issue, before declaring done, or when asked if an issue is satisfied.
| name | plugins |
| description | Installable UI plugins for WeGotWorkspace — registry, activation, ZIP install, static assets, and Flysystem/WebDAV boundaries. Use when working on plugin.json, PUT /plugins/{id}/activation, or wgw-plugins/. |
| paths | ["packages/api/app/Services/Plugins/**","packages/api/app/Http/Controllers/Api/V1/Plugins/**","apps/wegotworkspace/wgw-plugins/**","packages/api/tests/Feature/Plugins/**"] |
Plugins are installed ZIP packages under wgw-plugins/{id}/ with a plugin.json manifest and built static assets. Laravel discovers them via PluginRegistryService; the UI loads active plugin routes through PluginHtmlResponder.
| Task | Read |
|---|---|
| REST routes / OpenAPI | packages/api/openapi/openapi.json (/plugins, /plugins/{id}/activation) |
| Registry + activation | This file |
| Install from ZIP (admin) | packages/api/app/Services/Plugins/PluginInstallerService.php |
| Paths + assets | packages/api/app/Services/Plugins/PluginPaths.php |
| File I/O policy | api/storage-flysystem.md |
| WebDAV write restrictions | packages/api/app/Dav/Server/WebdavWriteGuardPlugin.php |
| Feature tests | packages/api/tests/Feature/Plugins/ |
| Path | Purpose |
|---|---|
{install}/wgw-plugins/{id}/plugin.json | Manifest (id, name, active, appTile, drive, integration, …) |
{install}/wgw-plugins/{id}/assets/index.html | App tile entry (required for registry listing) |
{install}/wgw-plugins/{id}/assets/editor.html or editor/index.html | Optional editor surface |
PluginPaths resolves manifests and index paths — no direct scandir in controllers.
active: true unless overridden.PUT /api/v1/plugins/{id}/activation with { "active": true|false } → ActivationController.app_settings key plugins_active_overrides via PluginRegistryService::setActive.Admin listing also exposes plugins at /api/v1/admin/plugins (install/upload flows).
PluginInstallerService:
.zip, size cap (512 MiB), safe zip entriesstorage/framework/cache/plugin.jsonwgw-plugins/{id}/Do not extract archives outside the plugins root. Do not bypass SafePath checks.
Plugins that touch user files (versioning, write guard, drive integration) must call Laravel services using WgwStorage / Storage::disk('wgw_files') — not readfile, Paths::data(), or ad hoc paths in plugin PHP.
Same files disk as REST drive and WebDAV file nodes — see storage-flysystem.md.
WebdavWriteGuardPlugin is a Sabre server plugin registered in SabreServerFactory. It blocks destructive mutations under principals/ and stray files/ paths while allowing normal CalDAV/CardDAV/file edits under allowed subtrees.
Do not reimplement path guards in plugin PHP — use this server plugin + storage services.
Active plugins with appTile.route serve static HTML from assets/index.html. Drive integration fields (openFileExtensions, newFileTemplates, …) and integration.sessionApiPath are normalized in PluginRegistryService::normalizeManifestPlugin.
cd packages/api && composer test -- --filter Plugins
Cover activation toggles, registry listing, and install validation in tests/Feature/Plugins/.
PluginPaths / Flysystem servicesAppSetting)active flag in registry