القائمة
UI architecture patterns for nypsi-website, e.g. how to fetch guild data for the user profile page tabs. Use when working on the user profile page or deciding how a UI section should fetch its data.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Apply established nypsi-website UI patterns. Use when creating or reviewing Svelte components, cards, profile tabs, tables, history views, empty states, status badges, or pagination controls.
Explains the session cookie, server-side locals.auth, client-side auth state, and the auth remote functions used for Discord OAuth. Use when reading or checking the authenticated user, or when adding auth-gated routes/remote functions.
Covers remote function patterns (query/form + Zod + Redis caching), the BigInt caching pitfall, preferring remote functions over API routes, data loading (+page.ts vs +page.server.ts), component naming, Svelte 5 runes usage, and the custom Prisma client import path. Use for any work involving src/lib/api/*.remote.ts, caching, data loading, components, or Prisma.
| name | architecture |
| description | UI architecture patterns for nypsi-website, e.g. how to fetch guild data for the user profile page tabs. Use when working on the user profile page or deciding how a UI section should fetch its data. |
Avoid expanding getBaseData for guild details on the user profile page. Fetch guild data via a dedicated remote function in src/lib/api/guilds.remote.ts and call it from the guild tab component directly.
