Use when writing or rewriting tutorial-style blog posts for Migie's site, especially onboarding content for junior lab members. Apply Migie's preferred tutorial structure, tone, example formatting, and command annotation style so posts stay practical, concise, and consistent.
Use this skill when writing tutorial-style blog posts for Migie's site, especially posts aimed at new lab members.
Write posts that help a new student get unblocked quickly.
The priority is:
Do not write like a textbook, product manual, or generic AI tutorial.
Assume the reader is:
Default audience for these posts is junior lab members, not internet-general beginners and not senior experts.
Use a calm, direct, slightly friendly tone.
The target voice is:
Keep judgment clear, but lower unnecessary pressure.
Good pattern:
Avoid:
For tutorial posts, prefer this structure unless the topic strongly demands another:
For large topics, split into:
Use this pattern when it helps new readers separate “what I need today” from “what I can learn later”.
For command examples, prefer annotated code blocks.
Default style:
pwd # show current directory
ls -l # list files with details
cd .. # go to parent directory
Apply this to most executable examples in tutorial posts.
Use line-by-line comments when:
Do not force comments onto:
For config examples, comment key fields inline when useful:
Host hpc # local alias
HostName xx.xx.xx.xx # remote host
User username # login user
Prioritize:
If relevant, tie examples back to real research use cases such as:
Avoid:
If one option is the best default for beginners, recommend it directly.
When merging multiple older posts into one tutorial:
If older posts will later be deleted, ensure the new post contains all essential operational content before removing references.
Assume long tutorial posts may have an automatic table of contents in the site layout.
So:
h2 and h3 headingsEnd tutorial posts by making the reader’s next state explicit.
Good endings:
The post should leave the reader with a clear shortest useful next step.