Microeconomics Review Builder
Quick Start
Read the relevant reference before doing the task:
references/master-prompt.mdfor the full review-note project, graph coverage rules, LaTeX pipeline, and completion checklist.references/exam-prediction-prompt.mdfor the upgraded exam-prediction workflow, narrowed exam scope, difficulty design, and question-writing standards.
If the user asks for broad review notes or graph explanations, start with master-prompt.md. If the user asks for a mock exam, exam prediction, question bank, or revision of prediction questions, start with exam-prediction-prompt.md.
Workflow
- Identify whether the task is review-note construction, graph repair, exam prediction, or LaTeX/PDF validation.
- Use textbook-faithful definitions and mechanisms; verify definitions against the local textbook/OCR when available.
- For graphs, redraw with TikZ and explain axes, slopes, areas, intersections, movements, and welfare meaning.
- For exam prediction, hide chapter labels in the question stem and put chapter tags in the answer block.
- Keep calculations simple but chained to interpretation.
Quality Rules
- Do not invent definitions, numerical facts, graph shapes, or policy conclusions.
- Prefer textbook wording for definitions; summarize only when the original is too long.
- Use cross-module questions for higher difficulty rather than merely wrapping a standard example in a new story.
- Ensure objective questions have one defensible correct answer and plausible distractors tied to common misconceptions.
LaTeX Guidance
Follow the reference pipeline. Preserve the existing pdflatex + CJKutf8 style unless the user explicitly changes the build approach. For TikZ, compute intersections where possible, fill regions before redrawing curves, and keep labels from overlapping curves or points.
Public Repository Boundary
This skill publishes workflow prompts and compact guidance only. Do not add textbook PDFs, OCR dumps, compiled review PDFs, screenshots, or large generated LaTeX products to this public repository unless the user explicitly confirms publication rights.