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/workbench-spec-template.md
View on GitHub# Workbench Specification
Create this file for every builder engagement and update it across all stages. Use `not applicable` instead of deleting a required heading.
## 1. Decision Record
- Working title:
- User goal:
- Output mode: direct | prompt-pack
- Communication mode: plain | guided | technical
- Complexity: L1 | L2 | L3 | L4
- Classification evidence:
- Specification status: draft | awaiting-confirmation | approved | changed-after-approval
- Current workflow state: draft | spec-approved | ui-approved | implementation-complete | verification-passed
- State evidence: `workflow_guard.py` input/output path or confirmation record
## 2. Users And Repeated Workflow
- Primary user:
- Other users:
- Trigger and frequency:
- Current workflow:
- Pain points:
- Desired outcome:
## 3. Confirmed Scope
| ID | Requirement in user's words | Acceptance condition | Status | Implementation order |
|---|---|---|---|---|
| - | - | - | confirmed | - |
## 4. Excluded AI Proposals
| Proposal | Why excluded |
|---|---|
| - | - |
## 5. Conflicts, Dependencies, And Approved Deferrals
| Item | Constraint or dependency | Options explained | User decision |
|---|---|---|---|
| - | - | - | - |
## 6. Information Architecture And UI
- Pages/modules:
- Navigation:
- Design method: generated
- Visual brief: product | audience | technical level | tone | formality | density | mobile priority | stack
- Reference sources:
- Reference license review:
- Visual fingerprint: layout | navigation | typography | color ratio | borders | shadows | component silhouette | background | icons | motion | mobile transformation
- Reference sanitation notes: status bars | browser chrome | watermarks | checkerboards | presentation frames | intended UI
- Theme mode: light | dark | system | no explicit theme control
- Expression:
- Motion:
- Density:
- Design system path: design-system/MASTER.md
- Page override paths:
- Fidelity target:
- UI confirmation status: draft | awaiting-confirmation | approved | inherited-without-change
- Accessibility needs:
- Empty/loading/error/success/permission/offline states:
## 7. Devices, Sync, And Data Lifecycle
- Primary devices:
- Mobile context: local | same-network | anywhere | not applicable
- Sync expectation: none | manual transfer | automatic cross-device sync
- Data importance: replaceable | important | hard to replace
- Acceptable data loss:
- Persistence approach:
- Deployment profile:
- Backup owner and frequency:
- Restore method:
- Demo-data removal: required
## 8. Data And Storage
| Entity | Important fields | Source | Retention | Import/export | Sensitivity |
|---|---|---|---|---|---|
| - | - | - | - | - | - |
- Backup envelope format/version:
- Current schema version:
- Migration path and tested source versions:
- Corrupt/future-version behavior:
- Import mode: merge | overwrite | user chooses per import
- Pre-overwrite backup:
- Last successful backup:
- Last restore rehearsal:
## 9. Users, Permissions, And Audit
- Authentication:
- Roles:
- Data isolation:
- Audit trail:
- Account/data deletion:
## 10. Integrations And Automation
| Integration | Direction | Classification | Credentials owner | Failure behavior | Cost/limit |
|---|---|---|---|---|---|
| - | - | public_readonly_api | - | - | - |
## 11. Architecture And Deployment
- Runtime:
- Storage/database:
- File storage:
- Hosting:
- Environments:
- Secret management:
- Monitoring:
- Recovery:
- Startup/port behavior when local service is selected:
- Ownership and recurring maintenance:
- User/AI responsibility split:
## 12. Privacy And Security Review
- Sensitive categories:
- Data minimization:
- Consent/legal notes:
- Threats and safeguards:
- Unresolved risk:
## 13. Verification Plan
### Control Inventory
| Control ID | Page/module | Label or accessible name | Intended behavior | Acceptance condition | Test method | Actual result | Evidence | Status |
|---|---|---|---|---|---|---|---|---|
| - | - | - | - | - | - | - | - | not-run |
### Required Scenarios
- Functional primary workflow:
- Persistence across refresh/restart:
- Import/export/merge/overwrite/recovery:
- Desktop/mobile/responsive:
- Accessibility and keyboard:
- Empty/loading/error/permission/offline:
- Security/privacy/integration failure:
- Tests actually run:
- Known limitations:
## 14. Version And Recovery Record
- `workbench-manifest.json` path:
- Generated by / skill version / app version:
- Current code baseline:
- Code snapshot or Git commit before material change:
- Data backup before migration or overwrite:
- Rollback target and result:
## 15. Confirmation Log
| Time | State or sections confirmed | Exact user decision | Reopened by |
|---|---|---|---|
| - | - | awaiting confirmation | - |
## 16. Delivery Checklist
- [ ] Runnable project or six prompt stages
- [ ] Usage instructions
- [ ] Backup and restore instructions
- [ ] Update and migration instructions
- [ ] Recovery and rollback instructions
- [ ] Deployment instructions and responsibility split
- [ ] `workbench-manifest.json`
- [ ] Control inventory and actual test evidence
- [ ] Remaining limitations
- [ ] Applicable license and third-party notices
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 |