hushh_Tech_website

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.

Use when a contributor PR changes Hushhtech API request or response behavior, route semantics, or page-to-API contract alignment.

Use when a contributor PR touches Hushhtech API routes, runtime helpers, or backend behavior and the correct narrower backend spoke is not yet obvious.

Use when PR triage or patching depends on contributor docs, policy docs, or documentation placement and wording.

Use when a contributor PR changes shared Hushhtech UI primitives, shell chrome, theme behavior, or reusable visual patterns.

Use when a contributor PR touches Hushhtech web pages, components, hooks, or frontend services and the correct narrower frontend spoke is not yet obvious.

Use when a contributor opens a pull request and a maintainer needs to decide whether to merge, patch-and-merge, request changes, or discard/close it.

Use when a request starts with scanning Hushhtech, mapping repo surfaces, or choosing which owner skill should take the next step.