agentleFS
Sign inStart free
yukiyokotaniyukiyokotani/office-open-xml-viewer/CLAUDE.md

office-open-xml-viewer

CLAUDE.md866 starsChanged 3 months agoMITView on GitHub

Claude-specific supplement. All agents should read AGENTS.md first; that file is the canonical workflow for this repository. This file only records Claude/Claude Code conventions and overrides. After reading this file: 1. Run pwd and identify the worktree role from the path. 2. Ensure spec exists in the worktree as a symlink to the main checkout's ignored OOXML specification directory, following AGENTS.md. 3. Read the package-level CLAUDE.md for any package you will edit. 4. Follow the ownership limits below unless the…

We split this CLAUDE.md into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After reading this file:

    line 9
  2. Very specific:

    Run pwd and identify the worktree role from the path.

    line 11
  3. Very specific:

    Ensure spec exists in the worktree as a symlink to the main checkout's ignored OOXML specification directory, following AGENTS.md.

    line 12
  4. Distinctive:

    Read the package-level CLAUDE.md for any package you will edit.

    line 14
  5. Distinctive:

    Follow the ownership limits below unless the user explicitly asks for a cross-package change.

    line 15
  6. Distinctive:

    Treat unexpected dirty files as user or peer-agent work.

    line 34
  7. Distinctive:

    Do not revert or overwrite unrelated changes.

    line 35
  8. Distinctive:

    When Claude authors a commit, include a co-author trailer with the actual model used for that task, for example:

    line 57
  9. Distinctive:

    If Claude starts or directs Codex for the work, include both the Claude/Fable and Codex co-author trailers with the models actually used …

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md

Claude-specific supplement. All agents should read AGENTS.md first; that file is the canonical workflow for this repository. This file only records Claude/Claude Code conventions and overrides.

Worktree Startup Checklist

After reading this file:

  1. Run pwd and identify the worktree role from the path.
  2. Ensure spec exists in the worktree as a symlink to the main checkout's ignored OOXML specification directory, following AGENTS.md.
  3. Read the package-level CLAUDE.md for any package you will edit.
  4. Follow the ownership limits below unless the user explicitly asks for a cross-package change.

Claude Worktree Roles

Some Claude sessions run in package-scoped worktrees:

  • .claude/worktrees/pptx or ooxml-pptx → PPTX session; edit packages/pptx only unless the task requires shared code.
  • DOCX-focused worktrees should primarily edit packages/docx.
  • XLSX-focused worktrees should primarily edit packages/xlsx.

Reading other packages is fine. Editing other packages should happen only for a coherent cross-package fix described in AGENTS.md.

Parallel Session Safety

Multiple Claude/Codex sessions may run at once.

  • Treat unexpected dirty files as user or peer-agent work.
  • Do not revert or overwrite unrelated changes.
  • Preserve dirty work before switching branches or pulling.
  • Private samples, local sample stories, WASM outputs, VRT screenshots, and reference images remain local/generated unless the user explicitly asks to commit them.

Claude Autonomous Work

Between 01:00 and 09:00 local time, Claude sessions may proceed without asking for confirmation for non-destructive work:

  • code changes,
  • tests,
  • WASM builds,
  • feature-branch commits and pushes,
  • package scripts.

Still ask before destructive operations, reference image updates, direct changes to main, or anything that conflicts with AGENTS.md.

Commit Attribution

When Claude authors a commit, include a co-author trailer with the actual model used for that task, for example:

Co-Authored-By: Claude <model-name> <noreply@anthropic.com>

If Claude starts or directs Codex for the work, include both the Claude/Fable and Codex co-author trailers with the models actually used for that task, as described in AGENTS.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free