القائمة
Production debugging guidance for diplicity-react — Railway CLI token conflict pattern, pgweb queries, write safety rules, and staging environments. Use when debugging production issues, querying the production database, or deploying PR staging environments.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Django backend guidance for diplicity-react — views, serializers, models, permissions, constants, transactions, and codegen. Use when implementing or reviewing backend features, modifying the Django service, or debugging API behavior.
React frontend guidance for diplicity-react — components, state management, forms, data loading, routing, mock data, screenshots, and testing. Use when implementing or reviewing React features, refactoring frontend code, or taking PR screenshots.
Android Capacitor guidance for diplicity-react — build workflow, ADB setup, Firebase Cloud Messaging, Google Sign-In, keystore management, SHA-1 fingerprints, and Fastlane releases. Use when building, deploying, or debugging the Android app, or managing Android credentials.
iOS Capacitor guidance for diplicity-react — build workflow, Xcode project setup, APNs and ASC credentials, code signing strategy, Fastlane releases, and GitHub Actions. Use when building, deploying, or debugging the iOS app, or managing iOS credentials.
Metabase analytics guidance for diplicity-react — native SQL patterns for multi-hop joins, base64 encoding workflow, and schema gotchas in the diplicity production database. Use when writing Metabase queries or working around schema limitations.
Testing guidance for diplicity-react — frontend Vitest and backend pytest patterns, fixtures, conftest organisation, MSW mocks, and performance tips. Use when writing or running tests, setting up fixtures, or reviewing test code.
استنادا إلى تصنيف SOC المهني
| name | production |
| description | Production debugging guidance for diplicity-react — Railway CLI token conflict pattern, pgweb queries, write safety rules, and staging environments. Use when debugging production issues, querying the production database, or deploying PR staging environments. |
| allowed-tools | Bash, Read, Glob, Grep |
App deployed on Railway (project: devoted-rejoicing, service: diplicity-react).
Two tokens, different scopes:
| Variable | Scope | Used for |
|---|---|---|
RAILWAY_API_TOKEN | Account | whoami, status, logs |
RAILWAY_TOKEN | Project | railway run (inject prod env vars) |
When both are set, Railway CLI v5 gives RAILWAY_TOKEN priority for all commands, breaking account-scoped ones with "Unauthorized". Always unset the irrelevant token:
# Account-scoped
env -u RAILWAY_TOKEN railway whoami
env -u RAILWAY_TOKEN railway status
env -u RAILWAY_TOKEN railway logs --lines 50
# Project-scoped
env -u RAILWAY_API_TOKEN railway run --service diplicity-react python manage.py shell
If any railway command fails with an auth or "not logged in" error, stop immediately. Tell the user:
"Railway is not configured in this session. Set
RAILWAY_API_TOKENin the Claude Code on the web environment, and allowlist*.railway.comand*.railway.appunder Custom network access."
railway run injects production env vars and runs locally against the live production database. Never execute write operations:
.create(), .update(), .delete(), .save() in Django ORMINSERT, UPDATE, DELETE in raw SQLmigrate, flush, loaddata)If the user asks to modify production data, refuse — production changes must go through a migration or controlled admin process.
env -u RAILWAY_TOKEN railway status # deployment health
env -u RAILWAY_TOKEN railway logs --lines 50 # recent logs
env -u RAILWAY_TOKEN railway logs --lines 200 | grep ERROR # filter errors
env -u RAILWAY_TOKEN railway logs --lines 200 | grep "GET /api" # filter by endpoint
Cloud sessions can't reach the production DB via railway run (Railway's internal hostname is not externally resolvable). Use pgweb instead — a web-based PostgreSQL client deployed as a Railway service over HTTPS.
Required env vars (set in cloud environment config; session-start hook exports them):
PGWEB_URL — e.g. https://pgweb-production-124e.up.railway.appPGWEB_USER / PGWEB_PASSWORD — basic-auth credentials# Write SQL to a file first (avoids shell escaping issues)
cat > /tmp/query.sql << 'EOF'
SELECT status, COUNT(*) FROM game_game GROUP BY status ORDER BY count DESC
EOF
curl -s -u "$PGWEB_USER:$PGWEB_PASSWORD" \
-X POST "$PGWEB_URL/api/query" \
--data-urlencode "query@/tmp/query.sql" \
| python3 -c "
import json, sys
d = json.load(sys.stdin)
print('\t'.join(d['columns']))
for row in d['rows']:
print('\t'.join(str(c) for c in row))
"
Use the /prod-query skill for guided read-only queries.
pgweb is read-only by configuration. Never issue INSERT, UPDATE, DELETE, or DDL.
Check https://status.railway.com for platform-wide incidents.
PRs can be deployed to an isolated staging environment with a copy of the production database — useful for testing migrations against real data or validating end-to-end behavior.
Add the deploy-to-staging label to a PR. .github/workflows/pr-staging.yml will:
staging-pr-<number>)pg_dump/pg_restoreThe Netlify deploy preview automatically derives the staging backend URL from the PR number (packages/web/netlify.toml uses REVIEW_ID).
Add the deploy-to-staging label again — the workflow reuses the existing environment and re-clones the database.
Staging environments are automatically deleted when the PR is closed or merged.
39039c2c-4f5d-4a37-8c0d-f8e4279fce61