uinaf
- 15 skills
- 0 followers
- 6 hours ago last updated
- ▌ Attach CLI · uinaf bundleUpload, share, or take down PR and validation media (screenshots, artifacts) on a self-hosted attach Worker through the installed attach CLI (`attach` or `gh attach`), or enroll a GitHub App agent for `att_` uploads. Use for any request to attach, upload, host, get a URL for, or delete media on attach.uinaf.dev (or a custom ATTACH_API_BASE), and for attach login/logout. Do not use for Worker deploy, vault, Cloudflare ops, or building another upload client.
- ▌ Uinaf Design · uinaf bundleRoute explicitly authorized uinaf interface, brand-asset, and repository-copy work through the live design.uinaf.dev contract. Use only when explicitly invoked for a uinaf-owned repository or surface; never use for put.io, OpenClaw, or unrelated projects. The skill carries workflow, not design rules.
- ▌ Uinaf Intake · uinaf bundleSave, capture, or intake a useful public article, video, tweet, podcast, paper, or research source into the shared uinaf/intake library. Use for explicit $uinaf-intake requests and natural requests such as "save this", "capture this source", or "intake this" when the target is public research material. Do not use for private documents, attachments, accounting intake, internal notes, or source material that cannot be retrieved well enough to summarize faithfully.
- ▌ Gh Setup · uinaf bundleSet up or align a repository's GitHub collaboration and delivery surface: repo settings, branch or ruleset policy, templates, Dependabot or Renovate, Actions hardening, Environments, releases, publishing, and deploy workflows. Use for GitHub setup, CI/CD policy, protected delivery, package releases, or app deployment. Do not use for product architecture, provider infrastructure internals, application security review, or repository boot/readiness work.
- ▌ Vite Plus · uinaf bundleCreate, migrate, or align frontend packages and monorepos on Vite+. Use for Vite+ scaffolding, migration, upgrades, `vp` commands, consolidated Vite/Oxlint/Oxfmt/Vitest configuration, hooks, packaging, or CI. Do not use for non-Vite toolchains or for release, deploy, and runtime behavior Vite+ does not own.
- ▌ React Ban Use Effect · uinaf bundleDetect, replace, and mechanically restrict direct React `useEffect` calls. Use when writing, refactoring, reviewing, or migrating React code that fetches, derives state, relays events, resets state, or synchronizes through effects. Do not use for unrelated React work or non-React effect systems.
- ▌ Wat · uinaf bundleShorten a rambling reply on /wat, tl;dr, or a wall-of-text complaint; keep subsequent replies concise without changing files.
- ▌ Slopprep · uinaf bundleInspect or improve repository and runner readiness for autonomous work, including boot, verification, and recovery.
- ▌ Slopspec · uinaf bundleSave agreed future work in the repository tracker as issues, epics, or durable plans; not an in-session checklist.
- ▌ Slopclean · uinaf bundleRemove AI tells from prose, code, or tests when asked to unslop or humanize an artifact; preserve its meaning and behavior.
- ▌ Slopguard · uinaf bundleReview a code change with the slopguard CLI when independent review is requested or required; validate findings and fix accepted issues.
- ▌ Slopnanny · uinaf bundleResolve review feedback and CI on an open change request, then merge when green unless asked to hold. Use for babysitting delivered work.
- ▌ Slopcourier · uinaf bundleOpen or update a change request for completed, verified work. Use for change-request delivery.
- ▌ Slopmachine · uinaf bundleExecute an agreed plan through implementation, verification, review, and delivery. Use when asked to run a plan end to end or work slopmachine-style; not for planning or assessment alone.
- ▌ Slopscriber · uinaf bundleUpdate repository documentation and agent guidance against current sources when fixing drift or cleaning up docs.