Testing Schedule Preview
Use when testing the AI Engineer Europe internal Bun schedule preview or public schedule page, including tooltip, modal, CFP metadata, and local preview workflows.
Install
npx skills add swyxio/skills --skill testing-schedule-previewgit clone --depth 1 https://github.com/swyxio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/testing-schedule-preview ~/.claude/skills/testing-schedule-previewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Testing the Europe Schedule
## Overview
There are two schedule views to test:
1. **Bun preview** at `http://127.0.0.1:1234/_deploy/` — internal tool with CFP data, session IDs, contact info
2. **Public schedule page** at `/europe/schedule` — public-facing with grid overview and session list
## Bun Preview (Internal)
### Starting the Server
```bash
cd /path/to/aiecode2025
pnpm europe:source:preview
```
This runs `bun run bun-preview.mjs` inside `src/pages/europe/source/`.
If port 1234 is already in use, kill the existing process first:
```bash
fuser -k 1234/tcp
```
Note: `lsof` may not be available; use `fuser` instead.
### Key Files
- `src/pages/europe/source/_deploy/index.html` — the preview HTML
- `src/pages/europe/source/schedule.json` — data source
- `src/pages/europe/source/photos/` — speaker photos
### What to Test
- Hover tooltips show speaker summary near cursor
- Click-to-expand modal shows full details (CFP data, session IDs, contacts)
- Modal close: ESC key, backdrop click, close button
- Tooltip hides when modal opens (no ghost tooltip behind overlay)
- CFP tag colors render in both tooltip and modal
## Public Schedule Page
### Accessing
- Local: `http://localhost:3000/europe/schedule` (requires Next.js dev server)
- Vercel preview: PRs get deployments at `https://aiecode2025-git-{branch}-aieng.vercel.app/europe/schedule`
### Key File
- `src/pages/europe/schedule.tsx` — React component with grid overview, session cards, modal, filtersDetails
- Skill name
testing-schedule-preview- Repository
- swyxio/skills
- Path
testing-schedule-preview/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Testing Schedule Preview skill do?
Use when testing the AI Engineer Europe internal Bun schedule preview or public schedule page, including tooltip, modal, CFP metadata, and local preview workflows.
How do I install the Testing Schedule Preview skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add swyxio/skills --skill testing-schedule-preview. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Testing Schedule Preview popular?
It lives in swyxio/skills, which has 201 GitHub stars and 12 forks.
Related skills
Accelevents API
201swyxio/skills
Use when reading or updating AI Engineer Europe speaker records through the Accelevents REST API, especially for full-record PUT updates, auth header quirks, and preserving existing speaker fields.
Accelevents Speaker Sync
201swyxio/skills
Use when website speaker, session, schedule, room, track, or headshot changes must be synchronized back to Accelevents for AI Engineer Europe 2026.
Agents SDK
201swyxio/skills
Build or debug stateful applications that specifically use Cloudflare's `agents` package, including Agent classes, routing, callable methods, synchronized state, scheduling, AIChatAgent, durable execution, or Agents SDK client hooks. Do not trigger for generic AI-agent design, the OpenAI Agents SDK, or ordinary Durable Object work that does not use the Cloudflare Agents SDK.
Vitest
228pproenca/dot-skills
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.
Test Strategy Hardening
201swyxio/skills
Diagnose or improve tests as a system, including flaky or nondeterministic suites, duplicated coverage, expensive fixtures, slow feedback, and test selection. Use only when the user explicitly makes test architecture or suite behavior the primary task. Do not trigger for ordinary implementation work, adding or fixing a regression test, resolving one product bug, or running existing checks.
Webpack Plugin Authoring
228pproenca/dot-skills
Writing webpack 5 plugins — hook selection (compiler vs compilation, tap vs tapAsync, processAssets stages), the asset pipeline (emitAsset, source classes, info metadata, source maps), watch-mode and persistent caching (file/context/missing/buildDependencies), plugin lifecycle (constructor purity, multi-compiler isolation, shutdown cleanup), schema-utils validation, WebpackError reporting, jest-worker parallelism, and compatibility patterns (compiler.webpack namespace, peerDependencies, getCompilationHooks WeakMap). Patterns are drawn from production plugins like mini-css-extract-plugin, terse
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.