Lingma helps your enterprise standardize the development process through AI-powered tools. It integrates with your IDEs to provide context-aware code completion, knowledge base as context for chat, and custom extensions. This guide introduces these features and gives brief best practices for each of them.
Enterprise knowledge base as context for code completion
When developers use the Lingma IDE plugin for inline code generation, it incorporates enterprise-uploaded code repositories as context. This ensures that code completion aligns more closely with your coding standards and business characteristics.
1. Prepare your code repository:
Upload frequently used code snippets or templates.
Add your enterprise frameworks and core business logic.
2. Follow the best practices:
Backend: Use comments or function signatures.
Frontend: Use tags or comments.
For more information, see Best practices for knowledge base as context for code completion.
Enterprise knowledge base as context for chat
Build your knowledge base
The enterprise knowledge base converts your documentation into searchable data. Upload documents to create a retrieval-enhanced knowledge source that aligns with your requirements.
Control access to your knowledge base
You can share standardized documents across teams or restrict sensitive information to specific groups. This access control helps you:
Maintain consistent documentation
Protect proprietary information
Support team-specific needs
For more information, see Best practices for knowledge base as context for chat.
Enterprise custom extensions
Define your own commands to personalize and simplify common development tasks.
Example scenarios
Code style checks:
Verify compliance before submission.
Prevent common issues.
API reference generation:
Generate API reference after development is completed.
Speed up service adoption.
Variable naming conventions:
Suggest standard-compliant name to improve code readability.
How it works
Select code using custom commands.
Receive AI-generated suggestions.
Apply changes.
For detailed examples, see Best practices for custom commands.