bc-agentic-dev-tools

Allocate the next available Business Central AL object ID/number by scanning .al files and idRanges in app.json using the bundled PowerShell script. Use when creating new tables/pages/codeunits/extensions and you need a free object number.

AL test development patterns with telemetry verification. MANDATORY when: (1) planning test implementation, (2) creating new tests, (3) modifying existing tests. Invoke proactively at ALL three stages. PLANNING: Structure plans with Red-Green-Refactor phases and use TodoWrite to track progress through each phase. CRITICAL RULE: DEBUG-* telemetry must be ZERO at both task START and END.

Local mirror of Microsoft AL Guidelines (alguidelines.dev) for searching agentic coding rules, vibe-coding standards, AL best practices, and community resources. Use when: (1) Writing or reviewing AL code and need naming conventions, code style, or formatting rules, (2) Implementing event subscribers, error handling, or performance patterns, (3) Setting up AI-assisted development with Claude/Copilot/Cursor agent configurations, (4) Looking for MCP server integrations (AL-ObjID, BC-Code-Intel, NAB), (5) Understanding classic NAV/BC patterns like Document, Journal, Hooks, or Master Data. Content includes: vibe-coding-rules/ (7 AL-specific rule files), BestPractices/ (~27 topics), patterns/ (facade, template-method, event-bridge), NAVPatterns/ (~50+ classic patterns), and CommunityResources/ (agent configs, MCP tools).