officeimo-conversion-operator
Use when contributing code that changes or validates OfficeIMO conversion behavior, especially DOCX/XLSX/PPTX/HTML/Markdown/PDF byte and stream APIs, browser-safe paths, or fidelity diagnostics. Prefer OfficeIMO core APIs first and keep hosts, websites, cmdlets, MCP tools, and demos thin.
소스 정보
- 저장소
- evotecit/officeimo
- 최근 소스 활동
- 2026년 9월 30일 21:19
- 감지된 SKILL.md 언어
- 영어
- 스타
- 565
- 포크
- 75
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- officeimo-conversion-operator
- description
- Use when contributing code that changes or validates OfficeIMO conversion behavior, especially DOCX/XLSX/PPTX/HTML/Markdown/PDF byte and stream APIs, browser-safe paths, or fidelity diagnostics. Prefer OfficeIMO core APIs first and keep hosts, websites, cmdlets, MCP tools, and demos thin.
# OfficeIMO Conversion Operator
Use this skill for OfficeIMO conversion work across Word, Excel, PowerPoint, Markdown, HTML, and PDF.
## Golden Path
1. Start by locating the owning reusable API.
- Word behavior belongs under `OfficeIMO.Word*`.
- Excel behavior belongs under `OfficeIMO.Excel*`.
- PowerPoint behavior belongs under `OfficeIMO.PowerPoint*`.
- Shared PDF behavior belongs in the PDF engine projects, not in a host wrapper.
2. Treat file paths as adapter concerns.
- Prefer byte array and stream entrypoints for conversion APIs.
- Keep browser, CLI, PowerShell, MCP, and website shells as orchestration only.
3. Validate real artifacts.
- For PDF output, at minimum verify the returned bytes start with `%PDF`.
- For browser work, validate inside a real Blazor WebAssembly runtime before calling it GitHub Pages-safe.
- For fidelity work, keep a named fixture and record the expected known gap.
4. Separate platform limits from conversion defects.
- Browser-safe means no Office automation, LibreOffice process, native graphics dependency, server filesystem dependency, or environment-only state.
- Font coverage, Unicode embedding, large memory use, and startup size are conversion quality gaps even when the browser runtime works.
5. Keep public surfaces friendly.
- Add simple options and presets at host layers only after the reusable OfficeIMO API already supports the behavior.
- Avoid hidden environment-variable switches for behavior that should be an explicit option.
## Useful Checks
```powershell
dotnet build OfficeIMO.Word.Pdf\OfficeIMO.Word.Pdf.csproj -c Release -f net10.0
dotnet test OfficeIMO.Word.Tests\OfficeIMO.Word.Tests.csproj -c Release --filter "*SaveAsPdf*"
dotnet test OfficeIMO.Html.Tests\OfficeIMO.Html.Tests.csproj -c Release --filter "*Html*"
dotnet test OfficeIMO.Markdown.Tests\OfficeIMO.Markdown.Tests.csproj -c Release --filter "*Markdown*"
```
When the work targets GitHub Pages or OfficeIMO.com, pair these with the browser conversion proof described in `Docs/officeimo.blazor-wasm-conversion-proof.md`.
GitHub에서 보기