[NEW CONTENT] Agentic development

[Unshure]

Proposed Content

I would like a new page on the strands documentation site that outlines different ways to integrate popular agentic products with strands documentation. This will be meant to help developers connect their dev environment with strands to get started building strands agents quickly and easily

Location

Nested under User Guide as a new "Guides" subsection.

Rationale

This will make it easier for humans to connect their agentic coding tools with strands documentation

---

Implementation Requirements

Based on clarification discussion and repository analysis:

Overview

Create a single comprehensive guide page that helps developers integrate popular AI coding assistants with the Strands Agents SDK. The guide will cover rules files, MCP server integration, and IDE configurations.

Technical Approach

• Location: docs/user-guide/guides/agentic-development.md
• Navigation: New "Guides" subsection under "User Guide" in mkdocs.yml
• Format: Single page with sections for each tool

Target Agentic Products

1. Kiro (AWS AI IDE)

   • Steering files (.kiro/steering/*.md)
   • AGENTS.md support
   • MCP server configuration
   • Reference: https://kiro.dev/docs/steering/

2. Claude Code (Anthropic)

   • CLAUDE.md files (project root or .claude/CLAUDE.md)
   • .claude/rules/ directory for modular rules
   • MCP server integration
   • Reference: https://docs.anthropic.com/en/docs/claude-code/memory

3. Cursor

   • .cursor/rules/ directory
   • MCP server configuration
   • Reference: https://docs.cursor.com/context/rules

4. Generic MCP Server Integration

   • Using strands-agents/mcp-server
   • Cross-reference existing MCP docs at docs/user-guide/concepts/tools/mcp-tools.md

Content Structure

# Agentic Development Guide

## Introduction
- What is agentic development
- Benefits of integrating AI coding tools with Strands

## Kiro
- Setting up steering files for Strands projects
- MCP server configuration
- Example steering file

## Claude Code  
- Creating CLAUDE.md for Strands projects
- Using .claude/rules/ for modular instructions
- MCP server setup
- Example CLAUDE.md

## Cursor
- Setting up rules for Strands projects
- MCP server configuration
- Example rules file

## Generic MCP Integration
- Using strands-agents/mcp-server
- Configuration examples for other tools

## Example Project Rules
- Template AGENTS.md/CLAUDE.md for Strands SDK projects
- Common instructions for building agents

Files to Create/Modify

1. Create: docs/user-guide/guides/agentic-development.md
2. Modify: mkdocs.yml - Add new "Guides" subsection under User Guide nav

Acceptance Criteria

• New "Guides" section appears in User Guide navigation
• Page includes setup instructions for Kiro, Claude Code, Cursor
• Page includes generic MCP server integration guide
• Example rules/steering files provided for Strands projects
• Cross-references existing MCP documentation
• Page builds successfully with mkdocs build
• Links are valid and formatting is consistent with existing docs

Out of Scope

• No GitHub workflow changes required
• No TypeScript code examples needed (documentation only)

References

• Kiro Steering Docs: https://kiro.dev/docs/steering/
• Claude Code Memory Docs: https://docs.anthropic.com/en/docs/claude-code/memory
• Cursor Rules Docs: https://docs.cursor.com/context/rules
• Strands MCP Server: https://github.com/strands-agents/mcp-server
• Existing MCP Docs: docs/user-guide/concepts/tools/mcp-tools.md

[Unshure]

/strands

[github-actions]

Repository Analysis & Clarifying Questions

I've analyzed the repository structure and have some questions to ensure proper implementation.

Repository Context

• Framework: MkDocs with Material theme (documentation site)
• Current Navigation: User Guide, Examples, Community, Labs, Contribute, Python API, TypeScript API
• Existing MCP Support: Strands already has MCP integration documented in docs/user-guide/concepts/tools/mcp-tools.md
• Existing AGENTS.md: Contains guidance for AI agents working on this repository (development guidance)
• No existing docs: I found no current documentation specifically about integrating agentic coding tools (Cursor, Windsurf, GitHub Copilot, Claude Code, etc.)

Clarifying Questions

1. Target Agentic Products

Which specific "popular agentic products" should this guide cover? For example:

• AI Code Assistants: Cursor, Windsurf, GitHub Copilot, Claude Code, Continue.dev, Cline, Aider, etc.?
• MCP-based integrations: Strands MCP Server configurations for various tools?
• Other: Something else entirely?

2. Integration Type

What does "integrate with strands documentation" mean in this context?

• Rules files: Creating .cursorrules, AGENTS.md, or similar files that help AI assistants understand Strands?
• MCP Server setup: Configuring the strands-agents/mcp-server with various tools?
• IDE configurations: Setting up specific IDE/editor configurations for Strands development?
• All of the above: A comprehensive guide covering multiple integration approaches?

3. Content Structure

Should this be:

• Single comprehensive page: One page covering all agentic tools?
• Multiple sub-pages: A "Guides" section with separate pages for each tool (e.g., /guides/cursor.md, /guides/windsurf.md)?
• Template-based: A general guide with tool-specific sections?

4. Navigation Placement

I see you suggested a new "Guides" dropdown. Should this be:

• Top-level tab (like User Guide, Examples, Community)?
• Nested under User Guide as a subsection?
• Nested under Community (since these are often community/ecosystem integrations)?

5. Scope Confirmation

For initial implementation, should this focus on:

• Getting started quickly: Minimal setup instructions for 2-3 popular tools?
• Comprehensive coverage: Detailed guides for many tools?

Implementation Notes

Based on my analysis, this feature would involve:

• Creating a new docs/guides/ directory
• Adding agentic-development.md (or similar) file(s)
• Updating mkdocs.yml to add the new navigation section
• No workflow changes required

This appears to be a well-scoped task suitable for a single PR.

[Unshure]

/strands

1. Lets go with kiro, calude code, cursor, and then generic mcp server integration
2. all of the above
3. Single page
4. nested under user guide
5. getting started quickly

[github-actions]

Task Refinement Complete

I've updated the issue description with comprehensive implementation requirements based on our discussion and repository analysis.

Summary of Changes

The issue now includes:

• Clear scope: Single page covering Kiro, Claude Code, Cursor, and generic MCP integration
• File locations: docs/user-guide/guides/agentic-development.md + mkdocs.yml update
• Content structure: Detailed outline with sections for each tool
• Acceptance criteria: Checklist for implementation validation
• References: Links to official documentation for each tool

Implementation Estimate

• Effort: ~1-2 days for a single developer
• Complexity: Low - primarily documentation content
• Files: 1 new file + 1 modification to mkdocs.yml

Ready for Implementation

This issue is now ready to be picked up for development. The implementation involves:

1. Creating the new guide page with setup instructions for each agentic tool
2. Adding the "Guides" subsection to the User Guide navigation
3. Including example rules/steering files for Strands projects

[Unshure]

/strands implement

[github-actions]

Unable to create pull request via API. You can create it manually by clicking here.