add files

This commit is contained in:
김경종
2026-04-30 17:05:19 +09:00
parent f3e01b5a8c
commit 7e985ae94a
135 changed files with 41205 additions and 0 deletions
@@ -0,0 +1,26 @@
---
description: Review conversion policy, architecture, ADRs, and AGENTS.md for consistency.
argument-hint: [optional-topic]
allowed-tools: [Read, Glob, Grep, Bash]
---
# /conversion-policy-review
## Arguments
The user invoked this command with: $ARGUMENTS
## Workflow
1. Read `AGENTS.md`, `docs/ARCHITECTURE.md`, `docs/CONVERSION_POLICY.md`, `docs/ADR.md`, `docs/PRD.md`, and `docs/TOOLCHAIN.md`.
2. Check for drift in parser responsibilities, output contract, runtime policy, logging/resume policy, environment pins, and sidecar scope.
3. Lead with concrete inconsistencies and file references.
4. Run `python scripts\validate_workspace.py` if file changes were made or if the user asks.
5. Do not edit files unless explicitly asked.
## Output
- **Findings**
- **Consistency Status**
- **Open Questions**
- **Suggested Fixes**
+28
View File
@@ -0,0 +1,28 @@
---
description: Verify the repo-local PDFtoMD Python environment, CUDA, and Nougat CLI.
argument-hint: [quick|full]
allowed-tools: [Read, Bash]
---
# /env-check
## Arguments
The user invoked this command with: $ARGUMENTS
## Workflow
1. Read `AGENTS.md`, `requirements.txt`, `docs/TOOLCHAIN.md`, and `PROGRESS.md`.
2. Run `.\venv\python.exe -m pip check`.
3. Run a CUDA smoke test with `torch.ones((1,), device="cuda")` unless `$ARGUMENTS` says `quick`.
4. Run `.\venv\Scripts\nougat.exe --help`.
5. Summarize versions and failures.
6. Do not install or upgrade packages unless the user explicitly asks.
## Output
- **Environment**
- **CUDA**
- **Nougat**
- **Dependency Health**
- **Action Needed**
+25
View File
@@ -0,0 +1,25 @@
---
description: Check model cache and offline-readiness assumptions for Marker, Nougat, and Hugging Face assets.
argument-hint: [cache-path-or-empty]
allowed-tools: [Read, Bash]
---
# /model-cache-check
## Arguments
The user invoked this command with: $ARGUMENTS
## Workflow
1. Read `AGENTS.md`, `docs/TOOLCHAIN.md`, `docs/ARCHITECTURE.md`, and `docs/CONVERSION_POLICY.md`.
2. Inspect relevant environment variables and common Hugging Face cache paths.
3. Check whether local cache paths are explicit enough for offline execution.
4. Do not download model weights unless the user explicitly asks.
## Output
- **Cache Paths**
- **Offline Readiness**
- **Missing Assets**
- **Documentation Gaps**
+28
View File
@@ -0,0 +1,28 @@
---
description: Draft Harness phase steps for PDFtoMD implementation without executing them.
argument-hint: [phase-goal]
allowed-tools: [Read, Glob, Grep, Write, Edit]
---
# /phase-draft
## Arguments
The user invoked this command with: $ARGUMENTS
## Workflow
1. Read `AGENTS.md`, `PLAN.md`, `PROGRESS.md`, `docs/PRD.md`, `docs/ARCHITECTURE.md`, `docs/CONVERSION_POLICY.md`, `docs/HARNESS.md`, `docs/ADR.md`, and `docs/TOOLCHAIN.md`.
2. Use `$harness-workflow` guidance if phase files should be created.
3. Keep each step self-contained and scoped to one layer or module.
4. Include executable acceptance commands.
5. Include a Sprint Contract with done criteria, hard thresholds, owned files, and dependencies.
6. Do not create phase files unless the user explicitly requested file generation.
## Output
- **Phase Goal**
- **Step List**
- **Dependencies**
- **Acceptance Commands**
- **Do Not**
+26
View File
@@ -0,0 +1,26 @@
---
description: Draft focused pytest coverage for PDFtoMD conversion quality.
argument-hint: [feature-or-sample-focus]
allowed-tools: [Read, Glob, Grep]
---
# /quality-plan
## Arguments
The user invoked this command with: $ARGUMENTS
## Workflow
1. Read `AGENTS.md`, `PLAN.md`, `PROGRESS.md`, `docs/PRD.md`, `docs/ARCHITECTURE.md`, and `docs/CONVERSION_POLICY.md`.
2. Identify focused tests for headings, formulas, tables, images, captions, links, chunk boundaries, Windows paths, Korean filenames, and no-exception conversion.
3. Prefer concrete pytest names and fixture inputs.
4. Do not write tests unless explicitly asked.
## Output
- **Test Goals**
- **Proposed Test Files**
- **Fixture Needs**
- **Acceptance Commands**
- **Residual Risks**
+27
View File
@@ -0,0 +1,27 @@
---
description: Audit samples/ PDFs for page counts, text-layer quality, images, and OCR candidates.
argument-hint: [pdf-glob-or-empty]
allowed-tools: [Read, Glob, Bash, Write, Edit]
---
# /sample-audit
## Arguments
The user invoked this command with: $ARGUMENTS
## Workflow
1. Read `AGENTS.md`, `PLAN.md`, `PROGRESS.md`, and `docs/CONVERSION_POLICY.md`.
2. Use PyMuPDF from `.\venv` to inspect matching `samples/*.pdf` files.
3. Report page count, first-page text length, image counts, suspected scan/OCR pages, Korean filename coverage, and obvious layout risks.
4. If the user asks to write metadata, create or update `samples/metadata.json`; otherwise only report.
5. Update `PROGRESS.md` when files are changed.
## Output
- **Corpus Summary**
- **Per-PDF Traits**
- **OCR Candidates**
- **Test Implications**
- **Recommended Metadata Changes**
+31
View File
@@ -0,0 +1,31 @@
---
description: Draft or review a step-level generator/evaluator contract before implementation.
argument-hint: [phase-dir step-number]
allowed-tools: [Read, Glob, Grep, Edit]
---
# /sprint-contract
## Arguments
The user invoked this command with: $ARGUMENTS
## Workflow
1. Read `AGENTS.md`, `PLAN.md`, `PROGRESS.md`, `docs/HARNESS.md`, and the target `phases/{phase}/stepN.md`.
2. Confirm the step has a concrete Sprint Contract:
- Done means
- Hard thresholds
- Files owned
- Dependencies
- Acceptance commands
- Explicit Do Not list
3. If the contract is missing or vague, edit only the target step file to make the contract executable by a fresh agent.
4. Do not implement the step.
## Output
- **Target Step**
- **Contract Status**: ready | updated | blocked
- **Evaluator Thresholds**
- **Remaining Ambiguity**
+27
View File
@@ -0,0 +1,27 @@
---
description: Summarize current PDFtoMD plan, progress, blockers, and next work.
argument-hint: [optional-focus]
allowed-tools: [Read, Glob, Grep, Bash]
---
# /status
## Arguments
The user invoked this command with: $ARGUMENTS
## Workflow
1. Read `AGENTS.md`, `PLAN.md`, `PROGRESS.md`, and `docs/HARNESS.md`.
2. Summarize the current project goal, scope, completed work, in-progress work, blockers, and next work.
3. If `$ARGUMENTS` names an area, focus the summary on that area.
4. Do not modify files.
## Output
- **Goal**
- **Current State**
- **Next Work**
- **Blockers**
- **Relevant Files**
- **Active Phase/Step**