A full-catalogue product enquiry and live website stock-check demo for Sia Huat.
CommerceTypeScript · PythonGitHub @Hi-Lite-DigiOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
Phase 1 is a conversational product-enquiry web application using Claude Sonnet 5 for replies and image analysis, OpenAI gpt-transcribe for voice transcription, and a Sia Huat catalogue in Supabase Postgres. The web application's runtime does not call the former n8n workflows.
See docs/CLAUDE-RESTORATION.md for the current provider configuration and verification.
Open the Hi-Lite × Sia Huat Product AssistantRead the full README ↗Phase 1 is a conversational product-enquiry web application using Claude Sonnet 5 for replies and image analysis, OpenAI gpt-transcribe for voice transcription, and a Sia Huat catalogue in Supabase Postgres. The web application's runtime does not call the former n8n workflows.
See docs/CLAUDE-RESTORATION.md for the current provider configuration and verification.
Open the Hi-Lite × Sia Huat Product Assistant
Current release: V_3.1.2
The website catalogue is discovered from Sia Huat's public sitemap and imported with the displayed item code as the unique identifier. Product discovery uses the cached Supabase catalogue; after the customer confirms an exact item, the app performs a fresh website check for the displayed price and stock status.
The assistant clarifies broad requests, searches real catalogue data, asks for quantity, calculates an estimated total deterministically, and prepares the result for human sales review. It never confirms an order or sends a customer message automatically.
See docs/ARCHITECTURE.md for the system design, trust boundaries, security model, and remaining production work.
.env.example to .env.local and add the server-only Anthropic and OpenAI keys and existing catalogue configuration.pnpm install.pnpm dev.http://localhost:3000 or the port printed by Next.js.Required application variables:
ANTHROPIC_API_KEY=your-anthropic-key
ANTHROPIC_MODEL=claude-sonnet-5
OPENAI_API_KEY=your-openai-key
OPENAI_TRANSCRIPTION_MODEL=gpt-transcribe
SUPABASE_URL=https://your-project.supabase.co
SUPABASE_PUBLISHABLE_KEY=your-publishable-key
The catalogue import scripts additionally require SIA_HUAT_PROJECT_REF and SIA_HUAT_POSTGRES_PASSWORD. Those administrative values are for local import/migration work and should not be configured in the deployed web application.
The public sitemap currently exposes more than 19,000 product pages. The crawler is resumable and writes sorted results plus a failure report under tmp/siahuat-crawl/.
pnpm catalogue:crawl -- --concurrency=8
pnpm catalogue:crawl -- --concurrency=8 --import
Use a small --limit=10 while testing. The checked-in n8n workflow export is n8n/sia-huat-b2b-phase-1.json; import it into n8n and configure SUPABASE_URL and SUPABASE_PUBLISHABLE_KEY in that n8n environment.
pnpm typecheck
pnpm lint
pnpm build
pnpm db:verify
pnpm qa:all
pnpm qa:text runs the Sia Huat conversation, relevance, memory, safety and
handoff regression suite derived from the chatbot SOP. pnpm qa:image checks
the two supplied product-photo fixtures. Both commands write machine-readable
evidence to tmp/qa-reports/.
The local test flow should cover:
Development and acceptance testing stay local. GitHub is the source repository. Vercel should be connected and deployed only once the user explicitly approves a release candidate, avoiding unnecessary builds during development.