Community Context Library Introduction

[Photonamus]

Community Context Library

Share and download context documents that turn general-purpose AI models into domain experts

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

This section is a community-driven 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.

Anyone can contribute. If you've built a context document that makes AI genuinely better at something, post it here for others to use. If you're looking for expertise on a topic, browse what's available and grab what fits.

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 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.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

How to Build Your Own

A method for turning scattered internet knowledge into dense, reusable guides that make any AI model an instant expert

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

AI models are general-purpose. They know a little about a lot. For niche or technical subjects — setting up pixel art workflows in ComfyUI, modding NES ROMs, configuring servers on Linux — their knowledge is shallow, scattered, and sometimes wrong. But they're extremely good at two things: searching the web for information, and synthesizing large amounts of raw data into organized, coherent documents.

The trick is using those strengths in sequence. Let the AI do what it's good at (searching, reading, condensing) so you end up with a document that solves what it's bad at (deep niche expertise). Once the doc exists, feeding it back in gives the model the equivalent of years of hands-on experience with the topic — in about 6,000 tokens.

A curated 5,000-word doc outperforms a raw 50,000-word dump every time. The editorial pass is what makes it work.

─── ◆ ───

Pass 1 — Cast the Wide Net

Start a conversation with the AI and give it a broad directive. Don't micromanage the search — tell it to go deep and bring back everything it can find.

Example prompt:

Code:

Search every corner of the internet, read every article you can find on [TOPIC]. Learn everything you possibly can about [SPECIFIC ASPECT]. Find every technique, every tool, every workflow. Then condense all of it into a single comprehensive reference document.

The AI will run multiple searches, fetch full articles, read documentation pages, and pull from forums, GitHub repos, and guides. It will then synthesize all of that into one structured document covering the entire topic.

What you get is a first-draft document that covers the major territory. It won't be complete yet, but it captures the bulk of available knowledge in one pass. A typical first pass runs 8–12 web searches and 4–6 full page reads, producing a 4,000–7,000 word document at around 20–40KB. That's roughly 70–80% of the available knowledge on the topic, captured in one shot.

─── ◆ ───

Pass 2 — Fill the Gaps

Feed the document back into a new conversation. Ask the AI to read what you already have and search specifically for what's missing.

Example prompt:

Code:

Here is a reference doc I am building on [TOPIC]. Read through it, identify any gaps or areas that need more depth, then search for additional information to fill those gaps. Update the document with the new findings.

Because the AI can see what's already covered, it won't waste searches re-finding the same material. Every fetch brings back new information only. The context window stays clean because you're not carrying redundant data.

─── ◆ ───

Pass 3+ — Refine and Verify

Repeat Pass 2 as needed. Each round gets more targeted and brings back less — that's how you know you're approaching completeness. When a pass comes back with only minor additions or confirmations of what's already there, you're done.

Typical progression:

• Pass 1: Major findings, core structure, 70–80% coverage
  
• Pass 2: Gap filling, edge cases, alternative approaches, 90% coverage
  
• Pass 3: Verification, corrections, minor additions, 95%+ coverage
  

Most topics reach diminishing returns by pass 2 or 3. Extremely broad subjects might benefit from 4–5 passes.

─── ◆ ───

Maintenance — Keep It Current

When you need to check if anything has changed:

Example prompt:

Code:

Here is my reference doc on [TOPIC], last updated [DATE]. Search for any new developments, updated tools, new versions, or changed information since then. Update the document with anything new and note what changed.

This is cheap — one pass, only fetching what's actually new. The doc stays current without rebuilding from scratch.

─── ◆ ───

What Makes a Good Topic

The method works best on subjects where information is scattered across many sources (forums, GitHub, wikis, blog posts, documentation), where no single definitive guide exists or the ones that do are outdated, where the subject is technical or procedural with specific tools, settings, and parameters, and where you'll need this knowledge more than once.

Good candidates: tool-specific workflows, hardware configuration guides, game technical breakdowns, niche software ecosystems, creative production pipelines, anything where AI models handle the topic poorly out of the box because it's too niche for their training data.

─── ◆ ───

Document Structure Tips

• Lead with the core problem the doc solves — why does this knowledge need to exist in one place
  
• Organize by task, not by source — readers need to find what to do, not where you found it
  
• Include specific settings, parameters, and values — these are what people actually need and what AI models get wrong most often
  
• Note tradeoffs and pitfalls — "this works but breaks if you do X" is more valuable than "this works"
  
• Keep a sources section at the bottom for anyone who wants to dig deeper
  
• Density over length — every line should earn its place. No filler, no padding, no restating things the model already knows. Maximum knowledge transfer per token.
  

─── ◆ ───

The Economics

A finished doc is typically 20–40KB. That's smaller than a single thumbnail image. Storage cost is effectively zero.

In token terms, a full guide is roughly 5,000–8,000 tokens when fed into a model. Most modern context windows are 100,000–200,000 tokens. Your reference doc uses 3–5% of the available space and gives the model expert-level knowledge on the entire subject.

Building the initial doc takes about 10–20 minutes of AI conversation time. The alternative — manually searching, reading, bookmarking, and re-searching every time you need the information — costs hours per session, every session, forever.

Plain text files. The oldest, smallest, most universal data format in computing — and now one of the most powerful tools in an AI-assisted workflow.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Post Format Guidelines

How to structure your library posts so everything stays consistent and usable

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Every document posted in this library should follow a three-part format to keep things browsable and functional:

Part 1 — Description

The top section of your post is a human-readable overview. Describe what the document covers, what it makes an AI an expert on, and when someone would want to use it. This is what people read to decide if the document is relevant to their needs. Write it for humans, not machines — the document itself is the machine-readable part.

Part 2 — Code Block

Below the description, include the full contents of your context document inside a

Code:

...

block. This lets people read through the actual material without downloading anything. It's the same content that's in the file — just displayed inline so they can preview it before committing to a download.

If your document is too large for the forum's character limit, skip this section and note in the description that the content is available in the download only. A good description with sample entries works fine as a substitute.

Part 3 — Attachment

Attach the document as a .zip file at the bottom of the post. This is the grab-and-go download — unzip it and feed the file directly to your AI assistant.

If for any reason the attachment fails or isn't available, users can always copy the contents directly from the code block in Part 2 and save it as a .md or .txt file. The code block is there as a built-in 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 your own and share it back.