roger-genius-note-style

name: roger-genius-note-style description: >- Reusable formatting and typographic specification for Markdown knowledge notes. Defines headings, paragraphs, code blocks, diagrams, emphasis, and further reading rules. Intended to be referenced by other skills that produce note files (e.g., roger-genius-noteweaver).

When to Use

This skill is not invoked directly by users. It is referenced by other content-generation skills (such as roger-genius-noteweaver) that need a consistent formatting specification for Markdown knowledge notes.

When another skill states that it follows roger-genius-note-style, apply all rules below to every note file that skill produces (including both configuration notes and main body notes).

Headings

Do not add a top-level topic title. Begin directly with the first knowledge point as a level-1 heading (#). Each subsequent knowledge point should also start with a level-1 heading if it represents a major topic, or use sub-levels (##, ###) as needed for subtopics.
All headings must be short (typically no more than 5-8 words), directly naming the content without extra modifiers.

Paragraphs & Layout

Overview prefix: Every body paragraph must begin with "概述：" (the word "概述" in bold, followed by a colon).
Keep technical terms in English where standard; surround with Chinese explanations if the conversation language requires (by default, mixed Chinese-English is acceptable).
Use ordered or unordered lists as needed; list items do not require the overview prefix.

Code & Diagrams

All code examples must be in fenced code blocks with the correct language tag. Code should be runnable where possible and kept concise.
Diagrams: Any relationships, flows, architectures, etc. must be presented using Mermaid code blocks. Never use text descriptions in place of diagrams.

Emphasis

Key terms or important concepts can be highlighted using **bold**, code, or ==highlight==.
Use ==highlight== for particularly critical points that need attention.

Depth vs. Brevity

Always strive for "study depth + concise phrasing": convey the core essence with minimum sentences; avoid textbook-length prose.
If expansion is needed, layer information progressively, but each paragraph should generally not exceed 6 lines.

Example

Overly verbose: "Spring Boot is a rapid application development framework based on Spring. It simplifies setup through auto-configuration, starter dependencies, and embedded servers. Auto-configuration automatically configures Spring based on classpath dependencies, starter dependencies are convenient dependency descriptors, and embedded servers allow running without external deployment..."
Concise but deep: "Spring Boot simplifies Spring app building via ==auto-configuration== (classpath-based inference), starter dependencies (aggregated modules), and ==embedded containers== (no external deployment)."

Formatting Checklist

When a referencing skill finishes producing note files, verify:

Headings are short and start at # level (no top-level topic title)
Body paragraphs start with "概述："
Diagrams use Mermaid code blocks
Key points use bold / code / highlight as appropriate
Each note ends with a ## Further Reading section
Depth and brevity are balanced (no fluff, no placeholders)