Skip to content

jedafe/japa / .claude/skills/jc-academy-audit

jc-academy-audit

Verified

JapaConnect Academy — Audit Skill

Work file-by-file. Conventions: jc-academy-develop.

A. SSR/CSR Boundary — Critical (Run First)

Scan every +page.server.ts:

  • No progress, enrollment, completedIds, or quiz-score data in any SSR load()
  • All user data fetched CSR with if (!data.session) return guard
  • Course content (title, curriculum, lesson HTML) correctly SSR Flag every +page.server.ts touching /api/v1/academy/progress/* as Critical.

B. API Consumption Verification

Every fetch()/load() route confirmed against JEOS catalog or live probe. Uncatalogued → Critical + ⚠️ MISSING BACKEND API ROUTES block.

C. Progress & Completion Logic

Set<number> for completedIds · $derived progressPercent · marking guard · optimistic + rollback · navigate-after-success only.

D. TipTap & Media

{@html} in .prose only · imgproxy URLs · post-render highlighting (dynamic import, browser-guarded) · lazy iframes with titles.

E. LayerChart Compliance

Learner dashboard / instructor analytics use LayerChart exclusively · var(--color-*) · fixed heights · skeletons · session-guarded data.

F. SEO

Per route: /courses ItemList · /courses/[slug] Course JSON-LD · lesson pages LearningResource JSON-LD · all canonicals → academy.japa.to · titles + descriptions present.

G. Performance

Lesson HTML SSR'd · highlight lib dynamically imported · lazy media · accordion renders only open sections.

H. Standard Compliance

Apply jc-main-audit §§B (Rule 16), D (Bits UI), B(runes), H (a11y — plus progressbar roles, aria-disabled locked lessons, labeled quiz inputs), I (i18n).

I. Japa Academy Marketplace (ADR-063)

  • Unified shell: since the ADR-063 consolidation there is one Academy shell — no host-detection branching. The edge routes academy.subdomain/academy.custom_domain hosts to this app. Flag any leftover dual-shell host checks or client-side host detection.
  • Marketplace catalog: /academy/tracks filters is_published_to_academy = true — flag if calling /academy/tracks instead (unpublished courses would leak).
  • Creator flow: instructor application, course submission, and instructor dashboard routes all verified via Gate. Flag any hardcoded creator/marketplace data (Rule 16).
  • Price display: price_kobo formatted as currency; NULL → "Free" or "Pro" (Pro status checked). Flag raw kobo display.
  • Pro dual-access: Pro subscribers see "Included with Pro" — flag if price shown to Pro users.
  • Course reviews: use polymorphic reviews (entity_type = 'academy_track') — flag a custom/separate review system (ADR-063 §2 violation).
  • SSR/CSR boundary for marketplace: instructor dashboard, payout data, and revenue are CSR (session-guarded) — flag any in SSR load() (same critical class as §A).
  • Instructor dashboard LayerChart: revenue-over-time chart uses LayerChart, Gate-verified data, CSS-var colors, fixed height, skeleton.

Report Format

Same structure as jc-main-audit with categories: SSR/CSR boundary · API routes · Rule 16 · Progress logic · LayerChart · Bits UI · Svelte 5 · SEO · Performance · A11y · Japa Academy marketplace (ADR-063).

App Shell & LayerChart (ADR-060 / ADR-059)

  • Academy uses the unified shell (ADR-058) adapted per ADR-060: collapsible left nav (learning-oriented, state via ui.nav_collapsed server-side — not localStorage), center, right sidebar (continue/streak/up-next). Flag surfaces built as a top-nav or standalone layout.
  • Lesson player is Academy's reading exception: collapsed nav + CurriculumRail (borderless, part of the content — not a second nav) + lesson-meta panel. Flag two-sidebar-looking rails.
  • TrackCard is one variant-driven card — flag per-level/type card forks.
  • Charts: pinned layerchart@2.0.1, colors via CSS vars, fixed height, Gate-verified data, per-chart skeleton — flag unpinned/@next or hardcoded chart colors.
  • Enforce the SSR/CSR boundary: user progress/enrollment must be CSR, never in +page.server.ts. V2 academy app: No new pages in v2. Japa Academy (ADR-063) is already implemented. The academy app may receive minor amendments if Japa Academy course visibility is affected by v2 persona authorship or the AI Content Studio publishing courses. Per ADR-060, v2 community features (§§79–89), functional tools (§§90–101), and mentorship (§102) are not part of the academy platform — they live in the Main app (community) and Tools app (functional tools). However, academy content may be cross-referenced from these features (e.g. a functional tool may link to a relevant academy track). Total platform route count is now ~819 (~475 v1 + ~344 v2); 18 Golden Rules (R18: always use bun).

V2 Feature Areas (Implement Only After Corresponding Backend Phase Is Complete)

FeatureBackend phaseKey sectionsGates
JapaBot (RAG-grounded)Phase 41§69/ai/chat amended
AI Content Studio (admin)Phase 42§75studio.* RBAC
Participation queue (admin)Phase 42§76participation.review RBAC
Visa ChecklistPhase 43§70checklist.use RBAC
Readiness AssessmentPhase 43§71assessment.take RBAC
Cost of Living CalculatorPhase 43§72col_calculator.use RBAC
Scholarship FinderPhase 43§73scholarship.browse RBAC
Remittance Rate TrackerPhase 44§74remittance.view RBAC
Referral systemPhase 45§60referral.use RBAC
Self-serve adsPhase 45§61ads.self_serve.create RBAC
NewsletterPhase 45§62newsletter.subscribe RBAC
Jobs boardPhase 45§63jobs.browse RBAC
GamificationPhase 45§64gamification.view RBAC
Content importPhase 46§65import.use RBAC
Advanced analyticsPhase 46§66analytics.advanced RBAC
Travel searchPhase 46§67travel.search RBAC

API-Readiness Gate applies to all v2 features. Verify against api-routes-catalog.md — all v2 routes are marked as "V2 planned" in the catalog. Once the corresponding backend phase lands, the planned routes become available.

Removed surface: apps/tools was consolidated into apps/main (/tools/{tool}) — ADR-086 superseded. tools.japa.to and per-tool subdomains 301 to japa.to/tools/{tool}; the jc-tools-* skills were deleted.

rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall