hackathon-learning-activities

Coordinate hackathon learning activity updates across data and UI layers.

2|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/passionseed/ps_app --skill hackathon-learning-activities
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hackathon-learning-activities
Source: https://github.com/passionseed/ps_app/tree/main/.agents/skills/hackathon-learning-activities
Command: npx skills add https://github.com/passionseed/ps_app --skill hackathon-learning-activities

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating updates to hackathon learning content across multiple data and UI layers can be error-prone and slow.

Core Features & Use Cases

  • Orchestrates renaming programs, phases, playlists, modules, and activities
  • Synchronizes content, metadata, and assessments across production and seed sources
  • Ensures alignment between live data and preview fallback for hackathon programs

Quick Start

Update the hackathon program content in production and seed sources, then verify alignment across programs, phases, playlists, modules, and activities.

Frequently Asked Questions about hackathon-learning-activities

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synchronize hackathon learning activities across production data and the UI?

To synchronize hackathon learning activities, inspect live Supabase tables, apply updates to the correct runtime layer, then sync seed files and frontend fallback to maintain consistency across data and UI.

What is the best way to rename hackathon programs and phases without breaking content alignment?

Renaming hackathon programs and phases requires orchestrating updates across data and UI layers, patching production Supabase data, and syncing seed files with the preview fallback to ensure content alignment.

Why does my hackathon preview fallback show outdated activity instructions and metadata?

Your hackathon preview fallback shows outdated activity instructions because seed files are not synced with production Supabase data after applying updates to the runtime layer.

Do I need to update Supabase tables before syncing seed files for hackathon content?

Yes, you must inspect and patch production Supabase tables first, then sync seed files with the preview fallback to ensure hackathon content remains consistent across all runtime layers.

Can I update hackathon activity assessments and durations directly in the frontend UI?

Updating hackathon activity assessments and durations requires applying changes to the correct runtime data layer first, then syncing seeds and frontend fallback to maintain data and UI consistency.