Below is that ChatGPT response when I ask it to output the remembered formatting preferences I use so that I can ask it to "write me a wiki page on...".
ChatGPT Formatting Prompt
# Wiki Formatting Preferences
This page describes my preferred formatting style for creating wiki pages, especially when working with Federated Wiki and with ChatGPT or other AI tools. The goal is to keep pages small, readable on mobile, and strongly hypertext-oriented.
# Page Style
Wiki pages should usually be:
- Personal and opinionated, written in the first person where appropriate.
- Focused on a single named concept per page.
- Short enough to read comfortably on a mobile screen.
- Easy to fork, remix, and link to from other pages.
When working with ChatGPT, wiki content should be provided inside a fenced Markdown code block so it can be copied directly into Federated Wiki.
# Headings
- Use only level-one headings: `# Heading`.
- Do not use `##`, `###`, or deeper heading levels.
- Prefer several short sections over one huge block of text.
# Links
Internal wiki links:
- Use `Title` syntax for internal links.
- Keep link titles short and simple, for example `Vision Holders` instead of `Role: Vision Holders in the Project`.
- Prefer to create a separate page for any recurring concept or bit of jargon, then link to it.
External links:
- Use Federated Wiki style references like this:
- `- example.com 
`
- Place the external link at the end of the paragraph it supports.
- Remove the final period before the link and insert a space before the hyphen.
- Avoid classic Markdown link syntax like `[example](https://example.com)` inside the main text.
# Lists and Layout
- Use flat bullet lists only.
- Avoid nested or multi-level bullet lists.
- Keep each bullet short and clear.
- Break complex processes into multiple pages rather than deep lists.
Example:
- Consultation Workflow
- Design Criteria
- Agentic Specification
Each of these bullets should ideally correspond to its own small wiki page.
# Tables
- Do not use tables.
- If information feels like it wants to be in a table, split it into multiple short sections or bullet lists on separate pages.
# Jargon and Concepts
- Hypertext jargon is acceptable if it is a hyperlinked concept with its own wiki page.
- When introducing a new term, link it the first time using `Term Name`.
- Use the linked page to explain the term in simple language, suitable for mobile reading.
Examples of jargon that should have their own pages:
- `Agentic Specification`
- `Substrate`
- `Vision Holders`
- `Hitchhiker Platform`
# Metadata and Front Matter
- Metadata about the page (for example page type, status, perspective) can be written as simple lines near the top of the page.
- Example:
Page type: agentic specification
Status: work-in-progress
Perspective: personal
- If YAML or Yam metadata is used, keep it separate and minimal, and do not let it dominate the visible content.
# Working With ChatGPT
When asking ChatGPT to help draft or edit wiki content:
- Paste this entire page into the conversation so the assistant understands the formatting preferences.
- Ask the assistant to:
- Return wiki content inside a fenced Markdown code block.
- Use only `#` headings.
- Use `Title` for internal links.
- Use Federated Wiki style for external links.
- Avoid tables and nested bullet lists.
- Keep pages small and focused on a single concept.
# Page Purpose
This page exists as a reference for collaborators and AI tools so that everyone can follow the same formatting style when creating or editing wiki pages in this project.
-
# See