hushh-labs

Use when changing One Voice capability authoring, Kai compatibility runtime contracts, generated action gateway contracts, typed-search and voice parity, persona/workspace gating, or BYOK-safe durable voice memory.

Use when reviewing an incoming pull request for north-star alignment, trust-boundary regressions, malicious or low-signal degradation, stale-vs-current CI interpretation, and true merge readiness beyond a green gate. Also owns PR train planning, merge queue cohorts, maintainer patch-then-merge, contributor harvest decisions, and backlog review waves.

Use when operating reviewer-account browser rehearsals that require BYOK unlock, memory-only decrypted information, and same-session client navigation.

Use when changing Hussh UI architecture, shared components, shell chrome, or styling rules inside the frontend owner family.

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.

Use when inspecting, summarizing, creating, triaging, or updating work on the Hussh Engineering Core GitHub board.

Use when changing Morphy AX shared agent-experience state, semantic assessment presentation, performance budgets, or cross-modal compatibility.

Use when changing Hussh frontend structure, route contracts, package-level conventions, or frontend verification ownership.

Use when deploying the HushhTech web app to UAT or PROD, triggering the deploy-uat / deploy-prod GitHub Actions workflows, picking a safe "green main" SHA to ship, or when deployments feel slow and you want to cut the CI/CD cycle time. Trigger this whenever the user mentions deploying, shipping, releasing, pushing to UAT / prod / Cloud Run, a slow build or deploy pipeline, or asks how to make deploys faster — even for tiny changes. Covers the exact deploy procedure, the safety gates, the full pipeline anatomy, and a prioritized playbook of levers to reduce deploy time.

Use when deciding which checks are authoritative for a Hushhtech PR and whether the right proof exists for the changed behavior.

Use when working on Hushhtech PR checks, CI/CD, branch protection, merge queue, deploys, env parity, or operational verification.

Use when auth, env, secrets, fail-closed behavior, or sensitive API routes make a Hushhtech PR risky to patch or merge.

Use whenever a task involves Supabase for this repo — editing or deploying edge functions, changing edge-function secrets, running migrations, or auditing Supabase dashboard config. Prefer the Supabase CLI for writes when the user has explicitly asked for deployment and the target project/ref is confirmed. If CLI is blocked, fall back to the user's Chrome session on port 9223 where ankit@hushh.ai is logged in. Trigger on any mention of Supabase edge functions, secrets, migrations, or "deploy create-link-token / an edge function".

Use whenever a task involves Supabase for this repo — editing or deploying edge functions, changing edge-function secrets, running migrations, or auditing Supabase dashboard config. Prefer the Supabase CLI for writes when the user has explicitly asked for deployment and the target project/ref is confirmed. If CLI is blocked, fall back to the user's Chrome session on port 9223 where ankit@hushh.ai is logged in. Trigger on any mention of Supabase edge functions, secrets, migrations, or "deploy create-link-token / an edge function".

Use when deploying the HushhTech web app to UAT or PROD, triggering the deploy-uat / deploy-prod GitHub Actions workflows, picking a safe "green main" SHA to ship, or when deployments feel slow and you want to cut the CI/CD cycle time. Trigger this whenever the user mentions deploying, shipping, releasing, pushing to UAT / prod / Cloud Run, a slow build or deploy pipeline, or asks how to make deploys faster — even for tiny changes. Covers the exact deploy procedure, the safety gates, the full pipeline anatomy, and a prioritized playbook of levers to reduce deploy time.

Use when generating Hushh Labs GitHub operations reports, contributor activity PDFs, missed-weekday red-alert sheets, or fair contribution/impact comparisons for named GitHub users across Hushh org repositories.

Diagnose hushh.ai website CI failures across typecheck, lint, tests, build, audits, dependency audit, and deploy-verification scripts. Use when Codex needs to reproduce a failing CI job, classify the breakage, identify the smallest safe fix, or summarize remaining release risk for this repository.

Promote or review hushh.ai website releases through the repo's SHA-only UAT and production workflows. Use when Codex needs to validate a deploy SHA, inspect the GitHub Actions and Cloud Build release path, verify rollout outputs, or prepare rollback guidance for this repository.

Verify hushh.ai website runtime readiness after local or deployed changes. Use when Codex needs to run or interpret route smoke checks, shell and SEO audits, env parity, public-domain verification, or Foundation route validation for this repository.