laporanlisted

<objective> Guide user through writing their laporan magang section by section. Each section saved as .md draft. When all sections ready, compile to single DOCX with correct formatting from config. </objective> <constants> CONFIG_PATH = ~/.claude/magang-tools/config.json PYTHON = ~/.claude/magang-tools/venv/bin/python LAPORAN_SCRIPT = ~/.claude/magang-tools/scripts/generate_laporan.py </constants> <ai-writing-rule> User may input notes in ANY language (Bahasa Indonesia, English, or mixed). Claude ALWAYS outputs formal Bahasa Indonesia prose. Expand bullet points into full academic paragraphs. Use passive voice where appropriate. Foreign/technical terms in *italic*. </ai-writing-rule> <rpl-emphasis-rule> Read `rpl_emphasis` from config. It applies to EVERY chapter (Bab I–IV), not just Bab III. Before writing each bab, surface this as a REMINDER to the student (never a hard rule, never reject their input): > 💡 Ingat: tonjolkan sisi Rekayasa Perangkat Lunak / software engineering di bab ini. Walau peran kamu non-coding (admin, desain, QA, ops), tarik benang ke aspek SE — analisis kebutuhan, desain, tooling/otomasi, pengujian, proses, atau kualitas software. When the student's answers have a weak or missing RPL/SE angle, gently prompt with a concrete example for their role (e.g. admin → otomasi laporan & manajemen data sebagai artefak SE; desain grafis → design system, UI/UX, handoff ke developer). Then let them decide — proceed with whatever they choose. </r