Use when diffing two Korean documents with `npx` and kordoc. Covers HWP, HWPX, and cross-format comparisons for requests such as 신구대조표 preparation, change review between document versions, block-level additions and removals, or invoking `kordoc:compare_documents` on two local files.
Use when identifying whether a Korean document file is HWP, HWPX, PDF, or unknown with `npx` and kordoc. Trigger for triage requests such as checking file type before parsing, validating uploads, routing mixed office files, or using `kordoc:detect_format` on local documents.
Use when converting Korean document files into readable text with `npx` and kordoc. Covers HWP, HWPX, and PDF parsing to Markdown or JSON, including metadata, outline, warnings, and page count. Trigger for requests such as reading a government document, extracting document contents, summarizing a Korean office file, or parsing a local .hwp/.hwpx/.pdf with `kordoc:parse_document`.
Use when extracting structured label-value fields from Korean forms with `npx` and kordoc. Trigger for requests involving applications, government forms, personnel sheets, contact fields, or any HWP, HWPX, or PDF document that should be processed with `kordoc:parse_form`.
Use when extracting document metadata with `npx` and kordoc instead of reading the full document text. Trigger for requests about title, author, created date, or quick inspection of local HWP, HWPX, and PDF files through `kordoc:parse_metadata`.
Use when parsing only part of a Korean document with `npx` and kordoc. Trigger for requests such as extracting pages 1-3, reading selected pages from HWP, HWPX, or PDF, limiting work on large files, or running `kordoc:parse_pages` with a page-range string.
Use when extracting a specific table from a Korean document with `npx` and kordoc. Trigger for requests such as pulling the first or Nth table from HWP, HWPX, or PDF, isolating tabular content for review, or using `kordoc:parse_table` with a zero-based table index.
Use when reviewing or writing eGovFrame 4.x or 5.x Java code — Controller, Service, DAO, configuration, or library usage. Covers inheritance requirements, forbidden call patterns, and architecture constraints. Assumes Spring Framework knowledge.