Skip to main content

Content-First Study Page Repair Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Replace repetitive enrichment with page-aware, student-useful study support and add essential subject bridge pages.

Architecture: Update scripts/enrich_student_notes.mjs into a content repair tool. It removes previously generated generic blocks, analyzes each page's real structure, inserts concise page-specific study aids, and creates subject bridge pages.

Tech Stack: Node.js ESM script, Markdown/MDX docs, Docusaurus, Mermaid.

Task 1: Replace Generic Generator​

Files:

  • Modify: scripts/enrich_student_notes.mjs

  • Rewrite the script so it removes the old generated blocks, parses front matter, detects headings outside code fences, extracts real page sections, and generates page-aware study blocks.

  • Add subject-specific example templates that are concrete but avoid unsupported facts.

  • Add quality flags for thin pages, missing examples, missing headings, and high-stakes pages that need source-backed expansion.

Task 2: Add Subject Bridge Pages​

Files:

  • Modify: scripts/enrich_student_notes.mjs

  • Create generated docs under each major subject directory.

  • Generate Core_Concepts_and_Study_Strategy.md for each major subject.

  • Generate Worked_Examples_and_Case_Studies.md for each major subject.

  • Keep bridge pages concise, student-facing, and clearly tied to the subject.

Task 3: Regenerate Docs​

Files:

  • Modify: docs/**/*.md

  • Run node scripts/enrich_student_notes.mjs --dry-run.

  • Run node scripts/enrich_student_notes.mjs.

  • Spot-check representative Computer Science, Law, Medicine, Electronics, Business, and interview-prep pages.

Task 4: Verify​

Files:

  • Read: generated docs and script output.

  • Scan for old generic sections.

  • Scan for new page-aware sections.

  • Scan for unbalanced code fences.

  • Run npm run build.

  • Commit the repair.

Last updated on