Imported from gabrielmoreira/agent-skills-mirror (mirrors/repos/iOfficeAI@AionUi/AGENTS.md). Install upstream with npx skills add gabrielmoreira/agent-skills-mirror --skill iOfficeAI@AionUi. Copyright stays with the author.

AionUi - Project Guide

All contributors (human and AI) must follow CONTRIBUTING.md before opening a PR. (Chinese version)

Code Conventions

File & Directory Structure

• Directory size limit: Prefer ≤ 10 direct children per directory; new or substantially reorganized directories must satisfy this.

See docs/contributing/file-structure.md for complete rules. Agents must also follow the architecture skill (.claude/skills/architecture/SKILL.md) when creating files or modules.

Naming

• Components: PascalCase (Button.tsx, Modal.tsx)
• Utilities: camelCase (formatDate.ts)
• Hooks: camelCase with use prefix (useTheme.ts)
• Constants files: camelCase (constants.ts) — values inside use UPPER_SNAKE_CASE
• Type files: camelCase (types.ts)
• Style files: kebab-case or ComponentName.module.css
• Unused params: prefix with _

UI Library & Icons

• Components: @arco-design/web-react — no raw interactive HTML (<button>, <input>, <select>, etc.)
• Icons: @icon-park/react

CSS

• Prefer UnoCSS utility classes; complex styles use CSS Modules (ComponentName.module.css)
• Colors must use semantic tokens from uno.config.ts or CSS variables — no hardcoded values
• Arco theme overrides go in packages/desktop/src/renderer/styles/arco-override.css; component-scoped Arco overrides use CSS Module with :global()
• Global styles only in packages/desktop/src/renderer/styles/

Formatting rules (Oxfmt, Prettier-compatible):

• Single-element arrays that fit on one line → inline: [{ id: 'a', value: 'b' }]
• Trailing commas required in multi-line arrays/objects
• Single quotes for strings

TypeScript

• Strict mode enabled — no any, no implicit returns
• Use path aliases: @/*, @process/*, @renderer/*
• Prefer type over interface (per Oxlint config)
• English for code comments; JSDoc for public functions

Internationalization (i18n)

New or changed user-facing text must use i18n keys; do not introduce hardcoded strings. Languages and modules are defined in packages/desktop/src/common/config/i18n-config.json.

See the i18n skill (.claude/skills/i18n/SKILL.md) for complete workflow, key naming, and validation steps.

Architecture

Two process types — never mix their APIs:

Cross-process communication must go through the IPC bridge (packages/desktop/src/preload/). See docs/architecture/overview.md for details.

Testing

Framework: Vitest 4 (vitest.config.ts). Project coverage target is ≥ 80%; ordinary changes should add focused tests for changed behavior.

bun run test              # run all tests
bun run test:coverage     # with coverage report

See the testing skill (.claude/skills/testing/SKILL.md) for complete workflow and quality rules.

Workflow

Scope & Enforcement

• Hard blockers: process boundary violations, TypeScript errors, failing tests, unsafe IPC usage, missing i18n for new or changed user-facing text, and raw interactive HTML in new UI.
• Current-change requirements: naming, CSS, file placement, tests, docs, directory size, and single-file-directory rules apply to files created or meaningfully modified by the current change.
• Ratchet rules: existing directory size or single-file-directory violations do not require cleanup during ordinary feature work or bugfixes, but the current change must not make them worse.
• No scope expansion: implementation plans and reviews must not create extra tasks, phases, or acceptance criteria for cleanup unless the user asks for that scope.
• Ignored working docs: docs/superpowers/ is intentionally gitignored for local Superpowers specs and plans. Do not force-add or otherwise commit files from this directory.

During Development

Auto-fix as you edit:

bun run lint:fix       # auto-fix lint issues (oxlint)
bun run format         # auto-format all files (oxfmt)
bunx tsc --noEmit      # verify no type errors

If your changes touch packages/desktop/src/renderer/, locales/, or packages/desktop/src/common/config/i18n, also run:

bun run i18n:types
node scripts/check-i18n.js

Before Pushing

AI agents must not push unless explicitly asked. When pushing, use just push, never git push:

just push                          # lint → format-check → typecheck → test → git push
just push -u origin feat/branch    # same checks, with extra git push args

Any step that fails aborts the push. Fix the issue, commit, then retry.

Note for AI agents: just push uses --quiet for lint — only errors cause failure. The project has many pre-existing lint warnings which do NOT indicate failure. Judge success by exit code, not by output volume.

Before PR (optional stricter check)

prek replicates the exact CI pipeline (includes end-of-file, trailing whitespace checks on all file types):

# One-time setup
npm install -g @j178/prek

# Run
prek run --from-ref origin/main --to-ref HEAD

prek is read-only — it reports but does not fix. If it reports issues, run the auto-fix commands above, commit, then re-run.

Commit & PR Format

Commits and PR titles must follow the Conventional Commit format defined in CONTRIBUTING.md:

<type>(<scope>): <subject>

Allowed types: feat, fix, perf, refactor, docs, style, chore, test, ci, build.

When opening a PR, fill in the PR body using .github/pull_request_template.md and complete its checklists honestly (only check items you actually ran or verified).

NEVER add AI signatures (Co-Authored-By, Generated with, etc.).

Skills Index

Skills are located in .claude/skills/ and contain project conventions that apply to all agents and contributors.