# officecli - Doramagic AI Context Pack > Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated. ## Sufficiency Principle - **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary. - **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work. ## How the Host AI Should Use This You are reading the AI Context Pack that Doramagic compiled for officecli. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project. ## Claim Consumption Rules - **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure. - **Minimum status for a fact**: `supported` - `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path. - `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying. - `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact. - `unverified`: Must not be used as fact; state clearly that evidence is insufficient. - `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf. ## Who It Fits Best - **AI researchers or builders of research-oriented Agents**: The README clearly centers on research, experiment, or paper workflows. Evidence: `README.md` Claim: `clm_0003` supported 0.86 - **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0004` supported 0.86 - **Users who want to bring professional workflows into a host AI**: The repo contains Skill documents. Evidence: `skills/morph-ppt/SKILL.md`, `skills/morph-ppt-3d/SKILL.md`, `skills/officecli-academic-paper/SKILL.md`, `skills/officecli-data-dashboard/SKILL.md` et al. Claim: `clm_0005` supported 0.86 ## What It Can Do - **AI Skill / Agent Instruction Asset Library** (Previewable before install): The project contains Skill or Agent instruction files that a host AI can read, useful for bringing professional workflows into hosts like Claude, Codex, or Cursor. Evidence: `skills/morph-ppt/SKILL.md`, `skills/morph-ppt-3d/SKILL.md`, `skills/officecli-academic-paper/SKILL.md`, `skills/officecli-data-dashboard/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0002` supported 0.86 ## How to Start - `curl -fsSL https://officecli.ai/SKILL.md` Evidence: `README.md` Claim: `clm_0006` supported 0.86, `clm_0008` supported 0.86 - `curl -fsSL https://raw.githubusercontent.com/iOfficeAI/OfficeCLI/main/install.sh | bash` Evidence: `README.md` Claim: `clm_0007` supported 0.86 - `curl -fsSL https://officecli.ai/SKILL.md -o ~/.claude/skills/officecli.md` Evidence: `README.md` Claim: `clm_0008` supported 0.86 ## Continue-or-Stop Decision Card - **Current recommendation**: Trial the research framework first - **Why**: This project targets research workflows; the core risk is source credibility and output quality. Verify the research framework with Prompt Preview first, then trial it in an isolated environment. ### 30-Second Read - **What to do now**: Trial the research framework first - **Minimum safe next step**: Verify the research framework with Prompt Preview first; trial in isolation only once satisfied - **Do not trust yet**: Research conclusions, citations, and experiment results cannot be trusted before install. - **Continuing will touch**: Research judgment, Command execution, Host AI configuration ### What You Can Trust Now - **Target-audience signal: AI researchers or builders of research-oriented Agents** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0003` supported 0.86 - **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0004` supported 0.86 - **Target-audience signal: Users who want to bring professional workflows into a host AI** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `skills/morph-ppt/SKILL.md`, `skills/morph-ppt-3d/SKILL.md`, `skills/officecli-academic-paper/SKILL.md`, `skills/officecli-data-dashboard/SKILL.md` et al. Claim: `clm_0005` supported 0.86 - **Capability exists: AI Skill / Agent Instruction Asset Library** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `skills/morph-ppt/SKILL.md`, `skills/morph-ppt-3d/SKILL.md`, `skills/officecli-academic-paper/SKILL.md`, `skills/officecli-data-dashboard/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0002` supported 0.86 - **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0006` supported 0.86, `clm_0008` supported 0.86 ### What You Cannot Trust Yet - **Research conclusions, citations, and experiment results cannot be trusted before install.** (unverified): A research Skill can organize questions and paths, but it cannot replace real literature search, paper verification, and experiment reproduction. - **Whether it fits your specific research field cannot be trusted directly.** (unverified): The Skill covering many research topics does not mean it is sufficient for your field, source requirements, and credibility standards. - **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project. - **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment. - **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `SKILL.md`, `skills/morph-ppt-3d/SKILL.md`, `skills/morph-ppt/SKILL.md`, `skills/officecli-academic-paper/SKILL.md` et al. - **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first. - **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment. - **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. ### What Continuing Will Touch - **Research judgment**: Problem decomposition, source paths, experiment paths, conclusion structure, and credibility judgment. Why: A research Skill can make output look more professional but cannot replace real evidence verification. - **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md` - **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `SKILL.md`, `skills/morph-ppt-3d/SKILL.md`, `skills/morph-ppt/SKILL.md`, `skills/officecli-academic-paper/SKILL.md` et al. - **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `README.md` - **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts. ### Minimum Safe Next Steps - **Run Prompt Preview first**: Verify whether it can correctly frame the research question and evidence boundaries first; do not trust the research output up front. (applies when: Applies to any project, especially when output quality is unknown.) - **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.) - **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.) - **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.) ### Exit Plan - **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable. - **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state. - **Keep a source and conclusion verification checklist**: If citations or experiment paths later prove unreliable, you can return to the evidence-boundary stage and re-check. - **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually. - **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck. ## What Can Only Be Previewed - Explain who the project fits and what it can do - Demonstrate a typical conversation flow based on project docs - Help the user decide whether it is worth installing or researching further ## What Must Be Verified After Install - Actually installing the Skill, plugin, or CLI - Running scripts, modifying local files, or accessing external services - Verifying real output quality, performance, and compatibility ## Boundary & Risk Decision Card - **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0009` inferred 0.45 - **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0010` supported 0.86 - **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment. - **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. - **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments. ## Pre-Work Working Context ### Loading Order - First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset. - Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative. - Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match. - When you need to carry out a concrete task, check role_skill_index first, then evidence_index. - For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required. ### Task Routes - **AI Skill / Agent Instruction Asset Library**: Use role_skill_index / evidence_index to help the user pick a usable role, Skill, or workflow first. Boundary: Can be experienced via a pre-install Prompt. Evidence: `skills/morph-ppt/SKILL.md`, `skills/morph-ppt-3d/SKILL.md`, `skills/officecli-academic-paper/SKILL.md`, `skills/officecli-data-dashboard/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0002` supported 0.86 ### Context Scale - Total files: 984 - Important-file coverage: 40/984 - Evidence index entries: 80 - Role / Skill entries: 10 ### Handling Insufficient Evidence - **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts. - **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install. - **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run. - **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version. ## Prompt Recipes ### Fit assessment - Goal: Judge whether this project fits the user's current task. - Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation. ```text Based on the AI Context Pack for officecli, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id. ``` ### Pre-install experience - Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise. - Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language. ```text Treat officecli as a pre-install experience asset, not an already-installed tool or a real runtime environment. Output exactly four parts: 1. Ask me 3 necessary questions first. 2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow. 3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run. 4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project. Hard boundaries: - Do not claim you have installed, run, executed tests, modified files, or produced real results. - Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing". - If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...". - The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating". - Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment. - Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions. ``` ### Role / Skill selection - Goal: Pick the best-matching asset from the project's roles or Skills. - Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed. ```text Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs. ``` ### Risk pre-check - Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting. - Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items. ```text Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have. ``` ### Host AI kickoff instruction - Goal: Turn the project context into a host AI instruction for the start of a conversation. - Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI. ```text Based on the AI Context Pack for officecli, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results. ``` ## Role / Skill Index - Indexed 10 role / Skill / project-doc entries. - **morph-ppt-3d** (skill): 3D Morph PPT — extends morph-ppt with GLB model insertion, cinematographic camera, model-content layout, and enriched visual design system. Activation hint: When the user's task is highly relevant to the workflow described by “morph-ppt-3d”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/morph-ppt-3d/SKILL.md` - **morph-ppt** (skill): Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style continuous motion, shapes that grow / move / rotate as the slide advances. Trigger on: 'morph', 'morph transition', 'smooth transition', 'continuous animation across slides', 'Keynote-style transition', 'animated slide sequence', 'shape continuity across slides'. Output is a single .pptx. This s… Activation hint: When the user's task is highly relevant to the workflow described by “morph-ppt”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/morph-ppt/SKILL.md` - **officecli-academic-paper** (skill): Use this skill to build academic-style .docx output: journal / conference / thesis chapters carrying formal citation style APA, Chicago, IEEE, MLA , numbered equations, figure & table cross-references, footnotes/endnotes, bibliography, or multi-column journal layout. Trigger on: 'research paper', 'journal paper', 'conference paper', 'manuscript', 'thesis', 'APA', 'MLA', 'Chicago', 'IEEE two-column', 'bibliography',… Activation hint: When the user's task is highly relevant to the workflow described by “officecli-academic-paper”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/officecli-academic-paper/SKILL.md` - **officecli-data-dashboard** (skill): Use this skill to build a multi-element Excel dashboard — Dashboard sheet on open, multiple formula-driven KPI cards, multiple charts, sparklines, and conditional formatting — from CSV or tabular input. Trigger on: 'dashboard', 'KPI dashboard', 'analytics dashboard', 'executive dashboard', 'metrics dashboard', 'CSV to dashboard', 'data visualization'. Output is a single .xlsx. Scene-layer on officecli-xlsx: inherits… Activation hint: When the user's task is highly relevant to the workflow described by “officecli-data-dashboard”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/officecli-data-dashboard/SKILL.md` - **officecli-docx** (skill): Use this skill any time a .docx file is involved -- as input, output, or both. This includes: creating Word documents, reports, letters, memos, or proposals; reading, parsing, or extracting text from any .docx file; editing, modifying, or updating existing documents; working with templates, tracked changes, comments, headers/footers, or tables of contents. Trigger whenever the user mentions 'Word doc', 'document', '… Activation hint: When the user's task is highly relevant to the workflow described by “officecli-docx”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/officecli-docx/SKILL.md` - **officecli-financial-model** (skill): Use this skill when the user wants to build a financial model — 3-statement model, DCF valuation, LBO, SaaS unit economics, sensitivity / scenario analysis, debt schedule, or fundraising projections — in Excel. Trigger on: 'financial model', '3-statement model', 'P&L + BS + CF', 'DCF', 'WACC', 'NPV', 'terminal value', 'LBO', 'debt schedule', 'cash sweep', 'MOIC', 'IRR / XIRR', 'sensitivity table', 'scenario analysis… Activation hint: When the user's task is highly relevant to the workflow described by “officecli-financial-model”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/officecli-financial-model/SKILL.md` - **officecli-pitch-deck** (skill): Use this skill when the user is building a fundraising / investor pitch deck — seed, Series A / B / C, convertible note, SAFE round, strategic raise. Trigger on: 'pitch deck', 'investor deck', 'Series A deck', 'Series B deck', 'Series C deck', 'fundraising deck', 'seed pitch', 'VC deck', 'raising capital', 'term sheet presentation'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inh… Activation hint: When the user's task is highly relevant to the workflow described by “officecli-pitch-deck”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/officecli-pitch-deck/SKILL.md` - **officecli-pptx** (skill): Use this skill any time a .pptx file is involved -- as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file; editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions 'deck', 'slides', 'present… Activation hint: When the user's task is highly relevant to the workflow described by “officecli-pptx”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/officecli-pptx/SKILL.md` - **officecli-word-form** (skill): Use this skill to create fillable Word forms .docx with real Content Controls SDT + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection. Trigger on: 'fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'only editable fields', 'protect document', 'onboarding form', 'HR intake', 'survey template', 'contract / SOW template', 'mail-merge template', 'compli… Activation hint: When the user's task is highly relevant to the workflow described by “officecli-word-form”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/officecli-word-form/SKILL.md` - **officecli-xlsx** (skill): Use this skill any time a .xlsx file is involved -- as input, output, or both. This includes: creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data from any .xlsx file; editing, modifying, or updating existing workbooks; working with formulas, charts, pivot tables, or templates; importing CSV/TSV data into Excel format. Trigger whenever the user mentions 'spreadsheet'… Activation hint: When the user's task is highly relevant to the workflow described by “officecli-xlsx”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/officecli-xlsx/SKILL.md` ## Evidence Index - Indexed 80 evidence entries. - **OfficeCLI** (documentation): OfficeCLI is the world's first and the best Office suite designed for AI agents. Evidence: `README.md` - **OfficeCLI Examples** (documentation): Comprehensive examples demonstrating OfficeCLI capabilities for Word, Excel, and PowerPoint automation. Evidence: `examples/README.md` - **officecli** (documentation): CLI for reading and writing Office documents .docx , .xlsx , .pptx via a document DOM API. Evidence: `npm/README.md` - **schemas/** (documentation): Agent-facing capability schemas for officecli. Single source of truth for what the CLI supports, consumed in three places: Evidence: `schemas/README.md` - **PowerPoint Style Templates** (documentation): Professional presentation style templates for OfficeCLI. Each style includes a pre-generated .pptx file and reference build script. Evidence: `examples/ppt/templates/README.md` - **@officecli/sdk** (documentation): A thin async Node.js client over officecli https://github.com/iOfficeAI/OfficeCLI 's resident pipe. It does one thing: forward a command to the running resident and hand back the response. There is no second vocabulary to learn — a command is the same object you'd put in an officecli batch list. Evidence: `sdk/node/README.md` - **officecli — Python SDK** (documentation): A thin Python SDK for the officecli https://officecli.ai resident pipe . It does one thing: forward an officecli command to a running resident over its named pipe and hand back the response — no per-command process spawn, so a loop of edits is ~hundreds of times faster than shelling out to the CLI per command. Evidence: `sdk/python/README.md` - **Package** (package_manifest): { "name": "@officecli/officecli", "version": "1.0.123", "description": "OfficeCLI — CLI for reading and writing Office documents .docx, .xlsx, .pptx via a document DOM API. The native binary is fetched on install for your platform.", "license": "Apache-2.0", "author": "goworm", "homepage": "https://github.com/iOfficeAI/OfficeCLI", "repository": { "type": "git", "url": "git+https://github.com/iOfficeAI/OfficeCLI.git" }, "bugs": { "url": "https://github.com/iOfficeAI/OfficeCLI/issues" }, "keywords": "office", "docx", "xlsx", "pptx", "word", "excel", "powerpoint", "ooxml", "cli" , "bin": { "officecli": "officecli.js" }, "main": "lib/install-binary.js", "exports": { ".": "./lib/install-binary.j… Evidence: `npm/package.json` - **Contributing to OfficeCLI** (documentation): 中文版 / Chinese version: CONTRIBUTING.zh.md ./CONTRIBUTING.zh.md Evidence: `CONTRIBUTING.md` - **officecli** (skill_instruction): AI-friendly CLI for .docx, .xlsx, .pptx. Single binary, no dependencies, no Office installation needed. Evidence: `SKILL.md` - **Package** (package_manifest): { "name": "@officecli/sdk", "version": "0.1.2", "description": "Node.js SDK for officecli — a thin async client over the officecli resident pipe read/write .docx/.xlsx/.pptx .", "license": "Apache-2.0", "author": "goworm", "homepage": "https://github.com/iOfficeAI/OfficeCLI/tree/main/sdk/node", "repository": { "type": "git", "url": "git+https://github.com/iOfficeAI/OfficeCLI.git", "directory": "sdk/node" }, "bugs": { "url": "https://github.com/iOfficeAI/OfficeCLI/issues" }, "keywords": "officecli", "office", "docx", "xlsx", "pptx", "word", "excel", "powerpoint", "ooxml", "sdk" , "main": "index.js", "types": "index.d.ts", "files": "index.js", "index.d.ts", "README.md" , "engines": { "node":… Evidence: `sdk/node/package.json` - **Morph PPT — 3D Extension** (skill_instruction): This skill extends morph-ppt . All morph-ppt rules naming, ghosting, design, verification apply in full. This file covers 3D-specific additions and an enriched design system combining morph-ppt aesthetics with concrete color palettes, font pairings, and layout quality guardrails. Evidence: `skills/morph-ppt-3d/SKILL.md` - **OfficeCLI Morph-PPT Skill** (skill_instruction): This skill is a scene layer on top of officecli-pptx . Every pptx hard rule — visual delivery floor title ≥ 36pt / body ≥ 18pt / title ≥ 2× body , 12-column grid on 33.87×19.05cm, canonical palettes, chart-choice decision table, connector canon, shell escape, resident + batch, Delivery Gate 1–5a — is inherited, not re-taught. This file adds only what Morph needs on top: cross-slide shape-name binding, Scene Actors vs content prefixing, ghost discipline, transition=morph CLI quirks, 52-style visual library lookup, and a morph-specific fresh-eyes Gate 5b extension. Evidence: `skills/morph-ppt/SKILL.md` - **OfficeCLI Academic Paper Skill** (skill_instruction): This skill is a scene layer on top of officecli-docx . Every docx hard rule — style architecture, heading hierarchy, shell quoting, break=newPage alias, belt-and-suspenders page breaks, live PAGE field, Delivery Gate, renderer quirks — is inherited, not re-taught. This file adds only what academic papers need on top: citation styles, equations, SEQ / PAGEREF cross-refs, multi-column journal layout, bibliography hanging indent, abstract/keywords/affiliation block. Evidence: `skills/officecli-academic-paper/SKILL.md` - **Data Dashboard scene-layer on officecli-xlsx** (skill_instruction): Data Dashboard scene-layer on officecli-xlsx Evidence: `skills/officecli-data-dashboard/SKILL.md` - **OfficeCLI DOCX Skill** (skill_instruction): - macOS / Linux : curl -fsSL https://d.officecli.ai/install.sh bash - Windows PowerShell : irm https://d.officecli.ai/install.ps1 iex Evidence: `skills/officecli-docx/SKILL.md` - **OfficeCLI Financial-Model Skill** (skill_instruction): This skill is a scene layer on top of officecli-xlsx . Every xlsx hard rule — shell quoting, incremental execution, Help-First Rule, visual delivery floor, CFO 4-color code blue input / black formula / green cross-sheet / yellow-fill assumption , number-format standards years as text, zero as - , % one decimal, negatives in parens , assumption-cell discipline, CSV batch import, chart data-feed forms a/b/c , the 5-gate Delivery cycle, cache-drift guidance, Known Issues the cross-sheet ! trap, batch + resident for formulas, renderer caveats — is inherited, not re-taught . This file adds only what a financial model requires on top: three-zone architecture, 3 model-type recipes 3-statement / DC… Evidence: `skills/officecli-financial-model/SKILL.md` - **OfficeCLI Pitch Deck Skill** (skill_instruction): This skill is a scene layer on top of officecli-pptx . Every pptx hard rule — visual delivery floor title ≥ 36pt / body ≥ 18pt / title ≥ 2× body , 12-column grid on 33.87×19.05cm, 4 canonical palettes, chart-choice decision table, connector canon shape / from / to / tailEnd=triangle , shell escape, resident + batch, Delivery Gate 1–5a — is inherited, not re-taught. This file adds only what fundraising needs on top: stage diagnosis A / B / C , 5 赛道 arc templates, 10 key-slide recipes cover / problem / solution / market / product / model / traction / team / financials / ask , pitch-specific numbers convention, a VC ship-check, and a pitch-specific fresh-eyes Gate 6. Evidence: `skills/officecli-pitch-deck/SKILL.md` - **OfficeCLI PPTX Skill** (skill_instruction): - macOS / Linux : curl -fsSL https://d.officecli.ai/install.sh bash - Windows PowerShell : irm https://d.officecli.ai/install.ps1 iex Evidence: `skills/officecli-pptx/SKILL.md` - **OfficeCLI Word-Form Skill** (skill_instruction): This skill is INDEPENDENT, not a scene layer on docx. A form's payload — controls, legacy fields, mail-merge, documentProtection — is a distinct element class from docx's paragraph/heading/style primitives. Its QA is different too: docx's Delivery Gate cares about visual layout and live PAGE fields, this skill's cares about data plumbing protection enforced / alias+tag / items injected / name ≤ 20 / no underscore anti-pattern . Reverse handoff: if the user's document has no fillable fields report, letter, memo, thesis, proposal , route to officecli-docx or a docx scene skill — don't use this one. Evidence: `skills/officecli-word-form/SKILL.md` - **OfficeCLI XLSX Skill** (skill_instruction): - macOS / Linux : curl -fsSL https://d.officecli.ai/install.sh bash - Windows PowerShell : irm https://d.officecli.ai/install.ps1 iex Evidence: `skills/officecli-xlsx/SKILL.md` - **License** (source_file): Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ Evidence: `LICENSE` - **Build** (source_file): set -e PROJECT="src/officecli/officecli.csproj" ALL TARGETS="osx-arm64:officecli-mac-arm64 osx-x64:officecli-mac-x64 linux-x64:officecli-linux-x64 linux-arm64:officecli-linux-arm64 linux-musl-x64:officecli-linux-alpine-x64 linux-musl-arm64:officecli-linux-alpine-arm64 win-x64:officecli-win-x64.exe win-arm64:officecli-win-arm64.exe" detect local rid { local OS=$ uname -s tr ' :upper: ' ' :lower: ' local ARCH=$ uname -m local LIBC="gnu" if "$OS" = "linux" ; then if command -v ldd /dev/null 2 &1 && ldd --version 2 &1 grep -qi musl; then LIBC="musl" elif -f /etc/alpine-release ; then LIBC="musl" fi fi case "$OS" in darwin case "$ARCH" in arm64 echo "osx-arm64" ;; x86 64 echo "osx-x64" ;; esac ;… Evidence: `build.sh` - **Dev Install** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "$0" " && pwd " PROJECT="$SCRIPT DIR/src/officecli/officecli.csproj" BINARY NAME="officecli" OS=$ uname -s tr ' :upper: ' ' :lower: ' ARCH=$ uname -m case "$OS" in darwin case "$ARCH" in arm64 RID="osx-arm64" ;; x86 64 RID="osx-x64" ;; echo "Unsupported architecture: $ARCH"; exit 1 ;; esac ;; linux LIBC="gnu" if command -v ldd /dev/null 2 &1 && ldd --version 2 &1 grep -qi musl; then LIBC="musl" elif -f /etc/alpine-release ; then LIBC="musl" fi case "$ARCH" in x86 64 if "$LIBC" = "musl" ; then RID="linux-musl-x64"; else RID="linux-x64"; fi ;; aarch64 arm64 if "$LIBC" = "musl" ; then RID="linux-musl-arm64"; else RID="linux-arm64"; fi ;; echo "Unsupported arc… Evidence: `dev-install.sh` - **Resolve the latest tag up-front so we download from the IMMUTABLE versioned** (source_file): set -e REPO="iOfficeAI/OfficeCLI" BINARY NAME="officecli" MIRROR BASE="https://d.officecli.ai" GITHUB RELEASE BASE="https://github.com/$REPO/releases/latest/download" GITHUB RAW BASE="https://raw.githubusercontent.com/$REPO/main" fetch with fallback { local primary="$1" fallback="$2" out="$3" if curl -fsSL --max-time 300 --connect-timeout 5 "$primary" -o "$out" 2 /dev/null; then echo " via mirror " return 0 fi echo " mirror unreachable, falling back to github..." curl -fsSL --max-time 300 "$fallback" -o "$out" 2 /dev/null } resolve version { local url url=$ curl -fsSL --max-time 30 --connect-timeout 5 -o /dev/null -w '%{url effective}' \ "$MIRROR BASE/releases/latest" 2 /dev/null case "$url… Evidence: `install.sh` - **Officecli** (source_file): Evidence: `officecli.slnx` - **Build** (source_file): rm -f "AURA COFFEE.pptx" officecli create "AURA COFFEE.pptx" python3 - << 'PYEOF' import json import sys commands = def add slide idx, transition="none" : commands.append { "command": "add", "parent": "/", "type": "slide", "props": { "background": "111111", "transition": transition } } def add shape slide idx, name, props : base props = {"name": name, "preset": "rect", "fill": "none", "line": "none", "font": "Helvetica"} base props.update props commands.append { "command": "add", "parent": f"/slide {slide idx} ", "type": "shape", "props": base props } ACTOR TEXTS = { "!!brand-title": "AURA COFFEE", "!!brand-sub": "纯 粹 之 境 极简高级精品咖啡", "!!statement-main": "少即是多，剥离繁杂，只为一杯纯粹好咖啡。", "!!statement-s… Evidence: `examples/ppt/templates/styles/brand--aura-coffee-dark/build.sh` - **Build** (source_file): set -e FILE="aura coffee.pptx" echo "Creating PPT..." officecli create "$FILE" officecli add "$FILE" '/' --type slide --prop layout=blank --prop background=F9F6F0 echo "Building Slide 1..." cat s1.json {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"!!bg-main","preset":"ellipse","fill":"F3EFE6","x":"15cm","y":"0cm","width":"25cm","height":"25cm","line":"none"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"!!circle-accent","preset":"ellipse","fill":"C2A878","x":"5cm","y":"14cm","width":"2cm","height":"2cm","line":"none"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"!!line-top","preset":"rect","fill":"2B2624","x":"0cm"… Evidence: `examples/ppt/templates/styles/brand--aura-coffee/build.sh` - **Build** (source_file): set -e FILE="未来已来 2050.pptx" echo "Creating PPT: $FILE" officecli create "$FILE" echo "Setting up Slide 1..." officecli add "$FILE" '/' --type slide --prop layout=blank --prop background=0B0C10 officecli add "$FILE" '/slide 1 ' --type shape --prop name="!!bg-orb" --prop preset=ellipse --prop fill=66FCF1 --prop opacity=0.08 --prop x=0cm --prop y=0cm --prop width=20cm --prop height=20cm officecli add "$FILE" '/slide 1 ' --type shape --prop name="!!bg-box" --prop preset=rect --prop fill=1F2833 --prop opacity=0.3 --prop x=2cm --prop y=2cm --prop width=8cm --prop height=15cm officecli add "$FILE" '/slide 1 ' --type shape --prop name="!!accent-line" --prop preset=rect --prop fill=66FCF1 --prop x=… Evidence: `examples/ppt/templates/styles/future--2050-vision/build.sh` - **Build** (source_file): set -e FILE="cat philosophy.pptx" echo "Creating PPTX: $FILE" officecli create "$FILE" echo "Adding Slide 1 hero ..." officecli add "$FILE" '/' --type slide --prop layout=blank --prop background=FFF9E6 echo ' {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"circle-main","preset":"ellipse","fill":"FF8A4C","x":"18cm","y":"3cm","width":"18cm","height":"18cm","opacity":"1.0"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"circle-sub","preset":"ellipse","fill":"FFC533","x":"26cm","y":"12cm","width":"10cm","height":"10cm","opacity":"1.0"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"round-box","preset":"roundRect","fill":"FF… Evidence: `examples/ppt/templates/styles/lifestyle--cat-philosophy/build.sh` - **Build** (source_file): set -e PPT FILE="Cat-Secret-Life.pptx" FONT MAIN="思源黑体" FONT TITLE="Montserrat" BG COLOR="FFF8E7" TEXT DARK="3D3B3C" TEXT LIGHT="FFFFFF" C ORANGE="FF8A65" C YELLOW="FFD54F" C TEAL="4DB6AC" C DARK="3D3B3C" echo "Creating PPT and Slide 1..." officecli create "$PPT FILE" officecli add "$PPT FILE" '/' --type slide --prop layout=blank --prop background="$BG COLOR" officecli add "$PPT FILE" '/slide 1 ' --type shape --prop name="blob-main" --prop preset=roundRect --prop fill="$C ORANGE" --prop opacity=0.15 --prop x=18cm --prop y=5cm --prop width=20cm --prop height=15cm --prop rotation=15 officecli add "$PPT FILE" '/slide 1 ' --type shape --prop name="dot-orange" --prop preset=ellipse --prop fill="… Evidence: `examples/ppt/templates/styles/lifestyle--cat-secret-life/build.sh` - **Build** (source_file): set -e OUTPUT="TimeTravel.pptx" echo "Creating $OUTPUT ..." officecli create "$OUTPUT" for i in 1 2 3 4 5 6; do officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=0B0F19 done FONT EN="Montserrat" FONT CN="Microsoft YaHei" COLOR TEXT="FFFFFF" COLOR SUB="8B949E" COLOR ACCENT="58A6FF" COLOR ACCENT2="7C3AED" COLOR DARK="161B22" officecli add "$OUTPUT" '/slide 1 ' --type shape --name="scene-circle" --prop preset=ellipse \ --prop fill=$COLOR ACCENT2 --prop opacity=0.15 --prop softEdge=60 \ --prop x=18cm --prop y=4cm --prop width=15cm --prop height=15cm officecli add "$OUTPUT" '/slide 1 ' --type shape --name="scene-slash" --prop preset=diamond \ --prop fill=$COLOR ACCEN… Evidence: `examples/ppt/templates/styles/product--geminicli-timetravel/build.sh` - **Build** (source_file): set -euo pipefail OUT="注意力预算-把手机时间变成创造时间.pptx" rm -f "$OUT" officecli create "$OUT" officecli add "$OUT" '/' --type slide --prop layout=blank --prop background=0B0F1A --prop transition=morph cat <<'JSON' officecli batch "$OUT" {"command":"set","path":"/slide 1 ","props":{"transition":"morph","background":"0B0F1A"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"bg-blob-1","preset":"ellipse","fill":"2BE4A8","opacity":"0.10","x":"0cm","y":"0cm","width":"14cm","height":"14cm"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"bg-blob-2","preset":"ellipse","fill":"FFB020","opacity":"0.08","x":"22cm","y":"9.8cm","width":"12cm","height":"12cm"}}, {"co… Evidence: `examples/ppt/templates/styles/productivity--attention-budget/build.sh` - **Build** (source_file): set +H set -e F="Alien Guide.pptx" echo "Building $F..." rm -f "$F" officecli create "$F" BG="0B0C10" CYAN="66FCF1" TEAL="45A29E" WHITE="FFFFFF" GRAY="C5C6C7" DARK="1F2833" a { officecli add "$F" "$1" --type shape "${@:2}"; } sl { officecli add "$F" / --type slide "$@"; } scene actors { local s="$1" local c x="$2" c y="$3" c w="$4" c o="$5" local r x="$6" r y="$7" r w="$8" r h="$9" r o="${10}" local a1 x="${11}" a1 y="${12}" local a2 x="${13}" a2 y="${14}" local lt x="${15}" lt y="${16}" lt w="${17}" local lb x="${18}" lb y="${19}" lb w="${20}" a "$s" --prop name="!!bg-circ" --prop preset=ellipse --prop x="${c x}cm" --prop y="${c y}cm" --prop width="${c w}cm" --prop height="${c w}cm" --prop… Evidence: `examples/ppt/templates/styles/science--alien-guide/build.sh` - **Build** (source_file): set -e FILENAME="太空探索历程.pptx" echo "Building $FILENAME..." -f "$FILENAME" && rm "$FILENAME" officecli create "$FILENAME" echo "Creating Slide 1: Hero..." cat << 'BATCH EOF' officecli batch "$FILENAME" {"command":"add","parent":"/","type":"slide","props":{"layout":"blank","background":"0A0E27"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"planet-main","preset":"ellipse","fill":"1E3A5F","opacity":"0.3","width":"12cm","height":"12cm","x":"24cm","y":"8cm"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"glow-accent","preset":"ellipse","fill":"4A5FFF","opacity":"0.08","width":"18cm","height":"18cm","x":"21cm","y":"5cm"}}, {"command":"add","paren… Evidence: `examples/ppt/templates/styles/science--space-exploration/build.sh` - **Build** (source_file): set -e cat build internal.py import json import os import subprocess file name = "Time Travel.pptx" def run batch name, batch data : with open f"{name}.json", "w", encoding="utf-8" as f: json.dump batch data, f subprocess.run f"cat {name}.json officecli batch {file name}", shell=True, check=True subprocess.run "officecli", "create", file name , check=True subprocess.run "officecli", "add", file name, "/", "--type", "slide", "--prop", "layout=blank", "--prop", "background=050510" , check=True slide1 = {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"!!bg-glow1","preset":"ellipse","fill":"8A2BE2","opacity":"0.15","x":"0cm","y":"0cm","width":"15cm","height":"15cm"}}, {"com… Evidence: `examples/ppt/templates/styles/science--time-travel/build.sh` - **Build** (source_file): set -e FILENAME="野生动物科技公司.pptx" echo "Creating PPT: $FILENAME" officecli create "$FILENAME" officecli add "$FILENAME" '/' --type slide --prop layout=blank --prop background=FFF8F0 cat << 'EOF' officecli batch "$FILENAME" { "command": "add", "parent": "/slide 1 ", "type": "shape", "props": { "name": "dot-accent1", "preset": "ellipse", "fill": "FF8C42", "opacity": "0.12", "x": "28cm", "y": "2cm", "width": "7cm", "height": "7cm" } }, { "command": "add", "parent": "/slide 1 ", "type": "shape", "props": { "name": "dot-accent2", "preset": "ellipse", "fill": "FFD166", "opacity": "0.15", "x": "2cm", "y": "13cm", "width": "5cm", "height": "5cm" } }, { "command": "add", "parent": "/slide 1 ", "type":… Evidence: `examples/ppt/templates/styles/tech--wildlife-company/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/bw brutalist raw.pptx" echo "Building: bw--brutalist-raw Brutalist Design " rm -f "$OUTPUT" officecli create "$OUTPUT" WHITE=FFFFFF BLACK=000000 RED=FF0000 echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$WHITE officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!border-box' \ --prop preset=rect \ --prop fill=$WHITE \ --prop line=$BLACK \ --prop lineWidth=3pt \ --prop x=20cm --prop y=2cm --prop width=10cm --prop height=8cm officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!block-solid' \ --prop preset=rect \ --prop… Evidence: `skills/morph-ppt/reference/styles/bw--brutalist-raw/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/bw mono line.pptx" echo "Building: bw--mono-line Minimalist Lines " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=FFFFFF BLACK=1A1A1A GRAY=C8C8C8 OFFSCREEN=36cm echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!line-h-top' \ --prop preset=rect \ --prop fill=$BLACK \ --prop x=0cm --prop y=1.5cm --prop width=20cm --prop height=0.05cm officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!line-h-mid' \ --prop preset=rect \ --prop fill=$GRAY \ --prop x=10cm --prop y=13c… Evidence: `skills/morph-ppt/reference/styles/bw--mono-line/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/bw swiss bauhaus.pptx" echo "Building: bw--swiss-bauhaus Swiss/Bauhaus Design " rm -f "$OUTPUT" officecli create "$OUTPUT" RED=E63322 BLACK=1C1C1C OFFWHITE=F5F5F5 echo "Building Slide 1: Cover..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$OFFWHITE officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!blk-a' \ --prop fill=$RED \ --prop x=0cm --prop y=0cm --prop width=14cm --prop height=19.05cm officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!blk-b' \ --prop fill=$BLACK \ --prop x=14cm --prop y=14cm --prop width=19.87cm --prop height=5.05cm o… Evidence: `skills/morph-ppt/reference/styles/bw--swiss-bauhaus/build.sh` - **Build** (source_file): set +H set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " F="$SCRIPT DIR/dark architectural plan.pptx" WHITE="FFFFFF" DARK="18293B" PANEL="B5D5E3" IMG1="4F92B0" YELLOW="F0BE3C" YLW LT="FEF0C0" GRAY="4A5B68" LGRAY="8BA0AE" CARD="EAF4FA" CARD B="BDD8E6" PILL="E3F1F8" FOOT="DAE9F0" a { officecli add "$F" "$1" --type shape "${@:2}"; } c { officecli add "$F" "$1" --type connector "${@:2}"; } sl { officecli add "$F" / --type slide "${@}"; } echo "Building $F..." rm -f "$F" officecli create "$F" dots { local path=$1 cur=$2 local xs= 14.03 14.83 15.63 16.43 17.23 18.03 for i in 1 2 3 4 5 6; do local x="${xs $ i-1 }" local fill; "$i" -eq "$cur" && fill=$DARK fill="C8DDED" a "$path" --… Evidence: `skills/morph-ppt/reference/styles/dark--architectural-plan/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/dark blueprint grid.pptx" echo "Building: dark--blueprint-grid AI Agent Platform " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=1B3A5C BLUE=4A90D9 WHITE=FFFFFF LIGHT BLUE=B8D0E8 OVERLAY=2C5F8A echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!grid-h1' \ --prop fill=$WHITE \ --prop opacity=0.25 \ --prop x=0cm --prop y=4cm --prop width=34cm --prop height=0.02cm officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!grid-h2' \ --prop fill=$WHITE \ --prop opacity=0.25… Evidence: `skills/morph-ppt/reference/styles/dark--blueprint-grid/build.sh` - **Thin green ring on circle** (source_file): set +H set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " F="$SCRIPT DIR/dark circle digital.pptx" BG="0D0E11" D2="171A20" D3="22252E" D4="2D3140" GREEN="C4FF00" GREEN D="8AAF00" WHITE="FFFFFF" LGRAY="6A7888" MGRAY="3C404C" C LEAF="1F6B38" C ART="7A2055" C TEAL="1A6070" C PURP="42257A" C WARM="7A4018" C SKY="1A3870" C ROOM="2A3540" C PERS="4A5560" a { officecli add "$F" "$1" --type shape "${@:2}"; } c { officecli add "$F" "$1" --type connector "${@:2}"; } sl { officecli add "$F" / --type slide "${@}"; } circ { a "$1" --prop "name=$2" --prop preset=ellipse \ --prop x="${3}cm" --prop y="${4}cm" \ --prop width="${5}cm" --prop height="${5}cm" \ --prop fill=$6 --prop line=none \ -… Evidence: `skills/morph-ppt/reference/styles/dark--circle-digital/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/dark cosmic neon.pptx" echo "Building: dark--cosmic-neon Cosmic Neon Sci-Fi " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=050510 PURPLE=8A2BE2 CYAN=00FFFF CARD=111122 WHITE=FFFFFF GRAY1=AAAAAA GRAY2=CCCCCC OFFSCREEN=36cm echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!bg-glow1' \ --prop preset=ellipse \ --prop fill=$PURPLE \ --prop opacity=0.15 \ --prop x=0cm --prop y=0cm --prop width=15cm --prop height=15cm officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!… Evidence: `skills/morph-ppt/reference/styles/dark--cosmic-neon/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/dark cyber future.pptx" echo "Building: dark--cyber-future 未来已来：2050 " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=0B0C10 CYAN=66FCF1 GRAY=1F2833 TEAL=45A29E WHITE=FFFFFF GRAY2=C5C6C7 OFFSCREEN=36cm echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!bg-orb' \ --prop preset=ellipse \ --prop fill=$CYAN \ --prop opacity=0.08 \ --prop x=0cm --prop y=0cm --prop width=20cm --prop height=20cm officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!bg-box' \ --prop fill=$GR… Evidence: `skills/morph-ppt/reference/styles/dark--cyber-future/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/dark diagonal cut.pptx" echo "Building: dark--diagonal-cut Industrial Design " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=1A1A1A ORANGE=FF6600 YELLOW=FFCC00 WHITE=FFFFFF GRAY=333333 LIGHT GRAY=CCCCCC OFFSCREEN=36cm echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!slash-orange' \ --prop preset=rect \ --prop fill=$ORANGE \ --prop opacity=0.9 \ --prop x=0cm --prop y=2cm --prop width=30cm --prop height=6cm --prop rotation=35 officecli add "$OUTPUT" '/slide 1 ' --type shape \ -… Evidence: `skills/morph-ppt/reference/styles/dark--diagonal-cut/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/dark editorial story.pptx" echo "Building: dark--editorial-story Editorial Magazine " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=FFFFFF DARK=2C3E50 RED=E74C3C GRAY BG=F5F5F5 TEXT DARK=2D3436 TEXT GRAY=666666 TEXT LIGHT=999999 OFFSCREEN=36cm echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!ellipse-1' \ --prop preset=ellipse \ --prop fill=$RED \ --prop opacity=0.08 \ --prop x=24cm --prop y=8cm --prop width=8cm --prop height=8cm officecli add "$OUTPUT" '/slide 1 ' --type shap… Evidence: `skills/morph-ppt/reference/styles/dark--editorial-story/build.sh` - **Build** (source_file): set -e OUTPUT="template.pptx" echo "Creating $OUTPUT ..." officecli create "$OUTPUT" for i in 1 2 3 4 5 6; do officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=1A1A2E done echo "Created 6 slides" echo "Building Slide 1..." officecli add "$OUTPUT" '/slide 1 ' --type shape --prop preset=rect --prop fill=0F3460 --prop opacity=0.3 --prop x=0cm --prop y=0cm --prop width=10cm --prop height=19.05cm officecli add "$OUTPUT" '/slide 1 ' --type shape --prop preset=rect --prop fill=16213E --prop opacity=0.5 --prop x=26cm --prop y=0cm --prop width=7.87cm --prop height=8cm officecli add "$OUTPUT" '/slide 1 ' --type shape --prop preset=rect --prop fill=E94560 --prop opacity=0.… Evidence: `skills/morph-ppt/reference/styles/dark--investor-pitch/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/dark liquid flow.pptx" echo "Building: dark--liquid-flow LUXE Brand Visual Upgrade " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=0F0F2D VIOLET=6C63FF MINT=48E5C2 CORAL=FF6B8A EBLUE=3D5AFE AMBER=F5AF19 TITLE=F5F5FF BODY=C8C8FF MUTED=8888CC OFFSCREEN=36cm echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!blob-1' \ --prop preset=ellipse \ --prop fill=$VIOLET \ --prop opacity=0.35 \ --prop rotation=15 \ --prop x=2cm --prop y=3cm --prop width=12cm --prop height=8cm officecli add… Evidence: `skills/morph-ppt/reference/styles/dark--liquid-flow/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/dark luxury minimal.pptx" echo "Building: dark--luxury-minimal AURA COFFEE " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=111111 GOLD=D4AF37 WHITE=FFFFFF GRAY1=888888 GRAY2=555555 GRAY3=333333 GRAY4=CCCCCC OFFSCREEN=36cm echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!deco-line' \ --prop fill=$GOLD \ --prop x=4cm --prop y=8.5cm --prop width=2cm --prop height=0.1cm officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!brand-title' \ --prop text="AURA COFFEE" \ --… Evidence: `skills/morph-ppt/reference/styles/dark--luxury-minimal/build.sh` - **Build** (source_file): set -euo pipefail SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUT="$SCRIPT DIR/dark neon productivity.pptx" echo "Building: dark--neon-productivity 注意力预算 " rm -f "$OUT" officecli create "$OUT" officecli add "$OUT" '/' --type slide --prop layout=blank --prop background=0B0F1A --prop transition=morph cat <<'JSON' officecli batch "$OUT" {"command":"set","path":"/slide 1 ","props":{"transition":"morph","background":"0B0F1A"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"bg-blob-1","preset":"ellipse","fill":"2BE4A8","opacity":"0.10","x":"0cm","y":"0cm","width":"14cm","height":"14cm"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{"name":"… Evidence: `skills/morph-ppt/reference/styles/dark--neon-productivity/build.sh` - **Show pillar cards** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/dark premium navy.pptx" echo "Building: dark--premium-navy Annual Strategy Review " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=0C1B33 GOLD=C9A84C NAVY=1E3A5F STEEL=8EACC1 WHITE=FFFFFF NAVY2=2C4F7C GRAY=5A7A9A OFFSCREEN=36cm echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!bar-gold' \ --prop fill=$GOLD \ --prop x=7.9cm --prop y=11.5cm --prop width=18cm --prop height=0.08cm officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!bar-navy' \ --prop fill=$NAVY \ --pr… Evidence: `skills/morph-ppt/reference/styles/dark--premium-navy/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/dark space odyssey.pptx" echo "Building: dark--space-odyssey 太空探索历程 " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=0A0E27 PLANET=1E3A5F GLOW=4A5FFF GOLD=FFD700 WHITE=FFFFFF BLUE=4A90E2 CYAN=00D9FF ORANGE=F5A623 RED=D84315 MARS RED=FF5722 MARS ORANGE=FF6B35 PURPLE=9B59B6 PURPLE DARK=8E44AD LIGHT BLUE=3498DB TEXT GRAY=B8C5D6 TEXT LIGHT=D0D8E5 TEXT BRIGHT=E5EAF3 OFFSCREEN=36cm echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!planet-main' \ --prop preset=ellipse \ --prop fill=$P… Evidence: `skills/morph-ppt/reference/styles/dark--space-odyssey/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " DECK="$SCRIPT DIR/dark spotlight stage.pptx" rm -f "$DECK" officecli create "$DECK" officecli add "$DECK" '/' --type slide --prop layout=blank --prop background=0A0A0A cat <<'BATCH' officecli batch "$DECK" {"command":"add","parent":"/slide 1 ","type":"shape","props":{ "name":"spotlight","preset":"ellipse","fill":"FFFFFF","opacity":"0.12", "x":"9cm","y":"1.5cm","width":"16cm","height":"16cm"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{ "name":"warm-glow","preset":"ellipse","fill":"FFE0B2","opacity":"0.06", "x":"11cm","y":"3.5cm","width":"12cm","height":"12cm"}}, {"command":"add","parent":"/slide 1 ","type"… Evidence: `skills/morph-ppt/reference/styles/dark--spotlight-stage/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " DECK="$SCRIPT DIR/light bold type.pptx" rm -f "$DECK" officecli create "$DECK" && \ officecli add "$DECK" '/' --type slide --prop layout=blank --prop background=F2F2F2 echo ' {"command":"add","parent":"/slide 1 ","type":"shape","props":{ "name":"!!giant-num","text":"01","font":"Segoe UI Black","size":"200", "color":"1A1A1A","opacity":"0.06","bold":"true", "x":"18cm","y":"4cm","width":"18cm","height":"16cm","fill":"none"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{ "name":"!!giant-letter","text":"B","font":"Segoe UI Black","size":"300", "color":"E8E8E8","opacity":"0.08","bold":"true", "x":"0cm","y":"0cm","… Evidence: `skills/morph-ppt/reference/styles/light--bold-type/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " DECK="$SCRIPT DIR/light isometric clean.pptx" rm -f "$DECK" officecli create "$DECK" officecli add "$DECK" '/' --type slide --prop layout=blank --prop background=F0F4F8 cat <<'BATCH' officecli batch "$DECK" {"command":"add","parent":"/slide 1 ","type":"shape","props":{ "preset":"diamond","fill":"E8ECF1","opacity":"0.50", "x":"12cm","y":"10cm","width":"10cm","height":"6cm","name":"platform"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{ "preset":"diamond","fill":"4A90D9","opacity":"0.85", "x":"14cm","y":"5cm","width":"6cm","height":"3.5cm","name":"blockA-top"}}, {"command":"add","parent":"/slide 1 ","type":"… Evidence: `skills/morph-ppt/reference/styles/light--isometric-clean/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/light minimal product.pptx" echo "Building: light--minimal-product Minimal Product " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=FAFAFA GREEN=00B894 DARK=2D3436 GRAY=636E72 LIGHT GRAY=B2BEC3 WHITE=FFFFFF GRAY BG=F5F5F5 OFFSCREEN=36cm echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!ellipse-1' \ --prop preset=ellipse \ --prop fill=$GREEN \ --prop opacity=0.08 \ --prop x=5cm --prop y=3cm --prop width=8cm --prop height=8cm officecli add "$OUTPUT" '/slide 1 ' --type shape \ --p… Evidence: `skills/morph-ppt/reference/styles/light--minimal-product/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/light watercolor wash.pptx" echo "Building: light--watercolor-wash AI Agent Platform " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=FFFDF7 BLUE=7AADCF ORANGE=E8A87C PURPLE=C5B3D1 GREEN=9BC4A8 PEACH=F2C0A2 DARK GREEN=5A7A6A BROWN=6A5A4A GRAY=8A7A6A OFFSCREEN=36cm echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!wash-1' \ --prop preset=ellipse \ --prop fill=$BLUE \ --prop opacity=0.08 \ --prop line=none \ --prop x=0cm --prop y=0cm --prop width=18cm --prop height=15cm --prop ro… Evidence: `skills/morph-ppt/reference/styles/light--watercolor-wash/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " DECK="$SCRIPT DIR/mixed duotone split.pptx" echo "Building: mixed--duotone-split Duotone Split " rm -f "$DECK" officecli create "$DECK" officecli add "$DECK" '/' --type slide --prop layout=blank --prop background=FFFFFF echo ' {"command":"add","parent":"/slide 1 ","type":"shape","props":{ "name":"!!panel-dark","preset":"rect","fill":"2D3436", "x":"0cm","y":"0cm","width":"16.63cm","height":"19.05cm","opacity":"1.0"}}, {"command":"add","parent":"/slide 1 ","type":"shape","props":{ "name":"!!panel-warm","preset":"rect","fill":"E17055", "x":"16.93cm","y":"0cm","width":"16.94cm","height":"19.05cm","opacity":"1.0"}}, {"command":"ad… Evidence: `skills/morph-ppt/reference/styles/mixed--duotone-split/build.sh` - **Build** (source_file): set -e SCRIPT DIR="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " OUTPUT="$SCRIPT DIR/vivid candy stripe.pptx" echo "Building: vivid--candy-stripe Rainbow Candy Stripes " rm -f "$OUTPUT" officecli create "$OUTPUT" BG=FFFFFF RED=FF5252 ORANGE=FF7B39 YELLOW=FFD740 GREEN=69F0AE BLUE=40C4FF PURPLE=7C4DFF BLACK=1A1A1A GRAY=555555 echo "Building Slide 1: Hero..." officecli add "$OUTPUT" '/' --type slide --prop layout=blank --prop background=$BG officecli add "$OUTPUT" '/slide 1 ' --type shape \ --prop 'name=!!stripe-red' \ --prop preset=rect \ --prop fill=$RED \ --prop opacity=0.85 \ --prop x=0cm --prop y=0cm --prop width=34cm --prop height=2cm officecli add "$OUTPUT" '/slide 1 ' --type shape \ -… Evidence: `skills/morph-ppt/reference/styles/vivid--candy-stripe/build.sh` - The remaining 20 evidence entries are in `AI_CONTEXT_PACK.json` or `EVIDENCE_INDEX.json`. ## Rules the Host AI Must Follow - **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `examples/README.md`, `npm/README.md` - **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `examples/README.md`, `npm/README.md` ## Questions the User Should Answer First - Which host AI or local environment do you plan to use it in? - Do you just want to experience the workflow first, or are you ready to actually install? - What matters most to you: install cost, output quality, or conflicts with your existing rules? ## Acceptance Checks - Every capability claim can be traced back to a file path in evidence_refs. - AI_CONTEXT_PACK.md does not package previews as a real run. - The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes. --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Overview & Architecture**: importance `high` - source_paths: README.md, src/officecli/Program.cs, src/officecli/CommandBuilder.cs, officecli.slnx, build.sh - **Document Operations & Command Reference**: importance `high` - source_paths: src/officecli/CommandBuilder.Add.cs, src/officecli/CommandBuilder.Set.cs, src/officecli/CommandBuilder.GetQuery.cs, src/officecli/CommandBuilder.View.cs, src/officecli/CommandBuilder.Raw.cs - **Resident Mode, Batch Execution & Live Preview**: importance `high` - source_paths: src/officecli/ResidentServer.cs, src/officecli/ResidentClient.cs, src/officecli/Core/BatchExecutor.cs, src/officecli/CommandBuilder.Batch.cs, src/officecli/CommandBuilder.Watch.cs - **AI Integration, Templates & Advanced Features**: importance `high` - source_paths: src/officecli/McpServer.cs, src/officecli/McpInstaller.cs, src/officecli/Core/SkillInstaller.cs, src/officecli/Core/TemplateMerger.cs, src/officecli/Core/Formula/FormulaEvaluator.cs ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `1ab5978a5ff583a28f7544caf533c8eb52e9f15d` - inspected_files: `README.md`, `examples/README.md`, `examples/excel/cell-formatting.md`, `examples/excel/cell-formatting.py`, `examples/excel/charts/charts-advanced.md`, `examples/excel/charts/charts-advanced.py`, `examples/excel/charts/charts-area.md`, `examples/excel/charts/charts-area.py`, `examples/excel/charts/charts-bar.md`, `examples/excel/charts/charts-bar.py`, `examples/excel/charts/charts-basic.md`, `examples/excel/charts/charts-basic.py`, `examples/excel/charts/charts-boxwhisker.md`, `examples/excel/charts/charts-boxwhisker.py`, `examples/excel/charts/charts-bubble.md`, `examples/excel/charts/charts-bubble.py`, `examples/excel/charts/charts-column.md`, `examples/excel/charts/charts-column.py`, `examples/excel/charts/charts-combo.md`, `examples/excel/charts/charts-combo.py` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://news.ycombinator.com/item?id=48807225 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.