mirror of
https://github.com/dong-nz/cv.git
synced 2026-11-23 00:20:40 +07:00
feat(resume): add version stamping and bilingual EN/VN PDF support
- Add version stamp footer 'Last updated: YYYY-MM-DD' to PDF - Implement bilingual support (English + Vietnamese) for resume PDF - Add Language type and *En optional fields to types - Add Vietnamese translations to profile, experience, projects data - resolveField utility for language-aware field resolution - Language-specific section labels (Experience/Kinh nghiệm, etc.) - --lang CLI arg: 'en' (default) or 'vi' - Output: resume.pdf (EN), resume-vi.pdf (VI) - Update CI workflow to generate and deploy both PDF versions - Add build:resume-all npm script - Update UI components (Hero, DownloadResume) for language selection - Add spec-v2-resume-future.md for deferred enhancements - Refactor spec-v2-resume-playwright.md (condense implementation notes)
This commit is contained in:
1 parent
26af25a39d
commit
0297c18bad
15 files changed
+395
-301
No files matched your search
@@ -0,0 +1,40 @@
|
||||
# Agent Rules
|
||||
|
||||
## 1. General Principles
|
||||
|
||||
- Understand the existing codebase before making changes.
|
||||
- Prefer simple, maintainable solutions over clever solutions.
|
||||
- Do not introduce unnecessary dependencies.
|
||||
- Do not rewrite working code unless there is a clear reason.
|
||||
- Preserve existing behavior unless the task explicitly requires a behavior change.
|
||||
- Follow the existing project architecture and coding conventions.
|
||||
- Keep changes small and focused on the requested task.
|
||||
|
||||
## 2. Before Making Changes
|
||||
|
||||
Before modifying code:
|
||||
|
||||
1. Inspect the relevant project structure.
|
||||
2. Identify the modules/classes/components affected.
|
||||
3. Read the existing implementation and related tests.
|
||||
4. Identify existing utilities that can be reused.
|
||||
5. Check whether similar functionality already exists.
|
||||
6. Understand the data flow before changing it.
|
||||
|
||||
Do not start coding based only on the user's description.
|
||||
|
||||
## 3. Change Workflow
|
||||
|
||||
1. **Investigate** — research the issue using the steps in Section 2.
|
||||
2. **Report** — present findings: root cause, affected files, proposed fix.
|
||||
3. **Confirm** — wait for user approval before applying any changes (code, config, docs, spec, or any file).
|
||||
4. **Execute** — apply the approved change, verify, then report results.
|
||||
|
||||
## 4. Conversation language
|
||||
|
||||
**IMPORTANT:** All responses are in Vietnamese. Source code and docs are in English.
|
||||
|
||||
## 5. Don't run the headless browser to verify.
|
||||
|
||||
It costs so much time for you to complete the verifying by headless browser.
|
||||
I will verify the result in a real browser and tell you if the change works.
|
||||
Reference in new issue
Block a user