genoffice: Instructions file for Claude Code

CLAUDE.md

genoffice CLAUDE.md is an instructions file for Claude Code from genspark-ai/genoffice. It costs 834 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for contributors and AI agents working on the genoffice project. They include mandatory rules for light and dark themes, including how interface colors must be defined and used.

In plain words
What is it for?
Use them when changing the project's interface, especially renderer styles, shared color tokens, or app-specific accent colors. They guide where theme values belong and how to satisfy the project's checks.
Why use it?
They prevent theme colors from becoming inconsistent or breaking in dark mode. They also ensure new color tokens are added for every supported theme.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md.

This is genspark-ai/genoffice's own configuration. It tells Claude Code how to work on genoffice itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything genoffice configures →

About the project

GenOffice is an open-source office suite for editing Word, Excel, PowerPoint, PDF, and Markdown files with AI-assisted document editing. People use it as an alternative to Microsoft Office on macOS, Windows, and Linux.

genspark-ai/genoffice · 6,274 stars · on GitHub · genoffice.ai

Reuse

Borrowing it

Nothing to install: this file belongs to genspark-ai/genoffice. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/genspark-ai/genoffice/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/genspark-ai/genoffice

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for genoffice CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/genspark-ai/genoffice/claude-md/github.svg)](https://agentmods.dev/instructions/genspark-ai/genoffice/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/genspark-ai/genoffice/claude-md"><img src="https://agentmods.dev/badge/instructions/genspark-ai/genoffice/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for genoffice CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/genspark-ai/genoffice/claude-md"><img src="https://agentmods.dev/badge/instructions/genspark-ai/genoffice/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 834 This file is loaded in full into every session.
When invoked 834 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00834 $0.00834
Opus 5 $0.00417 $0.00417
Sonnet 5 $0.00167 $0.00167
Haiku 4.5 $0.00083 $0.00083

Measured 3d ago against content hash 2e6f932ba886, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

genoffice CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

CLAUDE.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

Guidance for AI agents and human contributors working in this repo.

Theming rules (mandatory)

The suite supports light / dark / system UI themes. The switching mechanism is a data-theme attribute on <html> plus CSS custom properties defined once in packages/ui/src/tokens.css (light defaults in :root, overrides in [data-theme='dark'], and a prefers-color-scheme media-query fallback for system mode).

  1. UI chrome colors must use semantic tokens. Never write raw #hex / rgb() in renderer CSS rules or chrome-related inline styles — reference var(--surface), var(--text), var(--hover), etc. from packages/ui/src/tokens.css. Raw values are allowed only on custom-property definition lines (--x: #...; — token, accent, or app-scoped variable definitions). CI enforces this for new/changed renderer CSS lines (tools/check-theme-colors.mjs).
  2. Every new token gets both values. Adding a token means adding it to all three blocks in tokens.css (light, dark, system-dark fallback).
  3. Accent colors stay per-app. Each app defines --accent / --accent-dark / --accent-soft (and its dark-adjusted values) in its own styles.css. Shared rules reference var(--accent) and inherit the app's brand color.
  4. Document content is never re-authored by the theme. Page surfaces, cell fills, slide content, PDF page bitmaps, export/print stylesheets, chart palettes, highlight color maps, stamps, and WordArt presets are document data: they stay hardcoded, must not reference chrome tokens, and every save/export/print path must produce identical output in both themes. A Word/Excel-style dark page (Sheets via Univer's darkMode, Docs via apps/docs/src/renderer/editor/dark-page.ts) is a display-time remap only: the authored color stays the real declaration, the remapped twin lives in a screen-only --dk-* / .page-dark layer, and print/export never see it.
  5. Canvas-drawn UI affordances go through a constants table. Konva/canvas editing chrome (selection frames, guides, handles) reads from the app's canvas color table (e.g. canvas-colors.ts) keyed by the current theme — no inline hex in draw calls.

Read the full file on GitHub · 61 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago Changed · +4 lines · +83 tokens per session 2e6f932ba886
  2. 5d ago Changed · +9 lines · +124 tokens per session 3ac9ef4cd120
  3. 10d ago First seen · 48 lines · 627 tokens per session scan A 595f7e8c825c

Subscribe to this mod's changes

genoffice CLAUDE.md is an instructions file published in the GitHub repository genspark-ai/genoffice (6,274 stars, last pushed today), licensed Apache-2.0. It adds 834 tokens to every session, about $0.0042 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens