.png "Photonamus Industries Forums")
+- Photonamus Industries Forums (https://forum.photonamus.com)
+-- Forum: Administrator's Corner (https://forum.photonamus.com/forumdisplay.php?fid=28)
+--- Forum: [Site] AI Library - Photonamus.com (https://forum.photonamus.com/forumdisplay.php?fid=31)
+--- Thread: AI Context Library Description (/showthread.php?tid=43)
AI Context Library Description - Photonamus - 08-22-2026
Welcome to the AI Context Library
A growing collection of context documents that turn general-purpose AI models into domain experts
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
A growing collection of context documents that turn general-purpose AI models into domain experts
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
This section is a library of context documents — structured reference files designed to be fed directly to an AI assistant at the start of a conversation. Each one is a condensed knowledge package covering a specific tool, workflow, hardware platform, or creative domain. When you give one of these documents to a model, it doesn't just know the topic exists — it understands the details, the gotchas, the correct settings, and the real-world techniques that separate useful output from generic advice.
These aren't tutorials or guides written for humans to follow step by step. They're reference material formatted for AI consumption — dense, precise, and structured so a model can absorb the full picture and then help you work within it. You still drive. The document just makes sure the AI actually knows what it's talking about.
─── ◆ ───
How Each Post Is Laid Out
Every document in this library follows a consistent three-part format:
- Description — the top section of the post is a human-readable overview. It tells you what the document covers, what it makes the AI an expert on, and when you'd want to use it. Read this to decide if the document is relevant to what you're working on.
- Code Block — below the description, the full contents of the context document are displayed inside a code block. This lets you read through the actual material without downloading anything. It's the same content that's in the file — just displayed inline so you can preview it.
- Attachment — at the bottom of the post, the document is attached as a downloadable .zip file. Grab it, unzip it, and you've got the raw file ready to feed to your AI assistant of choice.
─── ◆ ───
How to Use a Context Document
The workflow is simple. Pick a document that covers what you're working on, then at the start of a new conversation with your AI assistant, either paste the document contents in or attach the file directly. The model reads it, absorbs the domain knowledge, and you proceed with your actual questions and tasks. The AI will now have the specific, detailed understanding that the document provides — correct syntax, proper settings, real techniques, known pitfalls — instead of relying on whatever it happens to remember from training.
Some documents pair well together. A music generation reference and a retro audio reference complement each other when you're trying to generate era-accurate game music, for example. Use as many as make sense for your session, keeping in mind that each one uses some of the model's context window.
─── ◆ ───
What Makes a Good Context Document
The documents in this library are built around a few principles:
- Density over length. Every line earns its place. No filler, no padding, no restating things the model already knows. The goal is maximum knowledge transfer per token.
- Specifics over generalities. Exact settings, real parameter values, actual command syntax, concrete examples. Vague guidance produces vague output.
- Gotchas and constraints. The stuff that trips people up — wrong defaults, common mistakes, things that silently break — is often more valuable than the happy path.
- Universal applicability. These documents work with any AI assistant that accepts text or file input. They're not locked to a specific platform or model.
─── ◆ ───
A Note on Downloads
Every post includes the document as a .zip attachment for easy download. If for any reason the attachment fails or isn't available, you can always copy the contents directly from the code block in the post and save it as a .md or .txt file yourself. Same content either way — the code block is there as a fallback so the document is always accessible regardless of what the forum attachment system decides to do on any given day.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Browse the threads below. Grab what's useful. Build something cool.