Locate canonical Business Central Standard behavior (BaseApp, System Application, APIV2, etc.) to identify events, event publishers, codeunits, tables/fields, tests, pages, codeunits, APIs, etc.. Use when you need standard behavior, event signatures, or reference implementation patterns.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bc-standard-reference:bc-standard-referenceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the canonical mirror of the Business Central Standard repo `fbakkensen/bc-w1` to locate events, APIs, tables, fields, tests, and implementation patterns. The focus is on *what* to find and *how to reason about it*, not on any specific tools.
Use the canonical mirror of the Business Central Standard repo fbakkensen/bc-w1 to locate events, APIs, tables, fields, tests, and implementation patterns. The focus is on what to find and how to reason about it, not on any specific tools.
Identify the relevant codeunits, tables, pages, and events for the behavior you need. Use any symbol discovery method available to you (dependency metadata, symbols, reference notes, or docs).
Search the repo fbakkensen/bc-w1 using object/event names and narrow by domain paths (e.g., Sales/Posting, Pricing, Inventory). Your goal is to find the exact file that defines the object or publishes the event.
Open the candidate file and confirm:
Use official documentation to confirm AL syntax, BC concepts, and best practices that contextualize what you saw in source.
For open-ended questions, delegate to a subagent with a focused brief:
Search the standard mirror `fbakkensen/bc-w1` for [topic]. Identify candidate files, inspect implementations, and report back with relevant events, patterns, and example locations.
For detailed examples and repository structure:
npx claudepluginhub fbakkensen/bc-agentic-dev-tools-marketplace --plugin bc-standard-referenceGuides SAP API documentation per SAP API Style Guide standards for REST, OData, Java, JavaScript, .NET, C/C++ APIs, covering naming, OpenAPI specs, comments, checklists, deprecation.
Generates RAP determination, validation, and custom action implementations by reading the RAP stack and filling empty method stubs in the behavior pool. Use when asked to implement RAP logic or generate custom action code.
Guides BAdI (Business Add-In) development and ABAP enhancement framework usage, including creating enhancement spots, BAdI definitions, fallback classes, filter-based BAdIs, and key user extensibility.