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/data-lifecycle.md
View on GitHub# Data Lifecycle
Read this file before choosing persistence, changing stored data, or implementing import, export, backup, restore, or migration.
## Required decisions
Before specification approval, record:
- Primary devices and whether mobile use is local, on the same network, or anywhere.
- Whether changes must synchronize automatically across devices.
- Data importance: replaceable, important, or hard to replace.
- Acceptable data loss and recovery effort.
- Storage location, backup owner, backup frequency, and restore method.
Do not silently choose browser storage for important data. Explain that browser- or app-container storage is device-specific and can be removed by cleanup, reset, uninstall, or migration.
## Backup envelope
Export one versioned envelope rather than unrelated module files:
```json
{
"format": "personal-workbench-backup",
"formatVersion": 1,
"appId": "creator-workbench",
"appVersion": "1.4.0",
"schemaVersion": 3,
"exportedAt": "2026-08-03T03:00:00Z",
"data": {}
}
```
Treat all fields except `data` as validation metadata. Reject an unsupported future `formatVersion` or `schemaVersion` without changing current data.
## Migration contract
- Keep migrations incremental: `v1 -> v2 -> v3`, not one untracked rewrite.
- Run migrations on a copy, then validate required fields and record counts before committing.
- Increase `schemaVersion` whenever a stored shape changes.
- Preserve unknown fields unless removal is explicitly required and approved.
- Test the oldest supported version, the current version, malformed input, and a future version.
- If parsing, validation, or migration fails, preserve the original import file and current stored data. Provide a recoverable copy or diagnostic reference when the runtime permits it.
## Import contract
1. Parse and validate the envelope without writes.
2. Show source app/version, export time, record counts, conflicts, and migration needs.
3. Require the user to choose `merge` or `overwrite` when existing data is present.
4. Create a current-state backup before `overwrite` or a destructive migration.
5. Import into a temporary copy, validate it, then commit atomically where the storage system supports transactions.
6. Return counts for `added`, `merged`, `overwritten`, `skipped`, and `failed`.
7. Re-read representative records and reconcile total counts after commit.
Never clear current data before a replacement import has passed parsing, migration, and validation.
## Backup and restore
- Make export and restore visible in the product when persistent user data exists.
- Scale backup frequency and automation to data importance and acceptable loss, rather than using one fixed retention count for every project.
- Keep code rollback separate from data restore. Reverting code must not silently replace current user records.
- Rehearse restore when data is important or hard to replace; creating a file without proving it can restore is incomplete.
- Record the actual persistence boundary, last successful backup, last restore rehearsal, and known limitations in `workbench-spec.md`.
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 |