njpinzon

Aurora Travel Backend — Development skill for Claude Code

Development community

A warm, playful travel-agent chatbot with procedurally-generated ambient soundscapes.

How to install Aurora Travel Backend

This entry records only its repository, not the path inside it, so there is no exact command to give. Open njpinzon/aurora-travel-backend and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Aurora Travel Backend does

A warm, playful travel-agent chatbot with procedurally-generated ambient soundscapes. Backend keeps your Anthropic API key secure while the frontend chats with Claude and generates music based on destinations.

Alternatives in Development

Mono Color Skill — One-ink editorial print image skill — warm paper, halftone photography, active negative space, and restrained 3k ★
SOUL — You're not a chatbot 1.3k ★
Travel Plan Viz — Migo · 旅行领航 —— 把旅行行程生成为单文件、可离线、手机优先的 HTML（交互地图+每日时间轴+出发前提醒） 347 ★

README

Aurora Travel App — with backend

This version keeps your Anthropic API key on the server instead of exposing it in the browser. The frontend (in `public/`) now calls your own local backend (`/api/chat` and `/api/analyze`), which forwards requests to Claude using a key stored in an environment variable.

Setup

Install Node.js 18+ if you don't have it.
In this folder, install dependencies:
```
npm install
```
Create your .env file from the example:
```
cp .env.example .env
```
Then open .env and paste in your real Anthropic API key.
Start the server:
```
npm start
```
Open http://localhost:8787 in your browser. That's Aurora, fully working, with the key safely on the server.

What changed from the browser-only version

public/index.html now calls /api/chat and /api/analyze (relative paths on your own server) instead of https://api.anthropic.com/v1/messages directly.
server.js holds the actual Anthropic API key (from .env) and is the only place that ever talks to Anthropic. The browser never sees the key.
The model name, max_tokens, and the web-search tool are now set server-side, so the client can't be tampered with to change them.

Notes

.env is meant to stay on your machine — don't commit it or share it. Only .env.example (with no real key) should be shared or committed.
If you ever deploy this somewhere public (Render, Railway, Fly.io, a VPS, etc.), set ANTHROPIC_API_KEY as an environment variable in that platform's dashboard rather than uploading your .env file.
The service worker (sw.js) and manifest are unchanged from the earlier PWA packaging — they still let you "install" Aurora as an app once served over http(s).