github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 00:51:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #14802] Documentation best practice for Modelfile system prompts — HADS standard #71621

New Issue
Closed
opened 2026-05-05 02:15:19 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-05 02:15:19 -05:00
Owner
Copy Link

Originally created by @catcam on GitHub (Mar 12, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/14802

Wanted to flag an open standard that could help Ollama users write better system prompts and documentation: HADS — Human-AI Document Standard.

https://github.com/catcam/hads

The idea: Tag sections of your docs so the model knows what to read and skip:

  • **[SPEC]** — facts to extract (terse, bullet lists)
  • **[NOTE]** — human context (model can skip)
  • **[BUG]** — known failures + fixes (always read)

An AI manifest at the top makes it explicit. Works in Modelfile SYSTEM blocks, knowledge docs, any Markdown.

Especially useful for smaller models (7B-13B) — they don't have to reason about document structure, the manifest tells them exactly what matters.

Worth a mention in Ollama docs or community resources?

Originally created by @catcam on GitHub (Mar 12, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/14802 Wanted to flag an open standard that could help Ollama users write better system prompts and documentation: **HADS** — Human-AI Document Standard. https://github.com/catcam/hads **The idea:** Tag sections of your docs so the model knows what to read and skip: - `**[SPEC]**` — facts to extract (terse, bullet lists) - `**[NOTE]**` — human context (model can skip) - `**[BUG]**` — known failures + fixes (always read) An AI manifest at the top makes it explicit. Works in Modelfile `SYSTEM` blocks, knowledge docs, any Markdown. **Especially useful for smaller models** (7B-13B) — they don't have to reason about document structure, the manifest tells them exactly what matters. Worth a mention in Ollama docs or community resources?
GiteaMirror added the documentation label 2026-05-05 02:15:19 -05:00
GiteaMirror commented 2026-05-05 02:15:20 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 12, 2026):

Not really an ollama issue. You can create a PR to add it to Community Integrations, but since it's more of a general guidelines doc and not specific to ollama it's uncertain if it will be merged.

<!-- gh-comment-id:4049292129 --> @rick-github commented on GitHub (Mar 12, 2026): Not really an ollama issue. You can create a PR to add it to Community Integrations, but since it's more of a general guidelines doc and not specific to ollama it's uncertain if it will be merged.
GiteaMirror commented 2026-05-05 02:15:21 -05:00
Author
Owner
Copy Link

@catcam commented on GitHub (Mar 13, 2026):

Fair enough — you're right that it's not Ollama-specific. The use case I had in mind was Modelfile SYSTEM blocks and user-side knowledge docs, but that's general best practice territory rather than an Ollama integration request.

I'll look at the Community Integrations PR route. Thanks for the pointer.

<!-- gh-comment-id:4056575661 --> @catcam commented on GitHub (Mar 13, 2026): Fair enough — you're right that it's not Ollama-specific. The use case I had in mind was Modelfile `SYSTEM` blocks and user-side knowledge docs, but that's general best practice territory rather than an Ollama integration request. I'll look at the Community Integrations PR route. Thanks for the pointer.
GiteaMirror commented 2026-05-05 02:15:22 -05:00
Author
Owner
Copy Link

@catcam commented on GitHub (Mar 13, 2026):

In the meantime, published a case study with the concrete numbers: https://github.com/catcam/hads/blob/main/case-studies/polymarket-bot.md — in case it's useful for anyone finding this via search.

<!-- gh-comment-id:4056617250 --> @catcam commented on GitHub (Mar 13, 2026): In the meantime, published a case study with the concrete numbers: https://github.com/catcam/hads/blob/main/case-studies/polymarket-bot.md — in case it's useful for anyone finding this via search.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#71621
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?