mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-05-18 21:31:15 +08:00
ec9ace9c54
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>
89 lines
2.8 KiB
Markdown
89 lines
2.8 KiB
Markdown
---
|
|
name: hermes-imports
|
|
description: Hermesデータインポート、マッピング、変換、およびデータインテグリティ検証。
|
|
origin: ECC
|
|
---
|
|
|
|
# Hermes Imports
|
|
|
|
Use this skill when turning a repeated Hermes workflow into something safe to ship in ECC.
|
|
|
|
Hermes is the operator shell. ECC is the reusable workflow layer. Imports should move stable patterns from Hermes into ECC without moving private state.
|
|
|
|
## When To Use
|
|
|
|
- A Hermes workflow has repeated enough times to become reusable.
|
|
- A local operator prompt should become a public ECC skill.
|
|
- A launch, content, research, or engineering workflow needs sanitized handoff docs.
|
|
- A workflow mentions local paths, credentials, personal datasets, or private account names that must be removed before publication.
|
|
|
|
## Import Rules
|
|
|
|
- Convert local paths to repo-relative paths or placeholders.
|
|
- Replace live account names with role labels such as `operator`, `default profile`, or `workspace owner`.
|
|
- Describe credential requirements by provider name only.
|
|
- Keep examples narrow and operational.
|
|
- Do not ship raw workspace exports, tokens, OAuth files, health data, CRM data, or finance data.
|
|
- If the workflow requires private state to make sense, keep it local.
|
|
|
|
## Sanitization Checklist
|
|
|
|
Before committing an imported workflow, scan for:
|
|
|
|
- absolute paths such as `/Users/...`
|
|
- `~/.hermes` paths unless the doc is explicitly explaining local setup
|
|
- API keys, tokens, cookies, OAuth files, or bearer strings
|
|
- phone numbers, private email addresses, and personal contact graphs
|
|
- client names, family names, or account names that are not already public
|
|
- revenue, health, or CRM details
|
|
- raw logs that include tool output from private systems
|
|
|
|
## Conversion Pattern
|
|
|
|
1. Identify the repeatable operator loop.
|
|
2. Strip private inputs and outputs.
|
|
3. Rewrite local paths as repo-relative examples.
|
|
4. Turn one-off instructions into a `When To Use` section and a short process.
|
|
5. Add concrete output requirements.
|
|
6. Run a secret and local-path scan before opening a PR.
|
|
|
|
## Example: Launch Handoff
|
|
|
|
Local Hermes prompt:
|
|
|
|
```text
|
|
Read my local workspace files and finalize launch copy.
|
|
```
|
|
|
|
ECC-safe version:
|
|
|
|
```text
|
|
Use the public release pack under docs/releases/<version>/.
|
|
Return one X thread, one LinkedIn post, one recording checklist, and the missing assets list.
|
|
```
|
|
|
|
## Example: Quiet-Hours Operator Job
|
|
|
|
Local Hermes job:
|
|
|
|
```text
|
|
Run my private inbox, finance, and content checks overnight.
|
|
```
|
|
|
|
ECC-safe version:
|
|
|
|
```text
|
|
Describe the scheduler policy, the quiet-hours window, the escalation rules, and the categories of checks. Do not include private data sources or credentials.
|
|
```
|
|
|
|
## Output Contract
|
|
|
|
Return:
|
|
|
|
- candidate ECC skill name
|
|
- sanitized workflow summary
|
|
- required public inputs
|
|
- private inputs removed
|
|
- remaining risks
|
|
- files that should be created or updated
|