web

Document the architecture and integration points of the squash-bot web service.

2|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hutoroff/squash-bot --skill web-hutoroff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web
Source: https://github.com/hutoroff/squash-bot/tree/main/.claude/skills/web
Command: npx skills add https://github.com/hutoroff/squash-bot --skill web-hutoroff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The web service serves the React SPA and a small JSON API for authenticated users. Authentication uses the Telegram Login Widget — no username/password. The React frontend is compiled and embedded in the Go binary. No database — all data comes from the management service via HTTP.

Core Features & Use Cases

  • Architecture reference for the squash-bot web service (cmd/web) to guide changes to authentication, frontend embedding, and HTTP APIs.
  • Provides detailed package structure, routes, and deployment considerations for the web service with embedded frontend.
  • Enables safe planning and onboarding by documenting the interaction with the management service and the Telegram Login Widget authentication flow.

Quick Start

Review this architecture reference before planning any changes to the web service.

Frequently Asked Questions about web

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does Telegram Login Widget authentication work in a Go web service?

Telegram Login Widget authentication in a Go web service validates Telegram-provided user data directly, bypassing traditional username/password flows. The web service issues JWT sessions for authenticated users after verifying the Telegram login payload.

How do I embed a React SPA frontend directly inside a Go binary?

Embedding a React SPA in a Go binary involves compiling the frontend assets into the Go executable. This squash-bot web architecture reference documents how the compiled React frontend is served without requiring separate static file hosting.

Can a web service operate without a database by proxying HTTP requests to a management API?

Yes, a web service can operate without a database by fetching all data via HTTP from a backend management service. This architecture reference details the integration points and HTTP interaction patterns required for this stateless web service design.

What is the recommended package structure for a Go web service with embedded frontend and JWT sessions?

The recommended package structure organizes the web service by separating the embedded frontend assets, JSON API routes, and JWT session middleware. This reference documents the specific entry points and module structure for safe onboarding and planning.

When should I review architecture documentation before modifying a web service's authentication flow?

You should review architecture documentation before any modifications to safely plan changes to authentication, frontend embedding, or HTTP APIs. This reference-only guide ensures you understand existing integration points and deployment considerations before altering the web service.