Files

T

parththakkar106andClaude Opus 4.8 8188ed3999 Play screen UX: sticky header + fix streaming autoscroll

- Pin the play header (Plot/Memory/Scripts/Insights toggles) just below
  the top nav so they stay reachable without scrolling back up to the
  first message.
- Fix streaming autoscroll: snap to the real document bottom instantly
  instead of smooth-scrolling to storyEndRef. That ref sits above the
  sticky composer, so block:'end' stopped short — hiding the latest line
  behind the input bar and yanking the reader back up when they scrolled
  down. Smooth behavior also never settled at per-token speed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TEpWMjnfPqzZ13nPMoGhs5

2026-07-20 16:57:16 +05:30

public

Initial commit: AI Dungeon clone (FastAPI backend + React frontend)

2026-07-06 16:08:19 +05:30

src

Play screen UX: sticky header + fix streaming autoscroll

2026-07-20 16:57:16 +05:30

.gitignore

Initial commit: AI Dungeon clone (FastAPI backend + React frontend)

2026-07-06 16:08:19 +05:30

.oxlintrc.json

Initial commit: AI Dungeon clone (FastAPI backend + React frontend)

2026-07-06 16:08:19 +05:30

index.html

Initial commit: AI Dungeon clone (FastAPI backend + React frontend)

2026-07-06 16:08:19 +05:30

package-lock.json

Regenerate package-lock.json with npm 11.18

2026-07-06 17:03:42 +05:30

package.json

Initial commit: AI Dungeon clone (FastAPI backend + React frontend)

2026-07-06 16:08:19 +05:30

README.md

Initial commit: AI Dungeon clone (FastAPI backend + React frontend)

2026-07-06 16:08:19 +05:30

vite.config.js

Initial commit: AI Dungeon clone (FastAPI backend + React frontend)

2026-07-06 16:08:19 +05:30

README.md

React + Vite

This template provides a minimal setup to get React working in Vite with HMR and some Oxlint rules.

Currently, two official plugins are available:

@vitejs/plugin-react uses Oxc
@vitejs/plugin-react-swc uses SWC

React Compiler

The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.

Expanding the Oxlint configuration

If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the TS template for information on how to integrate TypeScript and Oxlint's TypeScript related rules in your project.