Market Trends
Gemini Executive Synthesis
Expanding knowledge graph generation to include non-code assets and documentation
Technical Positioning
Comprehensive, interactive knowledge graph for entire project ecosystems, not just code
SaaS Insight & Market Implications
This feature request identifies a critical expansion opportunity for "Understand-Anything": moving beyond code-centric knowledge graphs to encompass an entire project ecosystem. Including non-code assets like Unity prefabs, Dockerfiles, Kubernetes manifests, and documentation (`docs-as-codes`) would significantly enhance its value. The ability to map relationships between these diverse artifacts provides crucial insights for human developers (e.g., "blast radius" analysis) and AI agents. This strategic pivot transforms the product from a code understanding tool into a holistic project intelligence platform, addressing a broader market need for comprehensive system comprehension and impact analysis.
Proprietary Technical Taxonomy
Raw Developer Origin & Technical Request
GitHub Issue
Mar 23, 2026
Repo: Lum1104/Understand-Anything
Understand things beyond code
Does this have good support for or plan to support building knowledge graph including things that are not code?
For example:
- Unity ScriptableObjects and prefabs
- Dockerfiles, docker-compose.yml, Kubernetes manifests, Terraform scripts
- CI/CD pipeline
- ... and many more things
Developer Debate & Comments
That's a fantastic idea! Expanding the knowledge graph to include non-code assets like Dockerfiles and Unity prefabs would be really powerful. Let's discuss this—what specific features or integrations do you have in mind?
Lmao @Lum1104 why are you typing like Claude right now? On a serious note, this sounds like an awesome idea and very achievable
lol. I did use it to polish the comment, but it sound wierd like that. Never mind and sorry in advance.
lol we're gonna have to get used to reading stuffs written by AI, i let my agent handle my issues too so no worries. Things like I mentioned above: - For Unity, the ScriptableObjects and Prefabs will also create a bunch of relationships between classes/other scriptables/other prefabs/even other assets like textures, shaders,... So having a interactive graph / up-to-date knowledge graph will help a lot for both human work (e.g. preview blast radius before removing some stuffs) and AI work. This is also what I need most right now. - Documents: many of my projects have docs-as-codes (.md files), they reference each other and somewhat depend on each other quite often, and some projects even have doc-over-code ratio being >50 so I suppose having a strong and fast "understanding graph" helps a lot too.
Hi, I made some update based on your suggestion, feel free to check if it can help~
Adjacent Repository Pain Points
Other highly discussed features and pain points extracted from Lum1104/Understand-Anything.
Extracted Positioning
Excessive token usage by parallel LLM agents during codebase analysis, leading to rapid consumption of session limits.
Optimizing resource efficiency and cost-effectiveness for LLM-driven codebase analysis, ensuring the tool remains viable within typical API usage plans.
Top Replies
Edit : is there a way to know about certain folders actually being drawn into the map?
@Lum1104 isn't a similar issue already open?
Yeah I remember that, I thought the token cost problem might be affect by the framework knowledge by , but it is not 😱. So I create a new pr to try to solve it.
Extracted Positioning
Documentation and clarity regarding command-line options for the `/understand` command.
Providing clear, accessible guidance for users to effectively utilize the codebase analysis tool, ensuring ease of use and reducing friction.
Top Replies
可以参考[这里](https://github.com/Lum1104/Understand-Anything/blob/main/understand-anything-plugin/skills/understand/SKILL.md#options)，不填也没问题的
> 可以参考[这里](https://github.com/Lum1104/Understand-Anything/blob/main/understand-anything-plugin/skills/understand/SKILL.md#options)，不填也没问题的 ok 还有一个问题 大佬有空看看 理论上已经搭建...
方便看看 `.understand-anything/` 文件夹下面的内容吗，看着像少了一个 `meta.json`
Extracted Positioning
Interoperability and integration capabilities with external "spec coding tools" like `spec kit` and `open spec`.
Positioning "Understand-Anything" as a central component in a broader developer toolchain, capable of interacting with other specialized code specification and generation tools. The product aims to "turn any codebase into an interactive knowledge graph."
Extracted Positioning
UI/UX improvements for the interactive knowledge graph, specifically regarding mind map visualization and landing page clarity.
Enhancing user experience for rapid codebase understanding and exploration through intuitive visualization and clear communication of core functionality. The goal is an "interactive knowledge graph you can explore, search, and ask questions about."
Extracted Positioning
Inconsistent node ID generation and invalid complexity values from parallel LLM subagents in a codebase analysis tool.
Ensuring data integrity and deterministic output from LLM-generated structured data, specifically for graph database node identification and attribute consistency. The system aims for a reliable, explorable knowledge graph.
Engagement Signals
Cross-Market Term Frequency
Quantifies the cross-market adoption of foundational terms like knowledge graph and non-code assets by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.