بنقرة واحدة
wiki-editing
Instructions and conventions for editing the GnollHack Wiki Markdown pages and handling images.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Instructions and conventions for editing the GnollHack Wiki Markdown pages and handling images.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Instructions for comparing monsters in GnollHackWiki with the GnollHack C code data structures (permonst) to spot mistakes in the documentation.
Instructions for comparing spells and spellbooks in GnollHackWiki with the GnollHack C code data structures (objclass and SPELL macro) to spot mistakes in the documentation.
Instructions for comparing artifacts in GnollHackWiki with the GnollHack C code data structures (artifact) to spot mistakes in the documentation.
Instructions for comparing regular object items (weapons, armor, tools, etc.) in GnollHackWiki with the GnollHack C code data structures (objclass) to spot mistakes in the documentation.
| name | wiki_editing |
| description | Instructions and conventions for editing the GnollHack Wiki Markdown pages and handling images. |
When editing or creating pages for the GnollHack Wiki, follow these conventions optimized for AI agents like Gemini 3.5 Flash.
.md) as the page title. Never start a page with an H1 (#) or H2 (##) heading that is identical to the page's name (the filename without extension). In such cases, omit the heading completely, as it is implied and provided to the page from the filename. Use a single H1 heading (#) on the very first line ONLY if you need a custom title that differs from the filename (e.g., incorrect filename casing or special pages like the home page). In most cases, an H1 is not needed.H2 (##) and lower for all other section headings.H1 at the very beginning of the file). This explicitly includes H2 (##) and H3 (###) headings, which must have an empty line above and below them./Monsters/, /Items/) to prevent naming conflicts and organize content.>) starting with a 👉 emoji, followed by bold text (e.g., > 👉 **This is the ingress.**).-) for Markdown lists instead of an asterisk (*) by default.[[Alias|Page Name]] or [[Page Name]]. IMPORTANT: The alias always comes first and the page name comes last![[#Section Name]] or [[Page Name#Section Name]]) to link to sections in Gollum wikis. It is best to avoid section links entirely. If a section link is absolutely needed, you must use standard Markdown link syntax: [Alias](#section-anchor). The section anchor must be:
-).-- becomes -).## 🪨 Plane of Earth, the section link should be [Plane of Earth](#plane-of-earth).[[/Items/potion of healing]], [[/Artifacts/Vorpal Blade]]) must start with a slash (/), regardless of whether the source file is located in the root directory or in a subdirectory. If a link points to a page in the root directory (e.g., [[Home]]), it should not start with a slash, unless the source document is in a subdirectory (e.g. Rooms/), in which case the link targeting the root page must start with a leading slash (e.g. [[/Rings]] or [[/Weapons]])..md extension in wikilinks./Items/, /Monsters/, /Dungeon/, /Conducts/). Only the final page name itself is case-insensitive in Gollum.[[/Roles/Priest]] instead of [[Priest|/Roles/Priest]]). Use an alias only when the link text must differ from the page name, such as to use the plural form of the page name (e.g., [[Priests|/Roles/Priest]]). Remember: Alias comes first, Page Name comes last.[[/Rooms/Shops/General store]] instead of [[General store|/Rooms/Shops/General store]][[/Rooms/shop]] instead of [[shop|/Rooms/Shop]][[/rings]] instead of [[rings|/Rings]] (from a subdirectory)[[weapons]] instead of [[weapons|Weapons]] (from the root directory)-) in Markdown filenames represent literal dashes, unlike GitHub wikis where they represent spaces. A space in a filename denotes a space (and is represented as %20 in URLs). Therefore, when linking to a page with a dash in its filename, keep the dash in the wikilink; do not replace it with a space.[[/Items/potion of healing]].[[/Items/Potion of healing]] instead of [[Potion of healing|/Items/potion of healing]].[[/Monsters/Nymphs]]).[[/Items/Gold]] or [[gold|/Items/Gold piece]]). Always leave the word "gold" or "gold pieces" as plain text.|) inside Markdown tables, because pipes can conflict with the table's column delimiters in some Markdown parsers. Always use simple wikilinks without aliases (e.g., [[/Items/potion of healing]]) in tables. If the display text needs to be lowercase, simply write the link path in lowercase (e.g., [[/Monsters/gnome king]] instead of [[gnome king|/Monsters/Gnome king]]); Gollum is case-insensitive for linking but will display exactly the casing you type in the link./uploads/ directory. Match the subdirectory structure of the document (e.g., an image for /Races/Dwarf.md goes to /uploads/Races/Dwarf/image.webp).. Any spaces in the image path must be URL-encoded as %20 (e.g., )./gollum/ or /.gollum/ directories. These are strictly reserved for wiki software functions and website files.--- or ***) anywhere in the wiki. They are not needed in Markdown documents.> [!IMPORTANT], > [!NOTE]). Use standard Markdown blockquotes with bold text and colored unicode icons as the best alternatives:
> ℹ️ **Note:** This is a note.> 💡 **Tip:** This is a tip.> 📢 **Important:** This is important.> ⚠️ **Warning:** This is a warning.> 🛑 **Caution:** This is caution.<ul> and <li> tags). Avoid using them in Markdown files, including inside tables. Instead, represent list items in tables using Unicode bullets (e.g., • ) separated by HTML line breaks (<br />).Level >= 3 or Luck >= 0), format them as plain text. Do not use KaTeX for simple expressions.$ and end with $.$P = \frac{1}{10 + 2 \times G \times A}$Luck >= 0 or 1 in 10STR18(x) (e.g., STR18(100)) should be formatted as 18/xx (e.g., 18/100).STR19(x) (e.g., STR19(25)) should be formatted strictly as x (e.g., 25). Do not write 125 or 19/25.Alt+p). Do not mention an extended command (e.g., #pray) for a game command if there is a keyboard shortcut available for it.e, Shift+e, Alt+e, Alt+Shift+e). A normal key is written as a single lowercase letter (e.g. e). A Shift key shortcut is written as Shift+lowercase letter (e.g. Shift+e). Apply this format to all modifier key combinations within the game: Ctrl shortcuts (e.g. Ctrl+e), Alt shortcuts (e.g. Alt+e), and combined modifiers (e.g. Ctrl+Shift+e, Alt+Shift+e).Ctrl+Alt+Shift+key, Alt+Shift+e, Ctrl+Shift+c, Ctrl+Alt+i).Ctrl+Shift+P, Ctrl+I, Ctrl+B, Ctrl+Shift+V, Win+R, Alt+Tab).When editing or creating headings for pages, always use appropriate Unicode icons/emojis immediately after the heading markers (## or ### ) to maintain a rich, consistent visual aesthetic across the wiki. Use this verified list as a guide:
📖 or ℹ️🌍🏁🎖️🏆🌟🕹️⚙️❓💻 or 📱 or 🖥️🛠️ or 🧑💻📋📋 or ✅📄 or 🔒🏆 or 🎖️ or 💯💡💪 or 🧬💪🎯 or 🤸🔋 or 🪵🧠📖 or 🦉✨ or 👑📈 or 🌟❤️🔮 or 💙⚖️⚖️ or 😇😐 or ☯️😈 or 🔥 or 🌀🏺🪓🦴🧪🛡️🥋⛪🗡️🏹⚔️📸⚡🪄🧑⛏️🧝🧙🐺👹🗺️🔀🧭🚩ℹ️🚪🌉⛏️🧩 or 🪨🌀📜 or 🕯️🌌🪜🔥 or 😈🏪 or 🏛️⛪ or 🕯️ or 🛐 or 🩸⛲🪤 or 🕳️ or 🕸️ or ⚠️🚶 or 🏃 or 👟🎒 or 🏋️🐾 or 🐶 or 🐱🤝 or 💂 or 💰⚔️ or 🗡️🏹 or 🎯👹 or 🐉 or 💀 or 👾👑 or 😈 or 💀🧙♂️🧛🐍🐐🪰😈🦠🐺👑🦖👁️ or 🤖👤🐣 or 🌱 or 📈👕 or 🛡️ or 🎒👕 or 🥋 or 🧥🛡️🪖🧥🧤🥾💪💍📿 or 🧿💎🔍 or 👁️🍏 or 🥩 or 🍞🍗 or 🍎🧪 or ⚗️🧪 or 💧💨 or 💥📜🪄📕 or 📖🛠️ or 🧰💎 or 🪨✨ or 👑🏁🧞 or ✨🔮 or 🧙✨ or ⚡🩹 or ❤️ or ➕💥 or 🔥 or ⚡👁️ or 🧪 or 🌀🩹 or 🤒🤢 or 🤒☠️ or 🤢🗿 or 🪨🐺💀 or 🖤 or ❌⭐ or 💛 or 👼🙈 or 🕶️🌀 or 💫🌈 or 🍄🪦 or 💀🎵 or 🔊 or 🎹🗣️ or 🎙️When formatting inline content, tables, lists, or callouts, use appropriate Unicode icons/emojis to maintain readability and visual distinction:
Alerts & Callouts (for blockquotes >):
ℹ️ (> ℹ️ **Note:** ...)💡 (> 💡 **Tip:** ...)📢 (> 📢 **Important:** ...)⚠️ (> ⚠️ **Warning:** ...)🛑 (> 🛑 **Caution:** ...)Document Structure:
👉 (> 👉 **Welcome...** at the top of a page)💡 (e.g., ## 💡 Conclusions)User Interface & Interaction Controls:
⌨️🖱️⚙️ or 🕹️ or 📱🖥️🔗Game Statuses & Indicators:
🟢 or ✅🟡 or 😐🔴 or ❌✅❌Inline Item & Ability Modifiers:
⭐ or 💛 or 👼💀 or 🖤 or 😈⚪🧬👕 or 🛡️ or 💍💎In-Text Alignment, Gender, & Role Modifiers:
⚖️ or 😇😐 or ☯️😈 or 🔥 or 🌀♂️♀️Economy & Value:
🪙 or 💰Arrows:
→ instead of ->← instead of <-When linking to or categorizing different types of articles (for instance, in lists or tables of contents), use the following Unicode icons to indicate the nature of the article. Note: These icons do not necessarily need to be inserted before each individual article link; they can instead be applied only to the overarching section heading for that group of articles.
🏗️ or 🧠 or 💡🎓 or 🏁📊 or 📖🛠️ or 🧑💻❓ or 🔧📋 or ✅📄 or ⚖️When referencing or comparing different games and NetHack variants, use the following Unicode icons:
🧙♂️ (Wizard)🐺 (Wolf)🪟 (Window)🧊 (3D Cube)🐙 (Octopus)😈 (Devil)🎲 (Dice)📱 (Mobile)🗝️ (Old Key)<sup> tag. For example, <sup>1</sup>.- <sup>1</sup> Footnote description.