init-project-course

Init Project Course

Bootstrap a university course or module folder into a clean, navigable structure. Designed for taught modules with lectures, workshops, assessments, and optionally recordings.

When to Use

• University modules with lectures + workshops + assessments
• Course folders that have accumulated files over a term
• When the user says "organise this module", "init course", "set up this module folder"
• Any taught course with recurring weekly components

When NOT to Use — Escalate

• To init-project-light if it's a one-off document collection (no lectures/workshops structure)
• To init-project-research if it's a research project that happens to be for a course

---

Phase 1: Scan

Read everything already in the directory before asking questions.

1. List all files and folders (excluding .claude/, .DS_Store)
2. Identify content types:
   • Lecture PDFs — files matching Lecture* or containing "lecture" in name
   • Seminar materials — files matching Seminar*, Session*, or containing "seminar" in name (discussion-based modules use seminars instead of lectures)
   • Lecture recordings — video files (.mp4, .mov, .mkv, .webm, .avi) or folders named recordings
   • Workshop folders — folders matching Workshop*, Lab*, Week*, or numbered folders with exercise content
   • Assessment folders — folders containing "group", "individual", "exam", "coursework", "assignment", "portfolio"
   • Workshop PDFs — PDFs inside workshop folders that are NOT lectures (exercise sheets, briefs)
   • Code projects — node_modules/, package.json, .py, .js, .ts files inside workshop folders
   • Notes — personal notes, reading lists, exercise solutions (common in student modules)
3. Detect duplicates: lecture PDFs that appear in multiple locations
4. Note workshop numbering gaps (normal — not every week has a workshop)
5. Check for existing organisation (already has lectures/, workshops/, etc.)