Thesis chapter engineering
Skill lihongqing2001-gif/chinese-thesis-production-skills/skills/thesis-chapter-engineering
Evidence-first Codex skills for guided Chinese STEM thesis production
npx -y skills add lihongqing2001-gif/chinese-thesis-production-skills --skill thesis-chapter-engineeringAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Design, restructure, draft, or deepen Chinese STEM thesis chapters from verified project evidence and school conventions. Use when aligning a thesis outline with supervisor requirements, integrating methods into research chapters, rewriting a chapter from small papers or raw results, improving cross-chapter logic, removing AI-like process language, or closing methods-results-conclusions loops.
SKILL.md
3.5 KB, as published. Nobody here has run it
Thesis Chapter Engineering
Build chapters around research questions, not around available file types.
Before drafting
- Load
thesis.project.json, scope, terminology, and authority record. - Read current school rules and at least one accepted local exemplar for structure and presentation patterns. Do not copy wording.
- Load only verified evidence relevant to the chapter.
- Create a chapter contract using references/chapter-contract.md.
- Validate the contract before prose expansion.
Research-chapter pattern
Follow the school and supervisor decision. When methods are chapter-specific, prefer:
- Chapter introduction and research question.
- Materials/reagents relevant to this chapter.
- Sample preparation or computational setup.
- Characterization/evaluation methods with complete conditions.
- Results and discussion organized by claims and figures.
- Chapter summary containing only established conclusions.
Do not create an independent universal methods chapter when the confirmed thesis structure integrates methods into each research chapter.
Paragraph construction
For each analytical paragraph:
- State the observation and point to a figure/table/equation.
- Quantify the relevant comparison when data exist.
- Distinguish sample, condition, time, and panel.
- Give the explanation at the evidence-appropriate strength.
- Compare with verified literature when useful.
- State the consequence for the chapter question.
Avoid paper-by-paper lists in reviews. Organize by mechanism, method, scale, disagreement, or design variable.
Figure-led writing
Do not describe a group figure generically. Map every panel first, then write comparisons such as (a) versus (c) only when the actual panel identities and conditions are verified.
Route caption and figure quality work to thesis-figure-table-audit.
Language rules
Read references/language-and-logic.md. Remove production traces such as “PPT shows”, “small paper”, “provided later”, “current version”, or “the user supplied”. Replace them only with scientifically accurate source descriptions, not invented provenance.
Use concrete nouns. Replace vague umbrella terms with the actual object when the scope supports it, for example water/glycerol molecules, tobacco fibers, heating conditions, or mesoporous silica.
Cross-chapter closure
Before finalizing a chapter:
- verify methods cover every reported result;
- verify every retained figure/table is discussed;
- verify every conclusion appears in results;
- verify the next chapter follows from a stated unresolved question;
- verify abstract and final conclusions use the same sample mapping and evidence strength.
Tool
python scripts/validate_chapter_contract.py chapter-contract.json \
--project-root /path/to/project --report reports/chapter-contract.json
Read references/stem-chapter-patterns.md for introduction, review, experiment, simulation, and conclusion patterns.