hushh-labs
@hushh-labs Organization
Public Skills
codex-bridge
by hushh-labs
Answers questions about and routes tasks for the hushh-research codebase. Use whenever the user asks about or wants to change anything this repo owns, including consent-protocol, Operons, HCT, Kai, MCP, IAM, PKM, vault, backend, frontend, mobile, security, docs, comms, ops, skill authoring, and any new specialist added under .codex/ later. Reads .codex/skills/, .codex/workflows/, and .codex/agents/ at invocation time, composes a briefing the way codex route-task does (workflow plus owner_skill plus default_spoke unioned), surfaces .codex/agents/* as advisory delegation lanes, and auto-discovers anything added to the tree without a bridge edit.
wire-voice-navigation
by hushh-labs
Add voice navigation (route.* actions) so a person can reach a set of app screens by saying their name -- "show my holdings", "open news". Use when asked to make a surface/domain voice-navigable, extend "what can I say" coverage, or wire the Kai action gateway for a new set of screens (Gmail, Calendar, or any future surface). First step is always sorting the requested capabilities into navigation vs. action -- see "Step 0" below before touching any file.
planning-board
by hushh-labs
Use when inspecting, summarizing, creating, triaging, or updating work on the Hussh Engineering Core (Project 73) or Hussh Action Items (Project 79) GitHub boards.
tri-flow-parity
by hushh-labs
Use when declaring, reviewing, or enforcing Web/iOS/Android tri-flow parity for a route or feature, including the excluded-route reason contract and the N/A declaration the PR template requires.
hushh-research-ship
by hushh-labs
The exact merge-and-deploy procedure for hushh-labs/hushh-research, written from a real
access-explained
by hushh-labs
Plain-English map of who can do what in Hushh's Google Cloud and GitHub, written for product and non-engineering people. Explains in tables why a deploy gets refused, why UAT is locked even for the boss, what each robot account is for, why logins keep expiring, and which error messages are actually normal. Use when someone asks "why can't I deploy", "do I have access", "what does this error mean", "who can approve this", or when a non-engineer needs to understand the access setup without reading the technical gcp-access skill.
location-header-system
by hushh-labs
The header contract for every One Location screen — the top-bar breadcrumb, the single back control, and the eyebrow/title pair. Use when adding, renaming, or redesigning any Location surface (a new ?action= flow, a /one/location/* route, a check-in or SOS or settings screen), when a screen shows two back buttons, when a screen has no breadcrumb, when a breadcrumb label disagrees with the on-screen title, or when a Location flow renders full-bleed over the app shell. Also use before changing oneLocationActionLabel or any Location TaskFlowHeader.
founder-brief-curation
by hushh-labs
Use when drafting or polishing founder-facing architecture briefs, presentation-grade markdown/html/pdf artifacts, generic report PDFs, Drive/shareable artifacts, or paper-style technical specs that must stay grounded in repo truth.
run-ios-sim
by hushh-labs
Build the hushh One webapp, sync it into the native iOS shell, and launch it on an iPhone simulator against the UAT backend. Use when the user asks to run/launch/build the app on the simulator, take a screenshot on device, or verify a change in the real native app. Wraps the mobile build gotchas (UAT backend override, Node 22, 8 GB heap, /tmp DerivedData) into one command.
release-ios-appstore
by hushh-labs
Compatibility entry point for the canonical Hushh iOS App Store release skill. Use only when explicitly asked to prepare or submit an App Store release.
gcp-access
by hushh-labs
The complete GCP identity, permission, and deploy-authority map for the
ship-discipline
by hushh-labs
The Hushh engineering operating standard for building, verifying, and reporting work. Release transitions are explicit user-authorized operations governed by the canonical Admin release SOP; ordinary code changes do not imply UAT or production deployment.
vault-pkm-governance
by hushh-labs
Use when changing vault boundaries, PKM storage rules, encrypted information handling, or ordinary vault/PKM persistence behavior inside the security-audit owner family.
ship-testflight
by hushh-labs
Cut a Hussh One iOS build from green main and get it onto your iPhone via TestFlight, self-serve, from any OS including Windows. Use when asked to release/push/cut a TestFlight build, test an iOS fix on a real device, or when a TestFlight dispatch was refused, produced no run at all, or the build never reached testers. Works for any teammate in the UAT allowlist; needs no Mac, no Xcode, and no signing certificates.
deploy-uat
by hushh-labs
Dispatch, watch, and verify a UAT deployment of hushh-research through the governed GitHub Actions lane. Use when asked to deploy to UAT, ship a merged SHA to UAT, check why a UAT dispatch was refused, or when a dispatch attempt produces no workflow run at all. Works for any teammate whose GitHub login is in the UAT allowlist; encodes the token-scope trap that makes dispatches silently never reach GitHub.
hushh-one-pkm
by hushh-labs
Use when an OpenClaw agent needs to access a Hussh One user's Personal Knowledge Model through the Hussh MCP bridge. This covers developer-token setup, dynamic scope discovery, explicit user consent in One/Kai, consent polling, scoped export retrieval, and the privacy boundary for external agents.
ship-without-actions
by hushh-labs
The complete release pipeline for when GitHub Actions is unavailable — runs every CI check, then deploys, as one command. Use when Actions runs sit queued or never start, when a deploy fails at "Validate deployment SHA against main", when someone says "GitHub Actions is down" / "deployment is down" / "runners are stuck", when asked to "run all the CI checks locally" or "verify before deploying", or when work must ship and the governed workflow cannot be scheduled.
emil-design-eng
by hushh-labs
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
review-animations
by hushh-labs
Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.
animate
by hushh-labs
Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use review-animations; for auditing a whole codebase use improve-animations.
improve-animations
by hushh-labs
Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.
prototype
by hushh-labs
Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Only runs when explicitly invoked; it does not trigger on its own.
pick-ui-library
by hushh-labs
Pick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.
impeccable
by hushh-labs
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.