mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-05-19 23:33:07 +08:00
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>
This commit is contained in:
50
docs/ja-JP/skills/enterprise-agent-ops/SKILL.md
Normal file
50
docs/ja-JP/skills/enterprise-agent-ops/SKILL.md
Normal file
@@ -0,0 +1,50 @@
|
||||
---
|
||||
name: enterprise-agent-ops
|
||||
description: オブザーバビリティ、セキュリティ境界、およびライフサイクル管理を備えた長寿命エージェントワークロードを運用します。
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Enterprise Agent Ops
|
||||
|
||||
Use this skill for cloud-hosted or continuously running agent systems that need operational controls beyond single CLI sessions.
|
||||
|
||||
## Operational Domains
|
||||
|
||||
1. runtime lifecycle (start, pause, stop, restart)
|
||||
2. observability (logs, metrics, traces)
|
||||
3. safety controls (scopes, permissions, kill switches)
|
||||
4. change management (rollout, rollback, audit)
|
||||
|
||||
## Baseline Controls
|
||||
|
||||
- immutable deployment artifacts
|
||||
- least-privilege credentials
|
||||
- environment-level secret injection
|
||||
- hard timeout and retry budgets
|
||||
- audit log for high-risk actions
|
||||
|
||||
## Metrics to Track
|
||||
|
||||
- success rate
|
||||
- mean retries per task
|
||||
- time to recovery
|
||||
- cost per successful task
|
||||
- failure class distribution
|
||||
|
||||
## Incident Pattern
|
||||
|
||||
When failure spikes:
|
||||
1. freeze new rollout
|
||||
2. capture representative traces
|
||||
3. isolate failing route
|
||||
4. patch with smallest safe change
|
||||
5. run regression + security checks
|
||||
6. resume gradually
|
||||
|
||||
## Deployment Integrations
|
||||
|
||||
This skill pairs with:
|
||||
- PM2 workflows
|
||||
- systemd services
|
||||
- container orchestrators
|
||||
- CI/CD gates
|
||||
Reference in New Issue
Block a user