interview-preplisted

Prepare for a software-engineering interview (frontend, backend, or mobile) from a job description (a public URL or pasted text): fetch and parse the posting, detect the discipline, stack, and seniority, choose a preparation size (short, medium, large, or extra large), pick a matching topic track, author reading notes and click-to-reveal Q&A at that depth, then build two self-contained static HTML editions from bundled templates: a tracker edition (per-section read checkboxes + progress saved in the browser, to continue day to day) and a distraction-free reading edition. Output as local static files and/or publish each edition as a private Claude artifact. Use to prepare for an interview from a JD. Writes files, so it is user-invoked only.
hcussi/claude-code-toolkit · ★ 0 · Web & Frontend · score 65

Install: claude install-skill hcussi/claude-code-toolkit

# interview-prep Turn a **job description** for a **software-engineering role (frontend, backend, or mobile)** into a tailored interview study pack, and output two self-contained static HTML editions from it: - **Tracker edition** (`tracker.html`): sidebar table of contents, a live progress ring, per-section **Mark read** checkboxes, and a **Resume** button. Progress is saved in the browser's local storage, so the candidate can stop and pick up where they left off the next day. - **Reading edition** (`reading.html`): the same content in a clean, distraction-free single scroll, no tracking. Both editions are generated from **one content model** (`content.json`) by a bundled build script, so the presentation is fixed and known-good and the only thing authored per job is the tailored content. This is a **content-authoring skill**: the real work is reading the JD, detecting the discipline (frontend, backend, or mobile), and writing accurate, role-specific material. The HTML is mechanical. **Output modes.** The build step always writes self-contained **static HTML** files that open in any browser with no server or network. On a host that supports hosted pages (for example Claude Code's Artifact tool), you can additionally publish each edition as a **private Claude artifact** and hand back a link. Offer both and let the user pick one or both. ## Arguments Free-form. Everything before an optional `|` is the **job description**; everything after `|` is optional **candi