원클릭으로 Manus에서 모든 스킬 실행

repo-performance-analytics-workflow

스타17

포크0

업데이트2026년 4월 27일 08:32

Maintains the dev performance analytics pipeline across browser instrumentation, persisted analytics API, Prisma storage, and editor analytics UI. Use when editing `performanceAnalytics`, `/api/performance-analytics`, analytics Prisma models, or editor analytics sections.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

emzinnia

emzinnia/emzinnia.dev

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Repo Performance Analytics Workflow

Use this skill when

Editing src/lib/stores/performanceAnalytics.svelte.ts
Changing src/lib/server/performanceAnalyticsIngest.ts
Updating src/routes/api/performance-analytics/+server.ts
Changing analytics Prisma models or migrations
Editing editor analytics UI under src/lib/components/editor/ or src/routes/editor/analytics/+page.svelte

Source-of-truth split

Browser-only collection and session state live in src/lib/stores/performanceAnalytics.svelte.ts.
Request validation, normalization, dedupe, and rate limiting live in src/lib/server/performanceAnalyticsIngest.ts.
Persistence and summary API behavior live in src/routes/api/performance-analytics/+server.ts.
Database shape lives in server/schema.prisma and server/migrations/.
Dev UI lives in src/lib/components/editor/EditorAnalyticsSection.svelte.

Rules

Keep analytics collection dev-only through $app/environment guards.
Do not let client-provided analytics fields bypass server-side normalization limits.
Keep event kind names aligned across client types, server mapKind, and Prisma AnalyticsEventKind.
Preserve capped in-memory queues and batching to avoid noisy dev sessions overwhelming storage.
Treat route, URL, detail, and session ID fields as untrusted user input at the API boundary.
If persistence shape changes, update Prisma schema, normalization, API serialization, UI summary types, and tests together.

Verification

Run npm run test:unit -- --run after changing normalization, summaries, or analytics helpers.
Run npm run check after client store or editor UI changes.
Manually verify /editor/analytics in dev mode when changing displayed metrics or persistence status.

이 저장소의 다른 Skills

같은 저장소

repo-content-markdown-workflow

emzinnia/emzinnia.dev

Maintains article, project, and markdown-backed content flows in this SvelteKit portfolio. Use when editing `src/articles/**`, blog/project routes, `src/lib/articles.ts`, `src/lib/markdown.ts`, content reader panels, or the dev content editor.

2026-04-2717

repo-design-system-catalog

emzinnia/emzinnia.dev

Maintains this repo's UI component library, design page, component documentation registry, and design-system docs. Use when editing `src/lib/components/ui/**`, `src/lib/components/design/**`, `src/lib/registry/designComponents.ts`, `src/routes/design/**`, or `docs/components/**`.

2026-04-2717

repo-homepage-grid-registry

emzinnia/emzinnia.dev

Maintains homepage registry data, grid item types, shuffled layout behavior, reader panels, and homepage block wiring. Use when editing `src/lib/registry/homepage.ts`, `src/lib/types/homepage.ts`, grid components, homepage blocks, or `src/routes/+page.svelte`.

2026-04-2717

repo-api-route-patterns

emzinnia/emzinnia.dev

Implements SvelteKit API routes in this repo using the existing server, env, and response conventions. Use when editing `src/routes/api/**/+server.ts`, adding new endpoints, or connecting server routes to Prisma or GitHub-backed data.

2026-04-1117

repo-editor-dev-surface

emzinnia/emzinnia.dev

Maintains the dev-only editor route and its shared homepage customization state. Use when changing `/editor`, grid layout behavior, local user settings, debug toggles, or editor section components.

2026-04-1117

repo-hero-3d-workflow

emzinnia/emzinnia.dev

Updates the homepage hero 3D effect across Threlte scene code, parameter stores, and persisted debug settings. Use when changing `Hero3D`, shader parameters, presets, motion tuning, or hero debug controls.

2026-04-1117

name	repo-performance-analytics-workflow
description	Maintains the dev performance analytics pipeline across browser instrumentation, persisted analytics API, Prisma storage, and editor analytics UI. Use when editing `performanceAnalytics`, `/api/performance-analytics`, analytics Prisma models, or editor analytics sections.

Repo Performance Analytics Workflow

Use this skill when

Editing src/lib/stores/performanceAnalytics.svelte.ts
Changing src/lib/server/performanceAnalyticsIngest.ts
Updating src/routes/api/performance-analytics/+server.ts
Changing analytics Prisma models or migrations
Editing editor analytics UI under src/lib/components/editor/ or src/routes/editor/analytics/+page.svelte

Source-of-truth split

Browser-only collection and session state live in src/lib/stores/performanceAnalytics.svelte.ts.
Request validation, normalization, dedupe, and rate limiting live in src/lib/server/performanceAnalyticsIngest.ts.
Persistence and summary API behavior live in src/routes/api/performance-analytics/+server.ts.
Database shape lives in server/schema.prisma and server/migrations/.
Dev UI lives in src/lib/components/editor/EditorAnalyticsSection.svelte.

Rules

Keep analytics collection dev-only through $app/environment guards.
Do not let client-provided analytics fields bypass server-side normalization limits.
Keep event kind names aligned across client types, server mapKind, and Prisma AnalyticsEventKind.
Preserve capped in-memory queues and batching to avoid noisy dev sessions overwhelming storage.
Treat route, URL, detail, and session ID fields as untrusted user input at the API boundary.
If persistence shape changes, update Prisma schema, normalization, API serialization, UI summary types, and tests together.

Verification

Run npm run test:unit -- --run after changing normalization, summaries, or analytics helpers.
Run npm run check after client store or editor UI changes.
Manually verify /editor/analytics in dev mode when changing displayed metrics or persistence status.