beifeng724/personal-workbench-skills / skills/personal-workbench-builder
personal-workbench-builder
VerifiedBuild a durable personal or professional workbench as a runnable application, or produce a six-stage generic prompt pack for building it. Use when the user wants to turn a recurring workflow into a dashboard, management system, workspace, personal operating system, or long-lived website with multiple connected modules and persistent state. Trigger for project, CRM, creator, learning, family, finance, travel, teaching, legal, or team workbenches. Do not trigger for marketing sites, one-off scripts, ordinary coding tasks, or informational questions.
references/module-contract.md
View on GitHub# Module And Storage Contract
Read this file when defining application architecture, module boundaries, persistence adapters, or generated metadata.
## Workbench manifest
Create `workbench-manifest.json` for every direct build:
```json
{
"generatedBy": "personal-workbench-builder",
"skillVersion": "1.0.0",
"appVersion": "1.0.0",
"schemaVersion": 1,
"generatedAt": "2026-08-03T03:00:00Z",
"complexity": "L2",
"deploymentProfile": "hosted-static",
"modules": [
{"id": "ideas", "version": "1.0.0", "schemaVersion": 1, "status": "ready"}
]
}
```
Use semantic application versions. Keep `schemaVersion` numeric and independent from `appVersion`. Do not reuse a PWA web manifest as this workbench manifest.
## Module boundaries
For each module record:
- Stable lowercase ID and owned routes or views.
- Data namespace or entities it owns.
- Inputs, outputs, events, and read/write permissions.
- Module and data schema versions.
- Requirement and acceptance IDs implemented by the module.
- Empty, loading, error, permission, and offline behavior where applicable.
A module must not edit another module's DOM, files, tables, or storage directly. Use declared events or read-only/query interfaces for cross-module consumption, and an explicit command interface for approved cross-module writes.
## Async storage adapter
Keep business modules independent from browser, file, SQLite, or cloud details. Provide asynchronous equivalents of:
```text
read(namespace, key)
write(namespace, key, value)
remove(namespace, key)
list(namespace, query?)
export()
import(envelope, { mode: "merge" | "overwrite" })
```
All methods return promises or the stack's equivalent asynchronous result. `import` returns `added`, `merged`, `overwritten`, `skipped`, and `failed` counts. Modules must not call `localStorage`, IndexedDB, SQL, filesystem APIs, or cloud SDKs outside the selected adapter.
The adapter must preserve the data-lifecycle rules in [data-lifecycle.md](data-lifecycle.md): validate before writes, migrate on a copy, back up before overwrite, and leave current data unchanged on failure.
## Architecture selection
- Use the project's existing stack when it meets the confirmed requirements.
- Add an adapter implementation only for the selected persistence profile; do not prebuild unused cloud or local-service layers.
- Keep secrets and privileged writes behind a server boundary.
- Treat a change from local storage to synchronized storage as a data migration, with export, count reconciliation, and rollback evidence.
- Treat a platform rewrite, such as web to a native mini-program, as a separate implementation unless the runtime is demonstrably compatible.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |