openwork-core▌
different-ai/openwork · updated Apr 8, 2026
openwork-core
Quick Usage (Already Configured)
Orientation
- Read
AGENTS.md,VISION.md,PRINCIPLES.md,PRODUCT.md, andARCHITECTURE.mdbefore changing behavior. - Ensure
vendor/opencodeexists for self-reference. - Use the
tauri-solidjsskill for stack-specific guidance.
Update the OpenCode mirror
git -C vendor/opencode pull --ff-only
Development workflow
pnpm tauri dev # Desktop development
pnpm tauri ios dev # iOS development
pnpm tauri android dev # Android development
# Or run directly in the desktop package:
pnpm -C packages/desktop tauri dev
OpenCode Integration
Spawn OpenCode CLI
opencode -p "your prompt" -f json -q
Read OpenCode database
~/.opencode/opencode.db # SQLite database
Key tables
sessions— Task runsmessages— Chat messages and tool callshistory— File change tracking
Common Gotchas
- OpenWork must stay within OpenCode's tool surface; avoid inventing new capabilities.
- Always expose plans, permissions, and progress for non-technical users.
- Use Tauri commands for all system access (file, shell, database).
- Keep UI at 60fps; avoid blocking the main thread.
- Mobile builds require platform-specific setup (Xcode, Android Studio).
UI Principles
- Slick and fluid: animations, transitions, micro-interactions.
- Mobile-first: touch targets, gestures, adaptive layouts.
- Transparency: show plans, steps, and tool calls.
- Progressive disclosure: hide advanced controls until needed.
First-Time Setup (If Not Configured)
Clone the OpenCode mirror
git clone https://github.com/anomalyco/opencode vendor/opencode
Initialize Tauri project
pnpm create tauri-app . --template solid-ts
Add mobile targets
pnpm tauri ios init
pnpm tauri android init
Common Gotchas
- OpenWork must stay within OpenCode’s tool surface; avoid inventing new capabilities.
- Always expose plans, permissions, and progress for non-technical users.
First-Time Setup (If Not Configured)
Clone the OpenCode mirror
git clone https://github.com/anomalyco/opencode vendor/opencode
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★41 reviews- ★★★★★Amelia Brown· Dec 28, 2024
Useful defaults in openwork-core — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Diego Diallo· Dec 24, 2024
openwork-core has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Valentina Huang· Dec 20, 2024
I recommend openwork-core for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Dhruvi Jain· Dec 4, 2024
openwork-core is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Oshnikdeep· Nov 23, 2024
openwork-core fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Valentina Kim· Nov 19, 2024
We added openwork-core from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Amelia Taylor· Nov 15, 2024
Solid pick for teams standardizing on skills: openwork-core is focused, and the summary matches what you get after install.
- ★★★★★Anika Haddad· Nov 7, 2024
Useful defaults in openwork-core — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ganesh Mohane· Oct 14, 2024
openwork-core has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Sakura Diallo· Oct 10, 2024
openwork-core reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 41