Restructure GDATP system prompt

Oleksandr Pysaryukrequested to merge
opysaryuk-main-patch-67e2 into main

Type of Change

  • New feature
  • Bug fix
  • Documentation update
  • Style guide or terminology update
  • Configuration change
  • Other (please describe)

Related Issues

Related to Align GDATP Japanese specifications with tech d... (#17 - closed)

Changes Made

See verbose description of changes to system prompt in this comment on issue 17: #17 (comment 3017347801)

Testing

  • Tested locally
  • Verified with sample translations
  • Checked against style guides
  • Other (please describe)
  • Not tested. We are dealing with non deterministic behaviour of AI. To test, full eval would be needed. I suggest we test the new prompt by using it

Changelog Entry

  • Changelog entry added to CHANGELOG.md
  • Entry is in the [Unreleased] section
  • Used appropriate category (Added/Changed/Fixed/Deprecated/Removed/Security)

Changelog Preview 

## [Unreleased]
- Streamlined system prompt: removed product module, consolidated from 6 sections to 2, simplified resource loading and validation

A bit more verbose summary that I am not adding to changelog:

### Changed

- Restructured system prompt from 6 sections to 2 (Mission and approach, Translation workflow)
- Simplified resource loading to single checklist with specific file paths
- Converted abstract validation criteria to concrete checkboxes
- Clarified translation scope for mixed-content files (existing translations + new English)

### Removed

- Product Translation Module
- Critical Success Metrics section (unmeasurable percentages)
- Supported Languages tone descriptions (redundant with style guides)
- Error Handling section
- Motivational closing statement

Checklist

  • Code follows project style guidelines
  • Documentation has been updated (if applicable)
  • Changelog entry has been added
  • No breaking changes (or documented if intentional)
  • Commit messages follow conventional commit format
  • All CI/CD checks pass

Additional Notes

Note: Merge requests without a changelog entry will trigger a warning in CI/CD. Please add one before merging to main.

For detailed changelog guidelines, see .gitlab/RELEASE.md.

Edited by Oleksandr Pysaryuk

Merge request reports