156 lines
3.2 KiB
Markdown
156 lines
3.2 KiB
Markdown
# NICE-TO-HAVE.md
|
|
|
|
# Future Enhancements for Conductor
|
|
|
|
The following features are considered desirable enhancements but are not required for the initial MVP.
|
|
|
|
---
|
|
|
|
# AI-Assisted Development
|
|
|
|
Conductor should be designed so that AI capabilities can be integrated without changing the underlying project architecture.
|
|
|
|
AI assistance should operate by reading and modifying the project's canonical JSON definition.
|
|
|
|
The application shall remain fully functional when AI services are unavailable.
|
|
|
|
---
|
|
|
|
## AI Chat
|
|
|
|
Provide an integrated conversational interface for interacting with a project.
|
|
|
|
Example requests:
|
|
|
|
* Build a login page.
|
|
* Add a table below the dropdown.
|
|
* Connect this button to a REST endpoint.
|
|
* Explain what this page does.
|
|
* Rename all references to "Environment" as "Target Environment."
|
|
* Improve the layout.
|
|
* Add validation to required fields.
|
|
* Document this application.
|
|
|
|
The AI should generate proposed project changes rather than modifying the project without user approval.
|
|
|
|
---
|
|
|
|
## AI Project Generation
|
|
|
|
Allow users to create an application from a natural language description.
|
|
|
|
Example:
|
|
|
|
> Build a form that accepts a hostname, environment, and owner, then calls a Rapid Infrastructure Automation workflow and displays the results.
|
|
|
|
The AI should generate:
|
|
|
|
* Pages
|
|
* Components
|
|
* Layout
|
|
* REST actions
|
|
* Bindings
|
|
* Default styling
|
|
|
|
The generated project should immediately open in the Visual Editor for refinement.
|
|
|
|
---
|
|
|
|
## AI-Assisted REST Configuration
|
|
|
|
The AI may assist users by:
|
|
|
|
* Creating REST action definitions
|
|
* Suggesting request bodies
|
|
* Generating headers
|
|
* Creating authentication configurations
|
|
* Mapping API responses to UI components
|
|
* Suggesting validation rules
|
|
|
|
---
|
|
|
|
## AI Documentation
|
|
|
|
Generate documentation from an existing project.
|
|
|
|
Potential outputs include:
|
|
|
|
* Markdown documentation
|
|
* API documentation
|
|
* End-user documentation
|
|
* Administrator documentation
|
|
* Project summaries
|
|
|
|
---
|
|
|
|
## AI Refactoring
|
|
|
|
Allow the AI to improve an existing project.
|
|
|
|
Examples include:
|
|
|
|
* Simplifying layouts
|
|
* Removing unused components
|
|
* Consolidating duplicate REST actions
|
|
* Improving naming consistency
|
|
* Reorganizing pages
|
|
* Suggesting accessibility improvements
|
|
|
|
---
|
|
|
|
## AI Validation
|
|
|
|
The AI may analyze projects for potential issues, including:
|
|
|
|
* Missing bindings
|
|
* Invalid REST configurations
|
|
* Unused components
|
|
* Circular dependencies
|
|
* Missing required inputs
|
|
* Security concerns
|
|
* Inconsistent naming
|
|
|
|
---
|
|
|
|
## AI Explainability
|
|
|
|
Allow users to ask questions about an existing project.
|
|
|
|
Examples include:
|
|
|
|
* What happens when this button is clicked?
|
|
* Which components call REST APIs?
|
|
* Which workflow launches this action?
|
|
* Where is this value used?
|
|
* Why is this field disabled?
|
|
|
|
---
|
|
|
|
## OpenAPI Integration
|
|
|
|
Allow users to import an OpenAPI specification and automatically generate:
|
|
|
|
* REST action definitions
|
|
* Forms
|
|
* CRUD pages
|
|
* Tables
|
|
* Documentation
|
|
|
|
---
|
|
|
|
## Additional Future Enhancements
|
|
|
|
* Multi-page applications
|
|
* Reusable component libraries
|
|
* Themes and styling templates
|
|
* Workflow templates
|
|
* Project version history
|
|
* Git integration
|
|
* Team collaboration
|
|
* Role-based access control
|
|
* Plugin architecture
|
|
* Additional authentication providers
|
|
* Internationalization
|
|
* Accessibility auditing
|
|
* Application packaging and deployment
|