Project Info
This project did not submit a demo video on Devpost.
Inspiration
We were inspired by a simple but painful truth: developers hate writing documentation. It's often the last thing anyone wants to do, and even when it gets done, it quickly becomes outdated. Static documentation rarely keeps up with evolving codebases, making it hard for teams to maintain internal knowledge. This becomes a real problem when developers leave and no one understands how the system works. Onboarding new team members becomes time-consuming and frustrating. Even worse, when software products are shipped with great features but poor documentation, it leads to low adoption and support overhead. We built llmao.ai to solve this problem once and for all - by automating documentation in a way that's both accurate and useful.
What it does
Companies can internally host an instance of llmao.ai to automate their documentation workflows. Implementation Documentation (internal to a company): The platform semantically analyzes a codebase (such as a GitHub-hosted repository), identifies relationships between modules, and captures their functionality as well as the overall system architecture. API/SDK References: It extracts the purpose, input, and output parameters of public APIs (e.g., those available through SDKs) from the repository. Developers have the option to review the generated documentation before it is published to internal knowledge bases or public platforms. Moreover, llmao.ai allows developers to interact with the documentation through AI assistants, enabling them to get specific answers to queries without reading the entire document.
How we built it
Our application is powered by Letta Cloud, Google Gemini, v0 by Vercel and GitHub MCP Server.
Challenges we ran into
This was all of our first time working with Letta Cloud, but it was a challenging yet rewarding experience.
Accomplishments we're proud of
We’re proud that llmao.ai can take any GitHub repository and generate clean, readable, and technically sound documentation - both proprietary and public. The dual-documentation flow using specialized agents was an ambitious idea, and we made it work. We also built a real-time AI chat experience that can answer technical questions with context-aware precision. Finally, we designed the system to be scalable and secure, with support for self-hosting in companies - making it a practical solution for real-world development teams.
What's next
We’re already working on several next steps. These include automatically triggering doc updates when the main branch is updated, and supporting multi-repo systems that span across several services. We also plan to generate release notes directly from pull requests, making changelogs easier to manage. We’re building integrations with popular platforms like Confluence, Notion, and Slack, so teams can push docs directly into their workflows.
Analysis
View
Metric
- 10
- 2
- 1
- 1
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- FlaskIn code
- Next.jsIn code
- PythonIn code
- ReactIn code
- Tailwind CSSIn code
- TypeScriptIn code
- Vercel AI SDKIn code
- Google GeminiClaimed
8 of 9 appear in the indexed code. 1 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
276 KB
Source files
79
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
ananya0996/llmao.ai
94 files · 289 KB · @ e9d5189
Structure
Interface
77 files · 82%Screens, components and styles rendered to the user.
API & routing
3 files · 3%Request entry points: routes, handlers and controllers.
Application logic
2 files · 2%Domain rules, services and shared utilities.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- TypeScript96%
- Python2%
- CSS2%
- Markdown0%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
ui/package.json
npm · 57- @hookform/resolvers
- @radix-ui/react-accordion
- @radix-ui/react-alert-dialog
- @radix-ui/react-aspect-ratio
- @radix-ui/react-avatar
- @radix-ui/react-checkbox
- @radix-ui/react-collapsible
- @radix-ui/react-context-menu
- @radix-ui/react-dialog
- @radix-ui/react-dropdown-menu
- @radix-ui/react-hover-card
- @radix-ui/react-label
- @radix-ui/react-menubar
- @radix-ui/react-navigation-menu
- @radix-ui/react-popover
- @radix-ui/react-progress
- @radix-ui/react-radio-group
- @radix-ui/react-scroll-area
- +39 more
backend/requirements.txt
pypi · 4- flask
- flask-cors
- python-dotenv
- requests
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.