github copilot
autonomous agentai-powered pair programmer and code completion
why i use it: essential for daily development workflow, providing intelligent code suggestions and accelerating development speed.
loading...
loading...
curated frameworks, programming languages, system utilities, and autonomous ai agents driving my daily engineering practice.
ai-powered pair programmer and code completion
why i use it: essential for daily development workflow, providing intelligent code suggestions and accelerating development speed.
advanced agentic ai coding assistant and workflow orchestrator
why i use it: autonomous multi-agent pair programming, planning mode, and complex full-stack execution.
next-generation agentic command-line coding tool
why i use it: deep contextual codebase reasoning, terminal-native workflows, and rapid autonomous refactoring.
javascript library for building user interfaces
why i use it: used extensively for designing and maintaining frontend architecture at openvia and neoception.
react framework for building server-side rendered applications
why i use it: used for developing scalable and maintainable frontend applications at openvia.
strongly typed programming language that builds on javascript
why i use it: used for developing scalable and maintainable frontend applications at openvia.
utility-first css framework
why i use it: quick and easy way to style components.
css framework for responsive web design
why i use it: used for creating and customizing views at openvia.
framework for building cross-platform mobile applications
why i use it: used for maintaining legacy projects at openvia.
platform for building web applications
why i use it: used for maintaining legacy projects at openvia.
programming language for web development
why i use it: used for web-based projects at neoception and legacy projects at openvia.
react component library
why i use it: used for developing reusable component libraries at neoception.
markup language for the web
why i use it: semantic, accessible html structure across all web applications.
stylesheets and modern styling
why i use it: responsive layouts, animations, and custom css styling.
end-to-end typesafe apis
why i use it: used for type-safe client-server contract development.
query language for apis
why i use it: used for connecting frontends with apis at openvia.
javascript runtime for building apis
why i use it: used for developing scalable and maintainable backend services at openvia.
architectural style for web services
why i use it: used for connecting frontends with backend services at openvia.
project management tool
why i use it: used for task management and tracking at both openvia and neoception.
git client for version control
why i use it: used for version control at openvia.
containerization platform
why i use it: used for deploying and managing applications at openvia.
cloud computing platform
why i use it: used for keeping projects live at openvia.
automation server for ci/cd
why i use it: used for continuous integration and deployment at openvia.
code quality and security tool
why i use it: used for ensuring code quality and preventing bugs at openvia.
javascript testing framework
why i use it: used for unit testing and ensuring code coverage at openvia.
distributed version control system
why i use it: standard version control system across all repositories and teams.
ci/cd and workflow automation
why i use it: automating continuous integration, linting, and automated checks.
module bundler for javascript
why i use it: asset bundling, optimization, and code splitting.
iterative software development framework
why i use it: collaborating in agile teams with daily stand-ups and bi-weekly sprints.
continuous integration and continuous deployment
why i use it: automated pipelines for testing and deployment with jenkins and docker.
quality-first development methodology
why i use it: writing tests to ensure regression-free features and maintainable architecture.
fluid multi-device interfaces
why i use it: architecting applications optimized for mobile, tablet, and desktop screens.
modular ui design methodology
why i use it: building reusable, composable, and accessible interface design systems.
clean api contract architecture
why i use it: designing robust, versioned, and intuitive data exchange patterns.
code editor
why i use it: primary code editor with over 90+ extensions for development.
database tool
why i use it: used for database management and queries.
operating system
why i use it: primary operating system for development.