hashorva
UserPortable orchestrator/worker harness kit for AI-assisted development
Categories
Indexed Skills (8)
dispatch-worker
How the orchestrator dispatches a WORKER_TASK to a local worker CLI (codex, agent/Cursor, agy/Antigravity, claude -p) via scripts/spawn-worker.sh and processes the result. MUST be used in the DISPATCH and REVIEW steps. Cursor: Grok for premium, Composer for economy (Grok falls back to Composer). Always prefer spawn-worker + fleet from fleet-inventory over hand-rolled flags. Orchestrator-only; workers never dispatch other workers.
mcp-hygiene
How to use MCP servers (Supabase, browser, GitHub, any connector) without polluting the context window. MUST be used whenever a task involves querying an MCP server, verifying database state, fetching external data mid-task, or when a session is getting long and slow. Also use when deciding whether to reach for MCP at all versus a CLI/script.
mission-init
Bootstrap an orchestrated mission: create a dated folder under docs/missions/ with GOAL.md, features.json, PROGRESS.md, and the first WORKER_TASK from the repo's templates. MUST be used whenever the user says "start a mission", "new goal", "bootstrap the loop", "let's run the orchestration on X", or asks to begin orchestrated work of any kind. Also use to re-scope an existing mission. Produces files mechanically from docs/missions/templates/ — never freestyle the formats. Runs fleet-inventory at GATE 0 and always shows the seat→model map for human confirm/swap. Default chair is Opus (Cursor intake plans briefly; Opus weighs and orchestrates) unless the human names otherwise.
react-conventions
Conventions for writing React components, hooks, and TypeScript in Vite + React + Tailwind projects in this studio. MUST be used whenever creating or refactoring a component, page, custom hook, or context; wiring data fetching; or adding types. Also use when deciding where a new file goes or whether logic belongs in a hook vs a component.
shadcn-luma
Install, verify, and use shadcn/ui components with the Luma style in any studio project (FinDuck, consulenza360, shyft.me, ...). MUST be used before installing ANY shadcn component, running shadcn init/add/apply, restyling UI, or building any new page or component. Also use when UI "looks wrong" or "doesn't match the design system". Installing default/new-york-style shadcn in a Luma project is a failed task.
skillify
Graduate a battle-tested procedure into a new SKILL.md in .agents/skills/. MUST be used at mission end (after the last feature passes), whenever the code-reviewer's flywheel notes flag the same failure class or procedure twice, or when the user says "skillify this", "make this a skill", or "we keep doing this". Orchestrator-only. Produces skills from EVIDENCE (PROGRESS.md, review findings, git log) — never from speculation.
supabase-migration
The only allowed workflow for writing AND applying a Supabase migration in any studio project. Activates on requests to add tables, alter columns, add indexes, add or modify RLS policies, add constraints, RPCs, or any other schema change — and on "push the migration", "apply the schema change". Do NOT use for seeding data, running read queries, or explaining schema. Applying SQL via MCP, the dashboard SQL editor, or a hand-named migration file is a failed task.
cloudflare-deploy
Deploy and verify Cloudflare Pages sites and Cloudflare Workers in this studio. MUST be used for any task involving deployment, wrangler, environment variables/secrets, CORS, custom domains, staging vs production, or "it works locally but not deployed". Also use before changing anything in wrangler.toml or Pages build settings.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.