mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-05-18 23:03:06 +08:00

Files

Claude ec9ace9c54 docs: add native Japanese translation of ECC documentation (ja-JP)

Translate everything-claude-code repository to Japanese including:
- 17 root documentation files
- 60 agent documentation files
- 80 command documentation files
- 99 rule files across 18 language directories (common, angular, arkts, cpp, csharp, dart, fsharp, golang, java, kotlin, perl, php, python, ruby, rust, swift, typescript, web)
- 199 skill documentation files

Total: 455 files translated to Japanese with:
- Consistent terminology glossary applied throughout
- YAML field names preserved in English (name, description, etc.)
- Code blocks and examples untouched (comments translated)
- Markdown structure and relative links preserved
- Professional translation maintaining technical accuracy

This translation expands ECC accessibility to Japanese-speaking developers and teams.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

2026-05-17 02:31:40 -04:00

2.5 KiB

Raw Blame History

name, description, origin

name	description	origin
google-workspace-ops	Google Workspace API操作、Sheets自動化、Gmail統合、およびドキュメント管理。	ECC

Google Workspace Ops

This skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.

When to Use

User needs to find a doc, sheet, or deck and update it in place
Consolidating plans, trackers, notes, or customer lists stored in Google Drive
Cleaning or restructuring a shared spreadsheet
Importing, repairing, or reformatting a Google Slides deck
Producing summaries from Docs, Sheets, or Slides for decision-making

Preferred Tool Surface

Use Google Drive as the entry point, then switch to the right specialist:

Google Docs for text-heavy docs
Google Sheets for tabular work, formulas, and charts
Google Slides for decks, imports, template migration, and cleanup

Do not guess structure from filenames alone. Inspect first.

Workflow

1. Find the asset

Start with the Drive search surface to locate:

the exact file
sibling assets
likely duplicates
recently modified versions

If several documents look similar, confirm by title, owner, modified time, or folder.

2. Inspect before editing

Before making changes:

summarize current structure
identify tabs, headings, or slide count
detect whether the task is local cleanup or structural surgery

Pick the smallest tool that can safely perform the work.

3. Edit with precision

For Docs: use index-aware edits, not vague rewrites
For Sheets: operate on explicit tabs and ranges
For Slides: distinguish content edits from visual cleanup or template migration

If the requested work is visual or layout-sensitive, iterate with inspection and verification instead of one giant blind update.

4. Keep the working system clean

When the file is part of a larger workflow, also surface:

duplicate trackers
outdated decks
stale docs vs canonical docs
whether the asset should be archived, merged, or renamed

Output Format

Use:

ASSET
- file name
- type
- why this is the right file

CURRENT STATE
- structure summary
- key problems or blockers

ACTION
- edits made or recommended

FOLLOW-UPS
- archive / merge / duplicate cleanup / next file to update

Good Use Cases

"Find the active planning doc and condense it"
"Clean up this customer spreadsheet and show me the churn-risk rows"
"Import this deck into Slides and make it presentable"
"Find the current tracker, not the stale duplicate"

2.5 KiB Raw Blame History