131 lines
3.6 KiB
Markdown
131 lines
3.6 KiB
Markdown
# Multi-Language Agent Configuration
|
|
|
|
## Agent: Python Expert (Visual Studio Style)
|
|
|
|
This agent specializes in Python development following Visual Studio coding standards and practices.
|
|
|
|
### Capabilities
|
|
- Python script development and debugging
|
|
- Module creation and packaging
|
|
- Error handling and logging implementation
|
|
- pytest test writing and execution
|
|
- PEP 8 compliance (with 100-char line length)
|
|
- Black and isort formatting
|
|
- Type hints and documentation
|
|
- Web3/blockchain development
|
|
|
|
### Commands Available
|
|
|
|
#### `/python-lint`
|
|
Run flake8, black, and isort on Python files to check and fix style issues. Use line length 100 and 4-space indentation.
|
|
```
|
|
/python-lint
|
|
```
|
|
|
|
#### `/python-test`
|
|
Run pytest on codebase and show test results with coverage. Focus on failing tests and suggest fixes.
|
|
```
|
|
/python-test
|
|
```
|
|
|
|
#### `/python-imports`
|
|
Organize imports using isort with black profile and 100 character line length
|
|
```
|
|
/python-imports
|
|
```
|
|
|
|
### Python Standards Applied (Visual Studio Style)
|
|
|
|
1. **Naming Conventions**
|
|
- Variables: `snake_case` (descriptive names)
|
|
- Functions: `snake_case` with descriptive verbs
|
|
- Classes: `PascalCase`
|
|
- Constants: `UPPER_CASE_WITH_UNDERSCORES`
|
|
- Private members: `_leading_underscore`
|
|
|
|
2. **Code Style**
|
|
- 4 spaces indentation (never tabs)
|
|
- Line length: 100 characters (not 79)
|
|
- Import organization: standard → third-party → local
|
|
- Docstrings for all functions and classes
|
|
- Type hints where appropriate
|
|
|
|
3. **Best Practices**
|
|
- PEP 8 compliance with 100-char lines
|
|
- f-strings for string formatting
|
|
- Context managers for resources
|
|
- Proper error handling with specific exceptions
|
|
- Configuration constants at module level
|
|
|
|
---
|
|
|
|
## Agent: PowerShell Expert
|
|
|
|
This agent specializes in PowerShell scripting, automation, and following Microsoft best practices.
|
|
|
|
### Capabilities
|
|
- PowerShell script development and debugging
|
|
- Module creation and packaging
|
|
- Error handling and logging implementation
|
|
- Pester test writing and execution
|
|
- PSScriptAnalyzer compliance
|
|
- Pipeline optimization
|
|
- Security best practices
|
|
|
|
### Commands Available
|
|
|
|
#### `/ps-lint`
|
|
Run PSScriptAnalyzer on PowerShell files and fix any issues found
|
|
```
|
|
/ps-lint
|
|
```
|
|
|
|
#### `/ps-test`
|
|
Run Pester tests and show results with suggested fixes
|
|
```
|
|
/ps-test
|
|
```
|
|
|
|
#### `/ps-format`
|
|
Format PowerShell code according to best practices using Invoke-Formatter
|
|
```
|
|
/ps-format
|
|
```
|
|
|
|
### PowerShell Standards Applied
|
|
|
|
1. **Naming Conventions**
|
|
- Variables: `$camelCase`
|
|
- Functions: `Pascal-Case` with approved verbs
|
|
- Constants: `$UPPER_SNAKE_CASE`
|
|
|
|
2. **Code Style**
|
|
- 4 spaces indentation
|
|
- Pipeline alignment with `|`
|
|
- Proper error handling with try/catch
|
|
- Comment-based help documentation
|
|
|
|
3. **Best Practices**
|
|
- PSScriptAnalyzer compliance
|
|
- Set-StrictMode usage
|
|
- Parameter validation
|
|
- Proper logging implementation
|
|
|
|
### Usage Tips
|
|
|
|
#### Python Development
|
|
- Use the "python" agent when working with `.py` files
|
|
- The agent will automatically apply Visual Studio Python style
|
|
- All generated code includes proper type hints and documentation
|
|
- Import organization follows the standard → third-party → local pattern
|
|
|
|
#### PowerShell Development
|
|
- Use the "powershell" agent when working with `.ps1`, `.psm1`, `.psd1` files
|
|
- The agent will automatically apply PowerShell best practices
|
|
- All generated code includes proper error handling
|
|
- Formatting follows Microsoft PowerShell style guidelines
|
|
|
|
#### Agent Switching
|
|
- Use `Ctrl+Shift+A` to list available agents
|
|
- Select "python" for Visual Studio Python style
|
|
- Select "powershell" for Microsoft PowerShell style |