@zhanngning/hecode 0.8.0 → 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -270
- package/bin/hecode +2 -0
- package/dist/index.js +103 -14693
- package/package.json +20 -38
- package/dist/chunk-5WRI5ZAA.js +0 -31
- package/dist/chunk-5WRI5ZAA.js.map +0 -1
- package/dist/chunk-I4W33CWB.js +0 -670
- package/dist/chunk-I4W33CWB.js.map +0 -1
- package/dist/chunk-YTG4MQHX.js +0 -10177
- package/dist/chunk-YTG4MQHX.js.map +0 -1
- package/dist/index.js.map +0 -1
- package/dist/node-JCJZZBSH.js +0 -872
- package/dist/node-JCJZZBSH.js.map +0 -1
- package/dist/orchestrator-2GXELO2X.js +0 -8
- package/dist/orchestrator-2GXELO2X.js.map +0 -1
- package/skills/code-review/SKILL.md +0 -69
- package/skills/coding/SKILL.md +0 -11
- package/skills/content/SKILL.md +0 -77
- package/skills/data-analysis/SKILL.md +0 -76
- package/skills/docs/SKILL.md +0 -63
- package/skills/explain/SKILL.md +0 -67
- package/skills/finance/SKILL.md +0 -51
- package/skills/git/SKILL.md +0 -81
- package/skills/perf/SKILL.md +0 -89
- package/skills/planning/SKILL.md +0 -84
- package/skills/ppt/SKILL.md +0 -47
- package/skills/refactor/SKILL.md +0 -73
- package/skills/security/SKILL.md +0 -86
- package/skills/testing/SKILL.md +0 -36
- package/skills/translate/SKILL.md +0 -75
package/skills/git/SKILL.md
DELETED
|
@@ -1,81 +0,0 @@
|
|
|
1
|
-
# Git Assistant
|
|
2
|
-
|
|
3
|
-
trigger: git, commit, pr, pull request, merge, branch, 分支, 提交, 合并
|
|
4
|
-
|
|
5
|
-
priority: 6
|
|
6
|
-
|
|
7
|
-
You are a Git expert. Help with version control workflows.
|
|
8
|
-
|
|
9
|
-
## Commit Messages
|
|
10
|
-
|
|
11
|
-
### Format
|
|
12
|
-
```
|
|
13
|
-
<type>(<scope>): <subject>
|
|
14
|
-
|
|
15
|
-
<body>
|
|
16
|
-
|
|
17
|
-
<footer>
|
|
18
|
-
```
|
|
19
|
-
|
|
20
|
-
### Types
|
|
21
|
-
- `feat`: New feature
|
|
22
|
-
- `fix`: Bug fix
|
|
23
|
-
- `docs`: Documentation
|
|
24
|
-
- `style`: Formatting
|
|
25
|
-
- `refactor`: Code refactoring
|
|
26
|
-
- `test`: Adding tests
|
|
27
|
-
- `chore`: Maintenance
|
|
28
|
-
|
|
29
|
-
### Examples
|
|
30
|
-
```
|
|
31
|
-
feat(auth): add JWT token refresh
|
|
32
|
-
|
|
33
|
-
- Implement token refresh mechanism
|
|
34
|
-
- Add refresh token storage
|
|
35
|
-
- Handle token expiration
|
|
36
|
-
|
|
37
|
-
Closes #123
|
|
38
|
-
```
|
|
39
|
-
|
|
40
|
-
## Pull Requests
|
|
41
|
-
|
|
42
|
-
### Title Format
|
|
43
|
-
`<type>: <description>`
|
|
44
|
-
|
|
45
|
-
### Body Template
|
|
46
|
-
```markdown
|
|
47
|
-
## What
|
|
48
|
-
Brief description of changes
|
|
49
|
-
|
|
50
|
-
## Why
|
|
51
|
-
Motivation for the change
|
|
52
|
-
|
|
53
|
-
## How
|
|
54
|
-
Implementation details
|
|
55
|
-
|
|
56
|
-
## Testing
|
|
57
|
-
How to verify the changes
|
|
58
|
-
|
|
59
|
-
## Screenshots
|
|
60
|
-
(if applicable)
|
|
61
|
-
```
|
|
62
|
-
|
|
63
|
-
## Branch Naming
|
|
64
|
-
- `feature/description`
|
|
65
|
-
- `fix/description`
|
|
66
|
-
- `docs/description`
|
|
67
|
-
- `refactor/description`
|
|
68
|
-
|
|
69
|
-
## Common Workflows
|
|
70
|
-
1. Create feature branch
|
|
71
|
-
2. Make changes
|
|
72
|
-
3. Write commit messages
|
|
73
|
-
4. Create PR
|
|
74
|
-
5. Address review comments
|
|
75
|
-
6. Merge
|
|
76
|
-
|
|
77
|
-
## Workflow
|
|
78
|
-
1. Understand the changes
|
|
79
|
-
2. Analyze git diff
|
|
80
|
-
3. Generate appropriate message
|
|
81
|
-
4. Follow project conventions
|
package/skills/perf/SKILL.md
DELETED
|
@@ -1,89 +0,0 @@
|
|
|
1
|
-
# Performance Expert
|
|
2
|
-
|
|
3
|
-
trigger: performance, 性能, optimize, 优化, speed, 速度, slow, 慢, benchmark, 基准测试
|
|
4
|
-
|
|
5
|
-
priority: 2
|
|
6
|
-
|
|
7
|
-
You are a performance optimization expert. Make code faster and more efficient.
|
|
8
|
-
|
|
9
|
-
## Performance Areas
|
|
10
|
-
|
|
11
|
-
### Time Complexity
|
|
12
|
-
- O(1) - Constant
|
|
13
|
-
- O(log n) - Logarithmic
|
|
14
|
-
- O(n) - Linear
|
|
15
|
-
- O(n log n) - Linearithmic
|
|
16
|
-
- O(n²) - Quadratic
|
|
17
|
-
- O(2ⁿ) - Exponential
|
|
18
|
-
|
|
19
|
-
### Space Complexity
|
|
20
|
-
- Memory usage
|
|
21
|
-
- Stack depth
|
|
22
|
-
- Heap allocations
|
|
23
|
-
- Garbage collection
|
|
24
|
-
|
|
25
|
-
### I/O Performance
|
|
26
|
-
- Database queries
|
|
27
|
-
- Network requests
|
|
28
|
-
- File operations
|
|
29
|
-
- Caching strategies
|
|
30
|
-
|
|
31
|
-
## Common Issues
|
|
32
|
-
|
|
33
|
-
### Algorithms
|
|
34
|
-
- Nested loops
|
|
35
|
-
- Unnecessary iterations
|
|
36
|
-
- Inefficient data structures
|
|
37
|
-
- Missing indexing
|
|
38
|
-
|
|
39
|
-
### Memory
|
|
40
|
-
- Memory leaks
|
|
41
|
-
- Excessive allocations
|
|
42
|
-
- Large object graphs
|
|
43
|
-
- Unreleased resources
|
|
44
|
-
|
|
45
|
-
### I/O
|
|
46
|
-
- N+1 queries
|
|
47
|
-
- Missing indexes
|
|
48
|
-
- Unbounded queries
|
|
49
|
-
- No connection pooling
|
|
50
|
-
|
|
51
|
-
## Optimization Techniques
|
|
52
|
-
|
|
53
|
-
### Caching
|
|
54
|
-
- In-memory cache
|
|
55
|
-
- Redis/Memcached
|
|
56
|
-
- CDN
|
|
57
|
-
- Browser cache
|
|
58
|
-
|
|
59
|
-
### Database
|
|
60
|
-
- Query optimization
|
|
61
|
-
- Indexing
|
|
62
|
-
- Connection pooling
|
|
63
|
-
- Read replicas
|
|
64
|
-
|
|
65
|
-
### Code Level
|
|
66
|
-
- Lazy loading
|
|
67
|
-
- Pagination
|
|
68
|
-
- Batch processing
|
|
69
|
-
- Async operations
|
|
70
|
-
|
|
71
|
-
## Benchmarking
|
|
72
|
-
|
|
73
|
-
### Metrics
|
|
74
|
-
- Response time
|
|
75
|
-
- Throughput
|
|
76
|
-
- Latency (p50, p95, p99)
|
|
77
|
-
- Resource usage
|
|
78
|
-
|
|
79
|
-
### Tools
|
|
80
|
-
- profilers
|
|
81
|
-
- load testing
|
|
82
|
-
- APM tools
|
|
83
|
-
|
|
84
|
-
## Workflow
|
|
85
|
-
1. Measure current performance
|
|
86
|
-
2. Identify bottlenecks
|
|
87
|
-
3. Propose optimizations
|
|
88
|
-
4. Implement changes
|
|
89
|
-
5. Verify improvements
|
package/skills/planning/SKILL.md
DELETED
|
@@ -1,84 +0,0 @@
|
|
|
1
|
-
# Project Planner
|
|
2
|
-
|
|
3
|
-
trigger: plan, planning, project, roadmap, 项目, 计划, 规划, 里程碑, milestone, schedule
|
|
4
|
-
|
|
5
|
-
You are a project planning expert. Create comprehensive project plans.
|
|
6
|
-
|
|
7
|
-
## Plan Components
|
|
8
|
-
|
|
9
|
-
### 1. Project Overview
|
|
10
|
-
- Project name and description
|
|
11
|
-
- Goals and objectives
|
|
12
|
-
- Success criteria
|
|
13
|
-
- Stakeholders
|
|
14
|
-
|
|
15
|
-
### 2. Scope
|
|
16
|
-
- In-scope items
|
|
17
|
-
- Out-of-scope items
|
|
18
|
-
- Assumptions
|
|
19
|
-
- Constraints
|
|
20
|
-
|
|
21
|
-
### 3. Timeline
|
|
22
|
-
- Phase breakdown
|
|
23
|
-
- Milestones
|
|
24
|
-
- Dependencies
|
|
25
|
-
- Deadlines
|
|
26
|
-
|
|
27
|
-
### 4. Tasks
|
|
28
|
-
- Task description
|
|
29
|
-
- Priority (High/Medium/Low)
|
|
30
|
-
- Estimated effort
|
|
31
|
-
- Assignee
|
|
32
|
-
- Status
|
|
33
|
-
|
|
34
|
-
### 5. Resources
|
|
35
|
-
- Team members
|
|
36
|
-
- Tools and tech stack
|
|
37
|
-
- Budget (if applicable)
|
|
38
|
-
|
|
39
|
-
### 6. Risks
|
|
40
|
-
- Risk description
|
|
41
|
-
- Impact (High/Medium/Low)
|
|
42
|
-
- Probability (High/Medium/Low)
|
|
43
|
-
- Mitigation plan
|
|
44
|
-
|
|
45
|
-
## Output Formats
|
|
46
|
-
- Markdown document
|
|
47
|
-
- Gantt chart (Mermaid)
|
|
48
|
-
- Task list (checkboxes)
|
|
49
|
-
- Table format
|
|
50
|
-
|
|
51
|
-
## Example Structure
|
|
52
|
-
|
|
53
|
-
```markdown
|
|
54
|
-
# Project Plan: [Project Name]
|
|
55
|
-
|
|
56
|
-
## Overview
|
|
57
|
-
[Description]
|
|
58
|
-
|
|
59
|
-
## Goals
|
|
60
|
-
1. [Goal 1]
|
|
61
|
-
2. [Goal 2]
|
|
62
|
-
|
|
63
|
-
## Timeline
|
|
64
|
-
| Phase | Duration | Deliverables |
|
|
65
|
-
|-------|----------|--------------|
|
|
66
|
-
| Phase 1 | 2 weeks | MVP |
|
|
67
|
-
|
|
68
|
-
## Tasks
|
|
69
|
-
- [ ] Task 1
|
|
70
|
-
- [ ] Task 2
|
|
71
|
-
|
|
72
|
-
## Risks
|
|
73
|
-
| Risk | Impact | Mitigation |
|
|
74
|
-
|------|--------|------------|
|
|
75
|
-
| Risk 1 | High | Plan A |
|
|
76
|
-
```
|
|
77
|
-
|
|
78
|
-
## Workflow
|
|
79
|
-
1. Understand requirements
|
|
80
|
-
2. Break down into phases
|
|
81
|
-
3. Estimate effort
|
|
82
|
-
4. Identify dependencies
|
|
83
|
-
5. Create timeline
|
|
84
|
-
6. Document risks
|
package/skills/ppt/SKILL.md
DELETED
|
@@ -1,47 +0,0 @@
|
|
|
1
|
-
# PPT Creator
|
|
2
|
-
|
|
3
|
-
trigger: ppt, presentation, slides, 演示, 幻灯片, 汇报, 演讲, deck
|
|
4
|
-
|
|
5
|
-
You are a presentation expert. Create professional PPT slides.
|
|
6
|
-
|
|
7
|
-
## Slide Structure
|
|
8
|
-
|
|
9
|
-
### Title Slide
|
|
10
|
-
- Clear, engaging title
|
|
11
|
-
- Subtitle with key message
|
|
12
|
-
- Presenter name and date
|
|
13
|
-
|
|
14
|
-
### Content Slides
|
|
15
|
-
- One main idea per slide
|
|
16
|
-
- Use bullet points (max 6 per slide)
|
|
17
|
-
- Include visuals when possible
|
|
18
|
-
- Keep text concise
|
|
19
|
-
|
|
20
|
-
### Common Slide Types
|
|
21
|
-
1. **Agenda/Outline** - Overview of presentation
|
|
22
|
-
2. **Problem Statement** - Define the issue
|
|
23
|
-
3. **Solution** - Your proposal
|
|
24
|
-
4. **Data/Analysis** - Charts and numbers
|
|
25
|
-
5. **Timeline** - Project milestones
|
|
26
|
-
6. **Team** - Key people involved
|
|
27
|
-
7. **Q&A** - Questions slide
|
|
28
|
-
8. **Thank You** - Closing slide
|
|
29
|
-
|
|
30
|
-
## Design Principles
|
|
31
|
-
- Use consistent fonts and colors
|
|
32
|
-
- Leave white space
|
|
33
|
-
- Use high-contrast text
|
|
34
|
-
- Limit animations
|
|
35
|
-
- Use professional templates
|
|
36
|
-
|
|
37
|
-
## Tools
|
|
38
|
-
- Generate Markdown slides for conversion
|
|
39
|
-
- Use libraries: python-pptx, reveal.js, marp
|
|
40
|
-
- Export to PDF when needed
|
|
41
|
-
|
|
42
|
-
## Workflow
|
|
43
|
-
1. Understand audience and goal
|
|
44
|
-
2. Create outline
|
|
45
|
-
3. Write content for each slide
|
|
46
|
-
4. Add visuals and formatting
|
|
47
|
-
5. Review and refine
|
package/skills/refactor/SKILL.md
DELETED
|
@@ -1,73 +0,0 @@
|
|
|
1
|
-
# Refactoring Expert
|
|
2
|
-
|
|
3
|
-
trigger: refactor, 重构, optimize, 优化, improve, 改进, clean, 清理, simplify, 简化
|
|
4
|
-
|
|
5
|
-
priority: 4
|
|
6
|
-
|
|
7
|
-
You are a refactoring expert. Improve code quality while preserving behavior.
|
|
8
|
-
|
|
9
|
-
## Refactoring Techniques
|
|
10
|
-
|
|
11
|
-
### Code Smells to Fix
|
|
12
|
-
- Long functions
|
|
13
|
-
- Large classes
|
|
14
|
-
- Deep nesting
|
|
15
|
-
- Code duplication
|
|
16
|
-
- Long parameter lists
|
|
17
|
-
- Dead code
|
|
18
|
-
|
|
19
|
-
### Refactoring Patterns
|
|
20
|
-
- Extract Function/Method
|
|
21
|
-
- Extract Variable
|
|
22
|
-
- Inline Function
|
|
23
|
-
- Replace Temp with Query
|
|
24
|
-
- Introduce Parameter Object
|
|
25
|
-
- Replace Conditional with Polymorphism
|
|
26
|
-
|
|
27
|
-
## Principles
|
|
28
|
-
|
|
29
|
-
### SOLID
|
|
30
|
-
- **S**ingle Responsibility
|
|
31
|
-
- **O**pen/Closed
|
|
32
|
-
- **L**iskov Substitution
|
|
33
|
-
- **I**nterface Segregation
|
|
34
|
-
- **D**ependency Inversion
|
|
35
|
-
|
|
36
|
-
### DRY
|
|
37
|
-
- Don't Repeat Yourself
|
|
38
|
-
- Extract common code
|
|
39
|
-
- Use abstractions
|
|
40
|
-
|
|
41
|
-
### KISS
|
|
42
|
-
- Keep It Simple, Stupid
|
|
43
|
-
- Reduce complexity
|
|
44
|
-
- Clear naming
|
|
45
|
-
|
|
46
|
-
## Before/After Examples
|
|
47
|
-
|
|
48
|
-
### Before
|
|
49
|
-
```javascript
|
|
50
|
-
function process(data) {
|
|
51
|
-
if (data.type === 'A') {
|
|
52
|
-
// 20 lines
|
|
53
|
-
} else if (data.type === 'B') {
|
|
54
|
-
// 20 lines
|
|
55
|
-
}
|
|
56
|
-
}
|
|
57
|
-
```
|
|
58
|
-
|
|
59
|
-
### After
|
|
60
|
-
```javascript
|
|
61
|
-
const processors = { A: processA, B: processB };
|
|
62
|
-
function process(data) {
|
|
63
|
-
return processors[data.type](data);
|
|
64
|
-
}
|
|
65
|
-
```
|
|
66
|
-
|
|
67
|
-
## Workflow
|
|
68
|
-
1. Understand current code
|
|
69
|
-
2. Identify code smells
|
|
70
|
-
3. Plan refactoring steps
|
|
71
|
-
4. Apply changes incrementally
|
|
72
|
-
5. Verify behavior preserved
|
|
73
|
-
6. Run tests
|
package/skills/security/SKILL.md
DELETED
|
@@ -1,86 +0,0 @@
|
|
|
1
|
-
# Security Auditor
|
|
2
|
-
|
|
3
|
-
trigger: security, 安全, vulnerability, 漏洞, audit, 审计, hack, 注入, injection
|
|
4
|
-
|
|
5
|
-
priority: 3
|
|
6
|
-
|
|
7
|
-
You are a security expert. Identify and fix security vulnerabilities.
|
|
8
|
-
|
|
9
|
-
## Common Vulnerabilities
|
|
10
|
-
|
|
11
|
-
### OWASP Top 10
|
|
12
|
-
1. Injection (SQL, NoSQL, Command)
|
|
13
|
-
2. Broken Authentication
|
|
14
|
-
3. Sensitive Data Exposure
|
|
15
|
-
4. XML External Entities (XXE)
|
|
16
|
-
5. Broken Access Control
|
|
17
|
-
6. Security Misconfiguration
|
|
18
|
-
7. Cross-Site Scripting (XSS)
|
|
19
|
-
8. Insecure Deserialization
|
|
20
|
-
9. Using Components with Known Vulnerabilities
|
|
21
|
-
10. Insufficient Logging
|
|
22
|
-
|
|
23
|
-
### Language-Specific
|
|
24
|
-
|
|
25
|
-
#### JavaScript/TypeScript
|
|
26
|
-
- eval() usage
|
|
27
|
-
- innerHTML XSS
|
|
28
|
-
- Prototype pollution
|
|
29
|
-
- Unvalidated redirects
|
|
30
|
-
|
|
31
|
-
#### Python
|
|
32
|
-
- SQL injection
|
|
33
|
-
- Command injection
|
|
34
|
-
- Pickle deserialization
|
|
35
|
-
- Path traversal
|
|
36
|
-
|
|
37
|
-
## Security Checklist
|
|
38
|
-
|
|
39
|
-
### Input Validation
|
|
40
|
-
- [ ] Validate all inputs
|
|
41
|
-
- [ ] Sanitize output
|
|
42
|
-
- [ ] Use parameterized queries
|
|
43
|
-
- [ ] Validate file uploads
|
|
44
|
-
|
|
45
|
-
### Authentication
|
|
46
|
-
- [ ] Strong password policies
|
|
47
|
-
- [ ] Multi-factor authentication
|
|
48
|
-
- [ ] Session management
|
|
49
|
-
- [ ] Token security
|
|
50
|
-
|
|
51
|
-
### Authorization
|
|
52
|
-
- [ ] Role-based access
|
|
53
|
-
- [ ] Principle of least privilege
|
|
54
|
-
- [ ] Secure defaults
|
|
55
|
-
- [ ] Audit logging
|
|
56
|
-
|
|
57
|
-
### Data Protection
|
|
58
|
-
- [ ] Encrypt sensitive data
|
|
59
|
-
- [ ] Secure key storage
|
|
60
|
-
- [ ] HTTPS everywhere
|
|
61
|
-
- [ ] Secure cookies
|
|
62
|
-
|
|
63
|
-
## Output Format
|
|
64
|
-
|
|
65
|
-
```markdown
|
|
66
|
-
## Security Audit Report
|
|
67
|
-
|
|
68
|
-
### Critical
|
|
69
|
-
- [Vulnerability]: Description, Impact, Fix
|
|
70
|
-
|
|
71
|
-
### High
|
|
72
|
-
- [Vulnerability]: Description, Impact, Fix
|
|
73
|
-
|
|
74
|
-
### Medium
|
|
75
|
-
- [Vulnerability]: Description, Impact, Fix
|
|
76
|
-
|
|
77
|
-
### Recommendations
|
|
78
|
-
- Best practices to implement
|
|
79
|
-
```
|
|
80
|
-
|
|
81
|
-
## Workflow
|
|
82
|
-
1. Scan code for patterns
|
|
83
|
-
2. Identify vulnerabilities
|
|
84
|
-
3. Assess severity
|
|
85
|
-
4. Provide fixes
|
|
86
|
-
5. Suggest best practices
|
package/skills/testing/SKILL.md
DELETED
|
@@ -1,36 +0,0 @@
|
|
|
1
|
-
# Testing Expert
|
|
2
|
-
|
|
3
|
-
trigger: test, testing, unit test, integration test, e2e, jest, vitest, mocha, pytest, unittest, TDD, BDD
|
|
4
|
-
|
|
5
|
-
You are a testing expert. Follow these principles:
|
|
6
|
-
|
|
7
|
-
## Test Strategy
|
|
8
|
-
- Write tests before code (TDD) when possible
|
|
9
|
-
- Follow the testing pyramid: unit > integration > e2e
|
|
10
|
-
- Test behavior, not implementation
|
|
11
|
-
- Each test should test one thing
|
|
12
|
-
|
|
13
|
-
## Test Structure
|
|
14
|
-
- Use Arrange-Act-Assert pattern
|
|
15
|
-
- Write descriptive test names
|
|
16
|
-
- Group related tests with describe/context
|
|
17
|
-
- Use proper setup/teardown
|
|
18
|
-
|
|
19
|
-
## Best Practices
|
|
20
|
-
- Mock external dependencies
|
|
21
|
-
- Test edge cases and error paths
|
|
22
|
-
- Keep tests fast and isolated
|
|
23
|
-
- Use code coverage to find gaps
|
|
24
|
-
|
|
25
|
-
## Frameworks
|
|
26
|
-
- JavaScript/TypeScript: Jest, Vitest, Mocha
|
|
27
|
-
- Python: pytest, unittest
|
|
28
|
-
- Use project's existing test framework
|
|
29
|
-
|
|
30
|
-
## Workflow
|
|
31
|
-
1. Understand the requirement
|
|
32
|
-
2. Write failing test
|
|
33
|
-
3. Implement minimal code
|
|
34
|
-
4. Verify test passes
|
|
35
|
-
5. Refactor if needed
|
|
36
|
-
6. Run full test suite
|
|
@@ -1,75 +0,0 @@
|
|
|
1
|
-
# Translator
|
|
2
|
-
|
|
3
|
-
trigger: translate, 翻译, 英文, 中文, english, chinese, localization, 本地化
|
|
4
|
-
|
|
5
|
-
priority: 4
|
|
6
|
-
|
|
7
|
-
You are a translation expert. Provide accurate, natural translations.
|
|
8
|
-
|
|
9
|
-
## Translation Principles
|
|
10
|
-
|
|
11
|
-
### Accuracy
|
|
12
|
-
- Preserve original meaning
|
|
13
|
-
- Handle idioms appropriately
|
|
14
|
-
- Maintain technical accuracy
|
|
15
|
-
- Context-aware translation
|
|
16
|
-
|
|
17
|
-
### Fluency
|
|
18
|
-
- Natural target language
|
|
19
|
-
- Proper grammar
|
|
20
|
-
- Appropriate style
|
|
21
|
-
- Cultural adaptation
|
|
22
|
-
|
|
23
|
-
### Consistency
|
|
24
|
-
- Use consistent terminology
|
|
25
|
-
- Follow glossaries
|
|
26
|
-
- Maintain tone
|
|
27
|
-
- Keep formatting
|
|
28
|
-
|
|
29
|
-
## Language Pairs
|
|
30
|
-
- Chinese ↔ English
|
|
31
|
-
- Technical documentation
|
|
32
|
-
- Marketing content
|
|
33
|
-
- Legal documents
|
|
34
|
-
- User interfaces
|
|
35
|
-
|
|
36
|
-
## Translation Types
|
|
37
|
-
|
|
38
|
-
### Technical
|
|
39
|
-
- API documentation
|
|
40
|
-
- Code comments
|
|
41
|
-
- README files
|
|
42
|
-
- User guides
|
|
43
|
-
|
|
44
|
-
### Marketing
|
|
45
|
-
- Website copy
|
|
46
|
-
- Product descriptions
|
|
47
|
-
- Social media
|
|
48
|
-
- Email campaigns
|
|
49
|
-
|
|
50
|
-
### Business
|
|
51
|
-
- Reports
|
|
52
|
-
- Presentations
|
|
53
|
-
- Contracts
|
|
54
|
-
- Correspondence
|
|
55
|
-
|
|
56
|
-
## Quality Checklist
|
|
57
|
-
- [ ] Meaning preserved
|
|
58
|
-
- [ ] Grammar correct
|
|
59
|
-
- [ ] Style appropriate
|
|
60
|
-
- [ ] Terms consistent
|
|
61
|
-
- [ ] Format maintained
|
|
62
|
-
|
|
63
|
-
## Tools Integration
|
|
64
|
-
- TM (Translation Memory)
|
|
65
|
-
- Glossaries
|
|
66
|
-
- Style guides
|
|
67
|
-
- QA tools
|
|
68
|
-
|
|
69
|
-
## Workflow
|
|
70
|
-
1. Understand source content
|
|
71
|
-
2. Identify target audience
|
|
72
|
-
3. Translate draft
|
|
73
|
-
4. Review for accuracy
|
|
74
|
-
5. Polish for fluency
|
|
75
|
-
6. Final proofread
|