-
-
Couldn't load subscription status.
- Fork 3
Description
📌 Overview
This issue initiates the design and implementation of an AI-driven development strategy for the Leverage CLI and, eventually, all binbash-maintained repositories. The objective is to integrate modern AI-native workflows into our development lifecycle to boost engineering velocity, improve collaboration, and unlock higher-value contributions.
🎯 Goals
- Establish the AI-first development environment for the
leverageCLI repository. - Evaluate and align AI tools like Cursor, Claude Code, and Kiro.dev (AWS IDE) with our Leverage workflows.
- Define internal best practices and reusable components to roll out AI-driven development org-wide.
🧩 Context & References
-
We’ve already started adopting Cursor IDE, with rules defined here:
https://github.com/binbashar/le-tf-infra-aws/tree/master/.cursor/rules -
We’re closely tracking alternatives like:
-
Long-term strategy is to use AI to improve:
- Developer onboarding
- CLI help and UX via AI-enhanced suggestions
- Test coverage and code quality
- Iteration speed across all binbash tooling
Related discussions and references:
- 📘 binbash AI-Driven Development Initiative
- 🧵 Initial conversation: Feature | cast tasks arguments and values loaded through .env files to the correct type #21 (comment)
- 📚 Ref Arch Docs: https://github.com/binbashar/le-ref-architecture-doc
- 🌐 Leverage Portal: https://leverage.binbash.co/
- 🔗 Related Issue: Feature | Integrate GenAI Doc into Leverage CLI Help Command #93
- 📄 Internal Wiki: https://binbash.atlassian.net/wiki/spaces/BDPS/pages/2485846018/Enhancing+Leverage+s+CLI+help+support+with+AI
✅ Tasks
- Research and document Cursor, Claude Code, and Kiro capabilities
- Define short-term goals for integrating AI in Leverage CLI development
- Create
.cursor/rulesand AI agent prompt strategy for CLI codebase - Draft AI-driven contribution guide and onboarding path
- Identify a pilot feature to be fully AI-assisted (e.g., CLI UX enhancement)
- Plan org-wide rollout and standardization across Leverage repos
Let’s embrace this evolution and deliver more value, faster. 🚀
cc: @binbashar/leverage-ref-architecture-aws-dev @binbashar/leverage-ref-architecture-aws-admin