메뉴
Build, run, and smoke-test the skorifydata library and its dev-server. Use when asked to start, run, test, build, or verify the skorifydata library or dev-server.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create a Knex migration file from entity changes between the current branch and main. Use when asked to create a migration, generate a migration from entity changes, or scaffold a migration file for schema changes.
Set up, migrate, and inspect the Skorify database stack — local Postgres via Docker, Knex migrations, and the AWS RDS scheduler schedule. Use when asked to start the database, run migrations, check migration status, rollback, or understand when the RDS starts and stops.
Understand, code, and modify the Skorify ETL pipeline inside the MatchProcessingStack (SkorifyEventBridge). Use when asked to add a feature, fix a bug, or understand how match ingestion, finish-match processing, notifications, or ranking calculation work. Covers football-data.org dependencies and backend API contracts.
Regenerate and keep all repository documentation up to date. Use when asked to update docs, refresh documentation, sync docs with code changes, or update the README. Writes to docs/DATABASE.md, docs/ENTITIES.md, docs/ETL.md, and Readme.md.
| name | run-skorify-data |
| description | Build, run, and smoke-test the skorifydata library and its dev-server. Use when asked to start, run, test, build, or verify the skorifydata library or dev-server. |
skorifydata is a TypeScript data-access library (TypeORM + PostgreSQL). "Running" it means compiling the library and exercising it through the Express dev-server in dev-server/. Drive it via the smoke script at .claude/skills/run-skorify-data/smoke.sh.
All paths below are relative to the repo root (Skorify_Data/).
Node.js and pnpm must be available (already present in this repo). Docker is required only for the --with-db mode.
Install root deps if node_modules is absent:
pnpm install
Install dev-server deps if absent:
cd dev-server && pnpm install && cd ..
pnpm run build
# → compiles lib/ + entities/ → dist/
Run the smoke script — it starts the dev-server, polls until ready, hits structural endpoints, then stops:
bash .claude/skills/run-skorify-data/smoke.sh
Expected output ends with === smoke OK ===. Logs at /tmp/skorify-dev.log.
To also spin up PostgreSQL via Docker and test entity endpoints:
bash .claude/skills/run-skorify-data/smoke.sh --with-db
# Runs pnpm run setup (docker compose + migrations) first, then entity checks
To keep the server running for ad-hoc curl calls:
(cd dev-server && node_modules/.bin/tsx server.ts) &> /tmp/skorify-dev.log &
# Wait for ready:
for i in $(seq 1 30); do curl -sf http://localhost:3000/health > /dev/null && break; sleep 0.5; done
curl http://localhost:3000/health # → {"ok":true}
curl http://localhost:3000/exports # → list of all exported symbols
curl http://localhost:3000/dbclient-shape # → DBClient prototype methods
# Entity endpoints — need DB:
curl http://localhost:3000/users
curl http://localhost:3000/tournaments
curl http://localhost:3000/matches
# Stop:
pkill -f "tsx server.ts"
Available entity names for /:entity: users, tournaments, teams, matches, predictions, tournament_instances, user_enrollments.
pnpm run setup # start DB + migrate
cd dev-server && pnpm run dev # hot-reload server on :3000; Ctrl-C to stop
tsx not on PATH — must use dev-server/node_modules/.bin/tsx server.ts from inside dev-server/. Running tsx server.ts directly from a plain shell will fail with "command not found."dist/, not source — it depends on skorifydata as file:.., which resolves to dist/lib/index.js. Changes to lib/ need pnpm run build to take effect in the dev-server./users, /tournaments, etc. attempt a TypeORM connection on each request. Without a running Postgres they return a 500. Use --with-db in the smoke script or run pnpm run setup first.