ChineseResearchLaTeX Content Migration Skill
This skill only does one thing: migrate the main content, references, etc., from old materials to the content layer of existing template projects in the current repository.
It is not a template development skill nor a public package refactoring skill. Any tasks that require modifying template source code, styles, skeleton files in
,
,
,
,
,
, profiles, styles, or build scripts should be transferred to
or the template development process of the corresponding product line.
Hard Boundaries
Must always comply with the following when processing tasks:
- Never modify any public package source code, template implementations, profiles, styles, scripts, or shared resources under
- Never modify any template styles, entry skeletons, wrappers, , , , , or Lua/Python build scripts under
- Only place content in the existing content layer locations of the target project
- If there is no suitable location in the existing template to accommodate the content, do not modify the template to fit it; clearly report "insufficient template locations, need template development skill intervention"
The default writable content layers in the current repository are only
(excluding
) and
.
Unless the configuration whitelist of this skill explicitly allows other paths in the future, all other paths are considered read-only.
Align with Current Repository Structure
This skill still needs to identify the target product line, but only to select the correct hosting project, not to judge "whether to modify
".
- NSFC: Select the appropriate
- SCI papers: Select
- Graduation theses: Select the closest
- Resumes: Select
Then map the main content from the old materials to the content files of these existing projects; by default, prioritize selecting the closest existing project rather than creating new or restructuring template structures.
Input Principles
Do not require users to organize inputs into a fixed protocol first. By default, accept and process any reasonable inputs, such as:
- A complete old project directory
- Multiple / / / / files
- PDFs, screenshots, images
- An existing template project path plus some migration target instructions
- A mix of multiple input types
If materials are incomplete, do not first ask for "standard input"; first determine the target product line, suitable hosting project, which content can be directly placed into
or
, and which requests have exceeded the content migration boundaries. Only request supplementary information if missing information will lead to incorrect placement of the main content.
Output Principles
Do not interpret the output as "arbitrary repository restructuring". The valid outputs of this skill are usually only:
- Migrate main content to of the target project
- Migrate references to of the target project
- Generate necessary migration instructions, risk warnings, and unplaced content lists
- Provide verification results after successful building
The following actions are beyond the boundaries of this skill: modifying template source code, fixing styles, restructuring wrappers /
/
/ README, and extracting public packages or沉淀 package-level capabilities. By default, treat users' original materials as read-only, and treat the target template as a read-only skeleton; only report style differences, do not modify them without permission.
Recommended Workflow
1. Identify Target Product Line and Hosting Project
First answer three questions: which product line does the user ultimately want to use, which existing project in the current repository is most suitable as the hosting container, and whether this task is "content migration" or has become "template development". If it has become template development, transfer it immediately and do not continue to pretend it is a content migration task.
2. Inventory Migratable Content
Extract directly reusable main content paragraphs, BibTeX, gaps that require manual confirmation, and over-limit requests that trigger template modification requirements from the input.
3. Perform Content Layer Mapping
Only perform mapping at the content layer:
- Old main content →
- Old references →
Do not interpret "mapping" as:
- Modifying chapter commands
- Modifying template title styles
- Modifying table of contents/cover/header/footer
- Modifying public package interfaces
4. Execute Migration
During execution, only allow overwriting target content files, creating new target content files (if the template has corresponding hosting locations), and writing or supplementing
files.
If a certain requirement can only be completed by modifying the template skeleton, do not continue to modify automatically; clearly mark the blocked location and reason, and recommend using
instead.
5. Official Entry Verification
After migration is completed, try to verify using the official entry of the corresponding product line as much as possible:
- NSFC:
python packages/bensz-nsfc/scripts/nsfc_project_tool.py build --project-dir <project path>
- SCI:
python packages/bensz-paper/scripts/paper_project_tool.py build --project-dir <project path>
- Thesis:
python packages/bensz-thesis/scripts/thesis_project_tool.py build --project-dir <project path>
- CV:
python packages/bensz-cv/scripts/cv_project_tool.py build --project-dir <project path> --variant all
If the build fails and the reason comes from template skeleton gaps, do not modify the template without permission; report truthfully.
Legacy CLI Positioning
and
are still retained, but only as backup entries for classic old/new directory migration. Even when using the legacy CLI, the hard boundaries in this document must still be followed: old projects can be read, new projects can only write to the content layer, and template protection cannot be bypassed via the CLI.
Inapplicable Scenarios
Do not directly use this skill for the following scenarios:
- Users want to "create a new template"
- Users want to "1:1 replicate old styles into the current repository"
- Users want to modify template entry or style files in ,
- Users want to add new template hosting locations, cover structures, table of contents structures, profiles, classes, styles
These should all be transferred to the template development pipeline.
Reference Materials
Prioritize reading this document. When details of the legacy CLI are needed, refer to:
references/config_guide.md
references/api_reference.md
When confirming boundaries, always follow the priorities:
- Only migrate content, do not modify template skeletons
- Only report style differences, do not modify them without permission