feat: Add Kiro IDE and CLI support for deploy-on-aws plugin

Adding Kiro IDE and CLI Support to the Deploy-on-AWS Plugin

The deploy-on-aws plugin lacked native support for the Kiro IDE and CLI, limiting its accessibility to developers using these tools. This meant that users of Kiro, a platform designed to streamline development workflows, couldn't directly leverage the plugin's capabilities for deploying applications to AWS without manual integration efforts.

Root Cause: Bridging the Gap Between Ecosystems

The root cause stemmed from the plugin's initial design, which didn't explicitly account for the Kiro environment. While the plugin adhered to Agent Skills and MCP standards, the absence of specific configuration and integration points for Kiro prevented seamless interoperability. Kiro relies on its own directory structure and configuration files (.kiro/mcp.json, .kiro/steering/) for managing agent interactions. Without these elements, the plugin couldn't be automatically discovered and utilized within the Kiro ecosystem.

Solution: Integrating Kiro Configuration and Steering

The solution involves introducing Kiro-specific configuration files and steering mechanisms, alongside updating the plugin's documentation to guide Kiro users. The following steps detail the integration process:

1. MCP Server Configuration: Create a .kiro/mcp.json file mirroring the existing .mcp.json. This file configures the MCP server for Kiro, enabling communication between the IDE/CLI and the plugin. A typical mcp.json file might look like this:

{
  "mcp_server_address": "localhost:50051",
  "secure": false
}

2. Auto-Activation Steering: Add a .kiro/steering/deploy.md file to automatically activate the deploy skill within Kiro. This Markdown file contains instructions that Kiro uses to determine when to engage the deployment skill. For example:

When the user asks to deploy the application to AWS, activate the deploy skill.

3. Symlinking the Skills Directory: Create a symbolic link from .kiro/skills to the existing skills/ directory. This avoids code duplication and ensures that Kiro uses the same skill definitions as other agents. The command to create the symlink would be:

ln -s ../../skills .kiro/skills

4. Documentation Updates: Update the README.md file with detailed instructions on installing and configuring the plugin for Kiro IDE and CLI. This should include version requirements for Kiro (>=0.9 for IDE, >=1.24.0 for CLI).
5. Requirements Section: Explicitly add Kiro to the Requirements section of the README.md, specifying the minimum supported versions.

Diagram Generation

A key feature requested was the ability to generate architecture diagrams. This functionality is now available as a skill located in the skills/aws-architecture-diagram directory. To utilize this, ensure the Kiro environment is properly configured to recognize and execute skills.

Practical Tips and Considerations

• Version Compatibility: Always verify the compatibility of the plugin with specific Kiro IDE and CLI versions. Regularly test the integration to ensure smooth operation after updates to either the plugin or Kiro.
• Customization: Kiro's steering mechanism allows for customization of skill activation. You can tailor the deploy.md file to match your specific deployment workflows.
• Troubleshooting: If you encounter issues, check the Kiro logs and the plugin's output for error messages. Ensure that the MCP server is running and accessible.
• Security: When configuring the MCP server, consider enabling secure communication ("secure": true) in production environments.