AI Prompts — Knowledge Wiki

AI Prompts — Knowledge Wiki

Context Claude Needed to Do This Right

Before any implementation, Claude needed to read the memory files at:
~/.claude/projects/-Users-kcossabo-Documents-Coding-Container-Managment/memory/

Specifically:
– project_container_pipeline.md — the Gitea/Komodo workflow, compose.yml conventions, unRAID labels, known landmines
– project_komodo_containers.md — server inventory, IP ranges, bridge names, Komodo field gotchas

Without this context, Claude would generate generic compose files that don’t match the existing pipeline (wrong network names, wrong IP ranges, wrong Komodo field behavior).

Prompt That Worked: Initial Planning

“I am thinking through the documentation, outside of the AI context/memory.
Think wiki-like, file-based. I mount a NAS folder that text/MD files are created with AI at the end of a project. The ‘app’ uses the file store as backend for its presentation layer. I can go to knowledge.cossaboon.net and see what and when things were done, projects that provide value, search across them. AI prompts would be a key part of this as in 6 months this desktop app might be completely different and AI tools grown, and need the ‘institutional’ knowledge to live on.
Based on this present a solution that would meet these needs and anything else that would be of value.”

Prompt That Worked: Project Close / Wiki Entry Generation

At the end of any session, use this to generate the wiki entry:

“Generate a project knowledge entry for /Volumes/knowledge/docs/projects/[YYYY-MM-slug]/.
Create:
– index.md — overview, architecture, key decisions, outcome
– ai-prompts.md — the context Claude needed, prompts that worked, what to watch for
– lessons.md — what broke, what surprised, what to do differently

Use frontmatter with title, date, tags (pick from: spacedock, dockyard, dockofthebay, containers, infrastructure, media, documentation, ai-prompts), server, status, ip.
Then run: kcommit ‘[description of what was added]'”

What to Watch For

• Claude needs to read your memory files at session start to know your network conventions. If it suggests wrong IPs, bridge names, or Komodo field values, point it at the memory files.
• The kcommit alias only works if /Volumes/knowledge is mounted. If the NAS is unreachable, the commit will fail silently by landing in the wrong directory.
• Always generate the wiki entry at the end of the session, not the beginning — the lessons section won’t be complete until you’ve hit the problems.

About the Author

Kevin Cossaboon

A networking profesional located in Northren Virginia, USA. My hobbies are Technology and Photography. Love playing with the latest technology, and will try to post reviews of them. Also love my life long journey of learning to capture light, to trigger emotions, through photography.