- Vibe Coding for AL
+ Getting Started With Agentic Coding
- AI-optimized coding rules and guidelines designed to enhance the AL developer experience in modern AI-powered IDEs like VS Code and Cursor.
+ Essential concepts and practices for working with AI coding assistants in your AL development workflow.
- Two API Related Design Patterns and one Best Practice for working with API's
+ AI-optimized coding rules and guidelines designed to enhance the AL developer experience in modern AI-powered IDEs.
- In the world of interfaces, it is important to preserve (certain) events over multiple implementation of the interface.
+ Model Context Protocol (MCP) servers that enhance AI assistants for Business Central development workflows.
diff --git a/content/docs/BestPractices/api-page/index.md b/content/docs/BestPractices/api-page/index.md
index b1dc4488..cc23701e 100644
--- a/content/docs/BestPractices/api-page/index.md
+++ b/content/docs/BestPractices/api-page/index.md
@@ -35,7 +35,7 @@ The properties that must be defined are:
- ODataKeyFields
### APIPublisher
-The name of the API publisher is usually the company creating the API. It is the first custom part in the URL for a given endpoint. The value is case insensitive.
+The name of the API publisher is usually the company creating the API. It is the first custom part in the URL for a given endpoint. While the value is case insensitive for HTTP operations (GET, POST, etc.), it is case sensitive when checking for active subscriptions.
Example:
@@ -44,7 +44,7 @@ APIPublisher = 'contoso';
```
### APIGroup
-Sets the group of the API endpoint that page or query is exposed in. In the URL the APIGroup comes after the APIPublisher. It can be used to distinguish different API apps or groups of APIs from each other. The value is case insensitive.
+Sets the group of the API endpoint that page or query is exposed in. In the URL the APIGroup comes after the APIPublisher. It can be used to distinguish different API apps or groups of APIs from each other. While the value is case insensitive for HTTP operations (GET, POST, etc.), it is case sensitive when checking for active subscriptions.
Example:
diff --git a/content/docs/Contributing/InstallHugo/ManuallyOnWindows11/index.md b/content/docs/Contributing/InstallHugo/ManuallyOnWindows11/index.md
index 671484d5..7e4b8105 100644
--- a/content/docs/Contributing/InstallHugo/ManuallyOnWindows11/index.md
+++ b/content/docs/Contributing/InstallHugo/ManuallyOnWindows11/index.md
@@ -2,7 +2,7 @@
title: "Manually on Windows 11"
---
-This guide will walk You thrugh installing Hugo on a Windows 11 PC. For the official install guide, You can wisit .
+This guide will walk You thrugh installing Hugo on a Windows 11 PC. For the official install guide, You can wisit .
## Download Binaries
diff --git a/content/docs/Contributing/InstallHugo/_index.md b/content/docs/Contributing/InstallHugo/_index.md
index b59eb861..30a2f7f6 100644
--- a/content/docs/Contributing/InstallHugo/_index.md
+++ b/content/docs/Contributing/InstallHugo/_index.md
@@ -4,6 +4,6 @@ title: Install Hugo
There are multiple ways to install Hugo for you to properly preview your contributions. Please select the scenario that matches your setup.
-For the official install guide, you can visit
+For the official install guide, you can visit
{{< youtube G7umPCU-8xc >}}
diff --git a/content/docs/NAVPatterns/3-cal-coding-guidelines/_index.md b/content/docs/NAVPatterns/3-cal-coding-guidelines/_index.md
index 84612f77..54e113cf 100644
--- a/content/docs/NAVPatterns/3-cal-coding-guidelines/_index.md
+++ b/content/docs/NAVPatterns/3-cal-coding-guidelines/_index.md
@@ -23,6 +23,6 @@ We're looking forward to your comments. Where you can, do provide concrete examp
-[anchor0]: https://blogs.msdn.microsoft.com/nav/2015/01/09/cal-coding-guidelines-used-at-microsoft-development-center-copenhagen "download the C/AL coding guidelines as pdf"
+[anchor0]: /files/CAL-Coding-Guidelines-at-Microsoft-Development-Center-Copenhagen.pdf "download the C/AL coding guidelines as pdf"
[anchor1]: /members/waldo/default.aspx "waldo"
[anchor2]: https://www.youtube.com/watch?v=z6skKy0pkmU&list=PLhZ3P-LY7CqmVszuvtJLujFyHpsVN0U_w&index=26
diff --git a/content/docs/NAVPatterns/_index.md b/content/docs/NAVPatterns/_index.md
index 644ec7ec..22ecc24f 100644
--- a/content/docs/NAVPatterns/_index.md
+++ b/content/docs/NAVPatterns/_index.md
@@ -1,6 +1,6 @@
+++
title = "NAV Patterns Archive"
-weight = 20
+weight = 4
tags = ["C/AL"]
+++
diff --git a/content/docs/NAVPatterns/patterns/blocked-entity/_index.md b/content/docs/NAVPatterns/patterns/blocked-entity/_index.md
index 79b0f5ac..402ba137 100644
--- a/content/docs/NAVPatterns/patterns/blocked-entity/_index.md
+++ b/content/docs/NAVPatterns/patterns/blocked-entity/_index.md
@@ -92,7 +92,9 @@ Entities where the Blocked Entity has been implemented include:
The [Released Entity][anchor4].
-{{< youtube O2R-fTSup1o >}}
+{{% alert title="Note" %}}
+There was previously a video demonstration of this pattern, but it is no longer available.
+{{% /alert %}}
[anchor0]: 2260.BlockedEntityPattern.png
[anchor1]: /navpatterns/1-patterns/blocked-entity/data-driven-blocked-entity/
diff --git a/content/docs/agentic-coding/CommunityResources/Agents/_index.md b/content/docs/agentic-coding/CommunityResources/Agents/_index.md
new file mode 100644
index 00000000..b463099f
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Agents/_index.md
@@ -0,0 +1,217 @@
+---
+title: "AI Coding Agents"
+linkTitle: "Agents"
+weight: 5
+description: >
+ Learn about different AI coding agents and how to use them for AL development
+---
+
+## Overview
+
+AI coding agents are intelligent assistants that help you write, review, and improve AL code for Business Central. This section explains the different types of agents available and how to choose the right one for your needs.
+
+## What are AI Coding Agents?
+
+AI coding agents are more than simple autocomplete tools. They can:
+- Understand natural language instructions
+- Generate complete code implementations
+- Explain existing code
+- Refactor and improve code quality
+- Help debug issues
+- Provide learning and guidance
+
+## Available Agents
+
+Explore detailed information about each AI coding agent:
+
+### [GitHub Copilot](github-copilot-agent)
+Microsoft's AI pair programmer integrated into VS Code.
+
+**Best For**:
+- Inline code completion as you type
+- Quick code generation
+- Learning AL patterns
+- Teams already using GitHub
+
+**Key Features**: Real-time suggestions, multi-file context, AL-aware completions
+
+---
+
+### [GitHub Copilot Chat](github-copilot-chat-agent)
+Conversational AI assistant from GitHub with deep VS Code integration.
+
+**Best For**:
+- Interactive code discussions
+- Code explanations and learning
+- Debugging assistance
+- Complex refactoring tasks
+
+**Key Features**: Natural language chat, context-aware responses, inline chat
+
+---
+
+### [Claude (via API or Claude.ai)](claude-agent)
+Anthropic's AI assistant with strong reasoning capabilities.
+
+**Best For**:
+- Complex problem solving
+- Detailed code analysis
+- Architecture discussions
+- Large codebase understanding
+
+**Key Features**: Long context window, strong analytical abilities, helpful explanations
+
+---
+
+### [Cursor](cursor-agent)
+AI-first code editor built on VS Code with integrated AI assistance.
+
+**Best For**:
+- All-in-one AI coding environment
+- Teams wanting deep AI integration
+- Multi-model AI access
+- Codebase-wide AI context
+
+**Key Features**: Multiple AI models, composer mode, codebase indexing, chat + autocomplete
+
+---
+
+## Comparison Matrix
+
+| Feature | GitHub Copilot | Copilot Chat | Claude | Cursor |
+|---------|---------------|--------------|---------|---------|
+| **Inline Completion** | ✓✓✓ Excellent | Limited | N/A | ✓✓✓ Excellent |
+| **Chat Interface** | N/A | ✓✓✓ Excellent | ✓✓✓ Excellent | ✓✓✓ Excellent |
+| **AL Awareness** | ✓✓ Good | ✓✓ Good | ✓ Basic | ✓✓ Good |
+| **Code Explanation** | Limited | ✓✓✓ Excellent | ✓✓✓ Excellent | ✓✓✓ Excellent |
+| **VS Code Integration** | ✓✓✓ Native | ✓✓✓ Native | ✗ Web/API | ✓✓✓ Fork |
+| **Context Window** | Medium | Medium | ✓✓✓ Very Large | Large |
+| **Multi-file Editing** | Limited | Limited | Manual | ✓✓✓ Excellent |
+| **Pricing** | $10-19/mo | Included | Free/Pro | $20/mo |
+| **Team Features** | ✓✓ Good | ✓✓ Good | Limited | ✓ Basic |
+
+**Legend**: ✓✓✓ Excellent | ✓✓ Good | ✓ Basic | Limited | ✗ Not Available | N/A Not Applicable
+
+## Choosing the Right Agent
+
+### For Individual Developers
+
+**Just Starting with AI?**
+→ Start with [GitHub Copilot](github-copilot-agent) + [Copilot Chat](github-copilot-chat-agent)
+- Easy setup
+- Great VS Code integration
+- Good AL support
+- One subscription for both
+
+**Want Maximum AI Power?**
+→ Try [Cursor](cursor-agent)
+- Multiple AI models
+- Strong codebase understanding
+- All-in-one solution
+- Advanced features
+
+**Need Deep Analysis?**
+→ Use [Claude](claude-agent) for complex tasks
+- Long context for large codebases
+- Excellent reasoning
+- Detailed explanations
+- Free tier available
+
+### For Teams
+
+**Microsoft/GitHub Ecosystem?**
+→ GitHub Copilot for Business
+- Centralized management
+- License management
+- Organization policies
+- Familiar tools
+
+**Maximum Flexibility?**
+→ Cursor for Teams
+- Multiple AI models
+- Strong collaboration
+- Advanced features
+- Modern interface
+
+**Hybrid Approach?**
+→ Combine tools:
+- GitHub Copilot for daily coding
+- Claude for complex analysis
+- Cursor for specific projects
+
+## Using Multiple Agents
+
+Many developers use multiple agents for different tasks:
+
+**Daily Coding**: GitHub Copilot (inline suggestions)
+**Learning & Debugging**: Copilot Chat or Cursor Chat
+**Complex Problems**: Claude (detailed analysis)
+**Refactoring**: Cursor (multi-file editing)
+
+**Example Workflow**:
+1. Write code with GitHub Copilot inline suggestions
+2. Ask Copilot Chat to explain complex BC patterns
+3. Use Claude for architecture review of large features
+4. Use Cursor for complex multi-file refactoring
+
+## Getting Started
+
+### New to AI Coding?
+
+1. **Start Simple**: [GitHub Copilot](github-copilot-agent)
+2. **Learn the Basics**: [Effective Prompting](../../gettingstarted/effective-prompting)
+3. **Try Examples**: [Getting More](../../gettingmore)
+4. **Explore Others**: Try Claude or Cursor for comparison
+
+### Already Using AI?
+
+**Expand Your Toolkit**:
+- If using Copilot → Try Cursor for advanced features
+- If using Claude → Add Copilot for inline completion
+- If using Cursor → Use Claude for deep analysis
+
+## Common Questions
+
+### Can I use multiple agents?
+Yes! Many developers use different agents for different tasks. They complement each other well.
+
+### Which is best for AL development?
+GitHub Copilot has the most AL-specific training, but all agents can be effective with good prompting.
+
+### Are these expensive?
+Most are $10-20/month for individual use. GitHub Copilot offers free access for students and open source maintainers.
+
+### Do I need internet?
+Yes, all current AI agents require internet connectivity to function.
+
+### Will AI replace AL developers?
+No. AI agents are tools to augment your capabilities, not replace your expertise and decision-making.
+
+## Privacy & Security
+
+All agents send code to external services. Consider:
+- Review your organization's AI usage policy
+- Don't include sensitive data in code
+- Use business/enterprise plans for better controls
+- Understand each tool's data handling policies
+
+See individual agent pages for specific privacy information.
+
+## Learning Path
+
+1. **Read agent pages** to understand capabilities
+2. **Choose one** to start with
+3. **Follow setup** instructions
+4. **Practice** with examples from [Getting More](../../gettingmore)
+5. **Experiment** with others as needed
+
+## Resources
+
+- [Setup Guide](../../gettingstarted/setup) - Environment configuration
+- [Effective Prompting](../../gettingstarted/effective-prompting) - Get better results
+- [Best Practices](../../gettingstarted/best-practices) - Use AI effectively
+- [Limitations](../../gettingstarted/limitations) - Understand constraints
+
+---
+
+**Questions?** Join the discussion at [GitHub Discussions](https://github.com/microsoft/alguidelines/discussions)
diff --git a/content/docs/agentic-coding/CommunityResources/Agents/claude-agent.md b/content/docs/agentic-coding/CommunityResources/Agents/claude-agent.md
new file mode 100644
index 00000000..828c5674
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Agents/claude-agent.md
@@ -0,0 +1,757 @@
+---
+title: "Claude Agent"
+linkTitle: "Claude"
+weight: 3
+description: >
+ Anthropic's AI assistant with strong reasoning and large context window for AL development
+---
+
+## Overview
+
+Claude is Anthropic's AI assistant known for its strong reasoning capabilities, long context window, and helpful, detailed responses. While not specifically designed for coding, it excels at code analysis, architecture discussions, and complex problem-solving for AL development.
+
+**Developer**: Anthropic
+**Type**: Conversational AI Assistant
+**Primary Use**: Code analysis, learning, complex problem-solving
+**Integration**: Web interface (Claude.ai) or API
+
+## What is Claude?
+
+Claude is a general-purpose AI assistant that:
+- Provides detailed, thoughtful analysis
+- Handles very large amounts of code
+- Reasons through complex problems
+- Explains concepts clearly
+- Generates well-structured code
+- Maintains context across long conversations
+
+### Access Methods
+
+**Claude.ai (Web)**:
+- Free tier available
+- Pro tier ($20/month) for more usage
+- Upload files directly
+- Conversation interface
+- No IDE integration
+
+**Claude API**:
+- Programmatic access
+- Can be integrated into tools
+- Pay-per-use pricing
+- Requires development
+
+**Note**: Unlike Copilot/Cursor, Claude doesn't have native VS Code integration.
+
+## Key Capabilities for AL Development
+
+### Exceptional Context Window
+
+**Claude 3.5 Sonnet**: ~200K tokens
+- Can analyze entire AL projects
+- Process multiple large files simultaneously
+- Maintain context across long conversations
+- Reference earlier parts of discussion
+
+**Practical Use**:
+```
+You can paste:
+- Multiple complete AL files
+- Entire codeunit implementations
+- Full table structures
+- Large amounts of documentation
+
+Claude maintains context and can reference any part.
+```
+
+### Strong Analytical Abilities
+
+**Code Analysis**:
+- Deep understanding of code structure
+- Identifies patterns and anti-patterns
+- Suggests architectural improvements
+- Explains complex logic clearly
+
+**Problem Solving**:
+- Reasons through complex scenarios
+- Considers multiple approaches
+- Explains trade-offs
+- Provides detailed rationale
+
+**Learning & Teaching**:
+- Patient, clear explanations
+- Step-by-step breakdowns
+- Answers follow-up questions
+- Adapts to your knowledge level
+
+## Strengths for AL Development
+
+### ✓ Exceptional At
+
+**Large Codebase Analysis**:
+```
+Paste your entire project:
+- All codeunits
+- Table structures
+- Page definitions
+- Integration logic
+
+Ask: "Review this AL project for architectural improvements"
+
+Claude can analyze it all and provide comprehensive feedback.
+```
+
+**Architecture & Design**:
+```
+Questions like:
+- "Should I use events or direct calls for this integration?"
+- "How should I structure this multi-tenant extension?"
+- "What's the best way to handle this complex business logic?"
+
+Claude provides thoughtful, reasoned analysis.
+```
+
+**Complex Problem Solving**:
+```
+Describe complex scenarios:
+- Multi-step business processes
+- Integration challenges
+- Performance optimization
+- Refactoring strategies
+
+Claude reasons through options and trade-offs.
+```
+
+**Learning & Understanding**:
+```
+Questions like:
+- "Explain Business Central's posting architecture"
+- "How does AL's event system work?"
+- "What are the differences between these BC patterns?"
+
+Claude provides detailed, educational responses.
+```
+
+### ⚠ Limitations
+
+**No IDE Integration**:
+- Manual copy-paste workflow
+- No inline suggestions
+- No automatic context
+- More context switching
+
+**AL-Specific Training**:
+- Not specifically trained on AL
+- May not know latest BC features
+- Might suggest non-AL patterns
+- Requires clear AL context
+
+**Real-Time Coding**:
+- Not designed for quick completions
+- Better for analysis than generation
+- Slower workflow than Copilot
+- Best for thoughtful tasks
+
+## Practical AL Examples
+
+### Architecture Review
+
+**You** (paste entire project):
+```
+I'm building a customer loyalty system for Business Central.
+Here are my main files:
+
+[Paste 5-10 AL files totaling thousands of lines]
+
+Review the architecture and suggest improvements.
+```
+
+**Claude Responds**:
+```
+I've analyzed your loyalty system implementation. Here's my review:
+
+Overall Architecture:
+Your implementation follows a good separation of concerns with:
+- Setup tables (Loyalty Tier, Loyalty Rules)
+- Transaction table (Loyalty Points Entry)
+- Processing codeunits (Points Calculator, Tier Evaluator)
+- Integration through event subscribers
+
+Strengths:
+1. Good use of events for extensibility
+2. Clear separation between setup and transactions
+3. Proper use of temporary tables for calculations
+
+Areas for Improvement:
+
+1. Performance Optimization (Table 50101 "Loyalty Points Entry"):
+ - Current implementation recalculates totals on every query
+ - Recommendation: Add a "Total Points" field on Customer table
+ - Use events to update when points are added/removed
+ - Reduces database load significantly
+
+2. Transaction Handling (Codeunit 50100):
+ Lines 45-67 process points without transaction wrapping.
+ This could lead to partial updates if an error occurs.
+
+ Suggested pattern:
+ procedure AwardPoints(...)
+ begin
+ // Wrap in Codeunit.Run for transaction
+ if not AwardPointsInternal(...) then
+ Error(GetLastErrorText());
+ end;
+
+ procedure AwardPointsInternal(...): Boolean
+ begin
+ // Processing logic here
+ end;
+
+3. Testing Considerations:
+ - No test codeunits provided
+ - Critical calculation logic in Points Calculator should have unit tests
+ - Recommendation: Create test codeunit with scenarios for:
+ * Points calculation accuracy
+ * Tier upgrades/downgrades
+ * Edge cases (negative points, expired points)
+
+4. Telemetry (Missing):
+ Consider adding Application Insights telemetry for:
+ - Points awarded/redeemed
+ - Tier changes
+ - Calculation performance
+ - Error conditions
+
+5. API Exposure:
+ For mobile/web integration, consider:
+ - API page for customer's current points balance
+ - API page for points history
+ - OData for reporting
+
+Would you like me to elaborate on any of these points or show
+specific code examples for the improvements?
+```
+
+### Complex AL Pattern Explanation
+
+**You**:
+```
+I found this code in standard BC. Can you explain in detail how
+this posting pattern works and why it's structured this way?
+
+[Paste complex BC posting code]
+```
+
+**Claude Explains**:
+```
+This is Business Central's standard document posting pattern.
+Let me break it down step by step:
+
+Structure Overview:
+1. OnRun trigger (lines 10-15): Entry point
+2. Main posting procedure (lines 20-150): Orchestration
+3. Helper procedures (lines 155+): Specific tasks
+4. Integration events: Extensibility points
+
+Detailed Explanation:
+
+Phase 1: Pre-Posting Validation (lines 22-35)
+--------------------------------------------
+The code first validates the document is ready to post:
+
+ OnRun()
+ begin
+ CheckDocumentIsReadyToPost(SalesHeader);
+ end;
+
+This separation ensures:
+- Validation logic is reusable
+- Errors caught before any changes
+- Can be tested independently
+
+Key validations:
+- Document not already posted
+- Required fields populated
+- Valid line items exist
+- Customer not blocked
+
+Phase 2: Table Locking (lines 40-45)
+------------------------------------
+ SalesHeader.LockTable();
+ SalesLine.LockTable();
+
+Critical for multi-user scenarios:
+- Prevents concurrent modifications
+- Ensures data consistency
+- Follows database transaction best practices
+
+This must happen INSIDE the implicit transaction
+(started by OnRun trigger).
+
+Phase 3: Integration Events "Before" (lines 50-55)
+-------------------------------------------------
+ OnBeforePostSalesDocument(SalesHeader, PostingResult);
+
+Allows extensions to:
+- Add additional validation
+- Modify posting parameters
+- Log custom data
+- Integrate with external systems
+
+Extensions subscribe to these events to add functionality
+without modifying base code.
+
+Phase 4: Core Posting Logic (lines 60-120)
+------------------------------------------
+The actual posting work:
+
+ PostSalesLines(SalesHeader); // Create ledger entries
+ PostCustomerLedger(SalesHeader); // Update customer balance
+ UpdateInventory(SalesHeader); // Adjust inventory
+ CreatePostedDocument(SalesHeader);// Archive posted doc
+
+Each step is a separate procedure because:
+- Clarity and maintainability
+- Reusability
+- Easier testing
+- Clear transaction boundaries
+
+Phase 5: Integration Events "After" (lines 125-130)
+--------------------------------------------------
+ OnAfterPostSalesDocument(SalesHeader, PostingResult);
+
+Allows extensions to:
+- Trigger follow-up actions
+- Send notifications
+- Update related data
+- Log completion
+
+Phase 6: Cleanup (lines 135-145)
+--------------------------------
+ DeleteAfterPosting(SalesHeader);
+ Commit;
+
+- Removes unposted document
+- Commits transaction
+- Frees locks
+
+Why This Pattern?
+
+1. Reliability:
+ - Explicit transaction boundaries
+ - Proper locking prevents conflicts
+ - Validation before any changes
+
+2. Extensibility:
+ - Events at every critical point
+ - Extensions can hook in without modification
+ - Standard pattern across all posting routines
+
+3. Maintainability:
+ - Clear, linear flow
+ - Each procedure has single responsibility
+ - Easy to understand and debug
+
+4. Performance:
+ - Table locks minimize deadlocks
+ - Efficient batch processing
+ - Single transaction reduces overhead
+
+5. Error Handling:
+ - OnRun trigger provides implicit error handling
+ - Transaction rolled back on error
+ - Clean state maintained
+
+This is the gold standard for BC posting routines. When creating
+your own posting logic, follow this same pattern for:
+- Custom documents
+- Batch processing
+- Any transactional operations
+
+Would you like me to explain any specific part in more detail,
+or show how to implement this pattern for a custom document?
+```
+
+### Migration Strategy
+
+**You**:
+```
+We have 50,000 lines of NAV 2018 C/AL code to migrate to BC AL.
+What's the best strategy?
+
+[Include examples of your NAV code]
+```
+
+**Claude Provides**:
+```
+Migrating 50K lines of C/AL to AL is substantial. Here's a strategic approach:
+
+Phase 1: Assessment & Planning (Week 1-2)
+-----------------------------------------
+
+1. Code Analysis:
+ - Categorize by object type
+ - Identify custom vs modified standard objects
+ - Map dependencies
+ - Find external integrations
+
+2. Risk Assessment:
+ HIGH RISK (manual migration priority):
+ - Heavy .NET interop
+ - Automation/OCX controls
+ - Client-side code
+ - File system access
+
+ MEDIUM RISK (tool + manual):
+ - Standard modifications
+ - Reports
+ - Complex business logic
+
+ LOW RISK (mostly automated):
+ - Simple tables
+ - Basic pages
+ - Straightforward codeunits
+
+3. Tool Selection:
+ - AL Object Designer for conversion
+ - txt2al for initial conversion
+ - Manual for complex cases
+
+Phase 2: Automated Conversion (Week 3-4)
+----------------------------------------
+
+1. Run automated tools on LOW/MEDIUM risk code
+2. Fix compilation errors
+3. Address obvious issues
+4. Don't spend time on perfect conversion yet
+
+Phase 3: Manual Review & Refactoring (Week 5-12)
+-----------------------------------------------
+
+Priority order:
+1. Core business logic (highest value)
+2. Integration points (highest risk)
+3. Reports (user-facing)
+4. Supporting code (lower priority)
+
+For each module:
+a) Understand business purpose
+b) Review automated conversion
+c) Refactor to AL patterns
+d) Add error handling
+e) Add telemetry
+f) Create tests
+
+Phase 4: Testing (Week 13-16)
+-----------------------------
+
+Comprehensive testing:
+- Unit tests for calculations
+- Integration tests for workflows
+- User acceptance testing
+- Performance testing
+- Migration testing (data)
+
+Phase 5: Incremental Deployment (Week 17+)
+------------------------------------------
+
+Consider:
+- Parallel run period
+- Module-by-module rollout
+- Rollback procedures
+- User training
+
+Specific Code Migration Tips:
+
+1. C/AL Automation → AL:
+ Your NAV code uses Word automation.
+ Replace with:
+ - BC Word Report Layouts (preferred)
+ - External API calls if complex
+ - Azure Functions for processing
+
+2. Client-Side Code → AL:
+ NAV Page code that ran on client.
+ Move to:
+ - Page triggers (server-side)
+ - Page extensions
+ - Control add-ins (if really needed)
+
+3. Record.SETCURRENTKEY → AL:
+ NAV: Rec.SETCURRENTKEY(Date, Amount);
+ AL: Rec.SetCurrentKey(Date, Amount);
+
+ Note: Case-sensitive in AL!
+
+4. Reports:
+ NAV RDLC reports need:
+ - AL report object
+ - Updated dataset
+ - Layout regeneration
+
+ Consider: RDL → Word layout migration
+
+5. .NET Interop:
+ NAV: DotNet variables
+ AL: Check if:
+ - Available in AL
+ - Use BC API instead
+ - Create Azure Function if needed
+
+AI-Assisted Migration Strategy:
+
+Use AI tools effectively:
+1. GitHub Copilot:
+ - Quick syntax fixes
+ - Pattern replacement
+ - Boilerplate generation
+
+2. Claude (me!):
+ - Complex logic understanding
+ - Architecture decisions
+ - Refactoring strategies
+
+3. Manual effort:
+ - Business logic validation
+ - Testing
+ - Critical decisions
+
+Realistic Timeline:
+- Simple migration: 4-6 months
+- Complex migration: 6-12 months
+- Very complex: 12-18 months
+
+Budget for:
+- 30% automated conversion
+- 40% manual refactoring
+- 30% testing and validation
+
+Would you like me to:
+1. Review specific NAV code samples?
+2. Elaborate on any phase?
+3. Discuss specific technical challenges?
+4. Create a detailed project plan template?
+```
+
+## How to Use Claude Effectively
+
+### Workflow
+
+**1. Preparation**:
+- Gather all relevant AL code
+- Prepare specific questions
+- Include context and requirements
+
+**2. Interaction**:
+- Paste code into Claude.ai
+- Ask clear, specific questions
+- Provide examples of what you want
+
+**3. Iterate**:
+- Ask follow-up questions
+- Clarify unclear points
+- Request alternatives
+- Explore trade-offs
+
+**4. Implementation**:
+- Copy suggested code
+- Adapt to your project
+- Test thoroughly
+- Refine as needed
+
+### Best Practices
+
+**Provide Full Context**:
+```
+Good:
+"I'm building an AL extension for BC v22 that integrates with Shopify.
+Here's my current implementation: [paste code]
+I need to handle rate limiting from the Shopify API.
+Show me the best AL pattern for this."
+
+vs.
+
+Poor:
+"How do I handle rate limiting?"
+```
+
+**Ask Specific Questions**:
+```
+Good:
+"Review this AL posting codeunit for performance issues,
+specifically focusing on database operations."
+
+vs.
+
+Poor:
+"Is this good?"
+```
+
+**Use for Complex Tasks**:
+- Architecture decisions
+- Code review of large modules
+- Learning complex concepts
+- Debugging intricate issues
+
+## How It Differs from Other Agents
+
+### vs. GitHub Copilot
+
+**Claude**:
+- ✓ Much larger context window
+- ✓ Better at analysis and reasoning
+- ✓ More detailed explanations
+- ✗ No IDE integration
+- ✗ No inline suggestions
+- ✗ Manual workflow
+
+**GitHub Copilot**:
+- ✓ IDE integration
+- ✓ Real-time suggestions
+- ✓ Fast workflow
+- ✗ Limited context
+- ✗ Less analytical
+
+**Use Both**: Copilot for daily coding, Claude for deep analysis
+
+### vs. Cursor
+
+**Claude**:
+- ✓ Larger context window
+- ✓ Better analytical depth
+- ✓ More thoughtful responses
+- ✗ No IDE integration
+- ✗ Manual copy-paste
+
+**Cursor**:
+- ✓ IDE integration
+- ✓ Multiple AI models (including Claude!)
+- ✓ Direct code editing
+- ✗ Smaller context per interaction
+- ✗ Different editor
+
+**Note**: Cursor can use Claude as its AI model, giving you Claude's capabilities with IDE integration!
+
+## Access & Pricing
+
+### Claude.ai (Web)
+
+**Free Tier**:
+- Limited messages per day
+- Claude 3.5 Sonnet access
+- Good for occasional use
+- No payment required
+
+**Pro Tier** ($20/month):
+- 5x more usage
+- Priority access
+- Claude 3 Opus (most capable model)
+- Early feature access
+
+### Claude API
+
+**Pay-per-use**:
+- Billed by tokens
+- Integration into tools
+- Programmatic access
+- See Anthropic pricing page
+
+**Link**: [Claude.ai](https://claude.ai) | [Anthropic Pricing](https://www.anthropic.com/pricing)
+
+## Privacy & Security
+
+### What Gets Sent
+- Your messages and questions
+- Code you paste
+- Files you upload
+- Conversation history
+
+### Data Usage
+- Not used for training (as of current policy)
+- Processed for improving responses
+- Retained per Anthropic's policy
+- Review privacy policy for details
+
+### Best Practices
+- Don't paste sensitive data
+- Avoid customer information
+- Review organization policies
+- Use sanitized code examples
+
+## When to Use Claude
+
+### ✓ Ideal For
+
+- **Large code reviews**: Paste entire projects
+- **Architecture discussions**: Complex design decisions
+- **Learning**: Detailed explanations of AL/BC concepts
+- **Problem solving**: Complex scenarios with many variables
+- **Migration planning**: NAV to BC conversions
+- **Refactoring strategies**: Large-scale code improvements
+- **API design**: Thoughtful API architecture
+
+### ⚠ Consider Alternatives
+
+- **Quick completions** → GitHub Copilot
+- **IDE integration** → Copilot or Cursor
+- **Real-time coding** → Copilot or Cursor
+- **Multi-file editing** → Cursor
+
+## Complementary Tools
+
+**Use With**:
+- GitHub Copilot for daily coding
+- VS Code for development
+- AL analyzers for code quality
+- Version control for safety
+
+**Workflow Example**:
+1. Code with Copilot in VS Code
+2. Review architecture with Claude
+3. Implement improvements in VS Code
+4. Test and validate
+
+## Tips for AL Development
+
+**Provide AL Context**:
+```
+"I'm working in AL for Business Central version 22.
+[Your question]"
+```
+
+**Reference BC Concepts**:
+```
+"Using BC's standard posting pattern..."
+"Following BC event subscriber patterns..."
+```
+
+**Ask for Alternatives**:
+```
+"Show me 3 different approaches to this problem,
+with pros and cons of each."
+```
+
+**Request Explanations**:
+```
+"Explain this like I'm familiar with C# but new to AL"
+```
+
+## Resources
+
+### Official
+- [Claude.ai](https://claude.ai)
+- [Anthropic Documentation](https://docs.anthropic.com)
+- [API Documentation](https://docs.anthropic.com/claude/reference)
+
+### AL Guidelines
+- [Effective Prompting](../../gettingstarted/effective-prompting)
+- [Best Practices](../../gettingstarted/best-practices)
+- [Code Review Examples](../../gettingmore/code-review)
+
+---
+
+**Next Steps**:
+- Try [Claude.ai](https://claude.ai) for free
+- Compare with [other AI agents](./)
+- Use alongside [GitHub Copilot](github-copilot-agent)
+
+**Questions?** Join [GitHub Discussions](https://github.com/microsoft/alguidelines/discussions)
diff --git a/content/docs/agentic-coding/CommunityResources/Agents/cursor-agent.md b/content/docs/agentic-coding/CommunityResources/Agents/cursor-agent.md
new file mode 100644
index 00000000..4e5fdfd1
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Agents/cursor-agent.md
@@ -0,0 +1,675 @@
+---
+title: "Cursor Agent"
+linkTitle: "Cursor"
+weight: 4
+description: >
+ AI-first code editor with integrated AI assistance and multi-file editing for AL development
+---
+
+## Overview
+
+Cursor is an AI-first code editor built on VS Code that integrates AI deeply into every aspect of development. It provides inline suggestions, chat assistance, and advanced features like Composer mode for multi-file editing, making it a powerful tool for AL development.
+
+**Developer**: Anysphere Inc.
+**Type**: AI-Integrated Code Editor
+**Primary Use**: Complete AI-assisted development environment
+**Integration**: Native (is a code editor)
+
+## What is Cursor?
+
+Cursor is a fork of Visual Studio Code with integrated AI capabilities:
+- Native AI code completion (like Copilot)
+- Built-in AI chat (like Copilot Chat)
+- Composer mode for multi-file editing
+- Codebase indexing for better context
+- Multiple AI model support
+- All VS Code extensions work
+
+### Key Differentiator
+
+Unlike tools that add AI to VS Code, Cursor **is** an AI-first editor built from the ground up with AI integration.
+
+**Think of it as**: VS Code + GitHub Copilot + Advanced AI Features + Better Context Understanding
+
+## Key Features
+
+### 1. Tab Completion (Like Copilot)
+
+Real-time AI suggestions as you type:
+```al
+// Type a comment
+/// Validate customer credit limit
+
+// Cursor suggests complete procedure
+procedure ValidateCreditLimit(CustomerNo: Code[20]): Boolean
+var
+ Customer: Record Customer;
+begin
+ // Full implementation suggested
+end;
+```
+
+**Plus**:
+- Faster than Copilot
+- Better context awareness
+- Multiple AI models available
+
+### 2. Chat Interface (Like Copilot Chat)
+
+Built-in AI chat in the sidebar:
+- Ask questions about code
+- Get explanations
+- Request code generation
+- Debug issues
+
+**Plus**:
+- Can use multiple AI models (GPT-4, Claude, etc.)
+- Better codebase understanding
+- More context awareness
+
+### 3. Cmd+K (Inline Chat)
+
+Quick inline AI assistance:
+- Press `Cmd+K` (Mac) or `Ctrl+K` (Windows)
+- Ask questions or request changes
+- AI suggests edits inline
+- Accept, reject, or modify
+
+**Example**:
+```al
+// Select code, press Cmd+K, type:
+"Add error handling and telemetry"
+
+// Cursor shows diff with changes
+// Accept to apply
+```
+
+### 4. Composer Mode ⭐
+
+**Most Powerful Feature**: Multi-file editing with AI
+
+- Create/edit multiple files simultaneously
+- AI understands file relationships
+- Generates complete features
+- Handles complex refactoring
+
+**Example**:
+```
+Press Cmd+I (Composer)
+Type: "Add a loyalty points system with table, page, and codeunit"
+
+Cursor creates:
+- Table 50100 "Loyalty Points Entry"
+- Page 50100 "Loyalty Points List"
+- Page 50101 "Loyalty Points Card"
+- Codeunit 50100 "Loyalty Points Manager"
+
+All properly connected and following AL patterns
+```
+
+### 5. Codebase Indexing
+
+Cursor indexes your entire workspace:
+- AI understands your project structure
+- References existing code
+- Follows your patterns
+- Suggests consistent code
+
+**Benefit for AL**:
+- Knows your table structures
+- Understands your naming conventions
+- Follows your coding patterns
+- References your existing codeunits
+
+### 6. Multiple AI Models
+
+Choose your AI model:
+- GPT-4 (OpenAI)
+- GPT-4 Turbo
+- Claude 3.5 Sonnet (Anthropic)
+- Claude 3 Opus
+- (More being added)
+
+**Why it matters**:
+- Different models have different strengths
+- Switch based on task
+- Try multiple for comparison
+- Use best for each scenario
+
+## Strengths for AL Development
+
+### ✓ Exceptional At
+
+**Multi-File Projects**:
+```
+Composer: "Create a complete order processing module with:
+- Order Header and Line tables
+- Card and List pages
+- Processing codeunit
+- Validation codeunit
+- Test codeunit
+Follow AL best practices"
+
+Cursor creates all files properly structured and connected.
+```
+
+**Large Refactoring**:
+```
+"Refactor this project to:
+- Add telemetry to all procedures
+- Standardize error handling
+- Add XML documentation
+- Update to use new AL patterns"
+
+Cursor makes changes across all relevant files.
+```
+
+**Project Generation**:
+```
+"Create a BC extension for customer surveys with:
+- Setup tables
+- Survey and response tables
+- Pages for all tables
+- Email sending logic
+- API for mobile access"
+
+Cursor scaffolds entire extension.
+```
+
+**Codebase Understanding**:
+- Knows your entire project
+- References existing patterns
+- Follows your conventions
+- Suggests consistent code
+
+### ⚠ Consider Limitations
+
+**Learning Curve**:
+- Different from VS Code workflow
+- New shortcuts to learn
+- Composer mode takes practice
+- More features to understand
+
+**Cost**:
+- $20/month (more than Copilot's $10)
+- No free tier for individuals
+- Worth it for heavy AI use
+
+**AL-Specific Training**:
+- Not specifically trained on AL
+- Requires good AL context
+- May need explicit AL patterns
+- Works best with symbols downloaded
+
+## Practical AL Examples
+
+### Composer Mode: Complete Feature
+
+**Command** (in Composer, `Cmd+I`):
+```
+Create a complete customer discount management system:
+
+Tables:
+- Discount Group Setup (code, description, percentage)
+- Customer Discount Assignment (customer no, discount group)
+
+Pages:
+- List and Card pages for each table
+
+Codeunit:
+- Calculate discount based on customer's group
+- Apply discount to sales lines
+- Event subscribers for sales line validation
+
+Include:
+- Proper AL naming conventions
+- XML documentation
+- Error handling
+- Data classification
+```
+
+**Cursor Creates** (all files):
+
+```
+Created Files:
+✓ Tables/DiscountGroupSetup.Table.al
+✓ Tables/CustomerDiscountAssignment.Table.al
+✓ Pages/DiscountGroupSetupList.Page.al
+✓ Pages/DiscountGroupSetupCard.Page.al
+✓ Pages/CustomerDiscountAssignmentList.Page.al
+✓ Codeunits/DiscountManager.Codeunit.al
+
+All files properly structured with:
+- AL best practices
+- XML documentation
+- Event subscribers
+- Error handling
+```
+
+### Chat: Code Review
+
+**You** (in Chat):
+```
+Review this codeunit for performance and best practices:
+
+[Paste codeunit]
+
+Specifically check:
+- Database operations
+- AL patterns
+- Error handling
+- Code analyzers compliance
+```
+
+**Cursor Analyzes**:
+```
+Found several issues:
+
+1. Performance Issue (Lines 45-52):
+ Multiple FindSet without SetLoadFields
+
+ Current:
+ SalesLine.SetRange("Document No.", OrderNo);
+ if SalesLine.FindSet() then
+
+ Recommended:
+ SalesLine.SetRange("Document No.", OrderNo);
+ SalesLine.SetLoadFields(Quantity, "Unit Price", Amount);
+ if SalesLine.FindSet() then
+
+2. Missing Error Handling (Lines 67-70):
+ No try-catch for posting operation
+
+ [Shows specific improvements]
+
+3. CodeCop Violations:
+ - Procedure names don't follow AL naming
+ - Missing XML documentation
+
+ [Lists specific fixes needed]
+
+Would you like me to apply these fixes?
+```
+
+### Inline Edit (Cmd+K)
+
+**Select procedure, press Cmd+K**:
+```
+"Add Application Insights telemetry to track execution time and parameters"
+```
+
+**Cursor Shows Diff**:
+```al
+- procedure ProcessOrder(OrderNo: Code[20])
++ procedure ProcessOrder(OrderNo: Code[20])
+ var
+ SalesHeader: Record "Sales Header";
++ Telemetry: Codeunit Telemetry;
++ CustomDimensions: Dictionary of [Text, Text];
++ StartTime: DateTime;
+ begin
++ StartTime := CurrentDateTime;
++ CustomDimensions.Add('OrderNo', OrderNo);
++
++ Telemetry.LogMessage('ORDER-001', 'Processing order started',
++ Verbosity::Normal, DataClassification::SystemMetadata,
++ TelemetryScope::ExtensionPublisher, CustomDimensions);
++
+ // Existing code...
++
++ CustomDimensions.Add('Duration', Format(CurrentDateTime - StartTime));
++ Telemetry.LogMessage('ORDER-002', 'Processing order completed',
++ Verbosity::Normal, DataClassification::SystemMetadata,
++ TelemetryScope::ExtensionPublisher, CustomDimensions);
+ end;
+```
+
+Accept with `Cmd+Enter`, reject with `Cmd+Backspace`
+
+### Codebase Chat
+
+**You**:
+```
+@codebase How is customer validation currently implemented in this project?
+```
+
+**Cursor** (searches entire project):
+```
+Found customer validation in 3 places:
+
+1. Codeunit 50100 "Customer Validator" (Lines 23-45):
+ - Main validation logic
+ - Checks blocked status
+ - Validates credit limit
+
+2. Table Extension 50100 "Customer Extension" (Lines 15-20):
+ - OnValidate trigger for custom field
+
+3. Event Subscriber in Codeunit 50105 (Lines 67-80):
+ - Subscribes to Customer OnAfterValidate
+ - Adds additional custom validation
+
+Recommendation: Consolidate validation logic into single codeunit
+for better maintainability.
+
+[Shows code snippets from each location]
+```
+
+## How It Differs from Other Agents
+
+### vs. GitHub Copilot
+
+**Cursor**:
+- ✓ Multiple AI models (including GPT-4)
+- ✓ Composer mode (multi-file editing)
+- ✓ Better codebase understanding
+- ✓ More advanced features
+- ✗ Higher cost ($20 vs $10)
+- ✗ Different editor (learning curve)
+
+**Copilot**:
+- ✓ Lower cost
+- ✓ Standard VS Code
+- ✓ Familiar workflow
+- ✗ Single AI model
+- ✗ No composer mode
+- ✗ Less context awareness
+
+### vs. Claude
+
+**Cursor**:
+- ✓ IDE integration
+- ✓ Multi-file editing
+- ✓ Direct code application
+- ✓ Can use Claude as AI model!
+- ✗ Smaller context per interaction
+
+**Claude**:
+- ✓ Larger context window
+- ✓ Better for analysis
+- ✓ Web interface
+- ✗ No IDE integration
+- ✗ Manual copy-paste
+
+**Note**: Cursor can use Claude as its AI model, giving you best of both!
+
+### vs. VS Code + Extensions
+
+**Cursor**:
+- ✓ Native AI integration
+- ✓ Optimized for AI workflow
+- ✓ Advanced features
+- ✓ All VS Code extensions work
+- ✗ Different app (not VS Code)
+- ✗ Subscription required
+
+**VS Code + Copilot**:
+- ✓ Standard VS Code
+- ✓ Familiar environment
+- ✓ Established workflow
+- ✗ Less AI integration
+- ✗ Fewer AI features
+
+## Setup & Configuration
+
+### Installation
+
+1. **Download Cursor**
+ - Visit [cursor.sh](https://cursor.sh)
+ - Download for your OS
+ - Install application
+
+2. **Sign Up**
+ - Create account
+ - Choose subscription plan
+ - Verify email
+
+3. **Configure AL Development**
+ - Install AL Language extension
+ - Import VS Code settings (optional)
+ - Download BC symbols
+ - Open your AL project
+
+### Migrating from VS Code
+
+**Import Settings**:
+```
+Cursor > Settings > Import Settings from VS Code
+```
+
+**Your Extensions**:
+- All VS Code extensions work
+- Install AL Language
+- Install AL Object Designer
+- Install other AL tools
+
+**Keyboard Shortcuts**:
+- Most VS Code shortcuts work
+- Learn Cursor-specific shortcuts:
+ - `Cmd+K`: Inline edit
+ - `Cmd+L`: Chat
+ - `Cmd+I`: Composer
+
+### Optimizing for AL
+
+**Workspace Setup**:
+- Keep `app.json` well-configured
+- Download symbols first
+- Organize files clearly
+- Use descriptive naming
+
+**AI Model Selection**:
+- GPT-4 for general coding
+- Claude for analysis
+- Experiment to find preference
+
+## Best Practices
+
+### Using Composer Mode
+
+**Clear Instructions**:
+```
+Good:
+"Create AL customer loyalty system with:
+- Tier setup table (code, name, min points, discount %)
+- Customer points table (customer no, points, tier code)
+- List and card pages for both
+- Codeunit to calculate and assign tiers
+- Event subscriber to update on purchase
+Follow AL naming conventions and add XML docs"
+
+Poor:
+"Make a loyalty system"
+```
+
+**Iterative Development**:
+1. Start with basic structure
+2. Review generated files
+3. Ask for refinements
+4. Add features incrementally
+
+### Using Chat Effectively
+
+**Reference Files**:
+```
+@filename.al What does this procedure do?
+@codebase How is posting handled in this project?
+```
+
+**Specific Questions**:
+```
+"Review CustomerProcessor.codeunit.al for:
+- Performance issues
+- AL best practices
+- Missing error handling"
+```
+
+### Using Inline Edit
+
+**Targeted Changes**:
+- Select specific code
+- Request specific improvements
+- Review diff carefully
+- Accept or modify
+
+## Pricing
+
+**Pro Plan**: $20/month
+- Unlimited AI completions
+- Unlimited chat
+- Composer mode
+- All AI models
+- Priority support
+
+**Business Plan**: Custom pricing
+- Team features
+- Organization management
+- Usage analytics
+- Enhanced security
+
+**Free Trial**: 14 days (typically)
+
+**Link**: [Cursor Pricing](https://cursor.sh/pricing)
+
+## Privacy & Security
+
+### What Gets Sent
+- Code you're working on
+- Files in your workspace
+- Chat messages
+- User interactions
+
+### Privacy Controls
+- Can disable AI features
+- Control what's indexed
+- Configure model usage
+- Review privacy settings
+
+### Best Practices
+- Don't include sensitive data
+- Review organization policies
+- Use privacy mode when needed
+- Understand data handling
+
+## When to Use Cursor
+
+### ✓ Ideal For
+
+- **New Projects**: Build from scratch with AI
+- **Large Refactoring**: Multi-file changes
+- **Learning**: Explore AL patterns
+- **Rapid Development**: Build features quickly
+- **Experimentation**: Try different approaches
+- **Team Development**: Consistent patterns
+
+### ⚠ Consider Alternatives
+
+- **Quick edits** → GitHub Copilot faster
+- **Just need VS Code** → Stick with Copilot
+- **Budget constrained** → Copilot cheaper
+- **Prefer standard tools** → VS Code + Copilot
+
+## Practical Workflows
+
+### Starting New Extension
+
+1. **Composer Mode**: Generate project structure
+2. **Chat**: Refine and improve
+3. **Inline Edit**: Add features
+4. **Tab**: Complete code quickly
+
+### Refactoring Existing Code
+
+1. **Chat**: "Analyze this project for improvements"
+2. **Review**: Understand suggestions
+3. **Composer**: Apply multi-file changes
+4. **Inline**: Fix specific issues
+
+### Learning AL Patterns
+
+1. **Generate example** with Composer
+2. **Ask Chat** to explain
+3. **Experiment** with variations
+4. **Apply** to real project
+
+## Complementary Tools
+
+**Use With**:
+- AL Language extension (required)
+- AL analyzers for quality
+- Git for version control
+- BC symbols for context
+
+**Workflow**:
+1. Cursor for development
+2. AL analyzers for validation
+3. Git for safety
+4. Claude (via Cursor) for analysis
+
+## Tips for AL Development
+
+**Provide AL Context**:
+```
+"Generate AL code for Business Central v22..."
+"Follow AL naming conventions..."
+"Use BC standard posting patterns..."
+```
+
+**Use Codebase Context**:
+```
+@codebase Reference existing table structures
+@CustomerTable.al Follow this naming pattern
+```
+
+**Leverage Models**:
+- GPT-4 for code generation
+- Claude for analysis
+- Try both for comparison
+
+**Iterate**:
+- Generate basic structure
+- Review and refine
+- Add complexity gradually
+- Test thoroughly
+
+## Resources
+
+### Official
+- [Cursor Website](https://cursor.sh)
+- [Cursor Documentation](https://docs.cursor.sh)
+- [Community Discord](https://discord.gg/cursor)
+
+### AL Guidelines
+- [Effective Prompting](../../gettingstarted/effective-prompting)
+- [Best Practices](../../gettingstarted/best-practices)
+- [Getting More Examples](../../gettingmore)
+
+## Learning Cursor
+
+### Start Simple
+1. Try tab completion (like Copilot)
+2. Use chat for questions
+3. Experiment with Cmd+K
+4. Practice Composer on small tasks
+
+### Progress to Advanced
+1. Multi-file projects with Composer
+2. Codebase-wide refactoring
+3. Multiple AI model usage
+4. Advanced keyboard shortcuts
+
+### Master Features
+1. Understand when to use each mode
+2. Optimize prompts for better results
+3. Integrate into daily workflow
+4. Share patterns with team
+
+---
+
+**Next Steps**:
+- Download [Cursor](https://cursor.sh)
+- Try free trial
+- Compare with [other AI agents](./)
+- Use alongside your existing tools
+
+**Questions?** Join [GitHub Discussions](https://github.com/microsoft/alguidelines/discussions)
diff --git a/content/docs/agentic-coding/CommunityResources/Agents/github-copilot-agent.md b/content/docs/agentic-coding/CommunityResources/Agents/github-copilot-agent.md
new file mode 100644
index 00000000..d7f62dce
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Agents/github-copilot-agent.md
@@ -0,0 +1,552 @@
+---
+title: "GitHub Copilot Agent"
+linkTitle: "GitHub Copilot"
+weight: 1
+description: >
+ Microsoft's AI pair programmer for real-time code completion and suggestions
+---
+
+## Overview
+
+GitHub Copilot is Microsoft's AI-powered coding assistant that provides real-time code suggestions directly in your editor. It's trained on billions of lines of public code and integrates seamlessly with Visual Studio Code.
+
+**Developer**: GitHub (Microsoft)
+**Type**: AI Code Completion Agent
+**Primary Use**: Inline code suggestions as you type
+**Integration**: Native VS Code extension
+
+## What is GitHub Copilot?
+
+GitHub Copilot acts as an AI pair programmer that:
+- Suggests code completions in real-time
+- Generates entire functions from comments
+- Provides multiple suggestion alternatives
+- Understands context from your codebase
+- Learns patterns specific to AL and Business Central
+
+### How It Works
+
+1. **You write**: A comment or start typing code
+2. **Copilot analyzes**: Your code, open files, and context
+3. **Copilot suggests**: Code completion in gray text
+4. **You decide**: Accept (Tab), reject (Esc), or modify
+
+**Example**:
+```al
+// Type this comment:
+/// Calculate total sales for customer including tax
+
+// Copilot suggests (press Tab to accept):
+procedure CalculateTotalSalesWithTax(CustomerNo: Code[20]): Decimal
+var
+ SalesLine: Record "Sales Line";
+ TotalAmount: Decimal;
+begin
+ SalesLine.SetRange("Sell-to Customer No.", CustomerNo);
+ SalesLine.SetRange(Type, SalesLine.Type::Item);
+ if SalesLine.FindSet() then
+ repeat
+ TotalAmount += SalesLine."Amount Including VAT";
+ until SalesLine.Next() = 0;
+ exit(TotalAmount);
+end;
+```
+
+## Key Capabilities
+
+### For AL Development
+
+**Understands AL Syntax**:
+- Recognizes AL keywords and patterns
+- Knows Business Central object types
+- Suggests BC-appropriate code structures
+- Follows AL naming conventions
+
+**Business Central Awareness**:
+- Familiar with BC table structures
+- Knows common BC APIs
+- Suggests standard BC patterns
+- Understands event subscriber patterns
+
+**Context-Aware**:
+- Reads your open AL files
+- Understands project structure
+- References your existing code
+- Adapts to your coding style
+
+### Code Generation Capabilities
+
+**From Comments**:
+```al
+/// Create a page extension for Customer Card that adds loyalty points field
+
+// Generates complete page extension structure
+```
+
+**From Partial Code**:
+```al
+procedure ValidateCustomer
+// Continue typing... Copilot completes with parameters, logic
+```
+
+**From Patterns**:
+```al
+[EventSubscriber(
+// Copilot suggests common event patterns
+```
+
+**Test Code**:
+```al
+[Test]
+procedure TestCustomerValidation
+// Generates test structure with Given-When-Then
+```
+
+## Strengths for AL Development
+
+### ✓ Excellent At
+
+**Boilerplate Code**:
+- Table and field definitions
+- Page layouts
+- Standard procedures
+- Variable declarations
+
+**Common Patterns**:
+- CRUD operations
+- Validation logic
+- Event subscribers
+- API pages
+
+**Code Structure**:
+- Procedure signatures
+- If-then-else logic
+- Loop structures
+- Error handling templates
+
+**Quick Edits**:
+- Adding fields
+- Extending objects
+- Creating similar code
+- Repetitive tasks
+
+### ⚠ Use With Care
+
+**Complex Business Logic**:
+- May not understand specific requirements
+- Review carefully for correctness
+- Validate against business rules
+
+**Performance-Critical Code**:
+- Check for efficient database queries
+- Verify optimal AL patterns
+- Profile if needed
+
+**Security-Sensitive Code**:
+- Review authentication logic
+- Validate input handling
+- Check authorization patterns
+
+## How It Differs from Other Agents
+
+### vs. GitHub Copilot Chat
+**Copilot (Inline)**:
+- ✓ Better for code completion
+- ✓ Faster for quick edits
+- ✓ Non-intrusive workflow
+- ✗ Limited explanation ability
+- ✗ Can't answer questions
+
+**Copilot Chat**:
+- ✓ Better for explanations
+- ✓ Can answer questions
+- ✓ Helps with debugging
+- ✗ Slower for quick completions
+- ✗ More context switching
+
+**Best Practice**: Use both together
+
+### vs. Claude
+**GitHub Copilot**:
+- ✓ Faster inline suggestions
+- ✓ Better VS Code integration
+- ✓ No context switching
+- ✗ Smaller context window
+- ✗ No deep analysis
+
+**Claude**:
+- ✓ Larger context window
+- ✓ Better for complex analysis
+- ✓ Strong reasoning
+- ✗ No inline completions
+- ✗ Manual copy-paste workflow
+
+**Best Practice**: Copilot for coding, Claude for analysis
+
+### vs. Cursor
+**GitHub Copilot**:
+- ✓ Works in standard VS Code
+- ✓ Familiar environment
+- ✓ Just code completion
+- ✗ Single AI model
+- ✗ Limited multi-file edits
+
+**Cursor**:
+- ✓ Multiple AI models
+- ✓ Advanced features (Composer)
+- ✓ Better multi-file editing
+- ✗ Different editor
+- ✗ Learning curve
+
+**Best Practice**: Copilot for standard workflow, Cursor for advanced needs
+
+## Practical AL Examples
+
+### Creating Tables
+
+**Input** (comment):
+```al
+/// Customer loyalty tier table with tier name, min points, and discount percentage
+```
+
+**Copilot Generates**:
+```al
+table 50100 "Customer Loyalty Tier"
+{
+ DataClassification = CustomerContent;
+
+ fields
+ {
+ field(1; "Code"; Code[20])
+ {
+ Caption = 'Code';
+ }
+ field(2; "Tier Name"; Text[50])
+ {
+ Caption = 'Tier Name';
+ }
+ field(10; "Minimum Points"; Integer)
+ {
+ Caption = 'Minimum Points';
+ MinValue = 0;
+ }
+ field(20; "Discount Percentage"; Decimal)
+ {
+ Caption = 'Discount Percentage';
+ MinValue = 0;
+ MaxValue = 100;
+ DecimalPlaces = 0 : 2;
+ }
+ }
+
+ keys
+ {
+ key(PK; "Code")
+ {
+ Clustered = true;
+ }
+ key(Points; "Minimum Points")
+ {
+ }
+ }
+}
+```
+
+### Event Subscribers
+
+**Input** (partial code):
+```al
+[EventSubscriber(ObjectType::Table, Database::Customer, 'OnAfterValidateEvent', 'Credit Limit (LCY)', false, false)]
+```
+
+**Copilot Completes**:
+```al
+local procedure OnAfterValidateCreditLimit(var Rec: Record Customer; var xRec: Record Customer; CurrFieldNo: Integer)
+begin
+ // Add your implementation
+ if Rec."Credit Limit (LCY)" > 100000 then
+ if not Confirm('Credit limit exceeds 100,000. Continue?') then
+ Error('');
+end;
+```
+
+### API Pages
+
+**Input**:
+```al
+/// API v2.0 page for items exposing no, description, unit price, inventory
+```
+
+**Copilot Generates**:
+```al
+page 50100 "Item API"
+{
+ APIVersion = 'v2.0';
+ APIPublisher = 'yourcompany';
+ APIGroup = 'inventory';
+ EntityCaption = 'Item';
+ EntitySetCaption = 'Items';
+ PageType = API;
+ SourceTable = Item;
+ DelayedInsert = true;
+ ODataKeyFields = SystemId;
+
+ layout
+ {
+ area(Content)
+ {
+ repeater(GroupName)
+ {
+ field(id; Rec.SystemId)
+ {
+ Caption = 'Id';
+ Editable = false;
+ }
+ field(number; Rec."No.")
+ {
+ Caption = 'No.';
+ }
+ field(description; Rec.Description)
+ {
+ Caption = 'Description';
+ }
+ field(unitPrice; Rec."Unit Price")
+ {
+ Caption = 'Unit Price';
+ }
+ field(inventory; Rec.Inventory)
+ {
+ Caption = 'Inventory';
+ }
+ }
+ }
+ }
+}
+```
+
+### Test Code
+
+**Input**:
+```al
+[Test]
+procedure TestCustomerCreditLimitValidation
+```
+
+**Copilot Suggests**:
+```al
+[Test]
+procedure TestCustomerCreditLimitValidation()
+var
+ Customer: Record Customer;
+ LibrarySales: Codeunit "Library - Sales";
+begin
+ // [GIVEN] A customer with credit limit set
+ Customer.Init();
+ Customer."No." := LibrarySales.CreateCustomerNo();
+ Customer."Credit Limit (LCY)" := 50000;
+ Customer.Insert();
+
+ // [WHEN] Credit limit is exceeded
+ Customer.Validate("Credit Limit (LCY)", 150000);
+
+ // [THEN] Appropriate validation occurs
+ // Add assertions here
+end;
+```
+
+## Setup & Configuration
+
+### Installation
+
+See the detailed [GitHub Copilot Tool Page](../Tools/github-copilot) for complete installation instructions.
+
+**Quick Start**:
+1. Install GitHub Copilot extension in VS Code
+2. Sign in with GitHub account
+3. Verify subscription is active
+4. Start coding in AL files
+
+### Optimizing for AL
+
+**VS Code Settings**:
+```json
+{
+ "github.copilot.enable": {
+ "*": true,
+ "al": true
+ },
+ "editor.inlineSuggest.enabled": true,
+ "editor.quickSuggestions": {
+ "other": true,
+ "comments": true,
+ "strings": true
+ }
+}
+```
+
+**Project Setup**:
+- Keep `app.json` well-configured
+- Download BC symbols
+- Use descriptive file names
+- Maintain good code organization
+
+## Best Practices
+
+### Getting Quality Suggestions
+
+**Write Clear Comments**:
+```al
+❌ // calc total
+✅ /// Calculate the total sales amount for a customer including tax and discounts
+```
+
+**Use Meaningful Names**:
+```al
+❌ procedure Calc(x: Code[20]): Decimal
+✅ procedure CalculateCustomerTotalSales(CustomerNo: Code[20]): Decimal
+```
+
+**Provide Context**:
+- Keep related files open
+- Use consistent naming
+- Follow AL conventions
+- Add XML documentation
+
+### Review Checklist
+
+Before accepting Copilot suggestions:
+
+- [ ] Does it match my requirements?
+- [ ] Is the AL syntax correct?
+- [ ] Are BC APIs used properly?
+- [ ] Is it performant?
+- [ ] Does it follow best practices?
+- [ ] Is error handling appropriate?
+- [ ] Are data types correct?
+
+### Workflow Integration
+
+**Effective Use**:
+1. Write descriptive comment or start typing
+2. Review Copilot's suggestion
+3. Accept if good, modify if needed
+4. Test the generated code
+5. Refine as necessary
+
+**Don't**:
+- Blindly accept every suggestion
+- Skip testing generated code
+- Ignore code analysis warnings
+- Use without understanding
+
+## Pricing
+
+**Individual**:
+- $10/month or $100/year
+- Free for verified students
+- Free for open source maintainers
+
+**Business**:
+- $19/user/month
+- Organization management
+- Policy controls
+- Usage insights
+
+**Free Trial**: Usually 30 days available
+
+**Link**: [GitHub Copilot Pricing](https://github.com/features/copilot)
+
+## Privacy & Security
+
+### What Gets Sent
+- Code snippets from your editor
+- File names and structure
+- Code you're working on
+- Acceptance/rejection of suggestions
+
+### What You Control
+- Enable/disable globally
+- Disable for specific files/repos
+- Block suggestions from public code
+- Telemetry settings
+
+### Best Practices
+- Don't commit secrets to code
+- Review organization policies
+- Use Business plan for enterprise control
+- Understand data retention policies
+
+## Troubleshooting
+
+### Common Issues
+
+**No Suggestions Appearing**:
+- Check extension is enabled
+- Verify subscription is active
+- Ensure AL files are recognized
+- Reload VS Code window
+
+**Poor Quality Suggestions**:
+- Download BC symbols
+- Add more context (comments, related files)
+- Use descriptive names
+- Open related AL files
+
+**Slow Performance**:
+- Close unnecessary files
+- Check internet connection
+- Reduce workspace size
+- Update VS Code
+
+## Learning Resources
+
+### Official Resources
+- [GitHub Copilot Documentation](https://docs.github.com/copilot)
+- [VS Code Extension Page](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot)
+- [Getting Started Guide](https://docs.github.com/copilot/gettingstarted-with-github-copilot)
+
+### AL Guidelines Resources
+- [Setup Guide](../../gettingstarted/setup)
+- [Effective Prompting](../../gettingstarted/effective-prompting)
+- [Best Practices](../../gettingstarted/best-practices)
+- [Code Review Examples](../../gettingmore/code-review)
+
+## When to Use GitHub Copilot
+
+### ✓ Ideal For
+
+- Daily AL development
+- Quick code generation
+- Learning AL patterns
+- Reducing boilerplate
+- Standard BC implementations
+- Exploring APIs
+
+### ⚠ Consider Alternatives
+
+- **Complex analysis** → Use Claude or Copilot Chat
+- **Multi-file refactoring** → Use Cursor
+- **Learning deep concepts** → Use Copilot Chat or Claude
+- **Architecture decisions** → Human expertise required
+
+## Complementary Tools
+
+**Use With**:
+- [GitHub Copilot Chat](github-copilot-chat-agent) - For explanations and debugging
+- [AL Language Extension](../Tools/al-language) - For AL support
+- [AL Code Analyzers](../Tools/al-codecop) - For quality checks
+
+**Workflow**:
+1. Copilot generates code
+2. AL analyzers check quality
+3. Copilot Chat explains complex parts
+4. You review and test
+
+---
+
+**Next Steps**:
+- Install and try [GitHub Copilot](../Tools/github-copilot)
+- Learn about [Copilot Chat](github-copilot-chat-agent) for complementary features
+- Compare with other [AI Agents](./)
+
+**Questions?** Join [GitHub Discussions](https://github.com/microsoft/alguidelines/discussions)
diff --git a/content/docs/agentic-coding/CommunityResources/Agents/github-copilot-chat-agent.md b/content/docs/agentic-coding/CommunityResources/Agents/github-copilot-chat-agent.md
new file mode 100644
index 00000000..378bbd5f
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Agents/github-copilot-chat-agent.md
@@ -0,0 +1,627 @@
+---
+title: "GitHub Copilot Chat Agent"
+linkTitle: "Copilot Chat"
+weight: 2
+description: >
+ Conversational AI assistant for code explanations, debugging, and interactive development
+---
+
+## Overview
+
+GitHub Copilot Chat is a conversational AI assistant integrated into Visual Studio Code that allows you to ask questions, get explanations, and receive guidance through natural language interaction.
+
+**Developer**: GitHub (Microsoft)
+**Type**: Conversational AI Agent
+**Primary Use**: Interactive code assistance, explanations, and debugging
+**Integration**: Native VS Code extension
+
+## What is GitHub Copilot Chat?
+
+GitHub Copilot Chat provides an interactive AI assistant that:
+- Answers questions about code and AL development
+- Explains complex code segments
+- Helps debug issues
+- Suggests refactoring approaches
+- Provides learning and guidance
+- Generates code based on detailed requirements
+
+### How It Works
+
+1. **You ask**: Questions in natural language via chat panel or inline
+2. **Chat analyzes**: Your code, context, and question
+3. **Chat responds**: With explanations, code, or suggestions
+4. **You interact**: Ask follow-ups, refine, or apply suggestions
+
+**Example Interaction**:
+```
+You: Explain how this procedure validates customer credit limits
+
+Chat: This procedure validates customer credit limits by:
+1. Retrieving the customer record
+2. Calculating current outstanding amount
+3. Comparing against credit limit
+4. Raising an error if exceeded
+
+The validation ensures customers cannot exceed their credit limits
+before creating new sales orders...
+```
+
+## Key Capabilities
+
+### For AL Development
+
+**Code Explanation**:
+- Describes what AL code does
+- Explains Business Central concepts
+- Breaks down complex procedures
+- Clarifies AL syntax and patterns
+
+**Interactive Learning**:
+- Teaches AL patterns
+- Explains BC APIs
+- Provides examples
+- Answers "how do I..." questions
+
+**Debugging Assistance**:
+- Helps diagnose errors
+- Suggests fixes
+- Explains error messages
+- Proposes debugging strategies
+
+**Code Generation**:
+- Creates code from detailed descriptions
+- Generates test cases
+- Produces documentation
+- Builds complex structures
+
+## How to Use Copilot Chat
+
+### Chat Panel
+
+**Open Chat**:
+- Press `Ctrl+Shift+I` (Windows/Linux)
+- Press `Cmd+Shift+I` (Mac)
+- Click chat icon in sidebar
+
+**Chat Interface**:
+```
+┌─────────────────────────────┐
+│ GitHub Copilot Chat │
+├─────────────────────────────┤
+│ Your conversation history │
+│ │
+│ You: How do I... │
+│ Copilot: You can... │
+│ │
+├─────────────────────────────┤
+│ Type your question... [>]│
+└─────────────────────────────┘
+```
+
+### Inline Chat
+
+**Open Inline**:
+- Press `Ctrl+I` in editor
+- Chat appears next to your code
+- Ask quick questions
+- Get instant suggestions
+
+**Use Cases**:
+- Quick refactoring
+- Explain selected code
+- Fix errors in place
+- Generate code snippets
+
+### Slash Commands
+
+Quick access to common tasks:
+
+| Command | Purpose | Example |
+|---------|---------|---------|
+| `/explain` | Explain selected code | `/explain this validation logic` |
+| `/fix` | Suggest fixes | `/fix the error in this procedure` |
+| `/tests` | Generate tests | `/tests for this codeunit` |
+| `/help` | Show commands | `/help` |
+| `/clear` | Clear chat | `/clear` |
+
+## Strengths for AL Development
+
+### ✓ Excellent At
+
+**Learning & Understanding**:
+- Explaining AL concepts
+- Teaching BC patterns
+- Clarifying syntax
+- Answering "why" questions
+
+**Debugging Help**:
+- Diagnosing errors
+- Suggesting fixes
+- Explaining error messages
+- Proposing test cases
+
+**Code Exploration**:
+- Understanding legacy code
+- Identifying patterns
+- Finding issues
+- Suggesting improvements
+
+**Documentation**:
+- Generating XML comments
+- Creating README files
+- Writing user guides
+- Explaining features
+
+### ⚠ Use With Care
+
+**Generated Code**:
+- Always review for correctness
+- Verify BC compatibility
+- Test thoroughly
+- Adapt to your standards
+
+**Complex Business Logic**:
+- May not understand specific requirements
+- Review carefully
+- Validate against rules
+
+**Performance Advice**:
+- General suggestions may not fit your scenario
+- Profile and test
+- Verify with BC best practices
+
+## AL-Specific Examples
+
+### Code Explanation
+
+**You**:
+```
+Explain this procedure and when I should use it
+
+[Select and paste this code]:
+procedure CheckCreditLimit(var SalesHeader: Record "Sales Header")
+var
+ Customer: Record Customer;
+ OutstandingAmount: Decimal;
+begin
+ Customer.Get(SalesHeader."Sell-to Customer No.");
+ Customer.CalcFields("Balance (LCY)");
+ OutstandingAmount := Customer."Balance (LCY)" + SalesHeader."Amount Including VAT";
+
+ if OutstandingAmount > Customer."Credit Limit (LCY)" then
+ Error('Customer %1 would exceed credit limit. Outstanding: %2, Limit: %3',
+ Customer."No.", OutstandingAmount, Customer."Credit Limit (LCY)");
+end;
+```
+
+**Chat Explains**:
+```
+This procedure validates customer credit limits before allowing sales orders:
+
+Purpose:
+- Prevents customers from exceeding their credit limits
+- Calculates total outstanding amount (existing balance + new order)
+- Raises an error if limit would be exceeded
+
+When to use:
+- Before posting sales orders
+- In OnValidate triggers for sales headers
+- As part of order validation workflow
+
+Key points:
+- Uses CalcFields to get current customer balance
+- Adds new order amount to existing balance
+- Compares total against credit limit
+- Provides clear error message with details
+
+Best practice considerations:
+- Consider making error message translatable
+- Might want to allow override with permission
+- Could log credit limit violations for reporting
+```
+
+### Generating Complex Code
+
+**You**:
+```
+Create a codeunit that processes sales orders in batch.
+
+Requirements:
+- Accept list of sales order numbers
+- Validate each order (check credit, inventory)
+- Post valid orders
+- Collect and return errors for failed orders
+- Log to telemetry
+- Show progress dialog
+
+Use proper error handling and AL best practices.
+```
+
+**Chat Generates**:
+```al
+codeunit 50100 "Batch Sales Order Processor"
+{
+ ///
+ /// Processes multiple sales orders in batch with validation and error handling
+ ///
+ procedure ProcessOrders(OrderNumbers: List of [Code[20]]): List of [Text]
+ var
+ SalesHeader: Record "Sales Header";
+ Errors: List of [Text];
+ Dialog: Dialog;
+ Counter: Integer;
+ TotalCount: Integer;
+ begin
+ TotalCount := OrderNumbers.Count;
+ Dialog.Open('Processing orders...\Order #1######### of #2#########');
+
+ foreach OrderNo in OrderNumbers do begin
+ Counter += 1;
+ Dialog.Update(1, Counter);
+ Dialog.Update(2, TotalCount);
+
+ if not ProcessSingleOrder(OrderNo, Errors) then
+ LogProcessingError(OrderNo, Errors);
+ end;
+
+ Dialog.Close();
+ LogBatchCompletion(TotalCount, Counter - Errors.Count, Errors.Count);
+ exit(Errors);
+ end;
+
+ local procedure ProcessSingleOrder(OrderNo: Code[20]; var Errors: List of [Text]): Boolean
+ var
+ SalesHeader: Record "Sales Header";
+ SalesPost: Codeunit "Sales-Post";
+ begin
+ if not SalesHeader.Get(SalesHeader."Document Type"::Order, OrderNo) then begin
+ Errors.Add(StrSubstNo('Order %1 not found', OrderNo));
+ exit(false);
+ end;
+
+ if not ValidateOrder(SalesHeader, Errors) then
+ exit(false);
+
+ if not SalesPost.Run(SalesHeader) then begin
+ Errors.Add(StrSubstNo('Order %1: %2', OrderNo, GetLastErrorText()));
+ exit(false);
+ end;
+
+ exit(true);
+ end;
+
+ // Additional helper procedures...
+end;
+```
+
+### Debugging Assistance
+
+**You**:
+```
+I'm getting error "The field Customer No. must have a value"
+when trying to post a sales order. Here's my code:
+
+[Paste problematic code]
+
+What's wrong?
+```
+
+**Chat Analyzes**:
+```
+The error occurs because the Customer No. field is empty when posting.
+
+Looking at your code, the issue is on line 15:
+ SalesHeader."Sell-to Customer No." := '';
+
+This explicitly sets the customer number to empty before posting.
+
+Likely causes:
+1. Customer lookup/validation failed earlier
+2. Field being cleared unintentionally
+3. Missing validation before assignment
+
+Recommended fixes:
+
+1. Remove the line setting it to empty
+2. Add validation:
+ if Customer.Get(CustomerNo) then
+ SalesHeader.Validate("Sell-to Customer No.", CustomerNo)
+ else
+ Error('Customer %1 does not exist', CustomerNo);
+
+3. Add defensive check before posting:
+ if SalesHeader."Sell-to Customer No." = '' then
+ Error('Customer must be specified before posting');
+
+Would you like me to show the corrected version of your code?
+```
+
+### Learning AL Patterns
+
+**You**:
+```
+What's the standard AL pattern for implementing a document posting routine?
+```
+
+**Chat Explains**:
+```
+Standard AL document posting routines follow this pattern:
+
+1. Structure:
+ - Main posting codeunit
+ - Optional posting preview codeunit
+ - Optional batch posting codeunit
+
+2. Main Posting Codeunit Pattern:
+
+codeunit 50100 "Document-Post"
+{
+ TableNo = "Your Document Header";
+
+ trigger OnRun()
+ begin
+ PostDocument(Rec);
+ end;
+
+ procedure PostDocument(var DocHeader: Record "Your Document Header")
+ var
+ DocLine: Record "Your Document Line";
+ begin
+ // 1. Pre-posting checks
+ CheckDocumentIsReadyToPost(DocHeader);
+
+ // 2. Run events (OnBeforePost)
+ OnBeforePostDocument(DocHeader);
+
+ // 3. Lock tables
+ DocHeader.LockTable();
+
+ // 4. Post with transaction
+ PostDocumentLines(DocHeader);
+ FinalizePosting(DocHeader);
+
+ // 5. Run events (OnAfterPost)
+ OnAfterPostDocument(DocHeader);
+ end;
+
+ // Additional procedures...
+
+ // Events for extensibility
+ [IntegrationEvent(false, false)]
+ local procedure OnBeforePostDocument(var DocHeader: Record "Your Document Header")
+ begin
+ end;
+}
+
+Key principles:
+- Use transactions (implicit in OnRun trigger)
+- Lock records being modified
+- Provide integration events
+- Validate before posting
+- Handle errors gracefully
+- Use Codeunit.Run for error handling
+
+Would you like examples of specific parts?
+```
+
+## How It Differs from Other Agents
+
+### vs. GitHub Copilot (Inline)
+
+**Copilot Chat**:
+- ✓ Better for explanations
+- ✓ Can answer questions
+- ✓ Helps with debugging
+- ✓ Teaches concepts
+- ✗ Slower for quick edits
+
+**Copilot (Inline)**:
+- ✓ Faster completions
+- ✓ Less disruptive
+- ✓ Great for quick coding
+- ✗ No explanations
+- ✗ Can't answer questions
+
+**Use Together**: Inline for coding, Chat for understanding
+
+### vs. Claude
+
+**Copilot Chat**:
+- ✓ Native VS Code integration
+- ✓ Automatic code context
+- ✓ No copy-paste needed
+- ✗ Smaller context window
+- ✗ Less analytical depth
+
+**Claude**:
+- ✓ Larger context window
+- ✓ Deeper analysis
+- ✓ Better reasoning
+- ✗ Manual workflow
+- ✗ No editor integration
+
+**Use Cases**: Chat for daily work, Claude for deep analysis
+
+### vs. Cursor
+
+**Copilot Chat**:
+- ✓ Standard VS Code
+- ✓ Familiar environment
+- ✓ Single purpose
+- ✗ One AI model
+- ✗ Limited features
+
+**Cursor**:
+- ✓ Multiple AI models
+- ✓ Composer mode
+- ✓ Advanced features
+- ✗ Different editor
+- ✗ Higher learning curve
+
+**Use Cases**: Chat for standard workflow, Cursor for advanced needs
+
+## Best Practices
+
+### Asking Good Questions
+
+**Be Specific**:
+```
+❌ "Explain this"
+✅ "Explain how this procedure handles inventory updates
+ and why it uses a transaction"
+```
+
+**Provide Context**:
+```
+❌ "How do I validate?"
+✅ "How do I validate customer credit limits in AL before
+ posting a sales order? Show me the BC standard pattern."
+```
+
+**Break Down Complex Questions**:
+```
+Instead of:
+"Build complete order management system"
+
+Try:
+1. "Show me pattern for order validation"
+2. "Now add posting logic"
+3. "Add error handling"
+4. "Add telemetry"
+```
+
+### Using Responses Effectively
+
+**Review Code**:
+- Understand what it does
+- Verify BC compatibility
+- Check best practices
+- Test thoroughly
+
+**Learn from Explanations**:
+- Read thoroughly
+- Try examples yourself
+- Ask follow-up questions
+- Apply to your own code
+
+**Iterate**:
+- Start with basic request
+- Refine based on response
+- Add requirements gradually
+- Build understanding
+
+## Setup & Configuration
+
+### Installation
+
+See [GitHub Copilot Chat Tool Page](../Tools/github-copilot-chat) for detailed setup.
+
+**Quick Start**:
+1. Install GitHub Copilot Chat extension
+2. Verify Copilot subscription
+3. Open chat panel (`Ctrl+Shift+I`)
+4. Start asking questions
+
+### Optimizing for AL
+
+**Provide Context**:
+- Keep relevant AL files open
+- Reference BC objects specifically
+- Mention AL version when relevant
+- Include app.json configuration
+
+## Pricing
+
+**Included with GitHub Copilot**:
+- Individual: $10/month or $100/year
+- Business: $19/user/month
+- Free for students and OSS maintainers
+
+No separate charge - comes with Copilot subscription.
+
+## Privacy & Security
+
+### What Gets Sent
+- Your chat messages
+- Selected code snippets
+- Context from open files
+- Workspace information (limited)
+
+### Best Practices
+- Don't paste sensitive data
+- Avoid customer information
+- Review organization policies
+- Use business plan for enterprise controls
+
+## When to Use Copilot Chat
+
+### ✓ Ideal For
+
+- Learning AL and BC concepts
+- Understanding existing code
+- Debugging issues
+- Getting explanations
+- Generating complex code
+- Exploring patterns
+- Documentation creation
+
+### ⚠ Consider Alternatives
+
+- **Quick completions** → Use GitHub Copilot (inline)
+- **Very large context** → Use Claude
+- **Multi-file refactoring** → Use Cursor
+- **Critical decisions** → Consult humans
+
+## Practical Workflow
+
+**Daily Development**:
+1. Write code with Copilot inline suggestions
+2. Use Chat to explain complex parts
+3. Ask Chat for debugging help when stuck
+4. Generate tests with Chat
+5. Create documentation with Chat
+
+**Learning**:
+1. Ask Chat about AL patterns
+2. Request examples
+3. Get explanations of BC concepts
+4. Explore APIs and features
+
+**Code Review**:
+1. Select code section
+2. Ask Chat to review
+3. Get suggestions for improvements
+4. Learn better patterns
+
+## Resources
+
+### Official Documentation
+- [Copilot Chat Docs](https://docs.github.com/copilot/github-copilot-chat)
+- [VS Code Extension](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot-chat)
+
+### AL Guidelines Resources
+- [Effective Prompting](../../gettingstarted/effective-prompting)
+- [Best Practices](../../gettingstarted/best-practices)
+- [Getting More Examples](../../gettingmore)
+
+## Complementary Tools
+
+**Use With**:
+- [GitHub Copilot](github-copilot-agent) - For inline completions
+- [AL Language Extension](../Tools/al-language) - For AL support
+- [AL Code Analyzers](../Tools/al-codecop) - For quality
+
+**Workflow**:
+1. Copilot generates code quickly
+2. Chat explains what it does
+3. You understand and refine
+4. Analyzers validate quality
+
+---
+
+**Next Steps**:
+- Install [GitHub Copilot Chat](../Tools/github-copilot-chat)
+- Try with [GitHub Copilot](github-copilot-agent)
+- Compare with other [AI Agents](./)
+
+**Questions?** Join [GitHub Discussions](https://github.com/microsoft/alguidelines/discussions)
diff --git a/content/docs/agentic-coding/CommunityResources/Tools/_index.md b/content/docs/agentic-coding/CommunityResources/Tools/_index.md
new file mode 100644
index 00000000..8bddcda3
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Tools/_index.md
@@ -0,0 +1,151 @@
+---
+title: "MCP Servers"
+linkTitle: "Tools"
+weight: 3
+description: >
+ Model Context Protocol (MCP) servers that enhance AI-assisted AL development
+---
+
+## Overview
+
+This section catalogs Model Context Protocol (MCP) servers designed to enhance AI coding assistants for Business Central development. MCP is an open standard that enables AI assistants to connect to external tools, databases, and knowledge sources, making them significantly more powerful for AL development workflows.
+
+**What is MCP?**
+- Standard protocol for connecting AI assistants to external capabilities
+- STDIO transport for local execution
+- Tool-based architecture for exposing features to AI assistants
+- Supported by Claude Desktop, GitHub Copilot, Cursor, VS Code extensions, and more
+
+Each MCP server below has its own dedicated page with detailed information, setup instructions, and integration guidance.
+
+---
+
+## AL & Business Central MCP Servers
+
+### [BC Code Intelligence MCP](bc-code-intelligence-mcp.md)
+
+**Key Features**:
+- 14 specialist AI personas for BC development (Sam Coder, Dean Debug, Alex Architect, etc.)
+- 20+ MCP tools for knowledge discovery, code analysis, and workflow orchestration
+- Seamless specialist handoffs with context preservation
+- Integration with GitHub Copilot, Claude Desktop, VS Code
+
+---
+
+### [AL Dependency MCP Server](al-dependency-mcp-server.md)
+
+**Key Features**:
+- Exposes AL workspace compiled symbols (.app files) to AI assistants
+- 6 token-optimized tools for symbol search and dependency analysis
+- O(1) lookups with optimized indexing for 50MB+ symbol files
+- Auto-discovers .alpackages directories
+
+---
+
+### [Serena MCP](serena-mcp.md)
+
+**Key Features**:
+- Multi-language LSP-based coding assistant with AL support
+- AL Language Server integration via VS Code AL extension
+- Symbolic operations (find references, definitions, document symbols)
+- Supports 20+ languages including AL, Python, TypeScript, Rust, Go
+
+---
+
+### [AL Object ID Ninja MCP](al-objid-mcp-server.md)
+
+**Key Features**:
+- AL object ID collision prevention and management
+- Two modes: LITE (individual developers) and STANDARD (teams)
+- Backend integration for shared ID pools and team collaboration
+- Automatic app identification via Git integration
+
+---
+
+## DevOps & Productivity MCP Servers
+
+### [Azure DevOps MCP](azure-devops-mcp.md)
+
+**Key Features**:
+- Official Microsoft MCP server for Azure DevOps integration
+- 50+ tools covering work items, repos, pipelines, wiki, and advanced security
+- Domain filtering to manage tool count and focus
+- Multiple authentication options (interactive, azcli, env)
+
+---
+
+### [Clockify MCP](clockify-mcp.md)
+
+**Key Features**:
+- Comprehensive Clockify time tracking integration
+- 33 tools for workspace, client, project, task, tag, and time entry management
+- Timer start/stop functionality and bulk operations
+- Full CRUD operations for all Clockify entities
+
+---
+
+### [BC Telemetry Buddy (Waldo)](waldo-bctelemetrybuddy.md)
+
+**Key Features**:
+- Simple helpers for collecting Business Central telemetry
+- Forward telemetry events to a custom endpoint for analysis
+- Lightweight and easy to add to development workflows
+
+---
+
+### [NAB AL Tools MCP](nab-al-tools-mcp.md)
+
+**Key Features**:
+- XLIFF/XLF translation tooling exposed as MCP tools
+- Rich validation and annotations (Zod schemas)
+- Multiple invocation options (npx, global, local)
+
+---
+
+## Contributing Tools
+
+**Created a tool for AI-assisted AL development?**
+
+Share it with the community!
+
+**Submission Guidelines**:
+- Must be useful for AL/BC development
+- Should enhance AI-assisted workflows
+- Open source preferred
+- Well documented
+
+**How to Submit**: See [Contributing](../../../contributing) section
+
+---
+
+## Tool Safety & Privacy
+
+### Privacy Considerations
+
+**What Gets Shared**:
+- Code in your workspace (with AI assistants)
+- File names and structure
+- Your prompts and questions
+
+**Best Practices**:
+- Review extension permissions
+- Understand data handling
+- Use organization-approved tools
+- Don't include sensitive data in code
+
+### Security
+
+**Verify Extensions**:
+- Check publisher reputation
+- Read reviews
+- Review permissions requested
+- Keep extensions updated
+
+---
+
+## Related Resources
+
+- [Setup Guide](../../gettingstarted/setup) - Environment configuration
+- [Blog Posts](../articles) - Tool reviews and comparisons
+- [Videos](../videos) - Tool demonstrations
+- [GitHub Discussions](https://github.com/microsoft/alguidelines/discussions) - Tool recommendations and support
diff --git a/content/docs/agentic-coding/CommunityResources/Tools/al-dependency-mcp-server.md b/content/docs/agentic-coding/CommunityResources/Tools/al-dependency-mcp-server.md
new file mode 100644
index 00000000..7f467316
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Tools/al-dependency-mcp-server.md
@@ -0,0 +1,45 @@
+---
+title: "AL Dependency MCP Server"
+linkTitle: "AL Dependency MCP"
+weight: 2
+description: >
+ Expose AL workspace compiled symbols to AI assistants for intelligent code navigation and dependency analysis
+---
+
+## Overview
+
+The AL Dependency MCP Server exposes all compiled AL package symbols (.app files) to AI assistants, enabling them to understand dependencies, navigate code, and provide accurate suggestions based on Microsoft base app and other extension symbols.
+
+**Created by**: [Stefan Maron](https://github.com/StefanMaron)
+
+---
+
+## Key Features
+
+**Symbol Database**:
+- O(1) lookup performance via optimized indices
+- Streaming JSON parser for large symbol files (handles 50MB+ Microsoft base app)
+- Sub-100ms query responses
+- <500MB memory usage even with massive symbol databases
+
+**6 Token-Optimized Tools**:
+- `al_search_objects` - Search for AL objects across all packages
+- `al_get_object_definition` - Get full object definition with all members
+- `al_get_object_summary` - Get token-optimized summary (96% smaller)
+- `al_get_object_members` - Get object members without full definition
+- `al_packages` - List all available AL packages
+- `al_get_stats` - Get database statistics and diagnostics
+
+**Auto-Discovery**:
+- Automatically finds .alpackages directories in your workspace
+- Detects package changes in real-time
+- Supports multiple package sources
+
+**Requirements**: Node.js 18+, .NET SDK 8.0+ (for development)
+
+---
+
+## Links
+
+- **GitHub**: https://github.com/StefanMaron/AL-Dependency-MCP-Server
+- **npm Package**: https://www.npmjs.com/package/al-mcp-server
diff --git a/content/docs/agentic-coding/CommunityResources/Tools/al-development-collection.md b/content/docs/agentic-coding/CommunityResources/Tools/al-development-collection.md
new file mode 100644
index 00000000..7312b533
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Tools/al-development-collection.md
@@ -0,0 +1,49 @@
+---
+title: "AL Development Collection"
+linkTitle: "AL Development Collection"
+weight: 1
+description: >
+ AI Native AL Development toolkit with 37 Agent Primitives for systematic Business Central development
+---
+
+## Overview
+
+The AL Development Collection provides a complete AI-native development toolkit for Microsoft Dynamics 365 Business Central. Instead of ad-hoc AI usage, you get systematic engineering through 37 Agent Primitives organized across 3 framework layers implementing the AI Native-Instructions Architecture.
+
+**Created by**: [Javier Armesto](https://github.com/javiarmesto)
+
+---
+
+## Key Features
+
+**6 Role-Based Specialist Agents**:
+- al-architect 🏗️ (solution design), al-developer 💻 (implementation), al-debugger 🐛 (troubleshooting)
+- al-tester ✅ (TDD/quality), al-api 🌐 (API development), al-copilot 🤖 (AI features)
+
+**4 Orchestra System Agents** (Multi-agent TDD):
+- al-conductor 🎭 (orchestration), al-planning-subagent 🔍 (research)
+- al-implement-subagent 💻 (TDD implementation), al-review-subagent ✅ (validation)
+
+**9 Auto-Applied Instructions**:
+- Code style, naming conventions, performance patterns
+- Error handling, events, testing standards
+- Context-aware loading via `applyTo` patterns
+
+**18 Agentic Workflows**:
+- Environment setup (al-initialize, al-build)
+- Development (al-events, al-pages, al-permissions)
+- Analysis (al-diagnose, al-performance, al-migrate)
+- Copilot features (al-copilot-capability, al-copilot-promptdialog, al-copilot-test)
+
+**Smart Complexity Routing (Experimental)**:
+- 🟢 LOW → al-developer (direct implementation)
+- 🟡 MEDIUM → al-conductor (TDD orchestration)
+- 🔴 HIGH → al-architect → al-conductor (full design + TDD)
+
+---
+
+## Links
+
+- **GitHub**: https://github.com/javiarmesto/AL-Development-Collection-for-GitHub-Copilot
+- **Quick Start**: https://github.com/javiarmesto/AL-Development-Collection-for-GitHub-Copilot/blob/main/QUICK-START.md
+- **Complete Development Flow**: https://github.com/javiarmesto/AL-Development-Collection-for-GitHub-Copilot/blob/main/docs/workflows/complete-development-flow.md
diff --git a/content/docs/agentic-coding/CommunityResources/Tools/al-objid-mcp-server.md b/content/docs/agentic-coding/CommunityResources/Tools/al-objid-mcp-server.md
new file mode 100644
index 00000000..a520f6ed
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Tools/al-objid-mcp-server.md
@@ -0,0 +1,44 @@
+---
+title: "AL Object ID Ninja MCP"
+linkTitle: "AL Object ID Ninja"
+weight: 5
+description: >
+ AL object ID collision prevention and management for Business Central development teams
+---
+
+## Overview
+
+The AL Object ID Ninja MCP Server manages AL object IDs to prevent collisions in Business Central development. It provides two modes: LITE for individual developers and STANDARD for teams with shared ID pools and backend integration.
+
+**Created by**: [SShadowS (Torben Leth)](https://github.com/SShadowS)
+
+---
+
+## Key Features
+
+**Two Modes**:
+- **LITE Mode** (4 tools) - Individual developers: authorization, config, allocate_id, analyze_workspace
+- **STANDARD Mode** (8 tools) - Teams: adds pool management, consumption reports, backend sync, activity logs
+
+**Collision Prevention**:
+- Automatic ID conflict detection
+- Smart ID allocation with preview/reserve/reclaim
+- Git integration for automatic app identification
+- Real-time workspace analysis
+
+**Team Collaboration** (STANDARD):
+- Shared ID pools across team members
+- Backend integration with AL Object ID Ninja service
+- Consumption tracking and reporting
+- Audit trail with activity logs
+
+**Configuration**:
+Set `MCP_MODE` environment variable to `lite` or `standard` (default: lite)
+
+---
+
+## Links
+
+- **GitHub**: https://github.com/SShadowS/al-objid-mcp-server
+- **npm Package**: https://www.npmjs.com/package/@sshadows/objid-mcp
+- **Backend Service**: AL Object ID Ninja (vjekocom-alext-weu.azurewebsites.net)
diff --git a/content/docs/agentic-coding/CommunityResources/Tools/azure-devops-mcp.md b/content/docs/agentic-coding/CommunityResources/Tools/azure-devops-mcp.md
new file mode 100644
index 00000000..1ab55260
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Tools/azure-devops-mcp.md
@@ -0,0 +1,46 @@
+---
+title: "Azure DevOps MCP"
+linkTitle: "Azure DevOps MCP"
+weight: 4
+description: >
+ Official Microsoft MCP server for comprehensive Azure DevOps integration with AI assistants
+---
+
+## Overview
+
+The Azure DevOps MCP Server is Microsoft's official Model Context Protocol implementation for Azure DevOps, providing AI assistants with comprehensive access to work items, repositories, pipelines, wiki, search, and advanced security features.
+
+**Publisher**: [Microsoft](https://github.com/microsoft)
+
+---
+
+## Key Features
+
+**50+ Tools Across All Azure DevOps Services**:
+- Core (projects, teams, identities)
+- Work (iterations, capacity)
+- Work Items (CRUD, queries, comments, linking)
+- Repositories (repos, branches, PRs, commits, file contents)
+- Pipelines (builds, logs, artifacts, triggering)
+- Wiki (pages, content, CRUD operations)
+- Search (code, wiki, work items)
+- Advanced Security (alerts, findings)
+
+**Domain Filtering**:
+- Enable only needed domains to reduce tool count
+- Example: `-d work-items -d repositories` for focused workflows
+
+**Multiple Authentication Options**:
+- Interactive (default) - Browser-based OAuth
+- Azure CLI - Use existing `az login` session
+- Environment variable - PAT via `AZURE_DEVOPS_PAT`
+
+
+---
+
+## Links
+
+- **GitHub**: https://github.com/microsoft/azure-devops-mcp
+- **npm Package**: https://www.npmjs.com/package/@azure-devops/mcp
+- **Getting Started**: https://github.com/microsoft/azure-devops-mcp/blob/main/docs/GETTINGSTARTED.md
+
diff --git a/content/docs/agentic-coding/CommunityResources/Tools/bc-code-intelligence-mcp.md b/content/docs/agentic-coding/CommunityResources/Tools/bc-code-intelligence-mcp.md
new file mode 100644
index 00000000..9597cc61
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Tools/bc-code-intelligence-mcp.md
@@ -0,0 +1,43 @@
+---
+title: "BC Code Intelligence MCP"
+linkTitle: "BC Code Intelligence"
+weight: 1
+description: >
+ Business Central knowledge base with 14 specialist AI personas for comprehensive development guidance
+---
+
+## Overview
+
+The BC Code Intelligence MCP Server provides atomic Business Central knowledge topics through an innovative specialist system. Instead of a single generic AI, you interact with 14 domain-expert personas who provide focused, expert guidance for specific BC development areas.
+
+**Created by**: [Jeremy Vyska](https://github.com/JeremyVyska)
+
+---
+
+## Key Features
+
+**14 BC Domain Specialists**:
+- Sam Coder (AL coding), Dean Debug (troubleshooting), Alex Architect (design)
+- Casey Cloud (cloud/SaaS), Morgan Modern (DevOps), Taylor Test (testing)
+- Quinn Quality (code quality), Riley Report (reporting), Parker Performance (optimization)
+- Jordan Journey (learning), Blake Business (business logic), Skyler Security (security)
+- Drew Data (data modeling), Finley Flow (workflow/UX)
+
+**Smart Routing**:
+- Automatic routing to the right specialist based on your question
+- Multi-specialist collaboration for complex questions
+- Seamless context handoffs between specialists
+
+**20+ MCP Tools**:
+- Knowledge discovery (search topics, get content)
+- Specialist management (routing, handoffs)
+- Code analysis (reviews, patterns, architecture)
+- Workflow orchestration
+
+---
+
+## Links
+
+- **GitHub**: https://github.com/JeremyVyska/bc-code-intelligence-mcp
+- **Knowledge Base**: https://github.com/JeremyVyska/bc-code-intelligence
+- **npm Package**: https://www.npmjs.com/package/bc-code-intelligence-mcp
diff --git a/content/docs/agentic-coding/CommunityResources/Tools/clockify-mcp.md b/content/docs/agentic-coding/CommunityResources/Tools/clockify-mcp.md
new file mode 100644
index 00000000..dd805816
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Tools/clockify-mcp.md
@@ -0,0 +1,44 @@
+---
+title: "Clockify MCP"
+linkTitle: "Clockify MCP"
+weight: 6
+description: >
+ Comprehensive Clockify time tracking integration for project management and invoicing
+---
+
+## Overview
+
+The Clockify MCP Server provides comprehensive integration with Clockify time tracking and project management. It exposes 33 tools for managing workspaces, clients, projects, tasks, tags, time entries, and timers through AI assistants.
+
+**Created by**: [Jeremy Vyska](https://github.com/JeremyVyska)
+
+---
+
+## Key Features
+
+**33 Tools for Complete Clockify Management**:
+- Workspace Management - list, get, update workspaces
+- Client Management - full CRUD operations
+- Project Management - full CRUD operations
+- Task Management - full CRUD operations
+- Tag Management - full CRUD operations
+- Time Entry Management - CRUD plus bulk operations
+- Timer Operations - start, stop, get active timer
+
+**Enhanced from Reference Implementation**:
+- Full CRUD operations (create, read, update, delete)
+- Bulk operations for time entries
+- Comprehensive filtering and pagination
+- Timer start/stop functionality
+
+**Requirements**:
+- Node.js 20+
+- CLOCKIFY_API_KEY from Clockify profile settings
+
+---
+
+## Links
+
+- **GitHub**: https://github.com/JeremyVyska/clockify-mcp
+- **Clockify API**: https://clockify.me/developers-api
+- **Get API Key**: https://app.clockify.me/user/settings (Profile Settings → API)
diff --git a/content/docs/agentic-coding/CommunityResources/Tools/nab-al-tools-mcp.md b/content/docs/agentic-coding/CommunityResources/Tools/nab-al-tools-mcp.md
new file mode 100644
index 00000000..a80c09c6
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Tools/nab-al-tools-mcp.md
@@ -0,0 +1,79 @@
+---
+title: "NAB AL Tools MCP"
+linkTitle: "NAB AL Tools"
+weight: 8
+description: >
+ XLIFF translation and localization tools exposed as an MCP server for AL projects.
+---
+
+## Overview
+
+The NAB AL Tools MCP Server exposes XLIFF translation management capabilities (the same core features used by the NAB AL Tools VS Code extension) as a standalone MCP server. It lets AI assistants and other MCP-compatible clients inspect, create, refresh and save XLF files used for AL localization workflows.
+
+**Publisher**: [nabsolutions / Johannes Wikman](https://github.com/jwikman)
+
+---
+
+## Key Features
+
+- Comprehensive XLF/XLIFF tooling: refresh, create language XLFs, search by keyword, get untranslated texts, and more
+- Proper MCP annotations and Zod input validation for robust error handling
+- Configurable: works with npx, global install, or local project install
+- Supports pagination, batch saves and performant parsing for large translation files
+- Designed to work locally (openWorldHint: false) and respects workspace boundaries
+
+---
+
+## Installation & Usage
+
+Recommended via npx (no install required):
+
+```bash
+npx -y @nabsolutions/nab-al-tools-mcp
+```
+
+Or install globally:
+
+```bash
+npm install -g @nabsolutions/nab-al-tools-mcp
+```
+
+MCP client example (npx):
+
+```json
+{
+ "mcpServers": {
+ "nab-al-tools": {
+ "command": "npx",
+ "args": ["-y", "@nabsolutions/nab-al-tools-mcp"]
+ }
+ }
+}
+```
+
+---
+
+## Notable Tools (summary)
+
+- `refreshXlf` — synchronize generated .g.xlf with target XLF
+- `getTextsToTranslate` — list untranslated units with pagination
+- `getTranslatedTextsMap` — fetch existing translations grouped by source
+- `getTranslatedTextsByState` — filter translations by state (needs-review, translated, final)
+- `saveTranslatedTexts` — batch save translated units (up to configured limits)
+- `createLanguageXlf` — generate new language XLFs (can optionally match base app translations)
+- `getTextsByKeyword` — search XLF content by keyword or regex
+- `getGlossaryTerms` — return builtin BC glossary pairs for consistent terminology
+
+---
+
+## Requirements
+
+- Node.js >= 20
+- npm (if installing)
+
+---
+
+## Links
+
+- **GitHub**: https://github.com/jwikman/nab-al-tools
+- **MCP readme (source)**: https://github.com/jwikman/nab-al-tools/blob/main/extension/MCP_SERVER.md
diff --git a/content/docs/agentic-coding/CommunityResources/Tools/serena-mcp.md b/content/docs/agentic-coding/CommunityResources/Tools/serena-mcp.md
new file mode 100644
index 00000000..2ead1ed0
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Tools/serena-mcp.md
@@ -0,0 +1,46 @@
+---
+title: "Serena MCP"
+linkTitle: "Serena MCP"
+weight: 3
+description: >
+ Multi-language LSP-based coding assistant with AL Language Server support for Business Central
+---
+
+## Overview
+
+Serena is an AI-first code editor that provides MCP (Model Context Protocol) integration with Language Server Protocol (LSP) support for 20+ programming languages, including Business Central AL. It enables AI assistants to perform accurate code navigation, symbol lookup, and refactoring by leveraging native language servers.
+
+**Created by**: [oraios](https://github.com/oraios)
+
+---
+
+## Key Features
+
+**AL Language Server Support**:
+- Automatic setup using VS Code AL extension (`ms-dynamics-smb.al`)
+- Native AL LSP integration with custom AL commands
+- Platform detection for Windows/Linux/macOS
+- Proper AL Language Server initialization
+
+**20+ Supported Languages**:
+- AL, Python, TypeScript/JavaScript, Rust, Go, C/C++, C#, Java, Ruby, PHP, Kotlin, Swift, and more
+- Each language uses native LSP implementation for maximum accuracy
+
+**Symbolic Operations**:
+- Find References - Locate all usages across codebase
+- Go to Definition - Jump to symbol definitions
+- Document/Workspace Symbols - Search and list symbols
+- Type & Call Hierarchy - Navigate relationships and call traces
+
+**Modes**:
+- Lite Mode - Minimal tool set for focused tasks
+- Standard Mode - Full tool suite with additional capabilities
+
+---
+
+## Links
+
+- **GitHub**: https://github.com/oraios/serena
+- **PyPI Package**: https://pypi.org/project/serena-mcp/
+- **Changelog**: https://github.com/oraios/serena/blob/main/CHANGELOG.md
+
diff --git a/content/docs/agentic-coding/CommunityResources/Tools/waldo-bctelemetrybuddy.md b/content/docs/agentic-coding/CommunityResources/Tools/waldo-bctelemetrybuddy.md
new file mode 100644
index 00000000..56ae5d8c
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/Tools/waldo-bctelemetrybuddy.md
@@ -0,0 +1,29 @@
+---
+title: "BC Telemetry Buddy (waldo)"
+linkTitle: "BC Telemetry Buddy"
+weight: 7
+description: >
+ A small utility to help collect and forward Business Central telemetry for analysis and debugging.
+---
+
+## Overview
+
+BC Telemetry Buddy (by waldo) is a community tool that simplifies collecting telemetry from Business Central extensions and forwarding events to analysis endpoints. It's useful for teams who want lightweight telemetry during development or targeted diagnostics in production-like environments.
+
+**Publisher**: [waldo1001](https://github.com/waldo1001)
+
+---
+
+## Key Features
+
+- Easy instrumentation helpers for common telemetry scenarios
+- Lightweight forwarding to custom endpoints
+- Works well in development environments and with local testing setups
+- Simple configuration and minimal dependencies
+
+---
+
+## Links
+
+- **GitHub**: https://github.com/waldo1001/waldo.BCTelemetryBuddy
+- **Marketplace**: [BC Telemetry Buddy](https://marketplace.visualstudio.com/items?itemName=waldoBC.bc-telemetry-buddy)
\ No newline at end of file
diff --git a/content/docs/agentic-coding/CommunityResources/_index.md b/content/docs/agentic-coding/CommunityResources/_index.md
new file mode 100644
index 00000000..c98ceb4c
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/_index.md
@@ -0,0 +1,131 @@
+---
+title: "Community Resources"
+linkTitle: "Community Resources"
+weight: 100
+description: >
+ Curated resources from the AL and Business Central community for agentic coding
+---
+
+## Overview
+
+The AL and Business Central community has created excellent resources for learning about and using AI-powered coding assistants. This section curates and summarizes these valuable community contributions.
+
+## Resource Categories
+
+### AI Coding Agents
+Learn about different AI assistants available for AL development, their capabilities, and when to use each one.
+
+- **[AI Coding Agents](Agents)** - Compare GitHub Copilot, Claude, Cursor, and other AI agents for AL development
+
+### Articles & Blog Posts
+In-depth articles and blog posts from community members sharing their experiences and insights with AI-assisted AL development.
+
+### Video Tutorials
+Video content demonstrating AI coding techniques, tips, and workflows for Business Central development.
+
+### Tools & Extensions
+Community-created tools and VS Code extensions that enhance AI-assisted development.
+
+- **[Tools & Extensions](Tools)** - Detailed guides for GitHub Copilot, AL Language extension, and other essential tools
+
+### Discussions & Forums
+Active community discussions about agentic coding practices, challenges, and solutions.
+
+## Featured Resources
+
+### Getting Started with AI for AL
+Collection of introductory resources for developers new to AI-assisted AL development.
+
+### Advanced Techniques
+Resources covering advanced AI prompting, workflow optimization, and specialized use cases.
+
+### Real-World Examples
+Case studies and examples from community members showing AI assistance in production projects.
+
+## Contributing Resources
+
+Found a great resource about AI-assisted AL development? We welcome contributions!
+
+**To suggest a resource:**
+1. Ensure it's relevant to AL/Business Central development
+2. Verify the content is high-quality and accurate
+3. Check it's not already listed
+4. Submit via the [Contributing](../../contributing) process
+
+**Resource Guidelines:**
+- Must be publicly accessible
+- Should provide clear value to AL developers
+- Content should be accurate and up-to-date
+- Appropriate for a professional audience
+
+## Resource Pages
+
+Explore detailed summaries and links for specific types of resources:
+
+- **[Blog Posts & Articles](articles)** - Written content from the community
+- **[Video Tutorials](videos)** - Visual learning resources
+- **[Tools & Extensions](Tools)** - Utilities that enhance AI development
+- **[Community Discussions](https://github.com/microsoft/alguidelines/discussions)** - Join the conversation on GitHub
+
+## Stay Connected
+
+### Community Platforms
+
+**Business Central Community**
+- [Business Central Community Forum](https://community.dynamics.com/business/)
+- Dedicated sections for development questions and AI tooling
+
+**GitHub**
+- [microsoft/AL](https://github.com/microsoft/AL) - AL Language repository
+- Various community extension repositories with AI-friendly code
+
+**Social Media**
+- Follow #MSDyn365BC hashtag
+- Follow #ALDevelopment hashtag
+- Connect with AL developers sharing AI tips
+
+**Discord & Slack**
+- Business Central developer communities
+- Channels dedicated to development tools and automation
+
+## Regular Contributors
+
+The community is grateful to developers who regularly share their knowledge about AI-assisted development. Check out content from active contributors in each resource category.
+
+## Learning Paths
+
+### For Beginners
+1. Start with [Getting Started](../gettingstarted) in this hub
+2. Watch introductory videos about AI coding assistants
+3. Read beginner-friendly blog posts
+4. Try simple prompts with your own code
+
+### For Intermediate Developers
+1. Review advanced prompting techniques
+2. Study real-world examples
+3. Experiment with specialized tools
+4. Participate in community discussions
+
+### For Advanced Users
+1. Explore cutting-edge use cases
+2. Contribute your own insights
+3. Develop tools for the community
+4. Mentor others in AI-assisted development
+
+## Quality Standards
+
+Resources listed here are reviewed for:
+- **Accuracy**: Content is technically correct
+- **Relevance**: Directly applicable to AL/BC development
+- **Value**: Provides genuine insights or learning
+- **Accessibility**: Publicly available and clearly presented
+
+## Updates
+
+This section is regularly updated with new community resources. Check back often for the latest content!
+
+**Last Updated**: Check individual resource pages for update dates.
+
+## Feedback
+
+Have feedback about these resources or suggestions for improvement? Please share through our [Contributing](../../contributing) channels.
diff --git a/content/docs/agentic-coding/CommunityResources/articles.md b/content/docs/agentic-coding/CommunityResources/articles.md
new file mode 100644
index 00000000..44ec92a6
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/articles.md
@@ -0,0 +1,112 @@
+---
+title: "Blog Posts & Articles"
+linkTitle: "Articles"
+weight: 1
+description: >
+ Written content from the community about AI-assisted AL development
+---
+
+## Overview
+
+This page curates blog posts, articles, and written guides from the Business Central community about using AI coding assistants for AL development.
+
+## Featured Articles
+
+### Getting Started
+
+#### "AI for BC Development - The Knowledge Gap That Ships to Production" — Kine
+**Author**: Kine (blog.kine.cz)
+**Published**: 2025
+**Summary**: A critical self-assessment guide on whether you are ready to validate what AI produces for BC development. Covers common AI mistakes in AL code (wrong field assignment, missing keys, reinventing standard libraries) and what BC knowledge areas you need to review AI output responsibly.
+
+**Key Takeaways**:
+- Common AI mistakes in AL code that ship to production
+- Self-assessment framework for AI-assisted development readiness
+- BC knowledge areas required to review AI output responsibly
+- Practical examples of wrong field assignments, missing keys, and reinvented standard libraries
+
+**Link**: https://blog.kine.cz/posts/bcdevelopmentserie-02b/
+
+---
+
+#### "Vibe Coding — yes or no?" — Demiliani
+**Author**: Demiliani
+**Published**: 2025-08-21
+**Summary**: A thoughtful exploration of the Vibe Coding approach and whether its rules and conventions help or hinder real-world AL development.
+
+**Key Takeaways**:
+- Pros and cons of strict Vibe Coding rules
+- When to adopt vs. adapt guidance for your team
+- Practical examples and trade-offs
+
+**Link**: https://demiliani.com/2025/08/21/vibe-coding-yes-or-no/
+
+---
+
+#### "Gestión de contexto y estados en servidores MCP" — TechSphere Dynamics
+**Author**: TechSphere Dynamics
+**Published**: 2025-08-15
+**Summary**: A Spanish-language deep dive into context handling and state management patterns for MCP servers, including practical patterns used in production systems.
+
+**Key Takeaways**:
+- Context lifecycle and state management strategies
+- Common pitfalls when preserving or discarding context
+- Examples of robust MCP server patterns
+
+**Link**: https://techspheredynamics.com/2025/08/15/gestion-de-contexto-y-estados-en-servidores-mcp/
+
+---
+
+#### "Testing GitHub Copilot: knowledge engineering — what actually works and what doesn't" — Nubimancy
+**Author**: Nubimancy
+**Published**: 2025-09-09
+**Summary**: An empirical look at how well GitHub Copilot handles knowledge-engineering tasks, with experiments and practical recommendations for prompt authors.
+
+**Key Takeaways**:
+- Which prompting patterns produce reliable results
+- When Copilot is prone to hallucination or brittle outputs
+- Strategies to validate and refine AI-suggested knowledge artifacts
+
+**Link**: https://nubimancy.com/2025/09/09/testing-github-copilot-knowledge-engineering-what-actually-works-and-what-doesnt/
+
+---
+
+Each of these are just great examples from those blogs, so make sure to explore around!
+
+---
+
+## Contributing Articles
+
+Have you written about AI-assisted AL development? We'd love to include high-quality, publicly accessible content from the community.
+
+Submission checklist:
+- Publicly accessible article or blog post
+- Clearly focused on AL / Business Central development
+- Accurate, well-written, and actionable
+- Original work or properly attributed
+
+How to submit:
+1. Review the [Contributing](../../../contributing) guidelines
+2. Open a pull request adding your article to this list
+3. Provide: Title, Author, Short Summary (1–2 lines), and Link
+
+## Article Quality Criteria
+
+Items listed on this page should meet these standards:
+- Technically accurate
+- Relevant to AL development
+- Clear and well-written
+- Provides actionable insights
+- Publicly accessible
+
+## Updates
+
+This is a living document — new resources will be added as the community publishes them. To suggest an addition, open a PR against this repository and follow the submission checklist above.
+
+---
+
+## Related Resources
+
+- [Video Tutorials](../videos) - Visual learning content
+- [Tools & Extensions](../tools) - Development utilities
+- [Discussions](../discussions) - Community conversations
diff --git a/content/docs/agentic-coding/CommunityResources/tools.md b/content/docs/agentic-coding/CommunityResources/tools.md
new file mode 100644
index 00000000..41e86422
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/tools.md
@@ -0,0 +1,569 @@
+---
+title: "Tools & Extensions"
+linkTitle: "Tools"
+weight: 3
+description: >
+ VS Code extensions and tools that enhance AI-assisted AL development
+---
+
+## Overview
+
+This page catalogs VS Code extensions, utilities, and tools that complement AI coding assistants for Business Central development.
+
+## AI Coding Assistants
+
+### GitHub Copilot
+**Publisher**: GitHub
+**Type**: AI Code Completion
+
+**Features**:
+- Inline code suggestions
+- Chat interface for questions
+- Multi-file context awareness
+- Code explanation and refactoring
+
+**AL-Specific Benefits**:
+- Understands AL syntax and patterns
+- Suggests Business Central APIs
+- Generates AL-compliant code
+- Helps with event subscribers and patterns
+
+**Installation**:
+```
+Extension ID: GitHub.copilot
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot)
+
+**Pricing**: Subscription required (free for students/open source maintainers)
+
+---
+
+### GitHub Copilot Chat
+**Publisher**: GitHub
+**Type**: AI Chat Assistant
+
+**Features**:
+- Interactive chat in VS Code
+- Code explanations
+- Debugging assistance
+- Inline code chat
+
+**Best For**:
+- Asking questions about AL code
+- Getting explanations of Business Central patterns
+- Debugging assistance
+- Code refactoring discussions
+
+**Installation**:
+```
+Extension ID: GitHub.copilot-chat
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot-chat)
+
+**Requires**: GitHub Copilot subscription
+
+---
+
+## AL Development Extensions
+
+### AL Language
+**Publisher**: Microsoft
+**Type**: Language Support
+
+**Why It's Essential**:
+- Core AL language support
+- Syntax highlighting
+- IntelliSense
+- Code analysis
+
+**AI Integration**:
+- Provides context for AI suggestions
+- Enables AL-aware completions
+- Works with AL code analyzers
+
+**Installation**:
+```
+Extension ID: ms-dynamics-smb.al
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-dynamics-smb.al)
+
+**Required**: Yes, for AL development
+
+---
+
+### AL Code Outline
+**Publisher**: Community
+**Type**: Code Navigation
+
+**Features**:
+- Visual code structure
+- Quick navigation
+- Object overview
+- Procedure list
+
+**AI Enhancement**:
+- Helps AI understand code structure
+- Easier to reference specific procedures in prompts
+- Better context for AI suggestions
+
+**Installation**:
+```
+Extension ID: davidfeldhoff.al-code-outline
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=davidfeldhoff.al-code-outline)
+
+---
+
+### AL Object Designer
+**Publisher**: Community
+**Type**: Object Browser
+
+**Features**:
+- Browse all AL objects
+- Search functionality
+- Quick navigation
+- Object creation
+
+**AI Enhancement**:
+- Quickly find objects to reference in prompts
+- Better workspace navigation
+- Context for AI when working with multiple objects
+
+**Installation**:
+```
+Extension ID: martonsagi.al-object-designer
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=martonsagi.al-object-designer)
+
+---
+
+### AL Variable Helper
+**Publisher**: Community
+**Type**: Variable Management
+
+**Features**:
+- Auto-declare variables
+- Variable suggestions
+- Type inference
+- Quick fixes
+
+**AI Complement**:
+- Use with AI-generated code to clean up variables
+- Auto-complete variables from AI suggestions
+- Streamline AI-generated code
+
+**Installation**:
+```
+Extension ID: rasmus.al-var-helper
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=rasmus.al-var-helper)
+
+---
+
+### AL Test Runner
+**Publisher**: Community
+**Type**: Test Framework
+
+**Features**:
+- Run AL tests from VS Code
+- Test results visualization
+- Code coverage
+- Test debugging
+
+**AI Use Cases**:
+- Test AI-generated code
+- Verify AI refactoring
+- Run tests for AI-written procedures
+
+**Installation**:
+```
+Extension ID: jamespearson.al-test-runner
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=jamespearson.al-test-runner)
+
+---
+
+## Code Quality Tools
+
+### AL CodeCop
+**Type**: Code Analyzer
+**Included In**: AL Language Extension
+
+**What It Does**:
+- Enforces AL coding standards
+- Identifies best practice violations
+- Provides code fixes
+
+**AI Integration**:
+- Review AI-generated code
+- Ensure AI follows standards
+- Auto-fix AI code issues
+
+**Usage**: Enabled in `app.json`:
+```json
+"codeAnalyzers": ["${CodeCop}"]
+```
+
+---
+
+### Business Central Performance Toolkit
+**Publisher**: Microsoft
+**Type**: Performance Testing
+
+**Features**:
+- Performance scenario testing
+- Load testing
+- Performance metrics
+
+**AI Use Cases**:
+- Test performance of AI-generated code
+- Validate AI optimization suggestions
+- Benchmark before/after AI refactoring
+
+**Link**: [GitHub Repository](https://github.com/microsoft/BusinessCentralPerfToolkit)
+
+---
+
+## Documentation Tools
+
+### AL XML Documentation
+**Publisher**: Community
+**Type**: Documentation Generator
+
+**Features**:
+- Generate XML documentation
+- Documentation snippets
+- Template support
+
+**AI Enhancement**:
+- Complement AI-generated docs
+- Standardize documentation format
+- Quick doc generation
+
+**Installation**:
+```
+Extension ID: andrzejzwierzchowski.al-xml-doc
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=andrzejzwierzchowski.al-xml-doc)
+
+---
+
+### Markdown All in One
+**Publisher**: Community
+**Type**: Markdown Editor
+
+**Features**:
+- Markdown preview
+- Keyboard shortcuts
+- Auto-completion
+- Table formatting
+
+**AI Use Cases**:
+- Edit AI-generated README files
+- Format AI-generated documentation
+- Create documentation with AI assistance
+
+**Installation**:
+```
+Extension ID: yzhang.markdown-all-in-one
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=yzhang.markdown-all-in-one)
+
+---
+
+## Productivity Enhancers
+
+### GitLens
+**Publisher**: GitKraken
+**Type**: Git Enhancement
+
+**Features**:
+- Code authorship
+- Commit history
+- Blame annotations
+- Git visualization
+
+**AI Context**:
+- See who wrote code (human vs AI-assisted)
+- Track AI-generated code changes
+- Review AI code evolution
+
+**Installation**:
+```
+Extension ID: eamodio.gitlens
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens)
+
+---
+
+### Code Spell Checker
+**Publisher**: Street Side Software
+**Type**: Spell Checker
+
+**Features**:
+- Spell checking in code
+- Supports AL/BC terms
+- Custom dictionaries
+
+**AI Complement**:
+- Catch spelling errors in AI-generated code
+- Improve AI-generated documentation
+- Ensure consistent terminology
+
+**Installation**:
+```
+Extension ID: streetsidesoftware.code-spell-checker
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker)
+
+---
+
+### Better Comments
+**Publisher**: Community
+**Type**: Comment Enhancement
+
+**Features**:
+- Color-coded comments
+- TODO highlighting
+- Comment categories
+
+**AI Use Cases**:
+- Mark AI-generated code sections
+- Highlight AI code for review
+- Track AI TODOs
+
+**Installation**:
+```
+Extension ID: aaron-bond.better-comments
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=aaron-bond.better-comments)
+
+---
+
+## Specialized Tools
+
+### AL Toolbox
+**Publisher**: Community
+**Type**: Utility Collection
+
+**Features**:
+- Code snippets
+- Quick actions
+- AL utilities
+- Productivity commands
+
+**AI Enhancement**:
+- Complements AI code generation
+- Quick fixes for AI code
+- Utilities for AI-generated projects
+
+**Installation**:
+```
+Extension ID: BartPermentier.al-toolbox
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=BartPermentier.al-toolbox)
+
+---
+
+### AZ AL Dev Tools
+**Publisher**: Community
+**Type**: Development Tools
+
+**Features**:
+- Code generators
+- AL object wizards
+- Development utilities
+- Code analysis
+
+**AI Complement**:
+- Generate boilerplate for AI to enhance
+- Analyze AI-generated code structure
+- Quick object creation
+
+**Installation**:
+```
+Extension ID: andrzejzwierzchowski.az-al-dev-tools-vscode
+```
+
+**Link**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=andrzejzwierzchowski.az-al-dev-tools-vscode)
+
+---
+
+## Recommended Extension Packs
+
+### Essential AL + AI Setup
+Minimal setup for AI-assisted AL development:
+
+1. **AL Language** (Microsoft)
+2. **GitHub Copilot** (GitHub)
+3. **GitHub Copilot Chat** (GitHub)
+4. **AL Code Outline** (Community)
+5. **AL Object Designer** (Community)
+
+### Complete AL Development Suite
+Comprehensive setup:
+
+- All from Essential Setup
+- AL Variable Helper
+- AL Test Runner
+- AL XML Documentation
+- GitLens
+- Code Spell Checker
+- Better Comments
+
+### Team Development
+Recommended for development teams:
+
+- Complete Suite extensions
+- AL Toolbox
+- AZ AL Dev Tools
+- Business Central Performance Toolkit
+
+## Configuration Tips
+
+### Optimizing for AI
+Add to your `settings.json`:
+
+```json
+{
+ // Enable GitHub Copilot for AL
+ "github.copilot.enable": {
+ "*": true,
+ "al": true
+ },
+
+ // Better inline suggestions
+ "editor.inlineSuggest.enabled": true,
+ "editor.suggest.showMethods": true,
+ "editor.suggest.showFunctions": true,
+
+ // Code analysis
+ "al.enableCodeAnalysis": true,
+ "al.codeAnalyzers": ["${CodeCop}", "${UICop}", "${PerTenantExtensionCop}"],
+
+ // Auto-save for better AI context
+ "files.autoSave": "afterDelay",
+ "files.autoSaveDelay": 1000
+}
+```
+
+### Keyboard Shortcuts
+Useful shortcuts when working with AI:
+
+- **Trigger Suggestion**: `Ctrl+Space` (Windows/Linux) or `Cmd+Space` (Mac)
+- **Accept Suggestion**: `Tab`
+- **Next Suggestion**: `Alt+]`
+- **Previous Suggestion**: `Alt+[`
+- **Open Copilot Chat**: `Ctrl+Shift+I`
+
+## Tool Integrations
+
+### Combining Tools Effectively
+
+**AI + Code Analysis**:
+1. Generate code with AI
+2. Run CodeCop to check standards
+3. Fix issues with AI assistance
+4. Verify with test runner
+
+**AI + Documentation**:
+1. Write code with AI
+2. Generate XML docs with AI
+3. Format with AL XML Documentation extension
+4. Create README with Markdown All in One
+
+**AI + Version Control**:
+1. Develop features with AI
+2. Review changes with GitLens
+3. Commit with clear AI-related messages
+4. Track AI productivity over time
+
+## Community-Created Tools
+
+### AL Prompt Templates
+**Type**: Snippet Collection
+**What**: Pre-written prompts for common AL tasks
+
+**Repository**: [Example - To be created by community]
+
+---
+
+### BC AI Helper Scripts
+**Type**: PowerShell Scripts
+**What**: Automation scripts for AI-assisted BC development
+
+**Repository**: [Example - To be created by community]
+
+---
+
+## Contributing Tools
+
+**Created a tool for AI-assisted AL development?**
+
+Share it with the community!
+
+**Submission Guidelines**:
+- Must be useful for AL/BC development
+- Should enhance AI-assisted workflows
+- Open source preferred
+- Well documented
+
+**How to Submit**: See [Contributing](../../../contributing) section
+
+## Tool Safety & Privacy
+
+### Privacy Considerations
+
+**What Gets Shared**:
+- Code in your workspace (with AI assistants)
+- File names and structure
+- Your prompts and questions
+
+**Best Practices**:
+- Review extension permissions
+- Understand data handling
+- Use organization-approved tools
+- Don't include sensitive data in code
+
+### Security
+
+**Verify Extensions**:
+- Check publisher reputation
+- Read reviews
+- Review permissions requested
+- Keep extensions updated
+
+## Updates
+
+Extensions are frequently updated. Check for updates regularly:
+
+- VS Code: `Ctrl+Shift+X` → Click update icon
+- Auto-update: Enable in VS Code settings
+
+---
+
+## Placeholder Notice
+
+> **Note**: Some tools listed may be examples for community-created utilities. As real tools are developed and published, they should be added here. The core Microsoft and established community extensions (GitHub Copilot, AL Language, etc.) are real and available now.
+
+---
+
+## Related Resources
+
+- [Setup Guide](../../gettingstarted/setup) - Environment configuration
+- [Blog Posts](../articles) - Tool reviews and comparisons
+- [Videos](../videos) - Tool demonstrations
+- [Discussions](../discussions) - Tool recommendations and support
diff --git a/content/docs/agentic-coding/CommunityResources/videos.md b/content/docs/agentic-coding/CommunityResources/videos.md
new file mode 100644
index 00000000..dc114325
--- /dev/null
+++ b/content/docs/agentic-coding/CommunityResources/videos.md
@@ -0,0 +1,66 @@
+---
+---
+title: "Video Tutorials"
+linkTitle: "Videos"
+weight: 2
+description: >
+ Curated videos demonstrating AI-assisted AL development techniques
+---
+
+## Overview
+
+Short, curated videos that show AI coding assistants in practical AL/Business Central workflows. The list below is a starting point — contribute more quality content via the contributing process.
+
+## Curated Videos (starter list)
+
+1. "Vibe Coding: Yes or No?" — demiliani
+ - Link: https://www.youtube.com/watch?v=vY5WfipEK8M
+ - Quick: discussion and viewpoints on the "vibe coding" approach when using AI assistants
+
+2. "Gestion de Contexto y Estados en Servidores MCP" — techspheredynamics
+ - Link: https://www.youtube.com/watch?v=PzEbaPw-E1o
+ - Quick: context and state management patterns for MCP servers (Spanish)
+
+3. "Testing GitHub Copilot Knowledge Engineering" — nubimancy
+ - Link: https://www.youtube.com/watch?v=K8nFVw5M-Po
+ - Quick: experiments and lessons around prompting and knowledge engineering for Copilot
+
+4. "Live Feature Build with AI Assistance" — community live stream
+ - Link: https://www.youtube.com/watch?v=SP1UJNjTN7s
+ - Quick: live coding session demonstrating end-to-end feature development with AI help
+
+## How to Use These Videos
+
+- Start with the shorter discussion/intro videos to build context
+- Watch demos and live coding to see practical workflows and gotchas
+- Rewatch technical deep dives for specific patterns or tools
+
+## Contribute a Video
+
+If you've created a high-quality video about AI-assisted AL development, please contribute it.
+
+Submission checklist:
+- Publicly accessible (YouTube, Vimeo, etc.)
+- Focused on AL / Business Central development
+- Provides clear, actionable content or valuable discussion
+
+How to submit:
+1. Review the [Contributing](../../../contributing) guidelines
+2. Open a pull request adding your video to this page
+3. Provide: Title, Creator, Short Summary (1–2 lines), and Link
+
+## Video Quality Criteria
+
+Videos listed here should meet these standards:
+- Clear audio and video
+- Accurate and relevant to AL development
+- Demonstrates techniques, patterns, or practical workflows
+- Publicly accessible
+
+---
+
+## Related Resources
+
+- [Blog Posts & Articles](../articles)
+- [Tools & Extensions](../tools)
+- [Discussions](../discussions)
diff --git a/content/docs/agentic-coding/GettingMore/_index.md b/content/docs/agentic-coding/GettingMore/_index.md
new file mode 100644
index 00000000..432eea27
--- /dev/null
+++ b/content/docs/agentic-coding/GettingMore/_index.md
@@ -0,0 +1,47 @@
+---
+title: "Getting More"
+linkTitle: "Getting More"
+weight: 20
+description: >
+ Practical examples and advanced techniques for AI-assisted AL development
+---
+
+This section provides hands-on examples of how to use AI assistants for common AL development tasks. Each guide walks through a realistic scenario with step-by-step instructions and prompts.
+
+## In This Section
+
+- **[AI-Assisted Code Review](code-review)** - Use AI to review code for quality, performance, and best practices
+- **[Generating Documentation](documentation)** - Automatically create and maintain documentation for your AL code
+- **[Adding Telemetry](telemetry)** - Instrument your extensions with Application Insights telemetry
+- **[Refactoring Legacy Code](refactoring)** - Modernize and improve existing AL code
+- **[Writing Tests](testing)** - Create comprehensive test coverage with AI assistance
+
+## How to Use These Guides
+
+Each guide follows a practical, scenario-based approach:
+
+1. **Scenario**: A realistic development task
+2. **Goal**: What you're trying to achieve
+3. **Step-by-Step**: Detailed instructions with actual prompts
+4. **Review Points**: What to check in the AI-generated code
+5. **Tips**: Additional insights and variations
+
+## Before You Start
+
+Make sure you've completed the [Getting Started](../gettingstarted) section to:
+- Understand agentic coding concepts
+- Set up your environment
+- Learn effective prompting
+- Know the best practices and limitations
+
+## Learning by Doing
+
+These examples are designed to be:
+- **Practical**: Based on real AL development tasks
+- **Detailed**: Step-by-step instructions you can follow
+- **Educational**: Explains why, not just what
+- **Adaptable**: Patterns you can apply to your own work
+
+## Contributing Examples
+
+Have a great example of AI-assisted AL development? Consider contributing! See the [Contributing](../../contributing) section for guidelines.
diff --git a/content/docs/agentic-coding/GettingMore/code-review.md b/content/docs/agentic-coding/GettingMore/code-review.md
new file mode 100644
index 00000000..0010d847
--- /dev/null
+++ b/content/docs/agentic-coding/GettingMore/code-review.md
@@ -0,0 +1,368 @@
+---
+title: "AI-Assisted Code Review"
+linkTitle: "Code Review"
+weight: 1
+description: >
+ Learn how to use AI assistants to review AL code for quality, performance, and best practices
+---
+
+## Scenario
+
+You've just finished implementing a new feature: a codeunit that processes sales orders and applies volume-based discounts. Before submitting for peer review, you want to use AI to catch potential issues.
+
+## Goal
+
+Use AI to identify:
+- Potential bugs or logical errors
+- Performance issues
+- AL best practice violations
+- Missing error handling
+- Code quality improvements
+
+## The Code to Review
+
+Here's the codeunit we'll review:
+
+```al
+codeunit 50100 "Sales Order Discount Processor"
+{
+ procedure ApplyVolumeDiscounts(var SalesHeader: Record "Sales Header")
+ var
+ SalesLine: Record "Sales Line";
+ TotalQuantity: Decimal;
+ DiscountPct: Decimal;
+ begin
+ TotalQuantity := 0;
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ if SalesLine.FindSet() then
+ repeat
+ TotalQuantity := TotalQuantity + SalesLine.Quantity;
+ until SalesLine.Next() = 0;
+
+ if TotalQuantity > 100 then
+ DiscountPct := 15
+ else if TotalQuantity > 50 then
+ DiscountPct := 10
+ else if TotalQuantity > 10 then
+ DiscountPct := 5;
+
+ SalesLine.Reset();
+ if SalesLine.FindSet() then
+ repeat
+ SalesLine."Line Discount %" := DiscountPct;
+ SalesLine.Modify();
+ until SalesLine.Next() = 0;
+ end;
+}
+```
+
+## Step-by-Step Review Process
+
+### Step 1: Initial Quality Review
+
+**Prompt**:
+```
+Review this AL codeunit for potential bugs, code quality issues, and best practice violations.
+
+[Paste the code above]
+
+Specifically check for:
+- Logical errors
+- Missing error handling
+- Variable declarations
+- Commit/transaction issues
+- Performance concerns
+```
+
+**Expected AI Findings**:
+The AI should identify issues like:
+- Missing `FindSet(true, false)` parameters for modification
+- No error handling
+- Multiple FindSet operations (inefficient)
+- Hard-coded discount percentages
+- No validation of input parameters
+- Missing ModifyAll opportunity
+- No telemetry or logging
+
+### Step 2: Performance Analysis
+
+**Prompt**:
+```
+Analyze the performance of this code, especially database operations.
+What are potential performance issues? How can it be optimized?
+
+[Include the code or reference it if in context]
+```
+
+**Expected AI Suggestions**:
+- Combine the two FindSet loops into one
+- Use ModifyAll instead of looping for discount application
+- Consider using SetLoadFields for better performance
+- Cache discount percentages instead of hard-coding
+
+### Step 3: Best Practices Check
+
+**Prompt**:
+```
+Check this code against AL coding best practices and Business Central development standards.
+What improvements would you recommend?
+```
+
+**Expected AI Recommendations**:
+- Add XML documentation
+- Extract discount calculation to separate function
+- Use constants for discount tiers
+- Add error handling
+- Implement proper transaction handling
+- Add telemetry for monitoring
+
+### Step 4: Request Improved Version
+
+**Prompt**:
+```
+Rewrite this codeunit implementing all the improvements you suggested.
+Include:
+- XML documentation
+- Error handling
+- Performance optimizations
+- Best practice compliance
+- Telemetry/logging
+- Discount tiers from setup table instead of hard-coded values
+```
+
+**Review the Generated Code**:
+The AI should generate something like:
+
+```al
+///
+/// Processes sales orders and applies volume-based discounts
+///
+codeunit 50100 "Sales Order Discount Processor"
+{
+ ///
+ /// Applies volume-based discounts to a sales order
+ ///
+ /// The sales header to process
+ procedure ApplyVolumeDiscounts(var SalesHeader: Record "Sales Header")
+ var
+ SalesLine: Record "Sales Line";
+ TotalQuantity: Decimal;
+ DiscountPct: Decimal;
+ begin
+ if SalesHeader."No." = '' then
+ Error('Sales order number cannot be empty.');
+
+ TotalQuantity := CalculateTotalQuantity(SalesHeader);
+ DiscountPct := GetDiscountPercentage(TotalQuantity);
+
+ if DiscountPct > 0 then
+ ApplyDiscountToLines(SalesHeader, DiscountPct);
+
+ LogTelemetry(SalesHeader."No.", TotalQuantity, DiscountPct);
+ end;
+
+ local procedure CalculateTotalQuantity(SalesHeader: Record "Sales Header"): Decimal
+ var
+ SalesLine: Record "Sales Line";
+ TotalQty: Decimal;
+ begin
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ SalesLine.SetLoadFields(Quantity);
+
+ if SalesLine.FindSet() then
+ repeat
+ TotalQty += SalesLine.Quantity;
+ until SalesLine.Next() = 0;
+
+ exit(TotalQty);
+ end;
+
+ local procedure GetDiscountPercentage(TotalQuantity: Decimal): Decimal
+ var
+ VolumeDiscountSetup: Record "Volume Discount Setup"; // Assuming this table exists
+ begin
+ VolumeDiscountSetup.SetFilter("Minimum Quantity", '<=%1', TotalQuantity);
+ VolumeDiscountSetup.SetCurrentKey("Minimum Quantity");
+ VolumeDiscountSetup.Ascending(false);
+
+ if VolumeDiscountSetup.FindFirst() then
+ exit(VolumeDiscountSetup."Discount Percentage");
+
+ exit(0);
+ end;
+
+ local procedure ApplyDiscountToLines(SalesHeader: Record "Sales Header"; DiscountPct: Decimal)
+ var
+ SalesLine: Record "Sales Line";
+ begin
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ SalesLine.ModifyAll("Line Discount %", DiscountPct, true);
+ end;
+
+ local procedure LogTelemetry(DocumentNo: Code[20]; TotalQty: Decimal; DiscountPct: Decimal)
+ var
+ Telemetry: Codeunit Telemetry;
+ CustomDimensions: Dictionary of [Text, Text];
+ begin
+ CustomDimensions.Add('DocumentNo', DocumentNo);
+ CustomDimensions.Add('TotalQuantity', Format(TotalQty));
+ CustomDimensions.Add('DiscountPercentage', Format(DiscountPct));
+
+ Telemetry.LogMessage('0001', 'Volume discount applied', Verbosity::Normal,
+ DataClassification::SystemMetadata, TelemetryScope::All, CustomDimensions);
+ end;
+}
+```
+
+## Review Points: What to Check
+
+After AI generates the improved code, verify:
+
+### ✅ Correctness
+- [ ] Logic matches business requirements
+- [ ] All edge cases handled
+- [ ] No regression in functionality
+- [ ] Error messages are clear
+
+### ✅ Performance
+- [ ] Efficient database queries
+- [ ] Proper use of SetLoadFields
+- [ ] ModifyAll used where appropriate
+- [ ] No unnecessary loops
+
+### ✅ Best Practices
+- [ ] XML documentation complete
+- [ ] Proper error handling
+- [ ] Appropriate transaction handling
+- [ ] Good function decomposition
+
+### ✅ AL Specifics
+- [ ] Correct AL syntax
+- [ ] Proper use of BC APIs
+- [ ] No deprecated features
+- [ ] Appropriate data types
+
+### ✅ Maintainability
+- [ ] Clear, descriptive names
+- [ ] Logical organization
+- [ ] Easy to test
+- [ ] Well documented
+
+## Additional Review Prompts
+
+### Security Review
+```
+Review this code for potential security issues:
+- Input validation
+- Authorization checks
+- Data access controls
+- Potential injection vulnerabilities
+```
+
+### Testability Review
+```
+Analyze this code for testability.
+What makes it easy or hard to test?
+How can it be restructured to be more testable?
+```
+
+### Documentation Review
+```
+Review the XML documentation for this code.
+Is it complete? Clear? Helpful?
+What additional documentation would be valuable?
+```
+
+## Common Issues AI Might Miss
+
+Be aware AI might not catch:
+
+1. **Business Logic Errors**
+ - AI doesn't know your specific discount rules
+ - Verify the logic matches actual requirements
+
+2. **Integration Issues**
+ - AI doesn't know about other extensions
+ - Check for conflicts with existing code
+
+3. **BC Version Compatibility**
+ - AI might use features not in your BC version
+ - Verify all APIs are available
+
+4. **Organization Standards**
+ - AI doesn't know your specific standards
+ - Adapt to match your conventions
+
+## Best Practices for AI Code Review
+
+### 1. Use Specific Review Criteria
+Instead of "review this code", specify what to look for:
+```
+Review for: performance, error handling, AL best practices, testability
+```
+
+### 2. Review in Layers
+Don't try to review everything at once:
+- First: Correctness and logic
+- Second: Performance
+- Third: Best practices
+- Fourth: Documentation
+
+### 3. Combine with Tools
+Use AI review alongside:
+- AL code analyzers
+- Static analysis tools
+- Peer review
+- Testing
+
+### 4. Iterate
+Review, improve, review again:
+```
+Review the updated code. Are there any remaining issues?
+```
+
+### 5. Document Findings
+Keep track of:
+- Common issues AI finds
+- Issues AI misses
+- Effective review prompts
+
+## Practice Exercise
+
+Try reviewing this code with AI:
+
+```al
+procedure CalculateShippingCost(SalesHeader: Record "Sales Header"): Decimal
+var
+ SalesLine: Record "Sales Line";
+ Weight: Decimal;
+begin
+ Weight := 0;
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ if SalesLine.Find('-') then
+ repeat
+ Weight := Weight + SalesLine.Quantity;
+ until SalesLine.Next() = 0;
+
+ if Weight < 10 then
+ exit(5.00)
+ else
+ exit(10.00);
+end;
+```
+
+**Your Tasks**:
+1. Ask AI to review for issues
+2. Request performance improvements
+3. Ask for best practice compliance
+4. Get an improved version
+5. Review the improved version yourself
+
+## Next Steps
+
+- Learn how to use AI for [generating documentation](../documentation)
+- See how AI can help with [adding telemetry](../telemetry)
+- Explore [refactoring legacy code](../refactoring) with AI assistance
diff --git a/content/docs/agentic-coding/GettingMore/documentation.md b/content/docs/agentic-coding/GettingMore/documentation.md
new file mode 100644
index 00000000..d853917b
--- /dev/null
+++ b/content/docs/agentic-coding/GettingMore/documentation.md
@@ -0,0 +1,661 @@
+---
+title: "Generating Documentation"
+linkTitle: "Documentation"
+weight: 2
+description: >
+ Use AI to create and maintain comprehensive documentation for your AL code
+---
+
+## Scenario
+
+You have a well-functioning AL extension but it lacks documentation. You need to create:
+- XML documentation comments for all procedures
+- A comprehensive README file
+- API documentation for public interfaces
+- User-facing feature documentation
+
+## Goal
+
+Use AI to quickly generate high-quality documentation that:
+- Explains what the code does
+- Documents parameters and return values
+- Provides usage examples
+- Helps developers and users understand the extension
+
+## Types of Documentation
+
+### 1. XML Documentation Comments
+In-code documentation for procedures, triggers, and events.
+
+### 2. README Files
+Project overview, setup instructions, and getting started guides.
+
+### 3. API Documentation
+Documentation for public APIs and integration points.
+
+### 4. User Documentation
+End-user guides and feature explanations.
+
+## Step-by-Step Guide
+
+### Step 1: XML Documentation for Procedures
+
+**Scenario**: You have a codeunit without documentation.
+
+**Starting Code**:
+```al
+codeunit 50100 "Customer Email Manager"
+{
+ procedure SendWelcomeEmail(CustomerNo: Code[20]): Boolean
+ var
+ Customer: Record Customer;
+ EmailMessage: Codeunit "Email Message";
+ begin
+ if not Customer.Get(CustomerNo) then
+ exit(false);
+
+ if Customer."E-Mail" = '' then
+ exit(false);
+
+ EmailMessage.Create(Customer."E-Mail", 'Welcome!', GetWelcomeEmailBody(Customer));
+ exit(EmailMessage.Send());
+ end;
+
+ local procedure GetWelcomeEmailBody(Customer: Record Customer): Text
+ begin
+ exit(StrSubstNo('Dear %1, welcome to our service!', Customer.Name));
+ end;
+}
+```
+
+**Prompt**:
+```
+Add XML documentation comments to all procedures in this codeunit.
+Include:
+- Summary for each procedure
+- Parameter descriptions
+- Return value descriptions
+- Example usage where helpful
+- Any important notes or warnings
+
+[Paste the code]
+```
+
+**Expected Result**:
+```al
+///
+/// Manages customer email communications
+///
+codeunit 50100 "Customer Email Manager"
+{
+ ///
+ /// Sends a welcome email to a customer
+ ///
+ /// The customer number to send the email to
+ /// True if the email was sent successfully, false otherwise
+ ///
+ /// The procedure will return false if:
+ /// - The customer does not exist
+ /// - The customer has no email address
+ /// - The email fails to send
+ ///
+ ///
+ /// if CustomerEmailManager.SendWelcomeEmail('C001') then
+ /// Message('Welcome email sent successfully');
+ ///
+ procedure SendWelcomeEmail(CustomerNo: Code[20]): Boolean
+ var
+ Customer: Record Customer;
+ EmailMessage: Codeunit "Email Message";
+ begin
+ if not Customer.Get(CustomerNo) then
+ exit(false);
+
+ if Customer."E-Mail" = '' then
+ exit(false);
+
+ EmailMessage.Create(Customer."E-Mail", 'Welcome!', GetWelcomeEmailBody(Customer));
+ exit(EmailMessage.Send());
+ end;
+
+ ///
+ /// Generates the body text for the welcome email
+ ///
+ /// The customer record to generate the email for
+ /// The formatted email body text
+ local procedure GetWelcomeEmailBody(Customer: Record Customer): Text
+ begin
+ exit(StrSubstNo('Dear %1, welcome to our service!', Customer.Name));
+ end;
+}
+```
+
+### Step 2: Batch Documentation for Multiple Files
+
+**Prompt**:
+```
+I have multiple AL files that need XML documentation.
+For each public procedure, add:
+- Summary
+- Parameter descriptions
+- Return value (if applicable)
+- Example usage
+
+Process these files:
+[List files or paste multiple code blocks]
+```
+
+**Tip**: Do this in batches of 3-5 files to maintain context and quality.
+
+### Step 3: Creating a README File
+
+**Prompt**:
+```
+Create a comprehensive README.md for my AL extension with the following information:
+
+Extension Name: Customer Engagement Suite
+Purpose: Enhance customer communication and engagement features
+Key Features:
+- Automated welcome emails
+- Customer portal access
+- Newsletter subscription management
+- Customer satisfaction surveys
+
+Include sections for:
+- Overview and purpose
+- Features list
+- Installation instructions
+- Configuration steps
+- Usage examples
+- Dependencies
+- Compatibility (BC version 21+)
+- Contributing guidelines
+- License (MIT)
+```
+
+**Expected Structure**:
+```markdown
+# Customer Engagement Suite
+
+> Enhance customer communication and engagement in Microsoft Dynamics 365 Business Central
+
+## Overview
+
+The Customer Engagement Suite is a Business Central extension that provides comprehensive
+tools for managing customer communications and engagement activities.
+
+## Features
+
+### Automated Welcome Emails
+Automatically send personalized welcome emails to new customers upon registration.
+
+### Customer Portal Access
+Enable customers to access a self-service portal for order tracking and account management.
+
+### Newsletter Subscription Management
+Allow customers to manage their newsletter preferences and subscriptions.
+
+### Customer Satisfaction Surveys
+Collect and analyze customer feedback through integrated surveys.
+
+## Installation
+
+### Prerequisites
+- Microsoft Dynamics 365 Business Central version 21.0 or higher
+- Email account configured in Business Central
+- System Application extension installed
+
+### Steps
+
+1. Download the extension file (.app)
+2. Open Business Central Administration Shell
+3. Run the installation command:
+ ```powershell
+ Publish-NAVApp -ServerInstance BC210 -Path "CustomerEngagementSuite.app"
+ Install-NAVApp -ServerInstance BC210 -Name "Customer Engagement Suite"
+ ```
+
+## Configuration
+
+### Email Setup
+1. Navigate to **Email Accounts** page
+2. Configure your SMTP settings
+3. Test the email connection
+
+### Welcome Email Template
+1. Go to **Customer Engagement Setup**
+2. Configure the welcome email template
+3. Enable automatic sending
+
+## Usage
+
+### Sending Welcome Emails
+```al
+codeunit 50100 "Customer Email Manager"
+{
+ procedure SendWelcomeEmail(CustomerNo: Code[20]): Boolean
+}
+```
+
+**Example:**
+```al
+CustomerEmailManager: Codeunit "Customer Email Manager";
+begin
+ if CustomerEmailManager.SendWelcomeEmail('C001') then
+ Message('Welcome email sent successfully');
+end;
+```
+
+## Dependencies
+
+- **System Application**: Core BC functionality
+- **Base Application**: Standard BC tables and pages
+
+## Compatibility
+
+- **Business Central**: Version 21.0 and higher
+- **Platform**: Compatible with both SaaS and On-Premises
+
+## Contributing
+
+We welcome contributions! Please see [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
+
+## License
+
+This project is licensed under the MIT License - see [LICENSE](LICENSE) file for details.
+
+## Support
+
+For issues and questions:
+- Create an issue in our [GitHub repository](https://github.com/yourorg/customer-engagement)
+- Email: support@yourcompany.com
+
+## Changelog
+
+See [CHANGELOG.md](CHANGELOG.md) for version history.
+```
+
+### Step 4: API Documentation
+
+**Prompt**:
+```
+Create API documentation for the public procedures in my Customer Email Manager codeunit.
+Format it as markdown suitable for a developer portal.
+
+Include:
+- Procedure signature
+- Description
+- Parameters with types and descriptions
+- Return values
+- Code examples
+- Error conditions
+- Notes and best practices
+
+[Include the codeunit code]
+```
+
+**Expected Output**:
+```markdown
+# Customer Email Manager API
+
+## Overview
+The Customer Email Manager provides functionality for sending customer-related emails.
+
+## Procedures
+
+### SendWelcomeEmail
+
+Sends a welcome email to a specified customer.
+
+**Signature:**
+```al
+procedure SendWelcomeEmail(CustomerNo: Code[20]): Boolean
+```
+
+**Parameters:**
+
+| Name | Type | Description |
+|------|------|-------------|
+| CustomerNo | Code[20] | The unique identifier of the customer |
+
+**Returns:**
+
+| Type | Description |
+|------|-------------|
+| Boolean | `true` if email sent successfully, `false` otherwise |
+
+**Example:**
+```al
+var
+ CustomerEmailManager: Codeunit "Customer Email Manager";
+ Success: Boolean;
+begin
+ Success := CustomerEmailManager.SendWelcomeEmail('C00001');
+ if Success then
+ Message('Email sent successfully')
+ else
+ Error('Failed to send email');
+end;
+```
+
+**Error Conditions:**
+
+The procedure returns `false` in the following cases:
+- Customer does not exist
+- Customer has no email address configured
+- Email service is unavailable
+
+**Best Practices:**
+- Always check the return value
+- Ensure email account is configured before calling
+- Consider calling asynchronously for better performance
+
+**See Also:**
+- Email Account Setup
+- Customer Configuration
+```
+
+### Step 5: User Documentation
+
+**Prompt**:
+```
+Create user-facing documentation for the Welcome Email feature.
+Target audience: Business users who are not developers.
+
+Explain:
+- What the feature does
+- How to enable/configure it
+- How to use it
+- Troubleshooting common issues
+
+Use simple language and include screenshots placeholders where helpful.
+```
+
+**Expected Output**:
+```markdown
+# Welcome Email Feature
+
+## What is the Welcome Email Feature?
+
+The Welcome Email feature automatically sends a personalized email to new customers
+when they are added to your system. This helps create a positive first impression
+and provides important information to your customers right away.
+
+## Enabling Welcome Emails
+
+1. Open Business Central
+2. Search for "Customer Engagement Setup"
+3. Check the box next to "Send Welcome Emails"
+4. Click "OK" to save
+
+![Setup Screenshot]
+
+## Configuring the Email Template
+
+### Step 1: Access Email Templates
+1. Search for "Email Templates"
+2. Find "Customer Welcome Email"
+3. Click "Edit"
+
+### Step 2: Customize the Message
+1. Update the email subject line
+2. Modify the email body
+3. Add your company logo
+4. Click "OK" to save
+
+### Step 3: Test the Email
+1. Open a test customer
+2. Click "Actions" > "Send Welcome Email"
+3. Check that you receive the email
+
+## Using Welcome Emails
+
+### Automatic Sending
+When enabled, welcome emails are sent automatically when:
+- A new customer is created
+- An existing customer is marked as active for the first time
+
+### Manual Sending
+You can also send welcome emails manually:
+
+1. Open the customer card
+2. Click "Actions" > "Email" > "Send Welcome Email"
+3. Confirm the action
+
+## Troubleshooting
+
+### Email Not Sending
+
+**Problem:** Welcome emails are not being sent
+
+**Solutions:**
+- Check that the feature is enabled in setup
+- Verify the customer has an email address
+- Confirm your email account is configured correctly
+- Check that email service is running
+
+### Wrong Email Template
+
+**Problem:** Customers receive the wrong email content
+
+**Solutions:**
+- Review the email template configuration
+- Ensure you're editing the correct template
+- Clear any cached templates
+
+### Customer Not Receiving Email
+
+**Problem:** Email shows as sent but customer didn't receive it
+
+**Solutions:**
+- Ask customer to check spam folder
+- Verify the email address is correct
+- Check email delivery logs
+- Test with a different email address
+
+## Tips and Best Practices
+
+- **Personalization**: Use customer name and company name in the email
+- **Timing**: Send welcome emails within 24 hours of customer creation
+- **Follow-up**: Consider a follow-up email series
+- **Feedback**: Ask customers if they received and found the email helpful
+
+## Need Help?
+
+Contact your Business Central administrator or support team for assistance.
+```
+
+## Review Points
+
+After generating documentation, verify:
+
+### ✅ Accuracy
+- [ ] Documentation matches actual code behavior
+- [ ] Parameter descriptions are correct
+- [ ] Return values accurately described
+- [ ] Examples work as shown
+
+### ✅ Completeness
+- [ ] All public procedures documented
+- [ ] All parameters explained
+- [ ] Edge cases mentioned
+- [ ] Error conditions documented
+
+### ✅ Clarity
+- [ ] Easy to understand
+- [ ] Appropriate level of detail
+- [ ] Good examples provided
+- [ ] Proper formatting
+
+### ✅ Maintenance
+- [ ] Easy to update
+- [ ] Versioned appropriately
+- [ ] Consistent style
+- [ ] Well organized
+
+## Advanced Documentation Prompts
+
+### Generate CHANGELOG
+```
+Create a CHANGELOG.md file documenting these changes from version 1.0 to 2.0:
+- Added: Customer portal access
+- Added: Newsletter preferences
+- Changed: Welcome email now includes portal link
+- Fixed: Email encoding issues with special characters
+- Deprecated: Old email API (will be removed in 3.0)
+
+Follow Keep a Changelog format.
+```
+
+### Create Migration Guide
+```
+Create a migration guide for users upgrading from version 1.x to 2.0.
+Include:
+- Breaking changes
+- New features
+- Configuration changes needed
+- Data migration steps
+- Deprecation warnings
+```
+
+### Generate Inline Code Comments
+```
+Add helpful inline comments to this complex procedure explaining the logic flow.
+Don't over-comment obvious code, but do explain:
+- Complex algorithms
+- Business rule implementations
+- Non-obvious optimizations
+- Workarounds
+
+[Paste code]
+```
+
+## Keeping Documentation Updated
+
+### When Code Changes
+**Prompt**:
+```
+I've updated this procedure to add a new parameter.
+Update the XML documentation to reflect the change:
+
+Old procedure:
+[paste old code]
+
+New procedure:
+[paste new code]
+```
+
+### Regular Documentation Reviews
+**Prompt**:
+```
+Review the documentation for this codeunit.
+Check for:
+- Outdated information
+- Missing documentation
+- Incorrect examples
+- Deprecated features
+
+[Paste codeunit]
+```
+
+## Best Practices
+
+### 1. Document As You Code
+```
+I'm about to write a procedure to validate customer credit limits.
+Create the XML documentation comment first, then we'll implement the procedure.
+```
+
+### 2. Use Consistent Style
+Create a documentation template:
+```
+Create an XML documentation template I can use for all my procedures.
+Include sections for: summary, parameters, returns, exceptions, examples, and remarks.
+```
+
+### 3. Generate Documentation in Batches
+Document related code together for consistency:
+```
+Document all procedures in this codeunit that relate to email sending.
+Use consistent terminology and structure.
+```
+
+### 4. Include Real Examples
+```
+Add a realistic code example to this procedure's documentation showing:
+- Typical usage
+- Error handling
+- Integration with other features
+```
+
+## Common Documentation Patterns
+
+### For Validation Procedures
+```
+Document this validation procedure. Include:
+- What is being validated
+- Valid conditions
+- Error messages that can be raised
+- Example of valid and invalid inputs
+```
+
+### For Event Subscribers
+```
+Document this event subscriber. Include:
+- What event it subscribes to
+- When it triggers
+- What it does
+- Side effects or implications
+- Integration points
+```
+
+### For APIs
+```
+Create REST API documentation for this AL API page.
+Include:
+- Endpoint URL
+- HTTP methods supported
+- Request/response examples
+- Authentication requirements
+- Error codes
+```
+
+## Practice Exercise
+
+Generate documentation for this code:
+
+```al
+codeunit 50110 "Order Status Manager"
+{
+ procedure UpdateOrderStatus(OrderNo: Code[20]; NewStatus: Enum "Order Status"): Boolean
+ var
+ SalesHeader: Record "Sales Header";
+ begin
+ if not SalesHeader.Get(SalesHeader."Document Type"::Order, OrderNo) then
+ exit(false);
+
+ SalesHeader.Status := NewStatus;
+ SalesHeader.Modify(true);
+ SendStatusNotification(OrderNo, NewStatus);
+ exit(true);
+ end;
+
+ local procedure SendStatusNotification(OrderNo: Code[20]; Status: Enum "Order Status")
+ begin
+ // Implementation
+ end;
+}
+```
+
+**Your Tasks**:
+1. Generate XML documentation
+2. Create a README section explaining this feature
+3. Write API documentation
+4. Create user documentation
+5. Review and improve the generated docs
+
+## Next Steps
+
+- Learn how to use AI for [adding telemetry](../telemetry)
+- Explore [refactoring legacy code](../refactoring) while maintaining documentation
+- See how to conduct [AI-assisted code reviews](../code-review)
diff --git a/content/docs/agentic-coding/GettingMore/refactoring.md b/content/docs/agentic-coding/GettingMore/refactoring.md
new file mode 100644
index 00000000..6aaac1c6
--- /dev/null
+++ b/content/docs/agentic-coding/GettingMore/refactoring.md
@@ -0,0 +1,1041 @@
+---
+title: "Refactoring Legacy Code"
+linkTitle: "Refactoring"
+weight: 4
+description: >
+ Use AI to modernize and improve existing AL code while maintaining functionality
+---
+
+## Scenario
+
+You've inherited a legacy AL codeunit from an older Business Central version. The code works, but it:
+
+- Uses deprecated patterns and APIs
+- Has poor structure and naming
+- Lacks documentation and error handling
+- Contains duplicated logic
+- Is difficult to test and maintain
+
+You need to modernize this code while ensuring it continues to work correctly.
+
+## Goal
+
+Use AI to help you:
+
+- Identify refactoring opportunities
+- Modernize deprecated APIs
+- Improve code structure
+- Enhance readability and maintainability
+- Add tests to ensure no regression
+
+## The Legacy Code
+
+Here's a typical legacy codeunit that needs refactoring:
+
+```al
+codeunit 50100 "Sales Order Management"
+{
+ procedure ProcessSalesOrder(DocNo: Code[20])
+ var
+ SH: Record "Sales Header";
+ SL: Record "Sales Line";
+ C: Record Customer;
+ I: Record Item;
+ qty: Decimal;
+ amt: Decimal;
+ begin
+ if DocNo = '' then
+ exit;
+
+ SH.Get(SH."Document Type"::Order, DocNo);
+ C.Get(SH."Sell-to Customer No.");
+
+ if C.Blocked <> C.Blocked::" " then begin
+ Message('Customer is blocked!');
+ exit;
+ end;
+
+ SL.SetRange("Document No.", DocNo);
+ if SL.Find('-') then
+ repeat
+ if SL.Type = SL.Type::Item then begin
+ I.Get(SL."No.");
+ if I.Inventory < SL.Quantity then
+ Message('Not enough inventory for item ' + I."No.");
+ end;
+ qty := qty + SL.Quantity;
+ amt := amt + SL."Line Amount";
+ until SL.Next() = 0;
+
+ if amt > 10000 then begin
+ SL.SetRange("Document No.", DocNo);
+ if SL.Find('-') then
+ repeat
+ SL."Line Discount %" := 5;
+ SL.Modify();
+ until SL.Next() = 0;
+ end;
+
+ Message('Processed order ' + DocNo + ' with total amount ' + Format(amt));
+ end;
+}
+```
+
+## Step-by-Step Refactoring Process
+
+### Step 1: Write Tests First
+
+{{% alert title="Critical: Test First!" color="warning" %}}
+Before refactoring any code, write tests that verify its current behavior. These tests act as a safety net, ensuring you don't accidentally break functionality during refactoring.
+{{% /alert %}}
+
+**Prompt**:
+
+```
+I need to refactor this legacy code, but first I need comprehensive tests for its current behavior.
+
+Create tests that verify:
+- All current functionality (even if imperfect)
+- Expected outputs for given inputs
+- Error conditions and edge cases
+- Current behavior (not ideal behavior)
+
+These tests should pass with the current code and catch any regressions during refactoring.
+
+[Paste the legacy code]
+```
+
+**Expected Test Code**:
+
+```al
+codeunit 50101 "Sales Order Mgmt. Tests"
+{
+ Subtype = Test;
+
+ var
+ Assert: Codeunit "Library Assert";
+ LibrarySales: Codeunit "Library - Sales";
+
+ [Test]
+ procedure TestCurrentBehaviorWithValidOrder()
+ var
+ SalesHeader: Record "Sales Header";
+ SalesOrderMgmt: Codeunit "Sales Order Management";
+ begin
+ // [GIVEN] A valid sales order (testing CURRENT behavior)
+ CreateTestSalesOrder(SalesHeader, 'CUST001', 5000);
+
+ // [WHEN] Processing the order
+ SalesOrderMgmt.ProcessSalesOrder(SalesHeader."No.");
+
+ // [THEN] No error occurs and discount is applied
+ // (These tests lock in current behavior before refactoring)
+ Assert.IsTrue(true, 'Process completed without error');
+ end;
+
+ [Test]
+ procedure TestCurrentBlockedCustomerBehavior()
+ var
+ SalesHeader: Record "Sales Header";
+ Customer: Record Customer;
+ SalesOrderMgmt: Codeunit "Sales Order Management";
+ begin
+ // [GIVEN] Order with blocked customer
+ CreateBlockedCustomerOrder(SalesHeader, Customer);
+
+ // [WHEN] Processing (currently just shows Message, doesn't error)
+ SalesOrderMgmt.ProcessSalesOrder(SalesHeader."No.");
+
+ // [THEN] Process completes (testing CURRENT behavior, even if not ideal)
+ // Note: After refactoring, this might throw an error instead
+ end;
+
+ // Additional tests for current behavior...
+}
+```
+
+**Why This Matters**:
+
+- Tests catch regressions immediately
+- You can refactor confidently
+- Tests document current behavior
+- You can run tests after each small refactoring step
+
+### Step 2: Initial Assessment
+
+**Prompt**:
+
+```
+Analyze this legacy AL code and identify refactoring opportunities.
+
+Categorize issues by:
+- Critical: Deprecated APIs, security issues, bugs
+- Major: Poor structure, missing error handling, performance issues
+- Minor: Naming, formatting, documentation
+
+[Paste the legacy code]
+
+For each issue, explain:
+- What the problem is
+- Why it's problematic
+- How to fix it
+```
+
+**Expected AI Findings**:
+
+**Critical Issues:**
+
+- Using `Message()` for errors instead of `Error()`
+- No proper error handling (could cause partial updates)
+- Using deprecated `Find('-')` syntax
+- Modifying records in a loop without proper handling
+
+**Major Issues:**
+
+- Poor variable naming (SH, SL, C, I, qty, amt)
+- Single large procedure doing multiple things
+- Hard-coded business rules (10000 threshold, 5% discount)
+- Inefficient database operations (multiple FindSet loops)
+- No validation of input parameters
+- Missing XML documentation
+- No telemetry or logging
+
+**Minor Issues:**
+
+- No separation of concerns
+- String concatenation for messages
+- Magic numbers without explanation
+- Inconsistent code style
+
+### Step 3: Create a Refactoring Plan
+
+**Prompt**:
+
+```
+Create a detailed refactoring plan for this code.
+
+I already have tests in place that verify current behavior.
+
+Break refactoring into phases:
+1. Safe refactorings (no behavior change)
+2. Structural improvements
+3. API modernization
+4. Behavioral improvements (may change behavior)
+5. Final enhancements
+
+For each phase, list specific changes and estimated risk level.
+After each phase, I'll run tests to ensure nothing broke.
+```
+
+**Expected Plan**:
+
+**Phase 0: Tests (COMPLETED)**
+
+- ✅ Written tests for current behavior
+- ✅ Tests pass with current code
+- ✅ Ready to refactor safely
+
+**Phase 1: Safe Refactorings (Low Risk)**
+
+- Rename variables to be descriptive
+- Add XML documentation
+- Extract magic numbers to constants
+- Format code consistently
+- Add code comments for complex logic
+
+**Phase 2: Structural Improvements (Medium Risk)**
+
+- Extract methods for each responsibility
+- Separate validation, calculation, and update logic
+- Remove code duplication
+- Improve error handling
+
+**Phase 3: API Modernization (Medium Risk)**
+
+- Replace deprecated Find('-') with FindSet()
+- Use proper Error() instead of Message()
+- Add SetLoadFields for performance
+- Use ModifyAll where appropriate
+
+**Phase 4: Behavioral Improvements (Medium Risk)**
+
+- Change Message() to Error() for validation failures
+- This CHANGES behavior, so update tests accordingly
+- Add new tests for improved error handling
+
+**Phase 5: Additional Testing (Low Risk)**
+
+- Add more edge case tests
+- Add tests for each extracted method
+- Expand test coverage
+
+**Phase 6: Enhancements (Low Risk)**
+
+- Add telemetry
+- Implement proper transaction handling
+- Add configuration instead of hard-coded values
+
+### Step 4: Run Your Tests
+
+**Before refactoring anything**, verify your tests pass:
+
+```powershell
+# Run the test codeunit
+Invoke-NAVCodeunit -CodeunitId 50101
+```
+
+**All tests should pass.** If they don't, fix the tests first.
+
+### Step 5: Phase 1 - Safe Refactorings
+
+**Prompt**:
+
+```
+Perform Phase 1 refactorings on this code:
+- Rename all variables to be descriptive
+- Add XML documentation to the procedure
+- Extract magic numbers (10000, 5) to constants
+- Add inline comments for complex logic
+- Improve code formatting
+
+[Paste the legacy code]
+```
+
+**Expected Result**:
+
+```al
+///
+/// Manages sales order processing including validation, inventory checking, and discount application
+///
+codeunit 50100 "Sales Order Management"
+{
+ var
+ LargeOrderThreshold: Decimal;
+ LargeOrderDiscountPct: Decimal;
+
+ ///
+ /// Processes a sales order by validating customer, checking inventory, and applying discounts
+ ///
+ /// The sales order number to process
+ procedure ProcessSalesOrder(DocumentNo: Code[20])
+ var
+ SalesHeader: Record "Sales Header";
+ SalesLine: Record "Sales Line";
+ Customer: Record Customer;
+ Item: Record Item;
+ TotalQuantity: Decimal;
+ TotalAmount: Decimal;
+ begin
+ // Initialize thresholds
+ LargeOrderThreshold := 10000;
+ LargeOrderDiscountPct := 5;
+
+ // Validate input
+ if DocumentNo = '' then
+ exit;
+
+ // Get sales order and customer
+ SalesHeader.Get(SalesHeader."Document Type"::Order, DocumentNo);
+ Customer.Get(SalesHeader."Sell-to Customer No.");
+
+ // Check if customer is blocked
+ if Customer.Blocked <> Customer.Blocked::" " then begin
+ Message('Customer is blocked!');
+ exit;
+ end;
+
+ // Check inventory and calculate totals
+ SalesLine.SetRange("Document No.", DocumentNo);
+ if SalesLine.Find('-') then
+ repeat
+ // Verify inventory availability for items
+ if SalesLine.Type = SalesLine.Type::Item then begin
+ Item.Get(SalesLine."No.");
+ if Item.Inventory < SalesLine.Quantity then
+ Message('Not enough inventory for item ' + Item."No.");
+ end;
+
+ // Accumulate totals
+ TotalQuantity := TotalQuantity + SalesLine.Quantity;
+ TotalAmount := TotalAmount + SalesLine."Line Amount";
+ until SalesLine.Next() = 0;
+
+ // Apply discount for large orders
+ if TotalAmount > LargeOrderThreshold then begin
+ SalesLine.SetRange("Document No.", DocumentNo);
+ if SalesLine.Find('-') then
+ repeat
+ SalesLine."Line Discount %" := LargeOrderDiscountPct;
+ SalesLine.Modify();
+ until SalesLine.Next() = 0;
+ end;
+
+ // Notify user of completion
+ Message('Processed order ' + DocumentNo + ' with total amount ' + Format(TotalAmount));
+ end;
+}
+```
+
+### Step 6: Run Tests After Phase 1
+
+**Critical**: After completing Phase 1 refactorings, run your tests:
+
+```powershell
+Invoke-NAVCodeunit -CodeunitId 50101
+```
+
+**All tests should still pass.** If any fail, the refactoring changed behavior - fix it before proceeding.
+
+### Step 7: Phase 2 - Structural Improvements
+
+**Prompt**:
+
+```
+Refactor this code to improve structure:
+
+1. Extract separate methods for:
+ - Customer validation
+ - Inventory checking
+ - Total calculation
+ - Discount application
+
+2. Replace Message() with proper Error() for validation failures
+
+3. Add proper error handling with try-catch where appropriate
+
+4. Use StrSubstNo for string formatting
+
+[Include the Phase 1 code]
+```
+
+**Expected Result**:
+
+```al
+///
+/// Manages sales order processing including validation, inventory checking, and discount application
+///
+codeunit 50100 "Sales Order Management"
+{
+ var
+ LargeOrderThreshold: Decimal;
+ LargeOrderDiscountPct: Decimal;
+ InsufficientInventoryErr: Label 'Insufficient inventory for item %1. Available: %2, Required: %3';
+ CustomerBlockedErr: Label 'Customer %1 is blocked and cannot place orders.';
+ OrderProcessedMsg: Label 'Successfully processed order %1 with total amount %2.';
+
+ ///
+ /// Processes a sales order by validating customer, checking inventory, and applying discounts
+ ///
+ /// The sales order number to process
+ procedure ProcessSalesOrder(DocumentNo: Code[20])
+ var
+ SalesHeader: Record "Sales Header";
+ TotalAmount: Decimal;
+ begin
+ LargeOrderThreshold := 10000;
+ LargeOrderDiscountPct := 5;
+
+ if DocumentNo = '' then
+ Error('Document number cannot be empty.');
+
+ if not SalesHeader.Get(SalesHeader."Document Type"::Order, DocumentNo) then
+ Error('Sales order %1 not found.', DocumentNo);
+
+ ValidateCustomer(SalesHeader);
+ CheckInventoryAvailability(SalesHeader);
+ TotalAmount := CalculateOrderTotal(SalesHeader);
+
+ if TotalAmount > LargeOrderThreshold then
+ ApplyLargeOrderDiscount(SalesHeader);
+
+ Message(OrderProcessedMsg, DocumentNo, Format(TotalAmount, 0, ''));
+ end;
+
+ ///
+ /// Validates that the customer is not blocked
+ ///
+ /// The sales header to validate
+ local procedure ValidateCustomer(SalesHeader: Record "Sales Header")
+ var
+ Customer: Record Customer;
+ begin
+ if not Customer.Get(SalesHeader."Sell-to Customer No.") then
+ Error('Customer %1 not found.', SalesHeader."Sell-to Customer No.");
+
+ if Customer.Blocked <> Customer.Blocked::" " then
+ Error(CustomerBlockedErr, Customer."No.");
+ end;
+
+ ///
+ /// Checks that sufficient inventory is available for all items on the order
+ ///
+ /// The sales header to check
+ local procedure CheckInventoryAvailability(SalesHeader: Record "Sales Header")
+ var
+ SalesLine: Record "Sales Line";
+ Item: Record Item;
+ begin
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ SalesLine.SetRange(Type, SalesLine.Type::Item);
+
+ if SalesLine.FindSet() then
+ repeat
+ if Item.Get(SalesLine."No.") then
+ if Item.Inventory < SalesLine.Quantity then
+ Error(InsufficientInventoryErr, Item."No.", Item.Inventory, SalesLine.Quantity);
+ until SalesLine.Next() = 0;
+ end;
+
+ ///
+ /// Calculates the total amount for the sales order
+ ///
+ /// The sales header to calculate totals for
+ /// The total amount of the order
+ local procedure CalculateOrderTotal(SalesHeader: Record "Sales Header"): Decimal
+ var
+ SalesLine: Record "Sales Line";
+ TotalAmount: Decimal;
+ begin
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ SalesLine.SetLoadFields("Line Amount");
+
+ if SalesLine.FindSet() then
+ repeat
+ TotalAmount += SalesLine."Line Amount";
+ until SalesLine.Next() = 0;
+
+ exit(TotalAmount);
+ end;
+
+ ///
+ /// Applies a discount to all lines on large orders
+ ///
+ /// The sales header to apply discounts to
+ local procedure ApplyLargeOrderDiscount(SalesHeader: Record "Sales Header")
+ var
+ SalesLine: Record "Sales Line";
+ begin
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ SalesLine.ModifyAll("Line Discount %", LargeOrderDiscountPct, true);
+ end;
+}
+```
+
+### Step 8: Run Tests After Phase 2
+
+Run your tests again after structural improvements:
+
+```powershell
+Invoke-NAVCodeunit -CodeunitId 50101
+```
+
+Tests should pass. If not, review the structural changes.
+
+### Step 9: Phase 3 - API Modernization
+
+**Prompt**:
+
+```
+Modernize this code to use current AL best practices:
+
+1. Replace deprecated Find('-') with FindSet()
+2. Add proper SetLoadFields for performance
+3. Use better error handling patterns
+4. Implement proper transaction handling
+5. Replace hard-coded values with setup table
+
+[Include the Phase 2 code]
+```
+
+**Expected Result**:
+
+```al
+///
+/// Manages sales order processing including validation, inventory checking, and discount application
+///
+codeunit 50100 "Sales Order Management"
+{
+ var
+ InsufficientInventoryErr: Label 'Insufficient inventory for item %1. Available: %2, Required: %3';
+ CustomerBlockedErr: Label 'Customer %1 is blocked and cannot place orders.';
+ OrderProcessedMsg: Label 'Successfully processed order %1 with total amount %2.';
+
+ ///
+ /// Processes a sales order by validating customer, checking inventory, and applying discounts
+ ///
+ /// The sales order number to process
+ procedure ProcessSalesOrder(DocumentNo: Code[20])
+ var
+ SalesHeader: Record "Sales Header";
+ TotalAmount: Decimal;
+ begin
+ if DocumentNo = '' then
+ Error('Document number cannot be empty.');
+
+ if not SalesHeader.Get(SalesHeader."Document Type"::Order, DocumentNo) then
+ Error('Sales order %1 not found.', DocumentNo);
+
+ ValidateCustomer(SalesHeader);
+ CheckInventoryAvailability(SalesHeader);
+ TotalAmount := CalculateOrderTotal(SalesHeader);
+
+ if ShouldApplyLargeOrderDiscount(TotalAmount) then
+ ApplyLargeOrderDiscount(SalesHeader);
+
+ LogOrderProcessing(DocumentNo, TotalAmount);
+ Message(OrderProcessedMsg, DocumentNo, Format(TotalAmount, 0, ''));
+ end;
+
+ local procedure ValidateCustomer(SalesHeader: Record "Sales Header")
+ var
+ Customer: Record Customer;
+ begin
+ Customer.SetLoadFields(Blocked);
+
+ if not Customer.Get(SalesHeader."Sell-to Customer No.") then
+ Error('Customer %1 not found.', SalesHeader."Sell-to Customer No.");
+
+ if Customer.Blocked <> Customer.Blocked::" " then
+ Error(CustomerBlockedErr, Customer."No.");
+ end;
+
+ local procedure CheckInventoryAvailability(SalesHeader: Record "Sales Header")
+ var
+ SalesLine: Record "Sales Line";
+ Item: Record Item;
+ begin
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ SalesLine.SetRange(Type, SalesLine.Type::Item);
+ SalesLine.SetLoadFields("No.", Quantity);
+
+ if SalesLine.FindSet() then begin
+ Item.SetLoadFields(Inventory);
+ repeat
+ if Item.Get(SalesLine."No.") then
+ if Item.Inventory < SalesLine.Quantity then
+ Error(InsufficientInventoryErr, Item."No.", Item.Inventory, SalesLine.Quantity);
+ until SalesLine.Next() = 0;
+ end;
+ end;
+
+ local procedure CalculateOrderTotal(SalesHeader: Record "Sales Header"): Decimal
+ var
+ SalesLine: Record "Sales Line";
+ TotalAmount: Decimal;
+ begin
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ SalesLine.SetLoadFields("Line Amount");
+
+ if SalesLine.FindSet() then
+ repeat
+ TotalAmount += SalesLine."Line Amount";
+ until SalesLine.Next() = 0;
+
+ exit(TotalAmount);
+ end;
+
+ local procedure ShouldApplyLargeOrderDiscount(TotalAmount: Decimal): Boolean
+ var
+ SalesSetup: Record "Sales & Receivables Setup";
+ begin
+ SalesSetup.Get();
+ exit(TotalAmount > SalesSetup."Large Order Threshold");
+ end;
+
+ local procedure ApplyLargeOrderDiscount(SalesHeader: Record "Sales Header")
+ var
+ SalesLine: Record "Sales Line";
+ SalesSetup: Record "Sales & Receivables Setup";
+ begin
+ SalesSetup.Get();
+
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ SalesLine.ModifyAll("Line Discount %", SalesSetup."Large Order Discount %", true);
+ end;
+
+ local procedure LogOrderProcessing(DocumentNo: Code[20]; TotalAmount: Decimal)
+ var
+ Telemetry: Codeunit Telemetry;
+ CustomDimensions: Dictionary of [Text, Text];
+ begin
+ CustomDimensions.Add('DocumentNo', DocumentNo);
+ CustomDimensions.Add('TotalAmount', Format(TotalAmount));
+
+ Telemetry.LogMessage('SALESORD-001', 'Sales order processed successfully',
+ Verbosity::Normal, DataClassification::SystemMetadata,
+ TelemetryScope::ExtensionPublisher, CustomDimensions);
+ end;
+}
+```
+
+### Step 10: Update Tests for Behavioral Changes
+
+Now that the code is cleaner, you may want to improve behavior (e.g., Error() instead of Message()):
+
+**Prompt**:
+
+```
+I want to change the behavior to use Error() instead of Message() for validation failures.
+
+First, update the tests to expect these errors:
+- TestBlockedCustomerError should expect an error
+- Update assertions to use asserterror and Assert.ExpectedError
+
+Then show the code changes needed.
+```
+
+### Step 11: Expand Test Coverage
+
+**Prompt**:
+
+```
+Now that refactoring is complete, add more comprehensive tests for edge cases.
+
+Include tests for:
+- Happy path: successful processing
+- Customer validation errors
+- Inventory availability checks
+- Large order discount application
+- Edge cases: empty document number, non-existent order
+
+Use the AL test framework with proper setup and teardown.
+```
+
+**Expected Test Codeunit**:
+
+```al
+codeunit 50101 "Sales Order Management Tests"
+{
+ Subtype = Test;
+
+ var
+ Assert: Codeunit "Library Assert";
+ LibrarySales: Codeunit "Library - Sales";
+ LibraryInventory: Codeunit "Library - Inventory";
+
+ [Test]
+ procedure TestSuccessfulOrderProcessing()
+ var
+ SalesHeader: Record "Sales Header";
+ SalesOrderMgmt: Codeunit "Sales Order Management";
+ begin
+ // [GIVEN] A valid sales order with sufficient inventory
+ CreateSalesOrderWithInventory(SalesHeader);
+
+ // [WHEN] Processing the order
+ SalesOrderMgmt.ProcessSalesOrder(SalesHeader."No.");
+
+ // [THEN] No error is raised
+ // Verified by test not failing
+ end;
+
+ [Test]
+ procedure TestBlockedCustomerError()
+ var
+ SalesHeader: Record "Sales Header";
+ Customer: Record Customer;
+ SalesOrderMgmt: Codeunit "Sales Order Management";
+ begin
+ // [GIVEN] A sales order for a blocked customer
+ CreateSalesOrderWithBlockedCustomer(SalesHeader, Customer);
+
+ // [WHEN] Processing the order
+ asserterror SalesOrderMgmt.ProcessSalesOrder(SalesHeader."No.");
+
+ // [THEN] Error is raised about blocked customer
+ Assert.ExpectedError(StrSubstNo('Customer %1 is blocked', Customer."No."));
+ end;
+
+ [Test]
+ procedure TestInsufficientInventoryError()
+ var
+ SalesHeader: Record "Sales Header";
+ Item: Record Item;
+ SalesOrderMgmt: Codeunit "Sales Order Management";
+ begin
+ // [GIVEN] A sales order with more quantity than available inventory
+ CreateSalesOrderWithInsufficientInventory(SalesHeader, Item);
+
+ // [WHEN] Processing the order
+ asserterror SalesOrderMgmt.ProcessSalesOrder(SalesHeader."No.");
+
+ // [THEN] Error is raised about insufficient inventory
+ Assert.ExpectedError('Insufficient inventory');
+ end;
+
+ [Test]
+ procedure TestLargeOrderDiscountApplied()
+ var
+ SalesHeader: Record "Sales Header";
+ SalesLine: Record "Sales Line";
+ SalesSetup: Record "Sales & Receivables Setup";
+ SalesOrderMgmt: Codeunit "Sales Order Management";
+ ExpectedDiscount: Decimal;
+ begin
+ // [GIVEN] A large order that qualifies for discount
+ SalesSetup.Get();
+ ExpectedDiscount := SalesSetup."Large Order Discount %";
+ CreateLargeSalesOrder(SalesHeader);
+
+ // [WHEN] Processing the order
+ SalesOrderMgmt.ProcessSalesOrder(SalesHeader."No.");
+
+ // [THEN] Discount is applied to all lines
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ SalesLine.FindSet();
+ repeat
+ Assert.AreEqual(ExpectedDiscount, SalesLine."Line Discount %", 'Discount not applied correctly');
+ until SalesLine.Next() = 0;
+ end;
+
+ local procedure CreateSalesOrderWithInventory(var SalesHeader: Record "Sales Header")
+ var
+ Item: Record Item;
+ SalesLine: Record "Sales Line";
+ begin
+ LibraryInventory.CreateItem(Item);
+ Item.Inventory := 100;
+ Item.Modify();
+
+ LibrarySales.CreateSalesHeader(SalesHeader, SalesHeader."Document Type"::Order, LibrarySales.CreateCustomerNo());
+ LibrarySales.CreateSalesLine(SalesLine, SalesHeader, SalesLine.Type::Item, Item."No.", 10);
+ end;
+
+ // Additional helper procedures...
+}
+```
+
+## Review Points: What to Check
+
+After each refactoring phase, verify:
+
+### ✅ Functionality Preserved
+
+- [ ] All original functionality still works
+- [ ] No regressions introduced
+- [ ] Tests pass (or create tests first!)
+- [ ] Edge cases still handled
+
+### ✅ Code Quality Improved
+
+- [ ] More readable and maintainable
+- [ ] Better structure and organization
+- [ ] Clearer naming and documentation
+- [ ] Proper error handling
+
+### ✅ Performance Not Degraded
+
+- [ ] Database operations optimized
+- [ ] No unnecessary loops or queries
+- [ ] Proper use of SetLoadFields
+- [ ] Efficient algorithms
+
+### ✅ Modern Practices Applied
+
+- [ ] Current AL syntax and APIs
+- [ ] No deprecated features
+- [ ] Proper telemetry
+- [ ] Good separation of concerns
+
+## Advanced Refactoring Patterns
+
+### Extract Interface for Testability
+
+**Prompt**:
+
+```
+Refactor this codeunit to use interfaces for dependencies, making it more testable.
+
+Extract interfaces for:
+- Customer validation
+- Inventory checking
+- Discount calculation
+
+This will allow us to mock these dependencies in tests.
+```
+
+### Convert to Event-Driven Architecture
+
+**Prompt**:
+
+```
+Refactor this code to use Business Central events:
+
+1. Publish events for:
+ - Before order processing
+ - After order validation
+ - Before discount application
+ - After order processing
+
+2. This allows other extensions to hook into the process
+```
+
+### Add Batch Processing Support
+
+**Prompt**:
+
+```
+Extend this codeunit to support batch processing of multiple orders.
+
+Include:
+- Progress tracking
+- Error handling per order (don't fail entire batch)
+- Summary reporting
+- Performance optimization for bulk operations
+```
+
+## Common Refactoring Challenges
+
+### Challenge 1: Unknown Business Logic
+
+**Problem**: Code has complex logic without documentation
+
+**Solution**:
+
+```
+Analyze this code and explain what business logic it implements:
+[paste complex code]
+
+Then suggest how to make the logic clearer through refactoring.
+```
+
+### Challenge 2: Tightly Coupled Code
+
+**Problem**: Code has many dependencies that are hard to untangle
+
+**Solution**:
+
+```
+This code is tightly coupled. Create a refactoring plan to:
+1. Identify dependencies
+2. Extract interfaces
+3. Use dependency injection
+4. Make code more modular
+```
+
+### Challenge 3: Large Procedures
+
+**Problem**: Single procedure doing too many things
+
+**Solution**:
+
+```
+This procedure is too large and complex.
+Apply the Single Responsibility Principle to break it into smaller procedures.
+Each procedure should have one clear purpose.
+```
+
+## Best Practices for Refactoring with AI
+
+### 1. Always Write Tests First
+
+{{% alert title="Golden Rule" color="primary" %}}
+**Never refactor without tests.** Tests are your safety net. Write them first, run them, then refactor.
+{{% /alert %}}
+
+```
+Before we start refactoring, let's write tests that lock in the current behavior.
+Even if the current behavior isn't perfect, we need to know if we change it.
+```
+
+### 2. Refactor in Small Steps
+
+Don't try to refactor everything at once. Use incremental changes:
+
+```
+Let's refactor this code in three phases:
+Phase 1: Just improve naming and documentation
+[Run tests - should pass]
+Phase 2: Extract methods
+[Run tests - should pass]
+Phase 3: Modernize APIs
+[Run tests - should pass]
+```
+
+### 3. Run Tests After Every Change
+
+```
+I've completed the naming refactoring.
+Let me run the tests to make sure nothing broke.
+
+[Run tests]
+
+Great, tests pass. Now let's proceed to Phase 2.
+```
+
+### 3. Use Git Commits for Each Phase
+
+```
+We've completed Phase 1: Safe Refactorings.
+Before moving to Phase 2, I'll commit these changes.
+Suggest a good commit message for these refactorings.
+```
+
+### 4. Document Why, Not Just What
+
+```
+For each major refactoring, add a comment explaining WHY the change was made:
+- Why was the old approach problematic?
+- What does the new approach solve?
+- Are there trade-offs?
+```
+
+### 5. Keep Performance in Mind
+
+```
+As we refactor this code, let's ensure we don't hurt performance.
+For each database operation change, explain the performance implications.
+```
+
+## Practice Exercise
+
+Refactor this legacy code:
+
+```al
+codeunit 50200 "Item Price Calculator"
+{
+ procedure CalcPrice(IN: Code[20]; CU: Code[10]; QT: Decimal): Decimal
+ var
+ I: Record Item;
+ C: Record Customer;
+ P: Decimal;
+ begin
+ I.Get(IN);
+ P := I."Unit Price";
+
+ if QT > 100 then
+ P := P * 0.9;
+
+ if CU <> '' then begin
+ C.Get(CU);
+ if C."Customer Price Group" = 'VIP' then
+ P := P * 0.95;
+ end;
+
+ exit(P);
+ end;
+}
+```
+
+**Your Tasks**:
+
+1. Assess the code and list issues
+2. Create a refactoring plan
+3. Apply naming improvements
+4. Extract methods for each responsibility
+5. Add proper documentation and error handling
+6. Create tests
+7. Add telemetry
+
+## Next Steps
+
+- Learn about [writing tests](../testing) for your refactored code
+- See how [code review](../code-review) catches refactoring issues
+- Explore [adding telemetry](../telemetry) to monitor refactored code
diff --git a/content/docs/agentic-coding/GettingMore/telemetry.md b/content/docs/agentic-coding/GettingMore/telemetry.md
new file mode 100644
index 00000000..c4d0c696
--- /dev/null
+++ b/content/docs/agentic-coding/GettingMore/telemetry.md
@@ -0,0 +1,599 @@
+---
+title: "Adding Telemetry"
+linkTitle: "Telemetry"
+weight: 3
+description: >
+ Use AI to instrument your AL extensions with Application Insights telemetry
+---
+
+## Scenario
+
+You have a Business Central extension that's running in production, but you have limited visibility into:
+- How often features are used
+- Where errors occur
+- Performance bottlenecks
+- User behavior patterns
+
+You want to add comprehensive telemetry using Application Insights to monitor your extension in production.
+
+## Goal
+
+Use AI to help you:
+- Add telemetry calls throughout your code
+- Log important events and errors
+- Track feature usage
+- Monitor performance
+- Create custom dimensions for better analysis
+
+## Prerequisites
+
+Understanding of:
+- Business Central telemetry concepts
+- Application Insights basics
+- When to log (without over-logging)
+- Data classification requirements
+
+## Step-by-Step Guide
+
+### Step 1: Understanding Your Code
+
+**Starting Code** (without telemetry):
+```al
+codeunit 50100 "Sales Order Processor"
+{
+ procedure ProcessOrder(var SalesHeader: Record "Sales Header"): Boolean
+ var
+ SalesLine: Record "Sales Line";
+ begin
+ if not ValidateOrder(SalesHeader) then
+ exit(false);
+
+ CalculateTotals(SalesHeader);
+ ApplyDiscounts(SalesHeader);
+
+ if not PostOrder(SalesHeader) then
+ exit(false);
+
+ exit(true);
+ end;
+
+ local procedure ValidateOrder(var SalesHeader: Record "Sales Header"): Boolean
+ var
+ Customer: Record Customer;
+ begin
+ if not Customer.Get(SalesHeader."Sell-to Customer No.") then begin
+ Error('Customer %1 does not exist.', SalesHeader."Sell-to Customer No.");
+ end;
+
+ if Customer.Blocked <> Customer.Blocked::" " then begin
+ Error('Customer %1 is blocked.', Customer."No.");
+ end;
+
+ exit(true);
+ end;
+
+ local procedure PostOrder(var SalesHeader: Record "Sales Header"): Boolean
+ var
+ SalesPost: Codeunit "Sales-Post";
+ begin
+ exit(SalesPost.Run(SalesHeader));
+ end;
+}
+```
+
+### Step 2: Request Telemetry Strategy
+
+**Prompt**:
+```
+I want to add Application Insights telemetry to this Business Central codeunit.
+
+Help me plan what to log:
+- What events should be logged?
+- What custom dimensions should be included?
+- What data classification is appropriate?
+- Where should we log errors vs. information?
+
+[Paste the code above]
+```
+
+**Expected AI Response**:
+The AI should suggest logging:
+
+**Events to Log:**
+1. Order processing started (Informational)
+2. Order validation completed (Informational)
+3. Order posted successfully (Informational)
+4. Validation failures (Warning)
+5. Posting failures (Error)
+6. Performance metrics (Informational)
+
+**Custom Dimensions:**
+- Order Number
+- Customer Number
+- Order Amount
+- Number of Lines
+- Processing Duration
+- Error Details (when applicable)
+
+**Data Classification:**
+- Order Number: CustomerContent
+- Customer Number: CustomerContent
+- Amounts: CustomerContent
+- Counts: SystemMetadata
+- Duration: SystemMetadata
+
+### Step 3: Add Telemetry to Main Procedure
+
+**Prompt**:
+```
+Add Application Insights telemetry to the ProcessOrder procedure.
+
+Include:
+- Start event when processing begins
+- Success event when complete
+- Error event on failure
+- Custom dimensions: OrderNo, CustomerNo, TotalAmount, LineCount, Duration
+- Use appropriate data classification
+- Use the Telemetry codeunit from System Application
+
+Update this code:
+[Paste ProcessOrder procedure]
+```
+
+**Expected Result**:
+```al
+procedure ProcessOrder(var SalesHeader: Record "Sales Header"): Boolean
+var
+ Telemetry: Codeunit Telemetry;
+ CustomDimensions: Dictionary of [Text, Text];
+ StartTime: DateTime;
+ Duration: Duration;
+ LineCount: Integer;
+begin
+ StartTime := CurrentDateTime;
+
+ // Log start of processing
+ AddOrderDimensions(CustomDimensions, SalesHeader);
+ Telemetry.LogMessage('SALESORD-001', 'Order processing started',
+ Verbosity::Normal, DataClassification::SystemMetadata,
+ TelemetryScope::ExtensionPublisher, CustomDimensions);
+
+ if not ValidateOrder(SalesHeader) then begin
+ LogProcessingError(SalesHeader, 'Validation failed');
+ exit(false);
+ end;
+
+ CalculateTotals(SalesHeader);
+ ApplyDiscounts(SalesHeader);
+
+ if not PostOrder(SalesHeader) then begin
+ LogProcessingError(SalesHeader, 'Posting failed');
+ exit(false);
+ end;
+
+ // Log successful completion
+ Duration := CurrentDateTime - StartTime;
+ Clear(CustomDimensions);
+ AddOrderDimensions(CustomDimensions, SalesHeader);
+ CustomDimensions.Add('Duration', Format(Duration));
+ CustomDimensions.Add('LineCount', Format(CountLines(SalesHeader)));
+
+ Telemetry.LogMessage('SALESORD-002', 'Order processing completed successfully',
+ Verbosity::Normal, DataClassification::SystemMetadata,
+ TelemetryScope::ExtensionPublisher, CustomDimensions);
+
+ exit(true);
+end;
+
+local procedure AddOrderDimensions(var CustomDimensions: Dictionary of [Text, Text]; SalesHeader: Record "Sales Header")
+begin
+ CustomDimensions.Add('OrderNo', SalesHeader."No.");
+ CustomDimensions.Add('CustomerNo', SalesHeader."Sell-to Customer No.");
+ CustomDimensions.Add('OrderType', Format(SalesHeader."Document Type"));
+end;
+
+local procedure LogProcessingError(SalesHeader: Record "Sales Header"; ErrorMessage: Text)
+var
+ Telemetry: Codeunit Telemetry;
+ CustomDimensions: Dictionary of [Text, Text];
+begin
+ AddOrderDimensions(CustomDimensions, SalesHeader);
+ CustomDimensions.Add('ErrorMessage', ErrorMessage);
+ CustomDimensions.Add('ErrorCallStack', GetLastErrorCallStack());
+
+ Telemetry.LogMessage('SALESORD-E001', StrSubstNo('Order processing failed: %1', ErrorMessage),
+ Verbosity::Error, DataClassification::SystemMetadata,
+ TelemetryScope::ExtensionPublisher, CustomDimensions);
+end;
+
+local procedure CountLines(SalesHeader: Record "Sales Header"): Integer
+var
+ SalesLine: Record "Sales Line";
+begin
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ exit(SalesLine.Count);
+end;
+```
+
+### Step 4: Add Error Tracking
+
+**Prompt**:
+```
+Update the ValidateOrder procedure to log validation failures with telemetry.
+
+For each validation check that fails:
+- Log a warning message
+- Include relevant details (customer number, block reason, etc.)
+- Use appropriate custom dimensions
+- Use proper data classification
+
+[Paste ValidateOrder procedure]
+```
+
+**Expected Result**:
+```al
+local procedure ValidateOrder(var SalesHeader: Record "Sales Header"): Boolean
+var
+ Customer: Record Customer;
+ Telemetry: Codeunit Telemetry;
+ CustomDimensions: Dictionary of [Text, Text];
+begin
+ if not Customer.Get(SalesHeader."Sell-to Customer No.") then begin
+ AddValidationDimensions(CustomDimensions, SalesHeader, 'Customer not found');
+ Telemetry.LogMessage('SALESORD-W001', 'Order validation failed: Customer not found',
+ Verbosity::Warning, DataClassification::SystemMetadata,
+ TelemetryScope::ExtensionPublisher, CustomDimensions);
+
+ Error('Customer %1 does not exist.', SalesHeader."Sell-to Customer No.");
+ end;
+
+ if Customer.Blocked <> Customer.Blocked::" " then begin
+ Clear(CustomDimensions);
+ AddValidationDimensions(CustomDimensions, SalesHeader, 'Customer blocked');
+ CustomDimensions.Add('BlockedReason', Format(Customer.Blocked));
+
+ Telemetry.LogMessage('SALESORD-W002', 'Order validation failed: Customer blocked',
+ Verbosity::Warning, DataClassification::SystemMetadata,
+ TelemetryScope::ExtensionPublisher, CustomDimensions);
+
+ Error('Customer %1 is blocked.', Customer."No.");
+ end;
+
+ exit(true);
+end;
+
+local procedure AddValidationDimensions(var CustomDimensions: Dictionary of [Text, Text]; SalesHeader: Record "Sales Header"; Reason: Text)
+begin
+ CustomDimensions.Add('OrderNo', SalesHeader."No.");
+ CustomDimensions.Add('CustomerNo', SalesHeader."Sell-to Customer No.");
+ CustomDimensions.Add('ValidationFailure', Reason);
+end;
+```
+
+### Step 5: Add Performance Tracking
+
+**Prompt**:
+```
+Add performance telemetry to track how long different operations take.
+
+Track duration for:
+- Overall processing
+- Validation
+- Calculation
+- Posting
+
+Log if any operation takes longer than expected thresholds:
+- Validation > 1 second
+- Calculation > 2 seconds
+- Posting > 5 seconds
+
+[Include the codeunit]
+```
+
+**Expected Result**:
+```al
+local procedure ValidateOrder(var SalesHeader: Record "Sales Header"): Boolean
+var
+ Customer: Record Customer;
+ Telemetry: Codeunit Telemetry;
+ CustomDimensions: Dictionary of [Text, Text];
+ StartTime: DateTime;
+ Duration: Duration;
+begin
+ StartTime := CurrentDateTime;
+
+ // Validation logic here...
+
+ Duration := CurrentDateTime - StartTime;
+
+ // Log if validation took too long
+ if Duration > 1000 then begin
+ AddOrderDimensions(CustomDimensions, SalesHeader);
+ CustomDimensions.Add('Duration', Format(Duration));
+ CustomDimensions.Add('Operation', 'Validation');
+
+ Telemetry.LogMessage('SALESORD-P001', 'Slow validation detected',
+ Verbosity::Warning, DataClassification::SystemMetadata,
+ TelemetryScope::ExtensionPublisher, CustomDimensions);
+ end;
+
+ exit(true);
+end;
+```
+
+### Step 6: Add Feature Usage Tracking
+
+**Prompt**:
+```
+Add telemetry to track feature usage for business analytics.
+
+Track:
+- How often each discount type is applied
+- Which payment methods are used
+- Popular shipping methods
+- Order size distribution
+
+Create a FeatureUsageTelemetry codeunit for this purpose.
+```
+
+**Expected Result**:
+```al
+codeunit 50101 "Feature Usage Telemetry"
+{
+ var
+ Telemetry: Codeunit Telemetry;
+
+ procedure LogDiscountApplied(DiscountType: Text; DiscountPct: Decimal; OrderNo: Code[20])
+ var
+ CustomDimensions: Dictionary of [Text, Text];
+ begin
+ CustomDimensions.Add('FeatureArea', 'Discounts');
+ CustomDimensions.Add('DiscountType', DiscountType);
+ CustomDimensions.Add('DiscountPercentage', Format(DiscountPct));
+ CustomDimensions.Add('OrderNo', OrderNo);
+
+ Telemetry.LogMessage('FEATURE-DISCOUNT', 'Discount applied',
+ Verbosity::Normal, DataClassification::SystemMetadata,
+ TelemetryScope::ExtensionPublisher, CustomDimensions);
+ end;
+
+ procedure LogPaymentMethod(PaymentMethodCode: Code[10]; Amount: Decimal)
+ var
+ CustomDimensions: Dictionary of [Text, Text];
+ begin
+ CustomDimensions.Add('FeatureArea', 'Payment');
+ CustomDimensions.Add('PaymentMethod', PaymentMethodCode);
+ CustomDimensions.Add('AmountRange', GetAmountRange(Amount));
+
+ Telemetry.LogMessage('FEATURE-PAYMENT', 'Payment method used',
+ Verbosity::Normal, DataClassification::SystemMetadata,
+ TelemetryScope::ExtensionPublisher, CustomDimensions);
+ end;
+
+ local procedure GetAmountRange(Amount: Decimal): Text
+ begin
+ case true of
+ Amount < 100:
+ exit('0-100');
+ Amount < 1000:
+ exit('100-1000');
+ Amount < 10000:
+ exit('1000-10000');
+ else
+ exit('10000+');
+ end;
+ end;
+}
+```
+
+## Telemetry Best Practices
+
+### ✅ Do's
+
+**Use Consistent Event IDs**
+```
+SALESORD-001: Processing started
+SALESORD-002: Processing completed
+SALESORD-E001: Processing error
+SALESORD-W001: Validation warning
+SALESORD-P001: Performance warning
+```
+
+**Use Meaningful Messages**
+```al
+// Good
+Telemetry.LogMessage('SALESORD-001', 'Sales order processing started for large order', ...);
+
+// Bad
+Telemetry.LogMessage('001', 'Started', ...);
+```
+
+**Include Helpful Custom Dimensions**
+```al
+CustomDimensions.Add('OrderNo', OrderNo);
+CustomDimensions.Add('CustomerNo', CustomerNo);
+CustomDimensions.Add('LineCount', Format(LineCount));
+CustomDimensions.Add('TotalAmount', Format(TotalAmount));
+CustomDimensions.Add('ProcessingDuration', Format(Duration));
+```
+
+**Use Appropriate Data Classification**
+```al
+// Customer data
+DataClassification::CustomerContent
+
+// System metrics
+DataClassification::SystemMetadata
+
+// Organizational data
+DataClassification::OrganizationIdentifiableInformation
+```
+
+### ❌ Don'ts
+
+**Don't Over-Log**
+```al
+// Too much logging
+Telemetry.LogMessage('001', 'Line 1', ...);
+Telemetry.LogMessage('002', 'Line 2', ...);
+// Don't log every single step
+```
+
+**Don't Log Sensitive Data**
+```al
+// Bad - logging password
+CustomDimensions.Add('Password', Password);
+
+// Bad - logging full credit card
+CustomDimensions.Add('CreditCard', CreditCardNo);
+
+// Bad - logging personal data unnecessarily
+CustomDimensions.Add('SSN', SSN);
+```
+
+**Don't Use Generic Messages**
+```al
+// Bad
+Telemetry.LogMessage('001', 'Error', ...);
+
+// Good
+Telemetry.LogMessage('SALESORD-E001', 'Failed to post sales order due to credit limit exceeded', ...);
+```
+
+## Advanced Telemetry Patterns
+
+### Pattern 1: Telemetry Wrapper
+**Prompt**:
+```
+Create a telemetry wrapper codeunit that simplifies logging for my extension.
+Include helper methods for:
+- LogStart/LogEnd (with automatic duration calculation)
+- LogError (with automatic call stack)
+- LogFeatureUsage
+- LogPerformanceWarning
+
+Prefix all event IDs with my extension prefix "SALESEXT-"
+```
+
+### Pattern 2: Telemetry Constants
+**Prompt**:
+```
+Create a codeunit with constants for all my telemetry event IDs and messages.
+This will ensure consistency and make it easier to update messages.
+```
+
+### Pattern 3: Contextual Telemetry
+**Prompt**:
+```
+Create a system that automatically adds common context to all telemetry:
+- User ID (anonymized)
+- Company name (anonymized)
+- Extension version
+- BC version
+- Environment type (Production/Sandbox)
+
+Make this context added automatically to all telemetry calls.
+```
+
+## Monitoring and Analysis
+
+### Creating Useful Queries
+
+**Prompt**:
+```
+Create KQL (Kusto Query Language) queries for Application Insights to analyze:
+
+1. Most common errors in the last 24 hours
+2. Average processing duration by order size
+3. Feature usage statistics
+4. Performance trends over time
+5. Error rate percentage
+
+Base the queries on the telemetry we added to the Sales Order Processor codeunit.
+```
+
+**Expected Result**:
+```kql
+// Most common errors in last 24 hours
+traces
+| where timestamp > ago(24h)
+| where message startswith "SALESORD-E"
+| summarize ErrorCount = count() by message, customDimensions.ErrorMessage
+| order by ErrorCount desc
+| take 10
+
+// Average processing duration by line count
+traces
+| where message == "SALESORD-002"
+| extend LineCount = toint(customDimensions.LineCount)
+| extend Duration = toint(customDimensions.Duration)
+| summarize AvgDuration = avg(Duration) by LineCountBucket = bin(LineCount, 5)
+| order by LineCountBucket asc
+
+// Feature usage - discount types
+traces
+| where message == "FEATURE-DISCOUNT"
+| summarize UsageCount = count() by DiscountType = tostring(customDimensions.DiscountType)
+| order by UsageCount desc
+
+// Performance warnings
+traces
+| where message startswith "SALESORD-P"
+| summarize WarningCount = count() by Operation = tostring(customDimensions.Operation), bin(timestamp, 1h)
+| render timechart
+
+// Error rate percentage
+let totalOrders = toscalar(
+ traces
+ | where message == "SALESORD-001"
+ | where timestamp > ago(24h)
+ | count
+);
+let failedOrders = toscalar(
+ traces
+ | where message startswith "SALESORD-E"
+ | where timestamp > ago(24h)
+ | count
+);
+print ErrorRate = (todouble(failedOrders) / todouble(totalOrders)) * 100
+```
+
+## Practice Exercise
+
+Add comprehensive telemetry to this code:
+
+```al
+codeunit 50200 "Inventory Adjustment Handler"
+{
+ procedure AdjustInventory(ItemNo: Code[20]; Quantity: Decimal; ReasonCode: Code[10])
+ var
+ Item: Record Item;
+ ItemJnlLine: Record "Item Journal Line";
+ begin
+ Item.Get(ItemNo);
+
+ ItemJnlLine.Init();
+ ItemJnlLine."Item No." := ItemNo;
+ ItemJnlLine.Quantity := Quantity;
+ ItemJnlLine."Reason Code" := ReasonCode;
+ ItemJnlLine.Insert(true);
+
+ CODEUNIT.Run(CODEUNIT::"Item Jnl.-Post Line", ItemJnlLine);
+ end;
+}
+```
+
+**Your Tasks**:
+1. Add start/end telemetry
+2. Add error handling and logging
+3. Track performance
+4. Log feature usage
+5. Add appropriate custom dimensions
+6. Create KQL queries for analysis
+
+## Next Steps
+
+- Learn about [refactoring legacy code](../refactoring) while adding telemetry
+- See how [code review](../code-review) can catch telemetry issues
+- Explore [testing strategies](../testing) for telemetry code
diff --git a/content/docs/agentic-coding/GettingMore/testing.md b/content/docs/agentic-coding/GettingMore/testing.md
new file mode 100644
index 00000000..3c9cfae7
--- /dev/null
+++ b/content/docs/agentic-coding/GettingMore/testing.md
@@ -0,0 +1,902 @@
+---
+title: "Writing Tests"
+linkTitle: "Testing"
+weight: 5
+description: >
+ Use AI to create comprehensive test coverage for your AL code
+---
+
+## Scenario
+
+You've developed new features for your Business Central extension, but you need comprehensive test coverage to:
+
+- Ensure code works as expected
+- Prevent regressions when making changes
+- Document expected behavior
+- Enable confident refactoring
+- Meet quality standards
+
+Writing tests manually is time-consuming, and you want to use AI to accelerate the process while maintaining test quality.
+
+## Goal
+
+Use AI to help you:
+
+- Generate unit tests for individual procedures
+- Create integration tests for complex workflows
+- Design test data and scenarios
+- Write test helpers and fixtures
+- Create mock objects for dependencies
+- Implement data-driven tests
+
+## The Code to Test
+
+Here's a codeunit that needs test coverage:
+
+```al
+codeunit 50100 "Order Discount Manager"
+{
+ procedure CalculateDiscount(var SalesHeader: Record "Sales Header"): Decimal
+ var
+ Customer: Record Customer;
+ DiscountPct: Decimal;
+ begin
+ if not Customer.Get(SalesHeader."Sell-to Customer No.") then
+ Error('Customer %1 not found', SalesHeader."Sell-to Customer No.");
+
+ DiscountPct := GetCustomerDiscount(Customer);
+ DiscountPct += GetVolumeDiscount(SalesHeader);
+ DiscountPct += GetSeasonalDiscount();
+
+ if DiscountPct > 50 then
+ DiscountPct := 50;
+
+ exit(DiscountPct);
+ end;
+
+ local procedure GetCustomerDiscount(Customer: Record Customer): Decimal
+ begin
+ case Customer."Customer Discount Group" of
+ 'VIP':
+ exit(10);
+ 'PREMIUM':
+ exit(5);
+ else
+ exit(0);
+ end;
+ end;
+
+ local procedure GetVolumeDiscount(SalesHeader: Record "Sales Header"): Decimal
+ var
+ SalesLine: Record "Sales Line";
+ TotalAmount: Decimal;
+ begin
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ SalesLine.CalcSums("Line Amount");
+ TotalAmount := SalesLine."Line Amount";
+
+ case true of
+ TotalAmount >= 10000:
+ exit(15);
+ TotalAmount >= 5000:
+ exit(10);
+ TotalAmount >= 1000:
+ exit(5);
+ else
+ exit(0);
+ end;
+ end;
+
+ local procedure GetSeasonalDiscount(): Decimal
+ begin
+ if Date2DMY(Today, 2) in [11, 12] then
+ exit(5);
+ exit(0);
+ end;
+}
+```
+
+## Step-by-Step Testing Process
+
+### Step 1: Generate Basic Test Structure
+
+**Prompt**:
+
+```
+Create a test codeunit for the Order Discount Manager.
+
+Include:
+- Proper test codeunit structure with Subtype = Test
+- Setup and teardown if needed
+- Test procedure stubs for all public procedures
+- Use AL test framework conventions
+- Include Assert codeunit
+- Add test isolation attributes where needed
+
+[Include the codeunit code]
+```
+
+**Expected Result**:
+
+```al
+codeunit 50101 "Order Discount Mgr. Tests"
+{
+ Subtype = Test;
+
+ var
+ Assert: Codeunit "Library Assert";
+ LibrarySales: Codeunit "Library - Sales";
+ LibraryUtility: Codeunit "Library - Utility";
+ IsInitialized: Boolean;
+
+ [Test]
+ procedure TestCalculateDiscountBasic()
+ begin
+ // Test basic discount calculation
+ end;
+
+ [Test]
+ procedure TestVIPCustomerDiscount()
+ begin
+ // Test VIP customer gets 10% discount
+ end;
+
+ [Test]
+ procedure TestVolumeDiscountTiers()
+ begin
+ // Test volume discount calculation at different amounts
+ end;
+
+ [Test]
+ procedure TestSeasonalDiscount()
+ begin
+ // Test seasonal discount in November/December
+ end;
+
+ [Test]
+ procedure TestMaximumDiscountCap()
+ begin
+ // Test discount cannot exceed 50%
+ end;
+
+ [Test]
+ procedure TestCustomerNotFoundError()
+ begin
+ // Test error when customer doesn't exist
+ end;
+
+ local procedure Initialize()
+ begin
+ if IsInitialized then
+ exit;
+
+ // Setup code here
+ IsInitialized := true;
+ end;
+}
+```
+
+### Step 2: Implement Happy Path Test
+
+**Prompt**:
+
+```
+Implement the TestCalculateDiscountBasic test using the Given-When-Then pattern.
+
+This test should verify:
+- A standard customer with a medium-size order
+- Gets the expected discount percentage
+- No errors are raised
+
+Use the Library codeunits for test data creation.
+Include clear comments for each section.
+```
+
+**Expected Result**:
+
+```al
+[Test]
+procedure TestCalculateDiscountBasic()
+var
+ Customer: Record Customer;
+ SalesHeader: Record "Sales Header";
+ OrderDiscountMgr: Codeunit "Order Discount Manager";
+ ActualDiscount: Decimal;
+ ExpectedDiscount: Decimal;
+begin
+ // [SCENARIO] Calculate discount for a standard order
+ Initialize();
+
+ // [GIVEN] A standard customer with no special discount group
+ Customer.Get(LibrarySales.CreateCustomerNo());
+ Customer."Customer Discount Group" := '';
+ Customer.Modify();
+
+ // [GIVEN] A sales order with total amount of 2000 (5% volume discount)
+ SalesHeader := CreateSalesOrderWithAmount(Customer."No.", 2000);
+
+ // [GIVEN] Expected discount is 5% (volume only, not in seasonal months)
+ ExpectedDiscount := 5;
+
+ // [WHEN] Calculating the discount
+ ActualDiscount := OrderDiscountMgr.CalculateDiscount(SalesHeader);
+
+ // [THEN] The discount matches expected value
+ Assert.AreEqual(ExpectedDiscount, ActualDiscount, 'Discount calculation incorrect');
+end;
+
+local procedure CreateSalesOrderWithAmount(CustomerNo: Code[20]; TotalAmount: Decimal): Record "Sales Header"
+var
+ SalesHeader: Record "Sales Header";
+ SalesLine: Record "Sales Line";
+ Item: Record Item;
+begin
+ LibrarySales.CreateSalesHeader(SalesHeader, SalesHeader."Document Type"::Order, CustomerNo);
+
+ Item."No." := LibraryUtility.GenerateRandomCode(Item.FieldNo("No."), Database::Item);
+ Item."Unit Price" := TotalAmount;
+ Item.Insert();
+
+ LibrarySales.CreateSalesLine(SalesLine, SalesHeader, SalesLine.Type::Item, Item."No.", 1);
+ SalesLine.Validate("Unit Price", TotalAmount);
+ SalesLine.Modify(true);
+
+ exit(SalesHeader);
+end;
+```
+
+### Step 3: Implement Error Case Tests
+
+**Prompt**:
+
+```
+Implement the TestCustomerNotFoundError test.
+
+This should verify:
+- When an invalid customer number is used
+- An appropriate error is raised
+- The error message contains the customer number
+
+Use asserterror and Assert.ExpectedError.
+```
+
+**Expected Result**:
+
+```al
+[Test]
+procedure TestCustomerNotFoundError()
+var
+ SalesHeader: Record "Sales Header";
+ OrderDiscountMgr: Codeunit "Order Discount Manager";
+ InvalidCustomerNo: Code[20];
+begin
+ // [SCENARIO] Error is raised when customer doesn't exist
+ Initialize();
+
+ // [GIVEN] A sales header with non-existent customer
+ InvalidCustomerNo := 'INVALID123';
+ LibrarySales.CreateSalesHeader(SalesHeader, SalesHeader."Document Type"::Order, '');
+ SalesHeader."Sell-to Customer No." := InvalidCustomerNo;
+ SalesHeader.Modify();
+
+ // [WHEN] Calculating discount for non-existent customer
+ asserterror OrderDiscountMgr.CalculateDiscount(SalesHeader);
+
+ // [THEN] Appropriate error is raised with customer number
+ Assert.ExpectedError(StrSubstNo('Customer %1 not found', InvalidCustomerNo));
+end;
+```
+
+### Step 4: Implement Data-Driven Tests
+
+**Prompt**:
+
+```
+Create a comprehensive test for all customer discount tiers (VIP, PREMIUM, standard).
+
+Use a data-driven approach where one test function tests all scenarios.
+Create a local helper that takes customer group and expected discount as parameters.
+
+Test these scenarios:
+- VIP customer: 10% discount
+- PREMIUM customer: 5% discount
+- Standard customer: 0% discount
+- Empty group: 0% discount
+```
+
+**Expected Result**:
+
+```al
+[Test]
+procedure TestCustomerDiscountTiers()
+begin
+ // [SCENARIO] Different customer types receive appropriate discounts
+ Initialize();
+
+ // [GIVEN] [WHEN] [THEN] VIP customers get 10% discount
+ VerifyCustomerTypeDiscount('VIP', 10);
+
+ // [GIVEN] [WHEN] [THEN] Premium customers get 5% discount
+ VerifyCustomerTypeDiscount('PREMIUM', 5);
+
+ // [GIVEN] [WHEN] [THEN] Standard customers get 0% discount
+ VerifyCustomerTypeDiscount('STANDARD', 0);
+
+ // [GIVEN] [WHEN] [THEN] Customers with no group get 0% discount
+ VerifyCustomerTypeDiscount('', 0);
+end;
+
+local procedure VerifyCustomerTypeDiscount(CustomerGroup: Code[10]; ExpectedDiscount: Decimal)
+var
+ Customer: Record Customer;
+ SalesHeader: Record "Sales Header";
+ OrderDiscountMgr: Codeunit "Order Discount Manager";
+ ActualDiscount: Decimal;
+begin
+ // Create customer with specific group
+ Customer.Get(LibrarySales.CreateCustomerNo());
+ Customer."Customer Discount Group" := CustomerGroup;
+ Customer.Modify();
+
+ // Create order with amount below volume discount threshold (< 1000)
+ SalesHeader := CreateSalesOrderWithAmount(Customer."No.", 500);
+
+ // Calculate discount
+ ActualDiscount := OrderDiscountMgr.CalculateDiscount(SalesHeader);
+
+ // Verify expected discount
+ Assert.AreEqual(ExpectedDiscount, ActualDiscount,
+ StrSubstNo('Incorrect discount for customer group %1', CustomerGroup));
+end;
+```
+
+### Step 5: Test Edge Cases and Boundaries
+
+**Prompt**:
+
+```
+Create tests for volume discount boundary conditions.
+
+Test these specific amounts:
+- 999: Just below 1000 threshold (expect 0% volume discount)
+- 1000: Exactly at threshold (expect 5% volume discount)
+- 4999: Just below 5000 threshold (expect 5% volume discount)
+- 5000: Exactly at threshold (expect 10% volume discount)
+- 9999: Just below 10000 threshold (expect 10% volume discount)
+- 10000: Exactly at threshold (expect 15% volume discount)
+
+Use descriptive test names and clear assertions.
+```
+
+**Expected Result**:
+
+```al
+[Test]
+procedure TestVolumeDiscountBoundaries()
+begin
+ // [SCENARIO] Volume discounts applied at exact thresholds
+ Initialize();
+
+ // Just below first threshold
+ VerifyVolumeDiscount(999, 0, 'Below 1000 threshold');
+
+ // Exactly at first threshold
+ VerifyVolumeDiscount(1000, 5, 'At 1000 threshold');
+
+ // Between first and second threshold
+ VerifyVolumeDiscount(4999, 5, 'Below 5000 threshold');
+
+ // Exactly at second threshold
+ VerifyVolumeDiscount(5000, 10, 'At 5000 threshold');
+
+ // Between second and third threshold
+ VerifyVolumeDiscount(9999, 10, 'Below 10000 threshold');
+
+ // Exactly at third threshold
+ VerifyVolumeDiscount(10000, 15, 'At 10000 threshold');
+end;
+
+local procedure VerifyVolumeDiscount(OrderAmount: Decimal; ExpectedVolumeDiscount: Decimal; Scenario: Text)
+var
+ Customer: Record Customer;
+ SalesHeader: Record "Sales Header";
+ OrderDiscountMgr: Codeunit "Order Discount Manager";
+ ActualDiscount: Decimal;
+begin
+ // Create standard customer (no customer discount)
+ Customer.Get(LibrarySales.CreateCustomerNo());
+ Customer."Customer Discount Group" := '';
+ Customer.Modify();
+
+ // Create order with specific amount
+ SalesHeader := CreateSalesOrderWithAmount(Customer."No.", OrderAmount);
+
+ // Calculate discount (assuming not in seasonal months)
+ ActualDiscount := OrderDiscountMgr.CalculateDiscount(SalesHeader);
+
+ // Verify volume discount
+ Assert.AreEqual(ExpectedVolumeDiscount, ActualDiscount,
+ StrSubstNo('Incorrect volume discount for %1 (amount: %2)', Scenario, OrderAmount));
+end;
+```
+
+### Step 6: Test Maximum Discount Cap
+
+**Prompt**:
+
+```
+Create a test that verifies the 50% maximum discount cap.
+
+Test scenario:
+- VIP customer (10% discount)
+- Large order (15% volume discount)
+- Seasonal period (5% discount)
+- Total would be 30%, which is under cap - verify this works
+- Then test a scenario that would exceed 50% and verify it's capped
+
+Consider: What combination would exceed 50%? We may need to modify setup or mock GetSeasonalDiscount.
+```
+
+**Expected Result**:
+
+```al
+[Test]
+procedure TestMaximumDiscountCap()
+var
+ Customer: Record Customer;
+ SalesHeader: Record "Sales Header";
+ OrderDiscountMgr: Codeunit "Order Discount Manager";
+ ActualDiscount: Decimal;
+begin
+ // [SCENARIO] Discount is capped at 50% even when combined discounts exceed it
+ Initialize();
+
+ // [GIVEN] VIP customer (10% discount)
+ Customer.Get(LibrarySales.CreateCustomerNo());
+ Customer."Customer Discount Group" := 'VIP';
+ Customer.Modify();
+
+ // [GIVEN] Large order (15% volume discount)
+ SalesHeader := CreateSalesOrderWithAmount(Customer."No.", 10000);
+
+ // [GIVEN] If testing in Nov/Dec, total would be 10+15+5=30% (under cap)
+ // [GIVEN] To test cap, we need a scenario that would exceed 50%
+ // Note: With current business logic, max is 30%, so cap isn't reached
+
+ // [WHEN] Calculating discount
+ ActualDiscount := OrderDiscountMgr.CalculateDiscount(SalesHeader);
+
+ // [THEN] Discount doesn't exceed 50%
+ Assert.IsTrue(ActualDiscount <= 50, 'Discount exceeds maximum allowed 50%');
+end;
+
+[Test]
+procedure TestDiscountCapWithMultipleDiscounts()
+var
+ Customer: Record Customer;
+ SalesHeader: Record "Sales Header";
+ OrderDiscountMgr: Codeunit "Order Discount Manager";
+ ActualDiscount: Decimal;
+begin
+ // [SCENARIO] Combined discounts that would exceed 50% are capped
+ // [NOTE] This test may need the business logic modified to make it relevant
+ // Current max possible: 10% (VIP) + 15% (volume) + 5% (seasonal) = 30%
+
+ Initialize();
+
+ // Create scenario with maximum possible discounts
+ Customer.Get(LibrarySales.CreateCustomerNo());
+ Customer."Customer Discount Group" := 'VIP';
+ Customer.Modify();
+
+ SalesHeader := CreateSalesOrderWithAmount(Customer."No.", 10000);
+
+ // Calculate discount
+ ActualDiscount := OrderDiscountMgr.CalculateDiscount(SalesHeader);
+
+ // Verify cap is applied if needed
+ Assert.IsTrue(ActualDiscount <= 50, 'Discount cap not enforced');
+end;
+```
+
+### Step 7: Test Time-Dependent Logic
+
+**Prompt**:
+
+```
+Create tests for the seasonal discount that depends on the current date.
+
+Since GetSeasonalDiscount uses Today, we need to:
+1. Test behavior for November (month 11)
+2. Test behavior for December (month 12)
+3. Test behavior for other months
+
+Explain how to handle date-dependent tests in AL.
+Options:
+- Make the date a parameter (refactor code)
+- Use test isolation / mocking
+- Create tests that work year-round
+```
+
+**Expected Result**:
+
+```al
+[Test]
+procedure TestSeasonalDiscountInNovember()
+var
+ Customer: Record Customer;
+ SalesHeader: Record "Sales Header";
+ OrderDiscountMgr: Codeunit "Order Discount Manager";
+ ActualDiscount: Decimal;
+ CurrentMonth: Integer;
+begin
+ // [SCENARIO] Seasonal discount is applied in November
+ // [NOTE] This test only passes when run in November
+
+ Initialize();
+
+ CurrentMonth := Date2DMY(Today, 2);
+ if CurrentMonth <> 11 then
+ exit; // Skip test if not November
+
+ // [GIVEN] Standard customer with small order (no other discounts)
+ Customer.Get(LibrarySales.CreateCustomerNo());
+ Customer."Customer Discount Group" := '';
+ Customer.Modify();
+
+ SalesHeader := CreateSalesOrderWithAmount(Customer."No.", 500);
+
+ // [WHEN] Calculating discount in November
+ ActualDiscount := OrderDiscountMgr.CalculateDiscount(SalesHeader);
+
+ // [THEN] 5% seasonal discount is applied
+ Assert.AreEqual(5, ActualDiscount, 'Seasonal discount not applied in November');
+end;
+
+[Test]
+procedure TestNoSeasonalDiscountInJanuary()
+var
+ Customer: Record Customer;
+ SalesHeader: Record "Sales Header";
+ OrderDiscountMgr: Codeunit "Order Discount Manager";
+ ActualDiscount: Decimal;
+ CurrentMonth: Integer;
+begin
+ // [SCENARIO] No seasonal discount in non-holiday months
+
+ Initialize();
+
+ CurrentMonth := Date2DMY(Today, 2);
+ if CurrentMonth in [11, 12] then
+ exit; // Skip test if in seasonal period
+
+ // [GIVEN] Standard customer with small order
+ Customer.Get(LibrarySales.CreateCustomerNo());
+ Customer."Customer Discount Group" := '';
+ Customer.Modify();
+
+ SalesHeader := CreateSalesOrderWithAmount(Customer."No.", 500);
+
+ // [WHEN] Calculating discount outside seasonal period
+ ActualDiscount := OrderDiscountMgr.CalculateDiscount(SalesHeader);
+
+ // [THEN] No discount is applied
+ Assert.AreEqual(0, ActualDiscount, 'Unexpected discount outside seasonal period');
+end;
+
+// [RECOMMENDATION] Refactor GetSeasonalDiscount to accept date parameter
+// This would make testing much easier and more reliable:
+// local procedure GetSeasonalDiscount(CheckDate: Date): Decimal
+```
+
+### Step 8: Integration Test
+
+**Prompt**:
+
+```
+Create an integration test that tests the complete workflow:
+
+1. Create a new customer with VIP status
+2. Create a sales order for that customer
+3. Add multiple lines totaling over 10,000
+4. Calculate the discount
+5. Verify all discount types are correctly combined
+6. Verify the discount is applied to the sales header
+
+This test should verify the codeunit works correctly with real BC data and tables.
+```
+
+**Expected Result**:
+
+```al
+[Test]
+procedure TestCompleteDiscountWorkflow()
+var
+ Customer: Record Customer;
+ SalesHeader: Record "Sales Header";
+ SalesLine: Record "Sales Line";
+ Item: Record Item;
+ OrderDiscountMgr: Codeunit "Order Discount Manager";
+ ExpectedDiscount: Decimal;
+ ActualDiscount: Decimal;
+ CurrentMonth: Integer;
+begin
+ // [SCENARIO] Complete workflow of discount calculation and application
+ Initialize();
+
+ // [GIVEN] A VIP customer
+ Customer.Get(LibrarySales.CreateCustomerNo());
+ Customer."Customer Discount Group" := 'VIP';
+ Customer.Modify();
+
+ // [GIVEN] A sales order with multiple lines totaling 12,000
+ LibrarySales.CreateSalesHeader(SalesHeader, SalesHeader."Document Type"::Order, Customer."No.");
+
+ // Add three items
+ CreateItemAndSalesLine(SalesHeader, 5000);
+ CreateItemAndSalesLine(SalesHeader, 4000);
+ CreateItemAndSalesLine(SalesHeader, 3000);
+
+ // [GIVEN] Expected discount calculation:
+ // - VIP customer: 10%
+ // - Volume (>10000): 15%
+ // - Seasonal (if Nov/Dec): 5%
+ CurrentMonth := Date2DMY(Today, 2);
+ if CurrentMonth in [11, 12] then
+ ExpectedDiscount := 30 // 10 + 15 + 5
+ else
+ ExpectedDiscount := 25; // 10 + 15
+
+ // [WHEN] Calculating the discount
+ ActualDiscount := OrderDiscountMgr.CalculateDiscount(SalesHeader);
+
+ // [THEN] The correct combined discount is calculated
+ Assert.AreEqual(ExpectedDiscount, ActualDiscount,
+ 'Complete discount calculation incorrect');
+
+ // [THEN] Verify order total is correct
+ SalesLine.SetRange("Document Type", SalesHeader."Document Type");
+ SalesLine.SetRange("Document No.", SalesHeader."No.");
+ SalesLine.CalcSums("Line Amount");
+ Assert.AreEqual(12000, SalesLine."Line Amount", 'Order total incorrect');
+end;
+
+local procedure CreateItemAndSalesLine(SalesHeader: Record "Sales Header"; Amount: Decimal)
+var
+ Item: Record Item;
+ SalesLine: Record "Sales Line";
+begin
+ Item."No." := LibraryUtility.GenerateRandomCode(Item.FieldNo("No."), Database::Item);
+ Item."Unit Price" := Amount;
+ Item.Insert();
+
+ LibrarySales.CreateSalesLine(SalesLine, SalesHeader, SalesLine.Type::Item, Item."No.", 1);
+ SalesLine.Validate("Unit Price", Amount);
+ SalesLine.Modify(true);
+end;
+```
+
+## Review Points: What to Check in Tests
+
+### ✅ Test Quality
+
+- [ ] Tests are independent (can run in any order)
+- [ ] Tests are repeatable (same result every time)
+- [ ] Tests have clear Given-When-Then structure
+- [ ] Test names clearly describe what is being tested
+- [ ] Assertions have descriptive error messages
+
+### ✅ Test Coverage
+
+- [ ] Happy path scenarios covered
+- [ ] Error cases tested
+- [ ] Edge cases and boundaries tested
+- [ ] All public procedures have tests
+- [ ] Integration scenarios tested
+
+### ✅ Test Maintainability
+
+- [ ] Helper methods reduce duplication
+- [ ] Test data creation is centralized
+- [ ] Tests are easy to understand
+- [ ] Tests don't depend on specific data
+- [ ] Setup and teardown properly implemented
+
+### ✅ Test Performance
+
+- [ ] Tests run quickly
+- [ ] Minimal database operations
+- [ ] Proper use of test isolation
+- [ ] No unnecessary waits or delays
+
+## Advanced Testing Patterns
+
+### Pattern 1: Test Fixtures
+
+**Prompt**:
+
+```
+Create a test fixture class for sales orders that provides:
+- Standard order (customer with no discounts, small amount)
+- VIP order (VIP customer, medium amount)
+- Large order (standard customer, large amount)
+- Complex order (VIP customer, large amount, multiple lines)
+
+These fixtures should be reusable across all tests.
+```
+
+### Pattern 2: Mock Objects
+
+**Prompt**:
+
+```
+The GetSeasonalDiscount procedure is hard to test because it depends on Today.
+
+Refactor the code to use dependency injection:
+1. Create an interface for date provider
+2. Inject the date provider into the codeunit
+3. Create a mock date provider for testing
+4. Show how to test with different dates
+```
+
+### Pattern 3: Test Data Builders
+
+**Prompt**:
+
+```
+Create a fluent test data builder for sales orders:
+
+SalesOrderBuilder
+ .WithCustomer(CustomerNo)
+ .WithVIPStatus()
+ .WithLine(ItemNo, Quantity, Price)
+ .WithTotalAmount(Amount)
+ .Build()
+
+This makes test data creation more readable and flexible.
+```
+
+## Best Practices for AI-Assisted Testing
+
+### 1. Start with Test Cases, Then Generate
+
+```
+Before generating test code, help me identify all test cases for this procedure:
+- What scenarios should be tested?
+- What are the edge cases?
+- What error conditions exist?
+- What are the boundary conditions?
+
+[Include procedure code]
+```
+
+### 2. Generate Tests in Batches
+
+```
+Generate tests for these three related procedures together so they share test helpers:
+- CalculateDiscount
+- ApplyDiscount
+- ValidateDiscount
+```
+
+### 3. Request Explanatory Comments
+
+```
+Generate the test with detailed comments explaining:
+- Why this test case is important
+- What could go wrong if this test didn't exist
+- Any gotchas or special considerations
+```
+
+### 4. Ask for Test Improvements
+
+```
+Review this test I wrote. Suggest improvements for:
+- Clarity and readability
+- Better assertions
+- Edge cases I might have missed
+- Ways to make it more maintainable
+```
+
+### 5. Generate Test Documentation
+
+```
+Create documentation for this test suite explaining:
+- What is being tested
+- Test coverage summary
+- How to run the tests
+- How to add new tests
+- Known limitations
+```
+
+## Common Testing Challenges
+
+### Challenge 1: Testing Private Methods
+
+**Problem**: Local procedures can't be tested directly
+
+**Solution**:
+
+```
+I need to test this local procedure. Options:
+1. Make it public (if appropriate)
+2. Test it indirectly through public procedures
+3. Extract to a separate testable codeunit
+
+Which approach is best for this scenario? [Include code]
+```
+
+### Challenge 2: Testing Database Operations
+
+**Problem**: Tests that modify database are slow and fragile
+
+**Solution**:
+
+```
+This codeunit performs database operations. Help me:
+1. Identify which operations need real database
+2. Which can be mocked or isolated
+3. Create a testing strategy that balances coverage and speed
+```
+
+### Challenge 3: Testing External Dependencies
+
+**Problem**: Code calls external services or APIs
+
+**Solution**:
+
+```
+This code calls an external API. Create:
+1. An interface for the API
+2. A mock implementation for testing
+3. Tests using the mock
+4. Integration tests for the real API (marked for manual runs)
+```
+
+## Practice Exercise
+
+Write comprehensive tests for this codeunit:
+
+```al
+codeunit 50200 "Credit Limit Checker"
+{
+ procedure CheckCreditLimit(CustomerNo: Code[20]; NewOrderAmount: Decimal): Boolean
+ var
+ Customer: Record Customer;
+ CustLedgerEntry: Record "Cust. Ledger Entry";
+ TotalOutstanding: Decimal;
+ begin
+ if not Customer.Get(CustomerNo) then
+ Error('Customer not found');
+
+ Customer.CalcFields("Balance (LCY)");
+ TotalOutstanding := Customer."Balance (LCY)" + NewOrderAmount;
+
+ if Customer."Credit Limit (LCY)" = 0 then
+ exit(true);
+
+ exit(TotalOutstanding <= Customer."Credit Limit (LCY)");
+ end;
+}
+```
+
+**Your Tasks**:
+
+1. List all test scenarios
+2. Create test codeunit structure
+3. Implement tests for:
+ - Customer not found
+ - No credit limit (unlimited)
+ - Within credit limit
+ - Exactly at credit limit
+ - Over credit limit
+ - Edge cases
+4. Add integration test
+5. Review and improve tests
+
+## Next Steps
+
+- Learn how [code review](../code-review) can verify test quality
+- See how [refactoring](../refactoring) benefits from good tests
+- Explore [documentation](../documentation) for test procedures
diff --git a/content/docs/agentic-coding/GettingStarted/_index.md b/content/docs/agentic-coding/GettingStarted/_index.md
new file mode 100644
index 00000000..2d092a76
--- /dev/null
+++ b/content/docs/agentic-coding/GettingStarted/_index.md
@@ -0,0 +1,20 @@
+---
+title: "Getting Started"
+linkTitle: "Getting Started"
+weight: 10
+description: >
+ Essential concepts and practices for working with AI coding assistants
+---
+
+This section covers the fundamentals you need to start working effectively with AI-powered coding assistants in your AL development workflow.
+
+## In This Section
+
+- **[What is Agentic Coding](what-is-agentic-coding)** - Understanding the core concepts and benefits
+- **[Glossary](glossary)** - Common terms and concepts explained
+- **[Setting Up Your Environment](setup)** - Configure your development environment for AI assistance
+- **[Effective Prompting](effective-prompting)** - Learn how to communicate clearly with AI assistants
+- **[Best Practices](best-practices)** - Guidelines for successful AI-assisted development
+- **[Understanding Limitations](limitations)** - Know when to use (and not use) AI assistance
+
+Start with understanding the concepts, then move through the practical setup and techniques to get the most value from your AI coding assistant.
diff --git a/content/docs/agentic-coding/GettingStarted/best-practices.md b/content/docs/agentic-coding/GettingStarted/best-practices.md
new file mode 100644
index 00000000..28698b30
--- /dev/null
+++ b/content/docs/agentic-coding/GettingStarted/best-practices.md
@@ -0,0 +1,415 @@
+---
+title: "Best Practices"
+linkTitle: "Best Practices"
+weight: 4
+description: >
+ Guidelines for successful AI-assisted AL development
+---
+
+## Overview
+
+AI coding assistants are powerful tools, but they work best when used thoughtfully. This guide provides best practices for integrating AI assistance into your AL development workflow.
+
+## General Principles
+
+### 1. AI Augments, Not Replaces
+**You are still the developer.** The AI is a tool to enhance your productivity, not a replacement for your expertise.
+
+✅ **Good Approach**:
+- Use AI to generate boilerplate code
+- Review and understand all generated code
+- Make architectural decisions yourself
+- Validate business logic
+
+❌ **Poor Approach**:
+- Blindly accept all AI suggestions
+- Skip code review for AI-generated code
+- Let AI make design decisions
+- Assume AI understands your business requirements
+
+### 2. Trust, but Verify
+Always review AI-generated code:
+
+```al
+// AI might generate this:
+procedure CalculateDiscount(Amount: Decimal): Decimal
+begin
+ exit(Amount * 0.1); // Always 10% discount
+end;
+
+// But you need to verify it matches requirements:
+// - Is 10% correct for all scenarios?
+// - Should it vary by customer type?
+// - Are there discount limits?
+// - Should it read from setup?
+```
+
+### 3. Provide Good Context
+Better context = better results:
+
+✅ **Provide**:
+- Clear file and folder names
+- XML documentation comments
+- Descriptive variable names
+- Project README with conventions
+- Open related files
+
+❌ **Avoid**:
+- Generic names like `Temp1`, `DoStuff`
+- Undocumented complex logic
+- Mixing unrelated code in one file
+
+## Code Generation Best Practices
+
+### Start with Structure
+Generate scaffolding first, then refine:
+
+1. **First**: Generate basic structure
+```
+Create a codeunit skeleton for "Sales Order Processor" with procedures for:
+- ValidateOrder
+- CalculateTotals
+- ProcessPayment
+- PostOrder
+```
+
+2. **Then**: Implement each procedure
+```
+Implement the ValidateOrder procedure with these checks:
+- Customer exists
+- All lines have positive quantities
+- Credit limit not exceeded
+```
+
+### Review Generated Code
+Check AI-generated code for:
+
+**Correctness**
+- Does it do what you asked?
+- Are there edge cases not handled?
+- Is the logic sound?
+
+**AL Best Practices**
+- Proper error handling
+- Appropriate use of transactions
+- Correct field validations
+- No unnecessary database calls
+
+**Business Central Standards**
+- Correct use of BC APIs
+- Proper event patterns
+- Standard naming conventions
+- Application area settings
+
+**Performance**
+- Efficient database queries
+- Appropriate filtering
+- Minimal record iterations
+- Proper use of FindSet vs FindFirst
+
+### Iterate and Refine
+Don't expect perfection on first try:
+
+```
+// Initial prompt
+Create a procedure to import customers from CSV
+
+// After reviewing generated code
+Add validation for required fields: Name and Email
+
+// After further review
+Add error logging and return a list of failed imports
+
+// Final refinement
+Add telemetry tracking for import metrics
+```
+
+## Code Review with AI
+
+### Use AI for Initial Review
+AI can catch common issues:
+
+```
+Review this code for:
+- Potential bugs
+- Performance issues
+- AL best practice violations
+- Missing error handling
+```
+
+### Don't Skip Human Review
+AI review is a supplement, not a replacement:
+
+- **AI catches**: Syntax issues, common patterns, style violations
+- **You catch**: Business logic errors, architectural concerns, context-specific issues
+
+### Review AI's Review
+The AI might miss context:
+
+```al
+// AI might flag this as inefficient:
+Customer.SetRange("No.", CustNo);
+if Customer.FindFirst() then
+ Customer.Name := NewName;
+
+// But might miss that in your context, you're in a loop
+// processing thousands of customers, which is inefficient
+```
+
+## Documentation with AI
+
+### Generate Drafts, Then Personalize
+Use AI for documentation drafts:
+
+```
+Generate XML documentation for this codeunit
+```
+
+Then review and enhance:
+- Add business context
+- Include usage examples
+- Document assumptions
+- Note dependencies
+
+### Keep Documentation Updated
+When AI generates code changes:
+
+```
+Update this procedure and its XML documentation to include the new parameter
+```
+
+### Create User-Facing Documentation
+AI can help with user docs too:
+
+```
+Create user documentation explaining how to set up customer discount categories.
+Target audience: Business users, not developers.
+```
+
+## Testing with AI
+
+### Generate Test Scaffolding
+```
+Create a test codeunit structure for testing the Sales Order Processor
+Include test methods for each public procedure
+```
+
+### Create Test Data Setup
+```
+Create a helper procedure that sets up test data:
+- One customer with normal credit limit
+- One customer with exceeded credit
+- Sample items with prices
+- Sales header with lines
+```
+
+### Don't Rely Only on AI Tests
+AI-generated tests might miss:
+- Edge cases specific to your business
+- Integration scenarios
+- Performance testing needs
+- User acceptance criteria
+
+## Refactoring with AI
+
+### Safe Refactoring Steps
+
+1. **Ensure Tests Exist**
+```
+Create tests for this procedure before we refactor it
+```
+
+2. **Refactor with AI**
+```
+Refactor this procedure to extract the discount calculation into a separate function
+```
+
+3. **Verify Tests Still Pass**
+Run your test suite to confirm behavior unchanged
+
+4. **Review Changes**
+Understand what changed and why
+
+### When to Refactor with AI
+✅ **Good for**:
+- Extracting methods
+- Renaming variables
+- Applying consistent formatting
+- Adding error handling
+- Modernizing deprecated APIs
+
+❌ **Be Careful with**:
+- Complex business logic changes
+- Architectural changes
+- Database schema modifications
+- Integration point changes
+
+## Learning from AI
+
+### Use AI as a Learning Tool
+
+**Ask for Explanations**:
+```
+Explain why this code uses Commit instead of direct posting
+```
+
+**Request Alternatives**:
+```
+Show me three different ways to implement this validation,
+with pros and cons of each
+```
+
+**Learn Patterns**:
+```
+Show me the standard AL pattern for implementing a document posting routine
+```
+
+### Build Your Knowledge
+Don't become dependent:
+- Understand the code, don't just use it
+- Learn the patterns being used
+- Research unfamiliar APIs or techniques
+- Practice writing code without AI assistance
+
+## Performance Considerations
+
+### AI and Code Performance
+AI doesn't automatically write optimal code:
+
+```al
+// AI might generate this:
+for i := 1 to Customer.Count do begin
+ Customer.Get(i);
+ ProcessCustomer(Customer);
+end;
+
+// You should refactor to:
+if Customer.FindSet() then
+ repeat
+ ProcessCustomer(Customer);
+ until Customer.Next() = 0;
+```
+
+### Review for Performance
+Always check AI-generated code for:
+- Database query efficiency
+- Unnecessary loops
+- Proper use of filters
+- Appropriate use of temporary tables
+
+## Security Considerations
+
+### Don't Share Sensitive Data
+Be careful what's in your workspace:
+- Production connection strings
+- Customer data
+- API keys or secrets
+- Proprietary algorithms
+
+### Review Security Aspects
+AI might not catch security issues:
+
+```al
+// AI might generate this:
+procedure ExecuteSQL(SQLStatement: Text)
+begin
+ // Direct SQL execution - potential SQL injection!
+end;
+
+// You need to catch security concerns
+```
+
+## Collaboration Best Practices
+
+### Team Standards
+Establish team guidelines:
+- When to use AI assistance
+- Required review process for AI code
+- Documentation requirements
+- Testing standards
+
+### Code Review Process
+For AI-generated code:
+1. Mark commits that include AI-generated code
+2. Extra scrutiny during review
+3. Explain AI usage in PR descriptions
+4. Share learnings with the team
+
+### Knowledge Sharing
+Help your team:
+- Share effective prompts
+- Document successful patterns
+- Discuss AI limitations found
+- Teach AI-assisted techniques
+
+## When NOT to Use AI
+
+### AI is Not Ideal For:
+
+**Critical Security Code**
+- Authentication and authorization
+- Encryption implementations
+- Security-sensitive validations
+
+**Highly Specialized Logic**
+- Unique business rules requiring deep domain knowledge
+- Complex calculations with many edge cases
+- Industry-specific compliance requirements
+
+**Exploration and Learning**
+- When you're trying to learn a new concept
+- When you need to deeply understand the solution
+- When the journey is as important as the destination
+
+**Quick, Simple Tasks**
+- You can type it faster than explaining it
+- It's simpler to do it yourself
+- The prompt would be longer than the code
+
+## Measuring Success
+
+### Track Your Productivity
+Monitor how AI affects your work:
+- Time saved on boilerplate code
+- Reduction in syntax errors
+- Faster documentation creation
+- More time for design and testing
+
+### Quality Metrics
+Ensure quality isn't suffering:
+- Bug rates in AI-assisted code
+- Code review findings
+- Test coverage
+- Performance benchmarks
+
+### Continuous Improvement
+- Refine your prompting skills
+- Learn from unsuccessful attempts
+- Share successes with your team
+- Update your practices as AI tools evolve
+
+## Quick Reference: Do's and Don'ts
+
+### ✅ Do
+- Review all AI-generated code
+- Provide clear, specific prompts
+- Use AI for boilerplate and repetitive tasks
+- Learn from AI-generated examples
+- Test AI-generated code thoroughly
+- Keep documentation updated
+- Share knowledge with your team
+
+### ❌ Don't
+- Blindly accept AI suggestions
+- Skip code review for AI code
+- Include sensitive data in prompts
+- Rely on AI for architectural decisions
+- Use AI-generated code you don't understand
+- Assume AI knows your business requirements
+- Let AI replace your expertise
+
+## Next Steps
+
+- Understand [AI limitations](../limitations) to know when caution is needed
+- Try the [practical examples](../../gettingmore) to apply these best practices
+- Explore [community resources](../../community-resources) for more tips and techniques
diff --git a/content/docs/agentic-coding/GettingStarted/effective-prompting.md b/content/docs/agentic-coding/GettingStarted/effective-prompting.md
new file mode 100644
index 00000000..d91ba1ab
--- /dev/null
+++ b/content/docs/agentic-coding/GettingStarted/effective-prompting.md
@@ -0,0 +1,358 @@
+---
+title: "Effective Prompting"
+linkTitle: "Effective Prompting"
+weight: 3
+description: >
+ Learn how to communicate clearly with AI assistants to get the best results
+---
+
+## Overview
+
+The quality of AI-generated code depends heavily on how you communicate your needs. This guide teaches you how to write effective prompts that lead to better results.
+
+## The Basics of Good Prompts
+
+### Be Specific
+Vague prompts lead to generic results. Provide clear, specific instructions.
+
+❌ **Vague**: "Create a page"
+```
+Create a page
+```
+
+✅ **Specific**: "Create a card page for Customer with fields No, Name, Address, and Phone Number"
+```
+Create a card page for the Customer table that displays these fields:
+- No.
+- Name
+- Address
+- Phone No.
+Include FactBoxes for Sales Statistics and Contact Information.
+```
+
+### Provide Context
+Help the AI understand what you're working on.
+
+❌ **No Context**: "Add a field"
+```
+Add a field to store email
+```
+
+✅ **With Context**: "Add an email field to the Customer table extension for newsletter subscriptions"
+```
+I'm extending the Customer table. Add a new field called "Newsletter Email" to store
+the email address customers want to use for newsletters. This is separate from their
+primary email. Make it a Text field with length 80.
+```
+
+### Include Examples
+Show the AI what you want by providing examples.
+
+✅ **With Example**:
+```
+Create an event subscriber for OnAfterValidate on Sales Header's "Sell-to Customer No."
+field, similar to this pattern:
+
+[EventSubscriber(ObjectType::Table, Database::"Sales Header", 'OnAfterValidateEvent', 'Sell-to Customer No.', false, false)]
+local procedure OnAfterValidateSellToCustomerNo(var Rec: Record "Sales Header")
+begin
+ // Your implementation here
+end;
+
+The subscriber should copy the Newsletter Email from the Customer to the Sales Header.
+```
+
+## Prompting Patterns for AL Development
+
+### 1. Code Generation
+
+**Pattern**: `Create a [object type] that [does what] with [specific requirements]`
+
+**Example**:
+```
+Create a codeunit named "Sales Order Validator" that validates sales orders before posting.
+It should:
+- Check that all lines have quantities > 0
+- Verify customer credit limit is not exceeded
+- Ensure all required fields are filled
+- Return a list of validation errors
+Use AL coding best practices.
+```
+
+### 2. Code Explanation
+
+**Pattern**: `Explain [what] in [level of detail]`
+
+**Examples**:
+```
+// Simple explanation
+Explain what this function does
+
+// Detailed explanation
+Explain this procedure in detail, including the purpose of each parameter
+and the business logic flow
+
+// For learning
+Explain this code as if I'm new to AL development
+```
+
+### 3. Code Improvement
+
+**Pattern**: `Improve this code by [what to improve]`
+
+**Examples**:
+```
+Improve this code to follow AL best practices
+
+Refactor this procedure to be more performant
+
+Add error handling to this code
+
+Make this code more testable by reducing dependencies
+```
+
+### 4. Code Review
+
+**Pattern**: `Review this code for [specific concerns]`
+
+**Examples**:
+```
+Review this code for potential bugs and performance issues
+
+Check this code against AL coding guidelines
+
+Identify security concerns in this procedure
+
+Find opportunities to reduce database calls in this code
+```
+
+### 5. Documentation
+
+**Pattern**: `Generate [documentation type] for [what]`
+
+**Examples**:
+```
+Generate XML documentation comments for all procedures in this file
+
+Create a README explaining what this extension does and how to install it
+
+Write user documentation for this new feature
+```
+
+### 6. Testing
+
+**Pattern**: `Create tests for [what] that [test scenarios]`
+
+**Example**:
+```
+Create test codeunit for the Sales Order Validator that tests:
+- Valid orders pass validation
+- Orders with zero quantities fail
+- Orders exceeding credit limit fail
+- All validation error messages are correct
+Use the AL Test framework with Given-When-Then pattern.
+```
+
+## Advanced Prompting Techniques
+
+### Chain of Thought
+Break complex requests into steps:
+
+```
+I need to create a new feature for automatic discount calculation. Let's approach this step by step:
+
+1. First, create a table extension for Sales Line to store discount category
+2. Then, create a discount setup table with categories and percentages
+3. Next, create a codeunit to calculate discounts based on category
+4. Finally, add an event subscriber to apply discounts automatically
+
+Let's start with step 1...
+```
+
+### Constraints and Requirements
+Be explicit about what you do and don't want:
+
+```
+Create a procedure to import customer data from CSV.
+Requirements:
+- Use streams for large file handling
+- Validate email format before importing
+- Skip duplicate records (based on external ID)
+- Log errors but continue processing
+- Return summary of imported, skipped, and failed records
+Do NOT:
+- Use temporary files
+- Import if any record fails validation
+- Modify existing customer records
+```
+
+### Reference Standards
+Point to specific coding standards or patterns:
+
+```
+Create a page extension following the AL coding standards in this repository.
+Use the same XML documentation pattern as in CustomerProcessor.codeunit.al.
+Follow the naming conventions in our README.md.
+```
+
+### Iterative Refinement
+Start broad, then refine:
+
+```
+// First prompt
+Create a codeunit to process sales orders
+
+// After seeing initial result, refine
+Add error handling using try-catch pattern
+
+// Further refinement
+Add logging using AL telemetry
+
+// Final touch
+Add XML documentation comments
+```
+
+## AL-Specific Prompting Tips
+
+### Specify AL Version
+```
+Create an AL procedure compatible with Business Central version 21
+```
+
+### Mention Dependencies
+```
+Create a page that uses the "Temp Blob" codeunit from the System Application
+```
+
+### Include Object Numbers (if applicable)
+```
+Create table 50100 "Custom Discount Setup" with fields...
+```
+
+### Specify Application Area
+```
+Create a page with ApplicationArea set to #Basic,#Suite
+```
+
+### Reference Standard BC Objects
+```
+Create a table extension for table 18 "Customer" that adds...
+```
+
+## Common Mistakes to Avoid
+
+### ❌ Too Vague
+```
+Make it better
+Fix this
+Create something for customers
+```
+
+### ❌ Asking Multiple Unrelated Things
+```
+Create a customer page, fix the sales order bug, and document the project
+```
+*Better*: Break into separate prompts
+
+### ❌ Assuming Too Much Context
+```
+Add the field we discussed
+```
+*Better*: Restate what you need
+
+### ❌ No Validation Criteria
+```
+Create a validation function
+```
+*Better*: Specify what to validate and how
+
+## Examples of Great Prompts
+
+### Example 1: Table Extension
+```
+Create a table extension for Table 36 "Sales Header" that adds these fields:
+- "Requested Delivery Date" (Date)
+- "Special Instructions" (Text[250])
+- "Requires Approval" (Boolean)
+
+Add triggers:
+- Set "Requires Approval" to true when amount exceeds $10,000
+- Validate "Requested Delivery Date" is not in the past
+
+Include XML documentation for all fields.
+```
+
+### Example 2: API Page
+```
+Create an API page for the Item table that exposes:
+- No.
+- Description
+- Unit Price
+- Inventory
+
+Follow AL API best practices:
+- Use API versioning (v1.0)
+- Include OData annotations
+- Handle GET, POST, PATCH methods
+- Validate required fields on POST
+```
+
+### Example 3: Test Code
+```
+Create a test codeunit for the "Sales Order Validator" codeunit.
+Tests needed:
+1. TestValidOrderPassesValidation - Create valid order, verify no errors
+2. TestZeroQuantityFails - Create order with 0 quantity, verify error
+3. TestCreditLimitExceeded - Create order exceeding limit, verify error
+4. TestMissingRequiredField - Skip required field, verify error
+
+Use:
+- [Test] attribute
+- Given-When-Then pattern
+- LibrarySales for test data
+- Assert for verification
+```
+
+## Practice Exercise
+
+Try improving this vague prompt:
+
+❌ **Vague**:
+```
+Create code for discounts
+```
+
+✅ **Improved Version** (your attempt):
+```
+[Think about: What type of code? What discounts? What should it do?
+What are the requirements? What standards should it follow?]
+```
+
+
+See Suggested Answer
+
+```
+Create a codeunit "Customer Discount Manager" that calculates volume-based discounts.
+
+Requirements:
+- Accept parameters: Customer No., Item No., Quantity
+- Return: Discount percentage (Decimal)
+- Business logic:
+ * 0-10 units: No discount
+ * 11-50 units: 5% discount
+ * 51-100 units: 10% discount
+ * 100+ units: 15% discount
+- Read discount tiers from a setup table
+- Log calculation to telemetry
+- Include error handling for invalid inputs
+- Add XML documentation
+- Follow AL best practices for procedure naming and structure
+```
+
+
+## Next Steps
+
+Now that you know how to write effective prompts:
+- Review the [best practices](../best-practices) for AI-assisted development
+- Try the [practical examples](../../gettingmore) with your new prompting skills
+- Understand the [limitations](../limitations) of AI assistants
diff --git a/content/docs/agentic-coding/GettingStarted/glossary.md b/content/docs/agentic-coding/GettingStarted/glossary.md
new file mode 100644
index 00000000..ebd356af
--- /dev/null
+++ b/content/docs/agentic-coding/GettingStarted/glossary.md
@@ -0,0 +1,213 @@
+---
+title: "Glossary"
+linkTitle: "Glossary"
+weight: 6
+description: >
+ Common terms and concepts in AI-assisted development
+---
+
+## AI & Coding Assistant Terms
+
+### Agent / Agentic AI
+An AI system that can take actions autonomously, make decisions, and use tools to accomplish tasks. In coding, an agentic AI can read files, write code, run commands, and iterate on solutions without constant human intervention.
+
+### AI Assistant / Coding Assistant
+Software that uses artificial intelligence to help you write code. Examples include GitHub Copilot, Claude, ChatGPT, Cursor, and Windsurf.
+
+### Context
+Information the AI has access to when responding to your request. This can include:
+- Your current file and selection
+- Open files in your workspace
+- Previous conversation messages
+- Project structure and files
+- Tools and external data sources
+
+**Why it matters**: The more relevant context the AI has, the better its responses. Limited context can lead to generic or incorrect suggestions.
+
+### Context Window
+The maximum amount of text (measured in tokens) an AI can process at once. Think of it as the AI's "working memory."
+
+**Example**: A 200K token context window can hold roughly 150,000 words of text—about 300 pages.
+
+### Hallucination
+When an AI generates information that sounds plausible but is incorrect or fabricated. This can include:
+- Non-existent AL objects or methods
+- Made-up API endpoints
+- Incorrect syntax or patterns
+
+**How to avoid**: Always verify AI suggestions, especially for critical code or unfamiliar APIs.
+
+### Inference
+The process of an AI model generating a response to your input. Each time you send a prompt and get a response, that's one inference.
+
+### Large Language Model (LLM)
+The AI technology powering coding assistants. LLMs are trained on vast amounts of text (including code) to understand and generate human-like responses.
+
+**Examples**: GPT-4, Claude 3.5 Sonnet, Llama, Gemini
+
+### Model
+The specific AI system you're interacting with. Different models have different capabilities, strengths, and context windows.
+
+**Examples**:
+- Claude 3.5 Sonnet (good at code and reasoning)
+- GPT-4o (fast, multimodal)
+- o1 (optimized for complex reasoning)
+
+---
+
+## Prompting & Communication
+
+### Prompt
+Your input or question to the AI. A prompt can be:
+- A question: "How do I post a sales invoice in AL?"
+- A command: "Add error handling to this function"
+- A request: "Refactor this code to use modern AL patterns"
+
+**Tip**: Clear, specific prompts get better results than vague ones.
+
+### System Prompt / Instructions
+Background instructions that guide the AI's behavior and personality. You typically don't see these, but they tell the AI how to respond (e.g., "You are a Business Central expert," "Be concise," "Provide code examples").
+
+### Few-Shot / One-Shot Prompting
+Providing examples in your prompt to guide the AI's response format.
+
+**Example**:
+```
+Create getter methods like this example:
+procedure GetCustomerName(): Text[100]
+begin
+ exit("Customer Name");
+end
+
+Now create a getter for "Customer Email"
+```
+
+### Chain of Thought
+Asking the AI to explain its reasoning step-by-step before providing an answer. This often improves accuracy for complex problems.
+
+**Example**: "Let's think through how to design this posting routine step by step..."
+
+---
+
+## Technical Terms
+
+### Token
+The basic unit of text that AI models process. Roughly:
+- 1 token ≈ 4 characters in English
+- 1 token ≈ ¾ of a word
+- 100 tokens ≈ 75 words
+
+**Why it matters**: Context windows, pricing, and API limits are measured in tokens.
+
+### Tool / Tool Calling / Function Calling
+External capabilities the AI can use to perform actions beyond text generation:
+- Read and write files
+- Run terminal commands
+- Search the web
+- Query databases
+- Execute MCP server tools
+
+**Example**: When you ask "What's in my app.json?", the AI uses a "read file" tool rather than guessing.
+
+### MCP (Model Context Protocol)
+An open standard for connecting AI assistants to external tools and data sources. MCP servers expose capabilities (like AL symbol databases, Azure DevOps, time tracking) that AI assistants can use.
+
+**Example**: The AL Dependency MCP Server lets your AI assistant search compiled AL packages.
+
+### RAG (Retrieval-Augmented Generation)
+A technique where the AI retrieves relevant information from external sources before generating a response. This helps provide accurate, up-to-date information beyond the AI's training data.
+
+**Example**: BC Code Intelligence MCP uses RAG to fetch specific Business Central knowledge topics.
+
+### Temperature
+A setting that controls how creative or deterministic the AI's responses are:
+- **Low temperature (0.0-0.3)**: Focused, consistent, predictable—good for code generation
+- **High temperature (0.7-1.0)**: Creative, varied, exploratory—good for brainstorming
+
+### Embeddings
+Mathematical representations of text that capture semantic meaning. Used to find relevant information by similarity rather than exact keyword matches.
+
+**Example**: Searching for "customer posting" would find content about "posting customer transactions" even without exact word matches.
+
+---
+
+## AL & Business Central Specific
+
+### AL Language Server
+A background service that provides intelligent code features for AL:
+- Code completion
+- Go to definition
+- Find references
+- Syntax checking
+
+**Note**: Some MCP servers (like Serena) integrate with the AL Language Server to give AI assistants these capabilities.
+
+### Symbol
+In AL, a symbol is any named code element:
+- Objects (tables, pages, codeunits)
+- Fields
+- Procedures
+- Variables
+
+### .app Package
+A compiled AL extension package containing symbols and metadata. AI assistants can't read these directly, which is why tools like AL Dependency MCP Server exist.
+
+### Object ID
+The numeric identifier for AL objects (tables, pages, codeunits, etc.). Managing these IDs across teams requires coordination to avoid conflicts—that's where AL Object ID Ninja MCP helps.
+
+---
+
+## Development Workflow
+
+### Pair Programming
+A development practice where two people work together on the same code. With AI assistants, you're essentially pair programming with an AI partner.
+
+### Code Review
+Examining code to find issues, ensure quality, and share knowledge. AI assistants can help with code review by analyzing patterns, suggesting improvements, and catching common mistakes.
+
+### Refactoring
+Improving code structure and readability without changing its behavior. AI assistants excel at refactoring tasks like renaming, extracting methods, and modernizing patterns.
+
+### Test-Driven Development (TDD)
+Writing tests before writing the code that satisfies them. AI assistants can help generate test cases and implementations.
+
+---
+
+## Common Acronyms
+
+| Term | Meaning |
+|------|---------|
+| **AI** | Artificial Intelligence |
+| **LLM** | Large Language Model |
+| **MCP** | Model Context Protocol |
+| **NLP** | Natural Language Processing |
+| **RAG** | Retrieval-Augmented Generation |
+| **TDD** | Test-Driven Development |
+| **LSP** | Language Server Protocol |
+| **IDE** | Integrated Development Environment |
+| **API** | Application Programming Interface |
+| **CRUD** | Create, Read, Update, Delete |
+| **CLI** | Command Line Interface |
+| **PAT** | Personal Access Token |
+
+---
+
+## Tips for Learning the Language
+
+**Don't worry about knowing everything!** Start with these core concepts:
+- **Prompt**: What you say to the AI
+- **Context**: What information the AI can see
+- **Token**: How AI text is measured
+- **Hallucination**: When AI makes things up
+- **Tool**: Actions the AI can take (like reading files)
+
+As you work with AI assistants, you'll naturally pick up more terminology. The important thing is understanding how to communicate effectively and knowing when to verify AI suggestions.
+
+---
+
+## Related Resources
+
+- **[What is Agentic Coding](../what-is-agentic-coding)** - Core concepts explained
+- **[Effective Prompting](../effective-prompting)** - How to communicate with AI
+- **[Understanding Limitations](../limitations)** - What AI can and can't do
+- **[Tools & MCP Servers](../../communityresources/tools)** - Extending AI capabilities
diff --git a/content/docs/agentic-coding/GettingStarted/limitations.md b/content/docs/agentic-coding/GettingStarted/limitations.md
new file mode 100644
index 00000000..3d78b238
--- /dev/null
+++ b/content/docs/agentic-coding/GettingStarted/limitations.md
@@ -0,0 +1,473 @@
+---
+title: "Understanding Limitations"
+linkTitle: "Limitations"
+weight: 5
+description: >
+ Know when to use (and not use) AI assistance in AL development
+---
+
+## Overview
+
+AI coding assistants are powerful tools, but they have limitations. Understanding these limitations helps you use AI effectively and avoid common pitfalls.
+
+## Knowledge Limitations
+
+### Training Data Cutoff
+AI models are trained on data up to a specific date:
+
+**Implication**:
+- May not know about the latest AL features
+- Might suggest deprecated APIs
+- Could miss recent Business Central updates
+- May not be aware of new best practices
+
+**What to Do**:
+- Verify suggestions against current documentation
+- Check for deprecated features
+- Stay updated on BC releases yourself
+- Supplement AI with official Microsoft docs
+
+### Lack of Real-Time Information
+AI doesn't know:
+- Your specific BC version and configuration
+- Your organization's custom extensions
+- Your specific business requirements
+- Current state of your codebase
+
+**What to Do**:
+- Provide context in your prompts
+- Specify BC version when relevant
+- Describe dependencies and extensions
+- Share organizational standards
+
+### Incomplete AL Knowledge
+AI might not fully understand:
+- Complex AL compiler behavior
+- Subtle differences between AL versions
+- Specific BC platform limitations
+- Performance characteristics of certain operations
+
+**What to Do**:
+- Test generated code thoroughly
+- Verify with official documentation
+- Profile performance-critical code
+- Consult AL experts for complex scenarios
+
+## Code Quality Limitations
+
+### May Generate Suboptimal Code
+
+**Example 1: Inefficient Database Access**
+```al
+// AI might generate:
+procedure CountCustomersInCity(CityName: Text): Integer
+var
+ Customer: Record Customer;
+ Counter: Integer;
+begin
+ Counter := 0;
+ if Customer.FindSet() then
+ repeat
+ if Customer.City = CityName then
+ Counter += 1;
+ until Customer.Next() = 0;
+ exit(Counter);
+end;
+
+// Better approach:
+procedure CountCustomersInCity(CityName: Text): Integer
+var
+ Customer: Record Customer;
+begin
+ Customer.SetRange(City, CityName);
+ exit(Customer.Count);
+end;
+```
+
+**Example 2: Missing Error Handling**
+```al
+// AI might generate:
+procedure GetCustomerEmail(CustomerNo: Code[20]): Text
+var
+ Customer: Record Customer;
+begin
+ Customer.Get(CustomerNo);
+ exit(Customer."E-Mail");
+end;
+
+// Should include error handling:
+procedure GetCustomerEmail(CustomerNo: Code[20]): Text
+var
+ Customer: Record Customer;
+begin
+ if not Customer.Get(CustomerNo) then
+ Error('Customer %1 does not exist.', CustomerNo);
+
+ if Customer."E-Mail" = '' then
+ Error('Customer %1 has no email address.', CustomerNo);
+
+ exit(Customer."E-Mail");
+end;
+```
+
+### May Not Follow Your Standards
+AI doesn't automatically know:
+- Your naming conventions
+- Your code organization preferences
+- Your error handling patterns
+- Your logging standards
+
+**What to Do**:
+- Include standards in prompts
+- Create prompt templates
+- Maintain coding guidelines document
+- Review and adapt generated code
+
+### May Create Inconsistent Code
+AI might:
+- Use different patterns across files
+- Mix coding styles
+- Apply inconsistent naming
+- Vary error handling approaches
+
+**What to Do**:
+- Establish clear patterns early
+- Refactor for consistency
+- Use linters and code analyzers
+- Conduct thorough code reviews
+
+## Business Logic Limitations
+
+### No Domain Knowledge
+AI doesn't understand:
+- Your specific business processes
+- Industry regulations you must follow
+- Your customers' needs
+- Your company's policies
+
+**Example**:
+```
+You ask: "Create discount calculation logic"
+
+AI generates: 10% flat discount
+
+But you need:
+- Tiered discounts by volume
+- Special rates for preferred customers
+- Regional pricing variations
+- Promotional discounts
+- Loyalty program integration
+```
+
+**What to Do**:
+- Provide detailed business requirements
+- Include business rules in prompts
+- Review logic for business correctness
+- Validate with business stakeholders
+
+### Can't Make Business Decisions
+AI shouldn't decide:
+- Which features to implement
+- How to prioritize requirements
+- What trade-offs to make
+- Which approach best fits your needs
+
+**You must decide**:
+- Architecture and design
+- Feature scope
+- Performance vs. complexity trade-offs
+- User experience choices
+
+## Technical Limitations
+
+### Context Window Limitations
+AI can only see:
+- A limited amount of code at once
+- Recently opened files
+- Content you explicitly share
+
+**Implications**:
+- Might miss dependencies in other files
+- May not see full context of large codebases
+- Could suggest code that conflicts with other parts
+
+**What to Do**:
+- Keep related files open
+- Provide context in prompts
+- Reference specific files and procedures
+- Review for integration issues
+
+### Can't Execute or Test Code
+AI can't:
+- Run your code
+- Execute tests
+- Connect to your database
+- Verify actual behavior
+
+**Implications**:
+- Might generate syntactically correct but broken code
+- Can't verify business logic works
+- Won't catch runtime errors
+- Can't validate performance
+
+**What to Do**:
+- Always test generated code
+- Run your test suite
+- Verify in actual BC environment
+- Profile performance-critical code
+
+### Can't Access External Systems
+AI doesn't know about:
+- Your database state
+- External APIs you integrate with
+- Third-party extensions installed
+- Network or security constraints
+
+**What to Do**:
+- Document external dependencies
+- Test integrations thoroughly
+- Verify API compatibility
+- Check security implications
+
+## Safety and Security Limitations
+
+### Limited Security Awareness
+AI might not catch:
+- SQL injection vulnerabilities
+- Authorization bypass issues
+- Data leakage risks
+- Insecure data handling
+
+**Example**:
+```al
+// AI might generate:
+procedure RunDynamicQuery(FilterText: Text)
+begin
+ // Could be SQL injection risk if FilterText comes from user
+ Customer.SetFilter(City, FilterText);
+end;
+
+// Need to add validation:
+procedure RunDynamicQuery(FilterText: Text)
+begin
+ ValidateFilterInput(FilterText); // Add validation
+ Customer.SetFilter(City, FilterText);
+end;
+```
+
+**What to Do**:
+- Security review all generated code
+- Validate inputs from users
+- Follow security best practices
+- Consult security experts
+
+### Privacy Concerns
+Be careful not to share:
+- Customer data
+- Production database content
+- API keys or credentials
+- Proprietary business logic
+
+**What to Do**:
+- Use sample data in prompts
+- Sanitize code before sharing
+- Review organizational policies
+- Use private AI instances if available
+
+## Reliability Limitations
+
+### Inconsistent Results
+AI might:
+- Give different answers to same question
+- Vary quality across generations
+- Make occasional "hallucinations"
+- Provide confident but wrong information
+
+**What to Do**:
+- Verify all suggestions
+- Don't assume correctness
+- Cross-check with documentation
+- Regenerate if quality is poor
+
+### Can Make Mistakes
+AI can:
+- Misunderstand requirements
+- Make logical errors
+- Suggest deprecated features
+- Create subtle bugs
+
+**Real Examples**:
+```al
+// AI might confuse similar concepts:
+// You ask for "customer balance"
+// It generates code for "customer credit limit"
+
+// AI might mix AL versions:
+// Suggest AL syntax not available in your BC version
+
+// AI might misapply patterns:
+// Use patterns from C# instead of AL conventions
+```
+
+**What to Do**:
+- Treat AI as a junior developer
+- Review everything carefully
+- Test thoroughly
+- Validate assumptions
+
+## Workflow Limitations
+
+### Can't Handle Complex Refactoring
+AI struggles with:
+- Large-scale architecture changes
+- Multi-file refactoring
+- Complex dependency updates
+- Breaking changes across modules
+
+**What to Do**:
+- Break into smaller steps
+- Do complex refactoring manually
+- Use AI for individual pieces
+- Plan architecture yourself
+
+### Limited Long-Term Memory
+AI doesn't remember:
+- Previous conversations (in some tools)
+- Decisions made earlier in project
+- Your preferences over time
+- Context from last week
+
+**What to Do**:
+- Restate context when needed
+- Document decisions
+- Include relevant background in prompts
+- Don't assume AI remembers
+
+### Can't Collaborate Directly
+AI can't:
+- Participate in code reviews
+- Attend planning meetings
+- Discuss with stakeholders
+- Make consensus decisions
+
+**What to Do**:
+- Use AI for preparation
+- Review AI suggestions with team
+- Make collaborative decisions yourself
+- Document team agreements
+
+## When to Be Extra Careful
+
+### High-Risk Scenarios
+
+**Financial Calculations**
+```
+Extra vigilance needed for:
+- Payment processing
+- Tax calculations
+- Currency conversions
+- Pricing logic
+```
+
+**Compliance and Audit**
+```
+Careful review for:
+- Regulatory compliance code
+- Audit trail functionality
+- Data retention policies
+- Access control
+```
+
+**Data Integrity**
+```
+Thorough testing for:
+- Database modifications
+- Data migrations
+- Batch processing
+- Transaction handling
+```
+
+**Integration Points**
+```
+Extensive validation for:
+- API integrations
+- Web service calls
+- External system connections
+- Data synchronization
+```
+
+## Recognizing AI Limitations
+
+### Warning Signs
+
+**The AI:**
+- Gives very generic solutions
+- Doesn't ask clarifying questions
+- Suggests deprecated features
+- Provides inconsistent answers
+- Seems overly confident about uncertain things
+- Generates syntactically correct but illogical code
+
+**What to Do:**
+- Seek second opinion
+- Consult documentation
+- Ask a colleague
+- Test more thoroughly
+- Provide more context
+- Try rephrasing prompt
+
+## Complementing AI with Other Resources
+
+### Use Multiple Sources
+
+**For Learning:**
+- Official Microsoft Learn
+- BC documentation
+- Community blogs
+- Training courses
+
+**For Problem Solving:**
+- Microsoft Docs
+- Community forums
+- Stack Overflow
+- Colleague expertise
+
+**For Best Practices:**
+- AL Guidelines (this site!)
+- Microsoft patterns
+- Community standards
+- Team conventions
+
+**For Validation:**
+- Code analyzers
+- Test frameworks
+- Peer review
+- Static analysis tools
+
+## The Bottom Line
+
+### AI is a Tool, Not a Solution
+- Use it to augment your skills
+- Don't rely on it exclusively
+- Maintain your expertise
+- Stay critical and thoughtful
+
+### Your Responsibilities Remain
+- Understand the code
+- Ensure correctness
+- Maintain quality
+- Make decisions
+- Own the results
+
+### Continuous Learning
+- AI tools will improve
+- Your skills must keep pace
+- Learn from AI's mistakes
+- Evolve your practices
+
+## Next Steps
+
+Now that you understand AI limitations:
+- Apply this knowledge in the [practical examples](../../gettingmore)
+- See how to work within these limitations in [best practices](../best-practices)
+- Explore [community resources](../../community-resources) for more insights
diff --git a/content/docs/agentic-coding/GettingStarted/setup.md b/content/docs/agentic-coding/GettingStarted/setup.md
new file mode 100644
index 00000000..cd5b007f
--- /dev/null
+++ b/content/docs/agentic-coding/GettingStarted/setup.md
@@ -0,0 +1,226 @@
+---
+title: "Setting Up Your Environment"
+linkTitle: "Setup"
+weight: 2
+description: >
+ Configure your development environment for optimal AI-assisted AL development
+---
+
+## Overview
+
+To get the most out of AI-powered coding assistance for AL development, you'll need to set up your environment properly. This guide covers the essential tools and configurations.
+
+## Prerequisites
+
+### Required
+- **Visual Studio Code**: The primary IDE for AL development
+- **AL Language Extension**: Microsoft's official AL extension for VS Code
+- **AI Coding Assistant**: One of the following:
+ - GitHub Copilot
+ - GitHub Copilot Chat
+ - Other compatible AI assistants
+
+### Recommended
+- **Git**: For version control and change tracking
+- **AL Test Runner**: For running and managing tests
+- **Business Central Docker Container**: For local development and testing
+
+## Installing GitHub Copilot
+
+GitHub Copilot is one of the most popular AI assistants for coding:
+
+1. **Sign up for GitHub Copilot**
+ - Visit [GitHub Copilot](https://github.com/features/copilot)
+ - Choose a subscription plan (free trial available)
+
+2. **Install the VS Code Extension**
+ - Open VS Code
+ - Go to Extensions (Ctrl+Shift+X)
+ - Search for "GitHub Copilot"
+ - Install both:
+ - GitHub Copilot
+ - GitHub Copilot Chat
+
+3. **Sign In**
+ - Click "Sign in to GitHub" when prompted
+ - Authorize the extension
+
+## Configuring VS Code for AL + AI
+
+### Workspace Settings
+
+Add these settings to your workspace `.vscode/settings.json`:
+
+```json
+{
+ // AL Language settings
+ "al.enableCodeAnalysis": true,
+ "al.codeAnalyzers": ["${CodeCop}", "${PerTenantExtensionCop}", "${UICop}"],
+
+ // GitHub Copilot settings
+ "github.copilot.enable": {
+ "*": true,
+ "al": true
+ },
+
+ // Editor settings for better AI integration
+ "editor.inlineSuggest.enabled": true,
+ "editor.quickSuggestions": {
+ "other": true,
+ "comments": true,
+ "strings": true
+ }
+}
+```
+
+### AL Project Structure
+
+Organize your AL project for better AI context:
+
+```
+MyExtension/
+├── .vscode/
+│ ├── settings.json
+│ └── launch.json
+├── src/
+│ ├── Tables/
+│ ├── Pages/
+│ ├── Codeunits/
+│ ├── Reports/
+│ └── ...
+├── test/
+│ └── ...
+├── app.json
+└── README.md
+```
+
+Clear folder organization helps AI assistants understand your project structure and provide more relevant suggestions.
+
+## Optimizing Context for AI
+
+AI assistants work better when they have good context. Here's how to provide it:
+
+### 1. Use Descriptive File Names
+```
+❌ Page1.al
+✅ CustomerListPage.al
+
+❌ Cod50100.al
+✅ SalesOrderProcessor.codeunit.al
+```
+
+### 2. Maintain a Good README
+Create a `README.md` in your project root with:
+- Project purpose and overview
+- Key features and functionality
+- Naming conventions
+- Architecture decisions
+
+### 3. Use XML Documentation
+Document your procedures and functions:
+```al
+///
+/// Calculates the total amount for a sales order including tax
+///
+/// The sales header record
+/// The total amount including tax
+procedure CalculateTotalWithTax(var SalesHeader: Record "Sales Header"): Decimal
+```
+
+### 4. Keep Related Code Together
+Place related functionality in the same files or nearby files. AI assistants can see open files and nearby code.
+
+## Testing Your Setup
+
+To verify everything is working:
+
+1. **Open an AL file** in your project
+2. **Start typing** a procedure declaration
+3. **Check for suggestions** - You should see inline suggestions appear
+4. **Open Copilot Chat** (if using GitHub Copilot)
+ - Press Ctrl+Shift+I (or Cmd+Shift+I on Mac)
+ - Try asking: "Explain this AL code"
+
+## Recommended Extensions
+
+Install these VS Code extensions to complement your AI assistant:
+
+- **AL Language**: Microsoft's official AL extension (required)
+- **AL Object Designer**: Navigate AL objects easily
+- **AL Code Outline**: View code structure
+- **AL Test Runner**: Run and manage AL tests
+- **AL Variable Helper**: Manage variable declarations
+- **GitLens**: Enhanced git integration
+
+## Workspace Best Practices
+
+### Open Relevant Files
+- Keep related files open in tabs
+- AI assistants can use open files for context
+
+### Use Multi-Root Workspaces (When Appropriate)
+If you have dependencies or multiple related projects:
+```json
+{
+ "folders": [
+ { "path": "./MyMainExtension" },
+ { "path": "./MyDependencyExtension" }
+ ]
+}
+```
+
+### Organize by Feature
+Consider organizing code by business feature rather than object type for complex projects:
+```
+src/
+├── SalesOrderProcessing/
+│ ├── SalesOrder.table.al
+│ ├── SalesOrderPage.page.al
+│ ├── SalesOrderProcessor.codeunit.al
+├── CustomerManagement/
+│ └── ...
+```
+
+## Security and Privacy Considerations
+
+### What Gets Sent to AI Services
+- Code snippets from your workspace
+- Currently open files
+- Your prompts and questions
+
+### What You Should NOT Include
+- Sensitive credentials or passwords
+- Customer data
+- Proprietary business logic (if restricted)
+
+### Best Practices
+- Review your organization's AI usage policy
+- Use `.gitignore` and `.copilotignore` files appropriately
+- Be mindful of what code is in your workspace
+- Consider using GitHub Copilot for Business for enterprise controls
+
+## Troubleshooting
+
+### AI Suggestions Not Appearing
+- Verify the AI extension is installed and enabled
+- Check you're signed in to your AI service
+- Ensure `editor.inlineSuggest.enabled` is true
+- Restart VS Code
+
+### Poor Quality Suggestions
+- Improve code context (better file names, comments)
+- Open related files for more context
+- Use more descriptive variable and function names
+- Add XML documentation comments
+
+### Performance Issues
+- Close unnecessary tabs/files
+- Disable AI for specific file types if needed
+- Check your system resources
+
+## Next Steps
+
+Now that your environment is set up:
+- Learn [effective prompting techniques](../effective-prompting)
+- Review [best practices](../best-practices) for AI-assisted development
+- Try the [practical examples](../../gettingmore) to see AI assistance in action
diff --git a/content/docs/agentic-coding/GettingStarted/what-is-agentic-coding.md b/content/docs/agentic-coding/GettingStarted/what-is-agentic-coding.md
new file mode 100644
index 00000000..aecf4e19
--- /dev/null
+++ b/content/docs/agentic-coding/GettingStarted/what-is-agentic-coding.md
@@ -0,0 +1,128 @@
+---
+title: "What is Agentic Coding?"
+linkTitle: "What is Agentic Coding"
+weight: 1
+description: >
+ Understanding AI-powered coding assistance and how it transforms development
+---
+
+## Overview
+
+**Agentic coding** is a development approach where you work collaboratively with AI-powered assistants (agents) that can understand context, generate code, provide suggestions, and help maintain your codebase. Unlike simple code completion tools, these agents can:
+
+- Understand natural language instructions
+- Analyze existing code and context
+- Generate complete implementations
+- Refactor and improve code
+- Explain complex code segments
+- Assist with debugging and problem-solving
+
+## How It Works
+
+AI coding assistants work by:
+
+1. **Understanding Context**: The agent analyzes your workspace, open files, and the surrounding code to understand what you're working on
+2. **Processing Instructions**: You provide instructions in natural language (or through inline comments)
+3. **Generating Solutions**: The agent creates code, documentation, or suggestions based on your needs
+4. **Iterative Refinement**: You review, provide feedback, and the agent adjusts the output
+
+## Key Capabilities for AL Development
+
+### Code Generation
+Generate AL code from natural language descriptions:
+- Complete procedures and functions
+- Table extensions and page extensions
+- API pages and queries
+- Event subscribers
+- Test code
+
+### Code Understanding
+Get help understanding existing code:
+- Explanations of complex logic
+- Documentation of dependencies
+- Impact analysis of changes
+
+### Code Improvement
+Enhance existing code:
+- Refactoring for better performance
+- Applying AL best practices
+- Modernizing legacy code
+- Adding error handling
+
+### Documentation
+Automatically create and maintain:
+- XML documentation comments
+- README files
+- API documentation
+- Code comments
+
+## Benefits for AL Developers
+
+### Faster Development
+- Quickly scaffold new objects and extensions
+- Implement common patterns without repetitive typing
+- Generate boilerplate code instantly
+
+### Higher Quality
+- Consistent application of best practices
+- Fewer common mistakes
+- Better code organization
+
+### Learning Accelerator
+- Learn AL patterns through examples
+- Understand Business Central APIs
+- Discover best practices in context
+
+### Reduced Cognitive Load
+- Focus on business logic, not syntax
+- Less context switching for documentation lookups
+- Automated handling of repetitive tasks
+
+## The Human-AI Partnership
+
+It's important to understand that agentic coding is a **collaborative** approach:
+
+### You Bring:
+- **Domain Knowledge**: Understanding of business requirements and Business Central functionality
+- **Decision Making**: Architectural choices and business logic decisions
+- **Quality Control**: Review and validation of generated code
+- **Context**: Specific requirements, constraints, and organizational standards
+
+### The AI Brings:
+- **Speed**: Rapid code generation and transformation
+- **Consistency**: Adherence to patterns and best practices
+- **Breadth**: Knowledge of many AL patterns and APIs
+- **Assistance**: Help with routine tasks and documentation
+
+## Common Use Cases
+
+### Daily Development
+- Creating new tables, pages, and codeunits
+- Implementing event subscribers
+- Writing test code
+- Adding XML documentation
+
+### Code Maintenance
+- Refactoring existing code
+- Adding telemetry to extensions
+- Improving error handling
+- Updating deprecated APIs
+
+### Code Review
+- Identifying potential issues
+- Suggesting improvements
+- Checking adherence to standards
+- Finding security concerns
+
+### Documentation
+- Generating README files
+- Creating API documentation
+- Writing user guides
+- Documenting complex algorithms
+
+## Next Steps
+
+Now that you understand what agentic coding is, learn how to:
+- [Set up your environment](../setup) for AI assistance
+- [Write effective prompts](../effective-prompting) to get better results
+- Follow [best practices](../best-practices) for AI-assisted development
diff --git a/content/docs/agentic-coding/_index.md b/content/docs/agentic-coding/_index.md
new file mode 100644
index 00000000..44002af2
--- /dev/null
+++ b/content/docs/agentic-coding/_index.md
@@ -0,0 +1,65 @@
+---
+title: "Agentic Coding"
+linkTitle: "Agentic Coding"
+weight: 50
+description: >
+ Learn how to effectively leverage AI-powered coding assistants for AL development in Business Central
+---
+
+{{% pageinfo %}}
+This section provides guidance on working with AI-powered coding assistants (agents) to enhance your AL development workflow for Microsoft Dynamics 365 Business Central.
+{{% /pageinfo %}}
+
+## What is Agentic Coding?
+
+Agentic coding refers to the collaborative approach of working with AI-powered assistants that can understand context, generate code, review implementations, and help maintain codebases. These AI agents act as intelligent partners in your development process, offering suggestions, automating repetitive tasks, and helping you follow best practices.
+
+## Why Use Agentic Assistance for AL Development?
+
+AI coding assistants can significantly enhance your AL development workflow by:
+
+- **Accelerating Development**: Generate boilerplate code, implement common patterns, and scaffold new features quickly
+- **Improving Code Quality**: Get real-time suggestions for code improvements and adherence to AL best practices
+- **Knowledge Augmentation**: Access contextual help about AL syntax, Business Central APIs, and development patterns
+- **Documentation**: Automatically generate and maintain code documentation
+- **Code Review**: Get automated reviews highlighting potential issues, performance concerns, and style violations
+- **Learning Tool**: Learn AL best practices and patterns through interactive assistance
+
+## What You'll Find Here
+
+This hub is organized into three main sections:
+
+### Getting Started
+Learn the fundamentals of working with AI coding assistants:
+- Understanding agentic coding concepts
+- Setting up your environment
+- Effective prompting techniques
+- Best practices for collaboration with AI
+
+### Getting More
+Practical examples and advanced techniques:
+- Conducting AI-assisted code reviews
+- Generating and maintaining documentation
+- Adding telemetry to your extensions
+- Refactoring legacy code
+- Testing strategies
+
+### Vibe Coding Rules
+Comprehensive AI-specific coding guidelines and instructions:
+- AL code style and formatting rules
+- Error handling patterns
+- Event-driven architecture guidelines
+- Performance optimization techniques
+- Testing and upgrade code best practices
+- Naming conventions and standards
+
+### Community Resources
+Curated resources from the AL and Business Central community:
+- Articles and blog posts
+- Video tutorials
+- Tools and extensions
+- Community discussions
+
+## Getting Help
+
+As you explore agentic coding, remember that AI assistants are tools to augment your capabilities, not replace your expertise. Always review generated code, understand what it does, and ensure it meets your specific requirements and follows your organization's standards.
diff --git a/content/docs/vibe-coding/README.md b/content/docs/agentic-coding/vibe-coding-rules/README.md
similarity index 100%
rename from content/docs/vibe-coding/README.md
rename to content/docs/agentic-coding/vibe-coding-rules/README.md
diff --git a/content/docs/vibe-coding/_index.md b/content/docs/agentic-coding/vibe-coding-rules/_index.md
similarity index 93%
rename from content/docs/vibe-coding/_index.md
rename to content/docs/agentic-coding/vibe-coding-rules/_index.md
index b002939d..4e4060e4 100644
--- a/content/docs/vibe-coding/_index.md
+++ b/content/docs/agentic-coding/vibe-coding-rules/_index.md
@@ -1,5 +1,6 @@
---
-title: "Vibe Coding for AL"
+title: "Vibe Coding Rules for AL"
+weight: 90
tags: ["AL", "Vibe Coding"]
categories: ["Vibe Coding"]
description: >
@@ -8,9 +9,9 @@ description: >
_Created by the Business Central Community, Enhanced for AI-powered AL Development_
-# Vibe Coding for AL
+# Vibe Coding Rules for AL
-Welcome to the **Vibe Coding for AL** initiative! This section contains AI-optimized coding rules and guidelines specifically designed to enhance the AL developer experience in modern AI-powered IDEs like VS Code and Cursor.
+Welcome to the **Vibe Coding Rules for AL** initiative! This section contains AI-optimized coding rules and guidelines specifically designed to enhance the AL developer experience in modern AI-powered IDEs like VS Code and Cursor.
## What is Vibe Coding?
diff --git a/content/docs/vibe-coding/al-code-style.md b/content/docs/agentic-coding/vibe-coding-rules/al-code-style.md
similarity index 100%
rename from content/docs/vibe-coding/al-code-style.md
rename to content/docs/agentic-coding/vibe-coding-rules/al-code-style.md
diff --git a/content/docs/vibe-coding/al-error-handling.md b/content/docs/agentic-coding/vibe-coding-rules/al-error-handling.md
similarity index 100%
rename from content/docs/vibe-coding/al-error-handling.md
rename to content/docs/agentic-coding/vibe-coding-rules/al-error-handling.md
diff --git a/content/docs/vibe-coding/al-events.md b/content/docs/agentic-coding/vibe-coding-rules/al-events.md
similarity index 100%
rename from content/docs/vibe-coding/al-events.md
rename to content/docs/agentic-coding/vibe-coding-rules/al-events.md
diff --git a/content/docs/vibe-coding/al-guidelines-rules.md b/content/docs/agentic-coding/vibe-coding-rules/al-guidelines-rules.md
similarity index 100%
rename from content/docs/vibe-coding/al-guidelines-rules.md
rename to content/docs/agentic-coding/vibe-coding-rules/al-guidelines-rules.md
diff --git a/content/docs/vibe-coding/al-naming-conventions.md b/content/docs/agentic-coding/vibe-coding-rules/al-naming-conventions.md
similarity index 100%
rename from content/docs/vibe-coding/al-naming-conventions.md
rename to content/docs/agentic-coding/vibe-coding-rules/al-naming-conventions.md
diff --git a/content/docs/vibe-coding/al-performance.md b/content/docs/agentic-coding/vibe-coding-rules/al-performance.md
similarity index 100%
rename from content/docs/vibe-coding/al-performance.md
rename to content/docs/agentic-coding/vibe-coding-rules/al-performance.md
diff --git a/content/docs/vibe-coding/al-testing.md b/content/docs/agentic-coding/vibe-coding-rules/al-testing.md
similarity index 100%
rename from content/docs/vibe-coding/al-testing.md
rename to content/docs/agentic-coding/vibe-coding-rules/al-testing.md
diff --git a/content/docs/vibe-coding/al-upgrade.md b/content/docs/agentic-coding/vibe-coding-rules/al-upgrade.md
similarity index 100%
rename from content/docs/vibe-coding/al-upgrade.md
rename to content/docs/agentic-coding/vibe-coding-rules/al-upgrade.md
diff --git a/content/docs/patterns/no-series/index.md b/content/docs/patterns/no-series/index.md
index a28c48ec..538a7eb9 100644
--- a/content/docs/patterns/no-series/index.md
+++ b/content/docs/patterns/no-series/index.md
@@ -10,6 +10,68 @@ _Created by Microsoft, Described by Jeremy Vyska (Spare Brained Ideas)_
The "Number Series" system is used extensively to provide numbers to master records, documents, and other transactions through Microsoft Dynamics 365 Business Central.
+## Important: BC v24+ Modern Pattern (Updated 2024)
+
+**As of Business Central version 24.0 and later**, Microsoft deprecated the `NoSeriesManagement` codeunit in favor of the new `codeunit "No. Series"` with simplified methods.
+
+### Modern Implementation (BC v24+)
+
+**Variable declaration:**
+```al
+var
+ NoSeries: Codeunit "No. Series";
+```
+
+**OnInsert pattern (simplified):**
+```al
+trigger OnInsert()
+begin
+ if "No." = '' then begin
+ MySetup.Get();
+ MySetup.TestField("Document Nos.");
+ "No. Series" := MySetup."Document Nos.";
+ if NoSeries.AreRelated(MySetup."Document Nos.", xRec."No. Series") then
+ "No. Series" := xRec."No. Series";
+ "No." := NoSeries.GetNextNo("No. Series");
+ end;
+end;
+```
+
+**OnValidate pattern (same as before):**
+```al
+trigger OnValidate()
+begin
+ if "No." <> xRec."No." then begin
+ MySetup.Get();
+ NoSeries.TestManual(MySetup."Document Nos.");
+ "No. Series" := '';
+ end;
+end;
+```
+
+### Key Differences from Legacy Pattern
+
+| Legacy (NoSeriesManagement) | Modern (No. Series) |
+|----------------------------|---------------------|
+| `NoSeriesMgt.InitSeries(...)` - 5 parameters | `NoSeries.GetNextNo(...)` - 1-2 parameters |
+| `NoSeriesMgt.TestManual(...)` | `NoSeries.TestManual(...)` - Same method name |
+| `NoSeriesMgt.TryGetNextNo(...)` | `NoSeries.PeekNextNo(...)` - New name |
+| `NoSeriesMgt.SelectSeries(...)` | `NoSeries.AreRelated(...)` - Simplified API |
+| Complex parameter passing | Simplified, intuitive API |
+
+### Migration Strategy
+
+For **backward compatibility** (supporting both BC v23 and v24+):
+1. Use conditional compilation with `#if` directives based on platform version
+2. Check runtime platform version and branch logic accordingly
+3. Implement both patterns in separate procedures with version detection
+
+{{% alert title="Note" color="warning" %}}
+**The examples below reflect the LEGACY pattern** (NoSeriesManagement codeunit) for reference and historical context. For new development on BC v24+, use the modern `codeunit "No. Series"` pattern shown above.
+{{% /alert %}}
+
+---
+
## Description
At the heart of things, the Number Series engine allows users to define structure for a sequential numeric or alphanumeric string (collectively referred to as a 'number series'), then assign that structure to different parts of the system.
@@ -283,4 +345,4 @@ For usage of number series, there is more information available on:
- [Microsoft Docs: Create Number Series](https://docs.microsoft.com/en-us/dynamics365/business-central/ui-create-number-series)
- [Microsoft Learn: Set up number series and trail codes](https://docs.microsoft.com/en-us/learn/modules/number-series-trail-codes-dynamics-365-business-central/)
-For more programming details, there is more information on [Microsoft Docs: Number Sequences in Business Central](https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-number-sequences).
\ No newline at end of file
+For more programming details, there is more information on [Microsoft Docs: Number Sequences in Business Central](https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-number-sequences).
diff --git a/go.mod b/go.mod
index c8b8727f..318448e4 100644
--- a/go.mod
+++ b/go.mod
@@ -2,4 +2,4 @@ module github.com/microsoft/alguidelines
go 1.23.0
-require github.com/google/docsy v0.10.0 // indirect
+require github.com/google/docsy v0.12.0 // indirect
diff --git a/go.sum b/go.sum
index 78bc9349..963e3a5b 100644
--- a/go.sum
+++ b/go.sum
@@ -1,4 +1,8 @@
github.com/FortAwesome/Font-Awesome v0.0.0-20240402185447-c0f460dca7f7/go.mod h1:IUgezN/MFpCDIlFezw3L8j83oeiIuYoj28Miwr/KUYo=
+github.com/FortAwesome/Font-Awesome v0.0.0-20241216213156-af620534bfc3/go.mod h1:IUgezN/MFpCDIlFezw3L8j83oeiIuYoj28Miwr/KUYo=
github.com/google/docsy v0.10.0 h1:6tMDacPwAyRWNCfvsn/9qGOZDQ8b0aRzjRZvnZPY5dg=
github.com/google/docsy v0.10.0/go.mod h1:c0nIAqmRTOuJ01F85U/wJPQtc3Zj9N58Kea9bOT2AJc=
+github.com/google/docsy v0.12.0 h1:CddZKL39YyJzawr8GTVaakvcUTCJRAAYdz7W0qfZ2P4=
+github.com/google/docsy v0.12.0/go.mod h1:1bioDqA493neyFesaTvQ9reV0V2vYy+xUAnlnz7+miM=
github.com/twbs/bootstrap v5.3.3+incompatible/go.mod h1:fZTSrkpSf0/HkL0IIJzvVspTt1r9zuf7XlZau8kpcY0=
+github.com/twbs/bootstrap v5.3.6+incompatible/go.mod h1:fZTSrkpSf0/HkL0IIJzvVspTt1r9zuf7XlZau8kpcY0=
diff --git a/static/files/CAL-Coding-Guidelines-at-Microsoft-Development-Center-Copenhagen.pdf b/static/files/CAL-Coding-Guidelines-at-Microsoft-Development-Center-Copenhagen.pdf
new file mode 100644
index 00000000..59ff8266
Binary files /dev/null and b/static/files/CAL-Coding-Guidelines-at-Microsoft-Development-Center-Copenhagen.pdf differ