Bring the Kyanite repo, MCP server, media pipeline, localization pass, or diagnostic you want running. Kyanite helps install it, adapt it to your setup, document the tradeoffs, and leave you with commands you can use again.
Open the repo, inspect the artifact, and pick the Kyanite build closest to the blocker you want running in your environment.
Use the gallery as a map: install one of the tools, read the build context, or start with a smaller asset before a scoped implementation conversation.
For builders who want mcp-video, Epoch, DialectOS, OpenGlaze, repo diagnostics, or another Kyanite build installed, adapted, and handed off cleanly.
Read the notes behind the project: what the tool does, where it is useful, what still needs care, and how the implementation surface should behave.
Use templates, workflows, and operator assets when you do not need a full implementation pass yet but want fewer blank-page starts.
Build logs and implementation notes show where a tool works, where it is rough, and what it takes to use it well.
The useful agent pattern is not a prettier prompt. It is a tool surface the agent can call, inspect, verify, and revise.
Repo history is a product signalA repo is not just storage. It is evidence of decisions, repairs, release behavior, naming drift, test gaps, and what the builder actually knows how to finish.
Implementation help is part of the product surfaceA useful open-source tool still needs a path from public repo to working environment. That path is product work, not an afterthought.
Tool you need running, repo you need installed, video pipeline you need usable, Spanish QA you need trusted, diagnostic you need explained, or a build you need handed off. If it connects to Kyanite's tools and practice, bring the blocker.
