Skip to content

Set up FRAGLINE dev environment + add Cursor Cloud instructions #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
P4ND4907 wants to merge 1 commit into
base: cursor/fragline-idle-manager-8e1b
Choose a base branch
from
Draft

Set up FRAGLINE dev environment + add Cursor Cloud instructions #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
# AGENTS.md

## Cursor Cloud specific instructions

This repo is primarily a community-health template repo, but the actual application is **FRAGLINE**, a React + TypeScript + Vite idle esports manager located in the `fragline/` subdirectory. All app commands must be run from `fragline/`, not the repo root.

### Services

There is a single service: the Vite dev server for `fragline/`.

- Run dev server: `cd fragline && npm run dev` (serves at `http://localhost:5173`).
- Lint: `cd fragline && npm run lint` (oxlint). Note: a pre-existing `no-unused-vars` warning in `scripts/stuck-feed.mts` is expected and not an error.
- Build: `cd fragline && npm run build` (runs `tsc -b` then `vite build`).
- Preview production build: `cd fragline && npm run preview`.

### Notes

- Node 20.19+ / 22+ is required (Vite 8). The VM's default Node (v22) works; do not force an older nvm-managed version.
- The app has no backend, database, or environment variables. State persists client-side via `localStorage`, so testing a fresh state may require clearing site data / localStorage in the browser.
- Dependencies live only in `fragline/package.json`; there is no root-level `package.json`.