jamditis

Remote JavaScript console and debugging on mobile. Use for phone/tablet console errors, responsive testing, Eruda, and vConsole.

Builds an Open Knowledge Format (OKF) knowledge base from existing docs, notes, or a repo. Use to scaffold an OKF wiki.

Generates CLAUDE.md project memory files that transfer institutional knowledge. Use when setting up projects or onboarding.

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Establishes how to find and use skills, requiring Skill tool invocation before any response. Use when starting any conversation.

Runs verification commands and confirms output before success claims. Use before claiming work done or committing or PRs.

Use when you have a spec or requirements for a multi-step task, before touching code

Draft a short daily beat briefing from a folder of incoming source documents. Use when the reporter wants a five-bullet summary of the day's material with attribution flags and follow-up actions.

Minimal skill template that students copy and customize to create their first Claude Code skill. Use this as the starting point when building a new custom skill for a specific beat or workflow.

Apply AP Style and common newsroom conventions when writing or editing news articles, briefs, and headlines. Use when drafting publishable copy, editing contributor submissions, or converting informal notes into news-ready language.

Design and edit professional PDF reports and proposals with local HTML/PDF generation, iterative previews, print layouts, brand systems, and opt-in uploads. Use when creating, revising, previewing, exporting, or securely uploading a report, proposal, budget…

This skill should be used when the user reports a bug, describes unexpected behavior, says something is "broken", "not working", "failing", mentions an "error", "issue", or "problem" in code, or asks to "fix" something. Enforces test-driven bug fixing…