bc-code-intelligence-mcp 1.5.5 β†’ 1.5.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (23) hide show
  1. package/README.md +153 -407
  2. package/dist/index.d.ts.map +1 -1
  3. package/dist/index.js +72 -43
  4. package/dist/index.js.map +1 -1
  5. package/dist/sdk/bc-code-intel-client.d.ts.map +1 -1
  6. package/dist/sdk/bc-code-intel-client.js +1 -1
  7. package/dist/sdk/bc-code-intel-client.js.map +1 -1
  8. package/dist/types/bc-knowledge.d.ts +4 -4
  9. package/embedded-knowledge/domains/alex-architect/samples/testability-design-patterns.md +223 -0
  10. package/embedded-knowledge/domains/alex-architect/testability-design-patterns.md +77 -0
  11. package/embedded-knowledge/domains/casey-copilot/long-running-session-instructions.md +263 -0
  12. package/embedded-knowledge/domains/casey-copilot/samples/long-running-session-instructions.md +323 -0
  13. package/embedded-knowledge/domains/eva-errors/codeunit-run-pattern.md +159 -0
  14. package/embedded-knowledge/domains/eva-errors/samples/codeunit-run-pattern.md +239 -0
  15. package/embedded-knowledge/domains/eva-errors/samples/try-function-usage.md +195 -0
  16. package/embedded-knowledge/domains/eva-errors/try-function-usage.md +129 -0
  17. package/embedded-knowledge/domains/morgan-market/partner-readiness-analysis.md +201 -0
  18. package/embedded-knowledge/domains/morgan-market/samples/partner-readiness-checklist.md +288 -0
  19. package/embedded-knowledge/domains/quinn-tester/isolation-testing-patterns.md +82 -0
  20. package/embedded-knowledge/domains/quinn-tester/samples/isolation-testing-patterns.md +424 -0
  21. package/embedded-knowledge/domains/roger-reviewer/samples/testability-code-smells.md +256 -0
  22. package/embedded-knowledge/domains/roger-reviewer/testability-code-smells.md +67 -0
  23. package/package.json +2 -2
package/README.md CHANGED
@@ -1,419 +1,165 @@
1
1
  # BC Code Intelligence MCP Server
2
2
 
3
- [![NPM Version](https://img.shields.io/npm/v/bc-code-intelligence-mcp)](https://www.npmjs.com/package/bc-code-intelligence-mcp)
4
3
  [![Install with NPX in VS Code](https://img.shields.io/badge/Install%20with%20NPX-VS%20Code-blue?style=for-the-badge&logo=visual-studio-code)](https://vscode.dev/redirect/mcp/install?name=bc-code-intel&config=%7B%22type%22%3A%22stdio%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22bc-code-intelligence-mcp%22%5D%7D)
5
4
  [![Installation Guide](https://img.shields.io/badge/Installation%20Guide-All%20Platforms-green?style=for-the-badge&logo=github)](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide)
6
5
 
7
- **Transform your Business Central development** with intelligent specialist consultation, seamless handoffs, smart discovery, and context-preserving workflows.
6
+ **Get instant help from AI Business Central experts** right in your favorite AI tool. No more searching docs - just ask and get expert guidance tailored to your specific BC development challenges.
8
7
 
9
8
  ---
10
9
 
11
- ## πŸ“š Quick Links
10
+ ## πŸš€ Quick Start
12
11
 
13
- - **[Company Layer Setup Guide](./examples/company-layer-setup.md)** - Add your company's BC standards
14
- - **[Installation Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide)** - Install in Claude, Copilot, or any MCP client
15
- - **[Configuration Examples](./bc-code-intel-config.example.yaml)** - All configuration options
16
- - **[Specialist Bundle](#-specialist-bundle-experience)** - Meet the 14 BC experts
12
+ 1. **Click the blue "Install with NPX" button above** (VS Code users)
13
+ 2. **Switch to Agent Mode** in VS Code's Copilot Chat
14
+ 3. **Just ask!** - Start with any prompt below
15
+
16
+ > **Other platforms?** See the [Installation Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide) for Claude Desktop, Cursor, and more.
17
17
 
18
18
  ---
19
19
 
20
- ## ✨ Enhanced Developer Workflows
21
-
22
- ### 🎯 Core Features
23
- - **πŸ€– Smart Specialist Discovery**: Intelligent routing to 14 BC domain experts based on query analysis
24
- - **πŸ”„ Seamless Handoffs**: Context-preserving transitions between specialists with full conversation history
25
- - **πŸš€ Agent-Friendly Onboarding**: Natural specialist team introduction optimized for coding agents
26
- - **πŸ’¬ Persistent Sessions**: Long-running conversations with accumulated context and recommendations
27
- - **🧠 Multi-Specialist Collaboration**: Bring multiple experts into the same conversation for complex challenges
28
-
29
- ### πŸ› οΈ Development Infrastructure
30
- - **πŸ“‹ 20+ MCP Tools**: Complete toolkit for knowledge discovery, specialist engagement, and workflow management
31
- - **πŸ”„ 9 Workflow Orchestration**: Persona-driven development pipelines with structured guidance
32
- - **🎯 MCP Prompts**: Discoverable workflow initiation through standardized prompts
33
- - **οΏ½ Layered Knowledge**: Embedded β†’ Company β†’ Team β†’ Project override system
34
- - **βš™οΈ Zero Configuration**: Works immediately with embedded knowledge
35
- - **πŸ”§ Extensible Architecture**: Support for git repositories, company standards, and project overrides
36
-
37
- ## οΏ½ BC Specialist Team (14 Experts)
38
-
39
- **Core Development Specialists:**
40
- - **πŸ—οΈ Alex Architect** - Solution Design & Requirements Expert
41
- - **πŸ’» Sam Coder** - Expert Development Accelerator
42
- - **πŸ” Dean Debug** - Performance & Troubleshooting Specialist
43
- - **⚠️ Eva Errors** - Error Handling & Exception Management
44
-
45
- **Quality & Security Specialists:**
46
- - **πŸ§ͺ Quinn Tester** - Testing Strategy & Validation Expert
47
- - **πŸ“ Roger Reviewer** - Code Quality & Standards Guardian
48
- - **πŸ”’ Seth Security** - Security & Permission Management
49
-
50
- **Integration & Architecture Specialists:**
51
- - **πŸŒ‰ Jordan Bridge** - Integration & Extensibility Architect
52
- - **πŸ›οΈ Logan Legacy** - Code Archaeology & System Analysis
53
-
54
- **User Experience & Business Specialists:**
55
- - **🎨 Uma UX** - User Experience & Interface Design
56
- - **πŸͺ Morgan Market** - AppSource & ISV Business Expert
57
-
58
- **Knowledge & Learning Specialists:**
59
- - **πŸ“š Taylor Docs** - Documentation & Knowledge Management
60
- - **πŸ‘©β€πŸ« Maya Mentor** - Teaching-Focused Development Guide
61
- - **πŸ€– Casey Copilot** - AI-Enhanced Development Coach
62
-
63
- ## πŸ€– Specialist Bundle Experience
64
-
65
- Experience collaborative BC development with intelligent specialist routing and seamless handoffs:
66
-
67
- ### Quick Start - Agent Integration
68
- ```javascript
69
- // 1. Discover the specialist team (agents do this automatically)
70
- const team = await mcp.call('introduce_bc_specialists', {
71
- context: 'Business Central development',
72
- focus_areas: ['performance', 'security', 'architecture']
73
- });
74
-
75
- // 2. Smart routing based on your challenge
76
- const suggestions = await mcp.call('discover_specialists', {
77
- query: 'My AL extension has performance issues with database queries'
78
- });
79
-
80
- // 3. Engage with the recommended specialist
81
- const session = await mcp.call('suggest_specialist', {
82
- specialist_id: 'dean-debug',
83
- user_query: 'Performance optimization needed',
84
- context: 'Business Central extension development'
85
- });
86
-
87
- // 4. Seamless handoffs when different expertise is needed
88
- await mcp.call('handoff_to_specialist', {
89
- target_specialist_id: 'alex-architect',
90
- handoff_type: 'transfer',
91
- handoff_reason: 'Need architectural review after performance fixes',
92
- work_completed: ['Optimized queries', 'Added caching'],
93
- continuation_points: ['Review overall architecture', 'Design scalability']
94
- });
95
- ```
96
-
97
- ### Specialist Bundle Tools
98
-
99
- **🎯 When to Use Each Tool Type:**
100
-
101
- **For Direct Conversations & Questions:**
102
- - `ask_bc_expert` - **USE FOR**: "Talk to Sam", "Ask Dean about debugging", "I took over this BC app"
103
- - βœ… **Direct questions get immediate specialist responses** (no methodology setup required)
104
- - βœ… **Broader requests** get structured methodology onboarding for systematic guidance
105
- - `suggest_specialist` - Start/continue specialist conversations
106
- - `get_specialist_advice` - Get expert guidance on specific topics
107
- - βœ… **Smart name matching**: "Sam" automatically finds "sam-coder", "Dean" finds "dean-debug"
108
-
109
- **For Structured Development Processes:**
110
- - `start_bc_workflow` - **USE FOR**: "Optimize my code systematically", "Conduct architecture review", "Security audit"
111
-
112
- **Discovery & Routing:**
113
- - `discover_specialists` - Intelligent specialist suggestions based on query analysis
114
- - `browse_specialists` - Browse by domain or expertise area
115
- - `get_specialist_info` - Detailed information about any specialist
116
- - `list_specialists` - See all available specialists
117
-
118
- **Onboarding & Navigation:**
119
- - `introduce_bc_specialists` - Agent-friendly team introduction
120
- - `get_specialist_introduction` - Individual specialist details
121
- - `suggest_next_specialist` - Intelligent next-step recommendations
122
-
123
- **Handoffs & Collaboration:**
124
- - `handoff_to_specialist` - Context-preserving specialist transitions (auto-creates sessions)
125
- - `bring_in_specialist` - Multi-specialist consultation
126
- - `get_handoff_summary` - Session history and analytics
127
-
128
- ## πŸš€ Workflow Orchestration
129
-
130
- Transform your BC development process with structured, persona-driven workflows:
131
-
132
- ### Available Workflows
133
- - **`workflow_code_optimization`** - Systematic code optimization with performance analysis
134
- - **`workflow_architecture_review`** - Comprehensive solution architecture evaluation
135
- - **`workflow_security_audit`** - Security analysis and compliance verification
136
- - **`workflow_performance_analysis`** - Performance bottleneck identification and resolution
137
- - **`workflow_integration_design`** - Robust integration pattern development
138
- - **`workflow_upgrade_planning`** - BC version upgrade with risk assessment
139
- - **`workflow_testing_strategy`** - Comprehensive testing approach development
140
- - **`workflow_new_developer_onboarding`** - Structured developer guidance and training
141
- - **`workflow_pure_review`** - Analysis-only workflow without implementation changes
142
-
143
- ### How It Works
144
- 1. **Discover Workflows**: Use MCP Prompts to see available workflows in your client
145
- 2. **Start Pipeline**: Initiate with project context and requirements
146
- 3. **Guided Phases**: Progress through specialist-led phases with targeted guidance
147
- 4. **Track Progress**: Monitor advancement and validate methodology compliance
148
- 5. **Constitutional Gates**: Ensure BC best practices and extensibility principles
149
-
150
- ### Example Usage
151
- ```typescript
152
- // In any MCP-compatible client (Claude, VS Code, etc.)
153
- // Prompts appear automatically for discovery
154
-
155
- // Start a workflow
156
- workflow_code_optimization({
157
- code_location: "src/MyCustomization.al",
158
- bc_version: "23.1"
159
- })
160
-
161
- // Advance through phases
162
- advance_workflow({
163
- workflow_id: "workflow-123",
164
- phase_results: "Completed performance analysis..."
165
- })
166
-
167
- // Check status
168
- get_workflow_status({ workflow_id: "workflow-123" })
169
- ```
170
-
171
- ## πŸ› οΈ MCP Tools Reference
172
-
173
- ### Knowledge Discovery
174
- - **`find_bc_topics`** - Search BC knowledge by specialist persona or expertise
175
- - **`consult_bc_specialist`** - Get specialist consultation and guidance
176
- - **`get_specialist_roster`** - List available specialists and their expertise
177
- - **`get_topic_content`** - Retrieve detailed topic information
178
-
179
- ### Workflow Management
180
- - **`advance_workflow`** - Progress workflow to next phase with results
181
- - **`get_workflow_status`** - Check current workflow progress and state
182
- - **`get_workflow_guidance`** - Get detailed phase-specific guidance
183
-
184
- ### Code Analysis
185
- - **`analyze_code_patterns`** - Analyze AL code for patterns and improvements
186
- - **`get_optimization_workflow`** - Get tailored optimization recommendations
187
-
188
- ### Methodology Support
189
- - **`load_methodology`** - Load structured development methodologies
190
- - **`get_phase_guidance`** - Get methodology phase-specific instructions
191
- - **`validate_completeness`** - Validate methodology phase completion
192
-
193
- ### System Management
194
- - **`get_layer_info`** - Information about configured knowledge layers
195
- - **`resolve_topic_layers`** - See layer resolution for specific topics
196
- - **`search_layered_topics`** - Search across all configured layers
197
- - **`get_configuration_status`** - System configuration and health status
198
- - **`reload_configuration`** - Reload configuration without restart
199
- - **`get_system_analytics`** - Usage analytics and performance metrics
200
-
201
- ## 🏒 Company Layer Setup
202
-
203
- Add your company's BC knowledge and standards to the MCP server using the **Company Layer** feature.
204
-
205
- > **πŸ“– Complete guide:** See [Company Layer Setup Guide](./examples/company-layer-setup.md) for detailed step-by-step instructions.
206
-
207
- ### Quick Setup (3 Steps)
208
-
209
- **1. Create your configuration directory:**
210
- ```powershell
211
- # Windows (PowerShell)
212
- mkdir $env:USERPROFILE\.bc-code-intel
213
-
214
- # macOS/Linux (Bash)
215
- mkdir ~/.bc-code-intel
216
- ```
217
-
218
- **2. Create your configuration file:**
219
-
220
- Create `~/.bc-code-intel/config.yaml` (Windows: `%USERPROFILE%\.bc-code-intel\config.yaml`)
221
-
222
- **3. Add your company layer:**
223
-
224
- ```yaml
225
- layers:
226
- # Embedded layer (required) - base BC knowledge
227
- - name: embedded
228
- priority: 0
229
- source:
230
- type: embedded
231
- path: ./embedded-knowledge
232
- enabled: true
233
-
234
- # Company layer - YOUR COMPANY STANDARDS
235
- - name: company
236
- priority: 20
237
- source:
238
- type: git
239
- url: "https://github.com/yourcompany/bc-knowledge" # Your Git repo URL
240
- branch: main # Your branch name
241
- subpath: "" # Optional: subdirectory path
242
- auth:
243
- type: token # or: az_cli, ssh_key, basic
244
- token_env_var: GITHUB_TOKEN # Environment variable with token
245
- enabled: true
246
-
247
- # Project layer (optional) - local workspace overrides
248
- - name: project
249
- priority: 100
250
- source:
251
- type: local
252
- path: ./bc-code-intel-overrides
253
- enabled: true
254
- ```
255
-
256
- ### Repository Structure
257
-
258
- Your company Git repository should contain:
259
-
260
- ```
261
- your-bc-knowledge-repo/
262
- β”œβ”€β”€ domains/ # OR topics/ (both supported!)
263
- β”‚ β”œβ”€β”€ naming-conventions.md
264
- β”‚ β”œβ”€β”€ error-handling.md
265
- β”‚ └── company-patterns.md
266
- β”œβ”€β”€ specialists/ # Optional: company-specific specialists
267
- β”‚ └── company-expert.md
268
- └── methodologies/ # Optional: company workflows
269
- └── company-review.md
270
- ```
271
-
272
- **Note:** Both `domains/` and `topics/` directory names are supported!
273
-
274
- ### Authentication Methods
275
-
276
- <details>
277
- <summary><b>GitHub (Personal Access Token)</b></summary>
278
-
279
- ```yaml
280
- auth:
281
- type: token
282
- token_env_var: GITHUB_TOKEN # Set: export GITHUB_TOKEN="ghp_yourtoken"
283
- ```
284
-
285
- Create token at: https://github.com/settings/tokens (needs `repo` scope)
286
- </details>
287
-
288
- <details>
289
- <summary><b>Azure DevOps (Azure CLI)</b></summary>
290
-
291
- ```yaml
292
- auth:
293
- type: az_cli # Uses Azure CLI authentication
294
- ```
295
-
296
- Prerequisites:
297
- ```powershell
298
- az login # Login once, credentials are cached
299
- ```
300
- </details>
301
-
302
- <details>
303
- <summary><b>GitLab (Personal Access Token)</b></summary>
304
-
305
- ```yaml
306
- auth:
307
- type: token
308
- token_env_var: GITLAB_TOKEN # Set: export GITLAB_TOKEN="glpat-yourtoken"
309
- ```
310
- </details>
311
-
312
- <details>
313
- <summary><b>SSH Key</b></summary>
314
-
315
- ```yaml
316
- auth:
317
- type: ssh_key
318
- ssh_key_path: "~/.ssh/id_rsa"
319
- ```
320
- </details>
321
-
322
- ### Configuration Discovery
323
-
324
- The MCP server automatically searches for configuration in this order:
325
-
326
- 1. **User-level** (recommended): `~/.bc-code-intel/config.yaml`
327
- 2. **Project-level**: `./bc-code-intel-config.yaml` (workspace root)
328
- 3. **Environment variable**: `BC_CODE_INTEL_CONFIG_PATH`
329
-
330
- **Important:** User-level configuration (including company layers) is **automatically loaded at startup**. No need to call `set_workspace_info` or configure per-workspace - your company standards are available globally across all projects!
331
-
332
- ### Priority System
333
-
334
- Lower numbers = higher priority. Company layers (priority 20) override embedded knowledge (priority 0):
335
-
336
- - **Priority 0**: Embedded base knowledge (always loaded)
337
- - **Priority 20**: Company standards (overrides embedded)
338
- - **Priority 100**: Project-specific (overrides everything)
339
-
340
- When topics have the same ID, the **higher priority layer wins**.
341
-
342
- ### Example Configurations
343
-
344
- **πŸ“– Full Setup Guide:** See [**Company Layer Setup Guide**](./examples/company-layer-setup.md) for complete step-by-step instructions.
345
-
346
- **Full Example:**
347
- See [`bc-code-intel-config.example.yaml`](./bc-code-intel-config.example.yaml) for all configuration options.
348
-
349
- **Minimal Company Setup:**
350
- ```yaml
351
- layers:
352
- - name: embedded
353
- priority: 0
354
- source:
355
- type: embedded
356
- enabled: true
357
-
358
- - name: company
359
- priority: 20
360
- source:
361
- type: git
362
- url: "https://dev.azure.com/YourOrg/YourProject/_git/BCGuidelines"
363
- branch: master
364
- subpath: "bc-company-guidelines" # Optional subdirectory
365
- auth:
366
- type: az_cli
367
- enabled: true
368
- ```
369
-
370
- ### Verification
371
-
372
- Test your configuration:
373
- ```bash
374
- # From the MCP server directory
375
- npx tsx -e "
376
- import { ConfigurationLoader } from './src/config/config-loader.js';
377
- const config = await ConfigurationLoader.loadConfiguration();
378
- console.log('βœ… Config loaded:', config.layers.map(l => l.name));
379
- "
380
- ```
381
-
382
- ### Troubleshooting
383
-
384
- **Config not loading?**
385
- - Check file location: `~/.bc-code-intel/config.yaml`
386
- - Verify YAML syntax (use a YAML validator)
387
- - Check file permissions
388
-
389
- **Git authentication failing?**
390
- - Token: Verify environment variable is set: `echo $GITHUB_TOKEN`
391
- - Azure CLI: Run `az login` and verify with `az account show`
392
- - SSH: Ensure key is added to ssh-agent: `ssh-add ~/.ssh/id_rsa`
393
-
394
- **No topics loading from company layer?**
395
- - Verify repository structure has `domains/` or `topics/` directory
396
- - Check branch name matches config
397
- - If using `subpath`, verify the path exists in your repo
398
-
399
- For more examples, see the [`examples/`](./examples/) directory.
400
-
401
- ## Quick Start
402
- ```bash
403
- npm install
404
- npm run build
405
- npm start
406
- ```
407
-
408
- ## Architecture
409
- - **πŸ”„ Workflow Orchestration**: Persona-driven pipeline management with session state
410
- - **πŸ“Š Layer Resolution**: Multi-source knowledge with intelligent override system
411
- - **πŸ“‹ Methodology Integration**: Structured development workflows with validation
412
- - **🎯 MCP Prompts**: Client-agnostic workflow discovery and initiation
413
- - **πŸ” Version Awareness**: BC version compatibility filtering throughout
414
- - **πŸ‘₯ Specialist System**: AI persona management with domain expertise
415
- - **⚑ Constitutional Gates**: BC development best practices enforcement
416
- - **πŸ—οΈ Pure TypeScript**: Clean separation from knowledge content
417
-
418
- ## Knowledge Source
419
- Knowledge content is linked via git submodule from [bc-code-intelligence](../bc-code-intelligence).
20
+ ## 🀝 New to AI-Assisted Development? Start with Parker
21
+
22
+ If you're not sure how to work with AI tools, or you're skeptical about letting AI touch your codeβ€”**that's exactly why Parker exists**.
23
+
24
+ Parker is a grizzled veteran who helps you work WITH AI safely:
25
+ - Creates **reviewable proposals** instead of making direct changes
26
+ - **Explains AI reasoning** so you understand what's happening and why
27
+ - **Coordinates other specialists** to validate suggestions before you commit
28
+ - Builds trust **gradually** through transparency and verification
29
+
30
+ **Just say:**
31
+ - "Parker, I'm new to AI development tools. Help me understand how this works."
32
+ - "Parker, I don't trust AI to write my code. What's a safe way to start?"
33
+ - "Parker, review what the AI just suggested before I accept it."
34
+
35
+ Once you're comfortable, you can work directly with any specialistβ€”but Parker's always there when you want that extra layer of verification and explanation.
36
+
37
+ ---
38
+
39
+ ## πŸ’¬ Just Ask - Example Prompts
40
+
41
+ The BC Code Intelligence specialists are ready to help. Just type naturally - here are some examples:
42
+
43
+ ### πŸ” Debugging & Performance (Dean)
44
+ - "Dean, help me debug this error: 'The record in table Customer already exists'"
45
+ - "I'm seeing slow performance when posting sales orders. Can Dean take a look?"
46
+ - "Ask Dean why my FlowField is always showing zero"
47
+
48
+ ### πŸ›οΈ Legacy Code & Upgrades (Logan)
49
+ - "Logan, I need to upgrade my extension from BC v24 to v27"
50
+ - "I inherited this old extension - can Logan help me understand what it does?"
51
+ - "Help me modernize this C/AL-style code to proper AL patterns"
52
+
53
+ ### πŸ—οΈ Architecture & Design (Alex)
54
+ - "Alex, review my extension's architecture before I submit to AppSource"
55
+ - "I need to design an integration with an external warehouse system"
56
+ - "What's the best way to structure a multi-company solution?"
57
+
58
+ ### πŸ’» Coding & Implementation (Sam)
59
+ - "Sam, help me write a function to calculate weighted average cost"
60
+ - "I need to create a FactBox that shows related sales history"
61
+ - "Show me the best way to implement a posting routine"
62
+
63
+ ### πŸ§ͺ Testing & Quality (Quinn)
64
+ - "Quinn, help me create test coverage for my posting codeunit"
65
+ - "What test scenarios should I include for this validation?"
66
+ - "Review my test codeunit for completeness"
67
+
68
+ ### πŸ“ Code Review (Roger)
69
+ - "Roger, review this codeunit for best practices"
70
+ - "Check if my code follows BC naming conventions"
71
+ - "Are there any code smells in my Customer Card extension?"
72
+
73
+ ### πŸ”’ Security (Seth)
74
+ - "Seth, review my permission sets for security issues"
75
+ - "How should I handle user permissions for this sensitive data?"
76
+ - "Check if my API is exposing too much information"
77
+
78
+ ### πŸŒ‰ Integration & Events (Jordan)
79
+ - "Jordan, help me design an event-driven integration"
80
+ - "What's the best way to subscribe to posting events?"
81
+ - "How do I create a clean API for external systems?"
82
+
83
+ ### ⚠️ Error Handling (Eva)
84
+ - "Eva, help me implement proper error handling for this process"
85
+ - "What's the best way to validate user input before posting?"
86
+ - "Review my Try/Catch implementation"
87
+
88
+ ### 🎨 User Experience (Uma)
89
+ - "Uma, help me improve my page layout for better usability"
90
+ - "Can we switch from simple Error calls in this app to ErrorInfo with suggested actions?"
91
+ - "Review my action menu structure"
92
+
93
+ ### πŸͺ AppSource & ISV (Morgan)
94
+ - "Morgan, help me prepare my app for AppSource submission"
95
+ - "What are the common AppSource validation failures?"
96
+ - "Review my app's technical baseline for AppSource"
97
+
98
+ ### πŸ‘©β€πŸ« Learning & Mentoring (Maya)
99
+ - "Maya, explain how dimensions work in BC"
100
+ - "I'm new to AL - help me understand events and subscribers"
101
+ - "Walk me through how posting routines work"
102
+
103
+ ### πŸ“š Documentation (Taylor)
104
+ - "Taylor, help me document this complex codeunit"
105
+ - "Generate XML documentation for my public procedures"
106
+ - "Review my app's README for completeness"
107
+
108
+ ### πŸ€– AI-Assisted Development (Casey)
109
+ - "Casey, help me use AI tools effectively in my BC development"
110
+ - "Based on this current project, what are some good instructions to help future agents understand working with this app immediately?"
111
+
112
+ ---
113
+
114
+ ## πŸ‘₯ Meet Your BC Specialist Team
115
+
116
+ | Specialist | Expertise | Best For |
117
+ |------------|-----------|----------|
118
+ | **🀝 Parker** | AI Trust & Transparency | New to AI tools, safe collaboration, verification-first |
119
+ | **πŸ—οΈ Alex** | Architecture & Design | Solution design, extension structure, integration patterns |
120
+ | **πŸ’» Sam** | Expert Coder | Writing AL code, implementation patterns, coding questions |
121
+ | **πŸ” Dean** | Debugging & Performance | Errors, slow queries, troubleshooting |
122
+ | **⚠️ Eva** | Error Handling | Validation, Try/Catch, error messages |
123
+ | **πŸ§ͺ Quinn** | Testing | Test codeunits, test scenarios, code coverage |
124
+ | **πŸ“ Roger** | Code Review | Best practices, naming conventions, code quality |
125
+ | **πŸ”’ Seth** | Security | Permissions, data protection, API security |
126
+ | **πŸŒ‰ Jordan** | Integration | APIs, events, external connections |
127
+ | **πŸ›οΈ Logan** | Legacy & Upgrades | Version migrations, old code, modernization |
128
+ | **🎨 Uma** | User Experience | Page design, usability, UI patterns |
129
+ | **πŸͺ Morgan** | AppSource & ISV | Publishing, validation, business concerns |
130
+ | **πŸ‘©β€πŸ« Maya** | Mentoring | Learning concepts, explanations, training |
131
+ | **πŸ“š Taylor** | Documentation | Code docs, READMEs, knowledge sharing |
132
+ | **πŸ€– Casey** | AI Development | Using AI tools, prompt engineering |
133
+ | **βš™οΈ Chris** | MCP Configuiration | Company/Project MCP knowledge layer help|
134
+
135
+ ---
136
+
137
+ ## πŸ“š Learn More
138
+
139
+ | Topic | Link |
140
+ |-------|------|
141
+ | **Full Installation Options** | [Installation Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide) |
142
+ | **Common Scenarios** | [Usage Patterns](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Common-Scenarios) |
143
+ | **All MCP Tools** | [Tools Reference](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/MCP-Tools-Reference) |
144
+ | **Company Standards** | [Enterprise Configuration](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Enterprise-Configuration) |
145
+ | **Structured Workflows** | [Methodology Framework](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Methodology-Framework) |
146
+ | **Troubleshooting** | [Common Issues](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Troubleshooting) |
147
+
148
+ ---
149
+
150
+ ## πŸ’‘ Tips
151
+
152
+ - **Just use first names** - "Ask Dean" works just as well as "Ask Dean Debug"
153
+ - **Be specific** - Include error messages, code snippets, or version numbers when relevant
154
+ - **Specialists collaborate** - They'll hand off to each other when needed
155
+ - **Context carries over** - Continue conversations naturally
156
+
157
+ ---
158
+
159
+ ## 🀝 Contributing
160
+
161
+ See the [Contributing Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Contributing-Guide) for how to contribute to this project.
162
+
163
+ ## πŸ“„ License
164
+
165
+ MIT License - see [LICENSE](LICENSE) for details.
@@ -1 +1 @@
1
- {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AAoDA;;;;;;GAMG;AACH,cAAM,wBAAwB;IAC5B,OAAO,CAAC,MAAM,CAAS;IACvB,OAAO,CAAC,gBAAgB,CAAoB;IAC5C,OAAO,CAAC,mBAAmB,CAAuB;IAClD,OAAO,CAAC,kBAAkB,CAAsB;IAChD,OAAO,CAAC,eAAe,CAAmB;IAC1C,OAAO,CAAC,YAAY,CAA4B;IAChD,OAAO,CAAC,wBAAwB,CAA4B;IAC5D,OAAO,CAAC,eAAe,CAAmB;IAC1C,OAAO,CAAC,0BAA0B,CAA8B;IAChE,OAAO,CAAC,wBAAwB,CAA4B;IAC5D,OAAO,CAAC,qBAAqB,CAAyB;IACtD,OAAO,CAAC,oBAAoB,CAAwB;IACpD,OAAO,CAAC,sBAAsB,CAA0B;IACxD,OAAO,CAAC,qBAAqB,CAAyB;IACtD,OAAO,CAAC,aAAa,CAA4B;IACjD,OAAO,CAAC,YAAY,CAAsB;IAC1C,OAAO,CAAC,aAAa,CAAuB;IAC5C,OAAO,CAAC,aAAa,CAAgB;IACrC,OAAO,CAAC,uBAAuB,CAAS;IACxC,OAAO,CAAC,cAAc,CAAkB;IACxC,OAAO,CAAC,mBAAmB,CAAS;IAEpC,OAAO,CAAC,iBAAiB;;IAwDzB,OAAO,CAAC,iBAAiB;IAwHzB;;OAEG;IACH,OAAO,CAAC,YAAY;IAiTpB;;OAEG;YACW,kBAAkB;IAyKhC;;OAEG;YACW,qBAAqB;IAuCnC;;OAEG;YACW,uBAAuB;IA8BrC;;OAEG;YACW,sBAAsB;IA8CpC;;OAEG;IACH,OAAO,CAAC,iCAAiC;IAqCzC;;OAEG;YACW,6BAA6B;YA2D7B,4BAA4B;IAwGpC,GAAG,IAAI,OAAO,CAAC,IAAI,CAAC;IA8D1B;;OAEG;YACW,sBAAsB;IAoEpC;;OAEG;YACW,2BAA2B;IAmBzC;;OAEG;YACW,gBAAgB;IAkF9B;;OAEG;YACW,uBAAuB;CAWtC;AA+ED,OAAO,EAAE,wBAAwB,EAAE,CAAC"}
1
+ {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AAoDA;;;;;;GAMG;AACH,cAAM,wBAAwB;IAC5B,OAAO,CAAC,MAAM,CAAS;IACvB,OAAO,CAAC,gBAAgB,CAAoB;IAC5C,OAAO,CAAC,mBAAmB,CAAuB;IAClD,OAAO,CAAC,kBAAkB,CAAsB;IAChD,OAAO,CAAC,eAAe,CAAmB;IAC1C,OAAO,CAAC,YAAY,CAA4B;IAChD,OAAO,CAAC,wBAAwB,CAA4B;IAC5D,OAAO,CAAC,eAAe,CAAmB;IAC1C,OAAO,CAAC,0BAA0B,CAA8B;IAChE,OAAO,CAAC,wBAAwB,CAA4B;IAC5D,OAAO,CAAC,qBAAqB,CAAyB;IACtD,OAAO,CAAC,oBAAoB,CAAwB;IACpD,OAAO,CAAC,sBAAsB,CAA0B;IACxD,OAAO,CAAC,qBAAqB,CAAyB;IACtD,OAAO,CAAC,aAAa,CAA4B;IACjD,OAAO,CAAC,YAAY,CAAsB;IAC1C,OAAO,CAAC,aAAa,CAAuB;IAC5C,OAAO,CAAC,aAAa,CAAgB;IACrC,OAAO,CAAC,uBAAuB,CAAS;IACxC,OAAO,CAAC,cAAc,CAAkB;IACxC,OAAO,CAAC,mBAAmB,CAAS;IAEpC,OAAO,CAAC,iBAAiB;;IA8DzB,OAAO,CAAC,iBAAiB;IAwHzB;;OAEG;IACH,OAAO,CAAC,YAAY;IAiTpB;;OAEG;YACW,kBAAkB;IA0LhC;;OAEG;YACW,qBAAqB;IAuCnC;;OAEG;YACW,uBAAuB;IA8BrC;;OAEG;YACW,sBAAsB;IA8CpC;;OAEG;IACH,OAAO,CAAC,iCAAiC;IAqCzC;;OAEG;YACW,6BAA6B;YA2D7B,4BAA4B;IAwGpC,GAAG,IAAI,OAAO,CAAC,IAAI,CAAC;IAuE1B;;OAEG;YACW,sBAAsB;IAoEpC;;OAEG;YACW,2BAA2B;IAmBzC;;OAEG;YACW,gBAAgB;IAkF9B;;OAEG;YACW,uBAAuB;CAWtC;AA+ED,OAAO,EAAE,wBAAwB,EAAE,CAAC"}