菜单
Visual conventions, formatting rules, diagram palettes, callout syntax, text style, and quality checklist for all Nordic NeTEx Profile documentation. Self-contained — no external files needed.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Complete rules for writing conceptual Guides (guides/) in the Nordic NeTEx Profile. Covers section structure, tone, length, formatting, and cross-referencing. Self-contained — no external files needed.
Complete rules for writing Object documentation (objects/) and Frame documentation (frames/) in the Nordic NeTEx Profile. Includes section templates, table format, structure overview notation, and naming conventions. Self-contained — no external files needed.
Use this skill when creating, reviewing, or updating documentation for the Nordic NeTEx Profile. Routes to the correct sub-skill based on what you're writing (object, frame, guide). Start here for orientation.
Use this skill any time the user asks a question about the Nordic NeTEx Profile — elements, frames, objects, cardinality, references, profile differences (MIN vs NP), XML structure, or how to model a specific transport scenario. Always consult the ontology and the specific Table_/Description_ files before answering. Do not answer from general NeTEx knowledge; the Nordic Profile is a constrained subset and details matter.
| name | netex-nordic-doc-visual |
| description | Visual conventions, formatting rules, diagram palettes, callout syntax, text style, and quality checklist for all Nordic NeTEx Profile documentation. Self-contained — no external files needed. |
All documentation in the Nordic NeTEx Profile must follow these formatting rules.
Use the docsify flexible-alerts plugin syntax. Never use emoji-based callouts (> 💡 **Tip:**).
> [!TIP]
> Best practice or recommendation.
> [!NOTE]
> Important but non-critical information.
> [!WARNING]
> Common pitfalls or things to watch out for.
> [!TIP] for best practices> [!NOTE] for informational callouts> [!WARNING] with bullet points for grouped pitfalls (Object section 5c)Use Mermaid for relationship graphs, tree structures, and flowcharts.
Blue palette (always apply):
| Level | Color | Usage |
|---|---|---|
| Darkest | #0D47A1 | Top-level / root nodes |
#1565C0 | Primary containers / frames | |
#1976D2 | Collections / groups | |
#1E88E5 | Intermediate elements | |
#42A5F5 | Leaf objects | |
#64B5F6 | Sub-elements | |
| Lightest | #90CAF9 | External / secondary refs |
Apply colors: style NodeId fill:#1976D2,stroke:#1976D2,color:#fff
When to use SVG instead: If a Mermaid diagram becomes unclear (too many nodes, overlapping labels, complex layouts), create a hand-crafted SVG in assets/images/.
Store in assets/images/. Follow these conventions:
Layout:
width="100%" with viewBox="0 0 680 450" (responsive, standard canvas)role="img" for accessibility<title> and <desc> inside <svg>Color palette (dark-mode friendly):
| Role | Fill | Stroke | Text |
|---|---|---|---|
| Domain A (e.g. timetable) | rgb(60, 52, 137) | rgb(175, 169, 236) | rgb(206, 203, 246) |
| Domain B (e.g. stop registry) | rgb(8, 80, 65) | rgb(93, 202, 165) | rgb(159, 225, 203) |
| Frame outlines | none | rgba(222, 220, 209, 0.15) | rgb(194, 192, 182) |
| Intra-domain arrows | — | rgb(83, 74, 183) | — |
| Cross-domain arrows | — | rgb(15, 110, 86) | — |
Typography:
"Anthropic Sans", -apple-system, BlinkMacSystemFont, "Segoe UI", sans-seriftext-anchor: middleShapes:
rx="8" (boxes), rx="12" (frame containers)0.5stroke-dasharray="6 4")opacity="0.7"File naming: netex_<topic>_<variant>.svg
Show profile-specific XML side by side:
<!-- tabs:start -->
#### **MIN**
` ` `xml
<Line id="MIN:Line:1" version="1">...</Line>
` ` `
#### **NP**
` ` `xml
<Line id="NP:Line:100" version="1">...</Line>
` ` `
<!-- tabs:end -->
Tabs persist selection across pages (persist: true, sync: true).
<span class="badge train">Train</span>
<span class="badge bus">Bus</span>
<span class="badge metro">Metro</span>
<span class="badge tram">Tram</span>
<span class="badge ferry">Ferry</span>
<span class="badge plane">Air</span>
Colors are defined in the docsify theme configuration (see index.html). Do not reuse transport colors for UI state.
<span class="profile-level min">MIN</span>
<span class="profile-level np">NP</span>
<span class="badge status-required">Required</span>
<span class="badge status-optional">Optional</span>
<span class="badge status-new">New in v3</span>
<span class="badge status-changed">Changed</span>
| Convention | Example |
|---|---|
| Object link | [JourneyPattern](../JourneyPattern/Table_JourneyPattern.md) |
| Reference in table | [JourneyPattern](../JourneyPattern/Table_JourneyPattern.md/)@ref |
| Glossary crosslink | > *→ [Glossary](../../guides/Glossary/Glossary.md#objectname)* |
Always use relative paths. Always verify links resolve to existing files.
xml language tag for syntax highlighting📄 **Full example:** [Example_Topic.xml](Example_Topic.xml)<details>
<summary>Advanced: XPath validation rules</summary>
Content here...
</details>
Use for content that might overwhelm newcomers.
Before finalising any artifact: