Vietnamese Academic Thesis Writer (Master's Level)

Overview

This skill guides writing chapters of master's-level essays, theses, and dissertations in Vietnamese following a professional, formal academic style with properly formatted citations.

When to Use

Activate this skill when the user requests Vietnamese academic content at master's level, including but not limited to:

• Writing a specific chapter (e.g., "write Chapter 2 theoretical background")
• Writing a section/subsection within a chapter (e.g., "write section 3.2 system architecture")
• Writing custom content on request (e.g., "write a comparison of TF-IDF and BM25")
• Editing / improving existing academic content
• Creating or editing a references list
• Writing research reports or graduation projects to academic standards

Operating Principles

IMPORTANT: This skill writes exactly what the user requests. Do NOT write the entire thesis or add sections the user did not ask for.

Workflow:

1. Identify the request: The user specifies which chapter, section, or content to write.
2. Read

   citation.md

   (critical — do this FIRST): Look for a centralized citation file (e.g.,

   docs/report/citation.md

   or similar path). This file is the single source of truth for all references across all chapters. From it:
   • Find the last citation number

     [M]

     — new references start from

     [M+1]

     .
   • Identify existing references to reuse their numbers (do NOT create duplicates).
3. Scan context of existing chapters: If previous chapters exist, read them to:
   • Note terms already introduced bilingually — do not re-introduce them, use the abbreviation.
   • Ensure consistent tone and style with previous chapters.
4. Gather technical context: Read PRDs, technical docs, source code (if available) to understand the content accurately.
5. Write only the requested section: Apply all rules below. Do NOT add a per-chapter references list — all references go to

   citation.md

   .
6. Update

   citation.md

   : After writing, append any new references to

   citation.md

   with correct numbering

   [M+1]

   ,

   [M+2]

   , etc. Update the mapping table if one exists.
7. Review: Run the checklist before returning the result.

Trigger Keywords

tiểu luận

luận văn

thạc sĩ

khóa luận

chương

tổng quan

cơ sở lý thuyết

phương pháp nghiên cứu

academic

thesis

dissertation

báo cáo nghiên cứu

đồ án tốt nghiệp

viết chương

viết mục

viết phần

MANDATORY RULES

Rule 1: Language and Tone

Strict compliance required:

1. Point of view: Use third person or passive voice. NEVER use first person ("tôi", "chúng tôi", "em", "nhóm tác giả"). Instead use: "đề tài", "hệ thống", "nghiên cứu này", "tác giả".

2. Formal tone: Use scientific, precise language. Avoid colloquial, informal, or emotionally expressive words.

3. Bilingual Vietnamese-English for technical terms: When mentioning a technical term for the first time, ALWAYS write it in Vietnamese followed by the English equivalent in parentheses, plus the abbreviation if applicable.

Standard patterns:

Truy hồi thông tin (Information Retrieval — IR)
Xử lý Ngôn ngữ Tự nhiên (Natural Language Processing — NLP)
Mô hình Không gian Vector (Vector Space Model — VSM)
Tần suất thuật ngữ — Tần suất nghịch đảo tài liệu (Term Frequency — Inverse Document Frequency, TF-IDF)
Độ tương đồng cosine (Cosine Similarity)
Tách từ (word segmentation)
Từ dừng (stopwords)

4. Subsequent mentions: May use the abbreviation introduced at first occurrence.

Correct example:

Truy hồi thông tin (Information Retrieval — IR) là lĩnh vực nghiên cứu...
Trong phạm vi đề tài, hệ thống IR được thiết kế dựa trên...

Incorrect example:

❌ "Tôi sẽ xây dựng hệ thống tìm kiếm..."
❌ "Chúng ta cần phải sử dụng TF-IDF..." (not introduced yet)
❌ "Cái này rất quan trọng vì..."

Rule 2: Chapter Structure

Each chapter MUST follow a hierarchical numbering system:

# CHƯƠNG N. CHAPTER TITLE (UPPERCASE)

## N.1. Level 1 heading

### N.1.1. Level 2 heading

#### N.1.1.1. Level 3 heading (if needed)

Numbering rules:

• Chapter:

  CHƯƠNG 1

  ,

  CHƯƠNG 2

  , ...
• Level 1:

  1.1.

  ,

  1.2.

  ,

  1.3.

  , ...
• Level 2:

  1.1.1.

  ,

  1.1.2.

  , ...
• Level 3:

  1.1.1.1.

  (limit usage — only when truly necessary)

Chapter titles: ALL UPPERCASE. Section titles: Capitalize first letter, rest in lowercase.

Rule 3: Citations and References

Use IEEE citation style (numbers in square brackets):

1. In-text: Number as

   [1]

   ,

   [2]

   ,

   [3]

   , ... in order of first appearance.

2. Citation placement: Immediately after the cited content, before the period.

In-text citation patterns:

Theo nghiên cứu của Manning và cộng sự [2], bài toán truy hồi thông tin...
Mô hình Vector Space Model được đề xuất bởi Salton (1975) [3].
Tách từ tiếng Việt là bước tiền xử lý bắt buộc [7].

3. Centralized references file (

   citation.md

   ): ALL references are stored in a single file (e.g.,

   docs/report/citation.md

   ), NOT at the end of each chapter. This is the single source of truth for citation numbering across the entire document.

   Why centralized? Scanning multiple chapter files for the last citation number is error-prone and slow. A single file makes it easy to:

   • Check the last number

     [M]

     instantly
   • Reuse existing references without duplicating
   • Maintain consistency across all chapters

   Format — IEEE style, compact (NO blank lines between entries):

   [1] Author_Name, "Paper title," _Journal/Conference Name_, vol. X, no. Y, pp. ZZ–ZZ, Year.
   [2] Author_Name, _Book Title_, Publisher, Year.
   [3] Author_Name, "Report title," _Organization Name_, Year.
   

   Formatting rules for

   citation.md

   :
   • Each

     [N]

     entry on its own line, immediately followed by the next — no blank lines between entries.
   • One blank line only after the heading

     # TÀI LIỆU THAM KHẢO

     and before the optional mapping table.
   • Keep entries compact to make it easy to scan the last number

     [M]

     .

   Optional mapping table:

   citation.md

   may include a

   ---

   separator followed by a table mapping each

   [N]

   to the chapters that cite it. Update this table when adding new references or writing new chapters.

4. IMPORTANT: Citation number

   [N]

   in the chapter text MUST match EXACTLY with

   [N]

   in

   citation.md

   . Review everything for consistency when finished.

5. CROSS-CHAPTER CONTINUITY (most important rule):

   Mandatory procedure:

   • Step 1: Read

     citation.md

     to find the last citation number

     [M]

     .
   • Step 2: When the current chapter needs a reference that already exists in

     citation.md

     , reuse that number — do NOT create a new entry.
   • Step 3: When the current chapter needs a NEW reference not yet in

     citation.md

     , assign

     [M+1]

     ,

     [M+2]

     , etc. and append them to

     citation.md

     after writing the chapter.

   Example:

   citation.md has [1] through [10]
   → Chapter 4 reuses [4], [5], [9] and adds new [11], [12]
   → After writing, append [11] and [12] to citation.md
   → citation.md now has [1] through [12]
   

   If

   citation.md

   does not exist (e.g., first chapter), create it and start from

   [1]

   .

   Chapter files should NOT contain a "Tài liệu tham khảo" section at the end. All references live in

   citation.md

   only.

Rule 4: Paragraphs and Argumentation

1. Minimum 3–5 sentences per paragraph. Each paragraph should focus on ONE main idea.

2. Paragraph argumentation structure:

   • Topic sentence → Supporting evidence / elaboration → Concluding / transition sentence

3. Paragraph linking: Use formal transition words/phrases:

- Opening: "Trong bối cảnh...", "Với sự phát triển của..."
- Addition: "Bên cạnh đó,", "Ngoài ra,", "Hơn nữa,"
- Contrast: "Tuy nhiên,", "Mặc dù vậy,", "Ngược lại,"
- Result: "Do đó,", "Vì vậy,", "Từ đó,"
- Enumeration: "Thứ nhất,", "Thứ hai,", "Cuối cùng,"
- Example: "Cụ thể,", "Chẳng hạn,", "Ví dụ,"

4. When listing multiple points: Use the pattern "Thứ nhất, ... Thứ hai, ... Thứ ba, ..." with each part starting in bold, followed by a detailed explanation.

Rule 5: Tables and Mathematical Notation

1. Tables: Use Markdown tables for comparisons, technical specifications.

2. Mathematical notation: Use Unicode characters when writing in Markdown:

Set notation: D = {d₁, d₂, ..., dₙ}
Subset: R ⊆ D
Calculation: w(t,d) = tf(t,d) × log(N/df(t))

3. Complex formulas: Present on separate lines, clearly explain each symbol.

Rule 6: Scope and Limitations

When writing the scope and limitations section, you MUST:

1. Categorize clearly by aspects: language, data, algorithms, architecture, evaluation, security.

2. Scope: State clearly WHAT is in scope, using bullet points.

3. Limitations: Present honestly WHAT is NOT covered and why — demonstrating academic self-awareness. This is not a weakness but scientific honesty.

STANDARD CHAPTER STRUCTURE

Chapter 1: OVERVIEW

1.1. Introduction
  1.1.1. Research background (why is this topic important?)
  1.1.2. Problem statement (what is the specific problem?)
  1.1.3. Challenges (domain-specific difficulties?)
  1.1.4. Modern trends and the topic's position
1.2. Objectives
  1.2.1. General objective (1 concise sentence)
  1.2.2. Specific objectives (3-5 sub-objectives, numbered)
1.3. Scope and limitations
  1.3.1. Research scope
  1.3.2. Limitations

Chapter 2: THEORETICAL BACKGROUND

2.1. Foundational concepts (formal definitions)
2.2. Related models / algorithms
  2.2.1. Model A (theory + formulas)
  2.2.2. Model B
2.3. Technologies used
  2.3.1. Framework / Library A
  2.3.2. Framework / Library B
2.4. Related work

Chapter 3: METHODOLOGY / SYSTEM DESIGN

3.1. Overall research methodology
3.2. System architecture (overview diagram)
3.3. Detailed design
  3.3.1. Module A
  3.3.2. Module B
3.4. Data processing flow
3.5. API / Interface design

Chapter 4: EXPERIMENTS AND RESULTS

4.1. Experimental environment
4.2. Dataset
4.3. Evaluation methods
4.4. Experimental results
  4.4.1. Quantitative results (tables, charts)
  4.4.2. Qualitative results (analysis, observations)
4.5. Comparison and discussion

Chapter 5: CONCLUSIONS AND FUTURE WORK

5.1. Conclusions
5.2. Contributions
5.3. Limitations
5.4. Future work

REFERENCE EXAMPLE

Below is a sample demonstrating the correct writing style for a paragraph in the Overview chapter. Use this as a style reference:

### 1.1.1. Bối cảnh nghiên cứu

Trong bối cảnh bùng nổ thông tin số hiện nay, lượng dữ liệu phi cấu trúc
— đặc biệt là văn bản — đang tăng trưởng với tốc độ chưa từng có. Theo ước
tính của International Data Corporation (IDC), tổng lượng dữ liệu toàn cầu
đã đạt hơn 120 Zettabyte vào năm 2023 và được dự báo sẽ tiếp tục tăng gấp
đôi sau mỗi hai năm [1]. Trong đó, dữ liệu văn bản chiếm một tỷ trọng đáng
kể, bao gồm các bài báo trực tuyến, bài đăng trên mạng xã hội, blog, tài
liệu kỹ thuật và nhiều nguồn nội dung số khác.

Truy hồi thông tin (Information Retrieval — IR) là lĩnh vực nghiên cứu về
các phương pháp tìm kiếm, trích xuất và xếp hạng các tài liệu có liên quan
đến nhu cầu thông tin của người dùng từ một tập hợp tài liệu lớn [2].

Note the key characteristics of this sample:

• Starts with broad context, narrows down gradually
• Specific data with citation

  [1]

• Bilingual terminology: "Truy hồi thông tin (Information Retrieval — IR)"
• Scientific, formal tone — no personal emotion
• Long but coherent sentences, not convoluted

CHECKLIST BEFORE COMPLETION

After writing each chapter, REVIEW against this checklist:

• Citation numbers

  [N]

  in text match entries in

  citation.md

• New references have been appended to

  citation.md

  (with correct

  [M+1]

  numbering)
• No per-chapter references section — chapter file does NOT contain "Tài liệu tham khảo" at the end
• No duplicate references in

  citation.md

  — reused existing numbers where applicable
• Technical terms introduced with English equivalent + abbreviation at first occurrence
• No first person (tôi, chúng tôi, em, nhóm tác giả)
• Section numbering follows hierarchical system (N.N.N.)
• Each paragraph has at least 3 sentences, focused on 1 main idea
• Tables have clear titles
• No Vietnamese spelling errors (especially dấu hỏi/ngã tone marks)
• Tone consistent and formal throughout
• Scope/limitations section presented honestly, no hidden weaknesses
• Transition sentences between paragraphs and sections flow smoothly

COMMON MISTAKES TO AVOID

[5]

[5]

FINAL NOTES

• This skill applies to master's-level essays, theses, and dissertations at Vietnamese universities.
• The writing style is extracted from real samples that received high quality ratings.
• Can be combined with other skills (e.g.,

  api-documentation

  ,

  architecture

  ) for detailed technical chapters.