Active build
Voice capture and AI workspace tools
Applications for recording spoken input, transcribing it, structuring it into useful outputs, and turning rough ideas into actionable documents, notes, tasks, or drafts.
AI applications in development
This page summarizes the kinds of AI applications currently represented in active repositories and development work. They are listed by function rather than by project name so the emphasis stays on what they do.
The common pattern is operational usefulness: tools for capturing information, tutoring users, generating assets, converting documents, supporting staff, orchestrating workflows, and giving teams more leverage without removing human review.
Active build
Applications for recording spoken input, transcribing it, structuring it into useful outputs, and turning rough ideas into actionable documents, notes, tasks, or drafts.
Working product
Tools that turn natural-language prompts and references into SVG-based vector graphics for design, branding, and visual production workflows.
Internal tool / prototype
Utilities that convert source material into cleaner markdown, structured content, or publishable formats for documentation and workflow automation.
Prototype
Learning applications designed to help people practice programming concepts, work through exercises, and receive guided support while learning Python.
In development
Repository-backed learning systems built for specific instructional or program needs, including custom interfaces, learning flows, and course support patterns.
Multiple builds in progress
Conversational interfaces for answering questions, routing requests, supporting staff, or giving users AI-assisted access to internal information and workflows.
Experimental development
Agent implementations built with Google ADK 2.0 for structured orchestration, tool use, and task-oriented AI workflow design.
Multiple internal builds
Developer-facing agent tools, command-line assistants, and automation workflows intended to speed up technical operations, content processing, and repository work.
AI application development works best when it is connected to a real operational need: support workflows, learning systems, documentation, asset creation, internal knowledge access, repetitive content preparation, or developer tooling. That is the lens we use for deciding what to build.
Some builds are experimental, some are internal tools, some are active products, and some are early versions of platforms still being shaped. The point is not to force AI everywhere. The point is to build the right application where AI genuinely reduces friction or expands capability.
Ask about a custom AI application