Prompt file imported from javiarmesto/SampleDynamicsMinds (.github/prompts/al-initialize.prompt.md). Fill in {{ProjectName}}, {{CodeCop}}, {{PerTenantExtensionCop}}, {{UICop}}, {{EnvironmentName}} before use. Copyright stays with the author.

AL Environment Initialization

Name: al-initialize
Author: javiarmesto

Your goal is to initialize the AL development environment and workspace for {{ProjectName}}.

This workflow covers both initial environment setup (VS Code, GitHub Copilot) and AL workspace configuration (project structure, symbols, dependencies).

Phase 1: Environment Setup

Prerequisites Check

Verify the following are available:

Required Tools:

Visual Studio Code (latest version)
AL Language Extension (Microsoft's official extension)
GitHub Copilot or compatible AI assistant
Git for version control

Recommended Tools:

AL Test Runner for test management
Business Central Docker Container for local development
AL Object Designer for navigation
GitLens for enhanced git integration

GitHub Copilot Installation

Step 1: Install VS Code Extensions

Open Visual Studio Code
Access Extensions marketplace (Ctrl+Shift+X or Cmd+Shift+X)
Install:
- GitHub Copilot - Code completion
- GitHub Copilot Chat - Interactive assistance
- AL Language - Business Central development

Step 2: Authentication

Sign in to GitHub when prompted
Authorize the extension
Verify connection is active

VS Code Workspace Configuration

Create or update .vscode/settings.json in the workspace root:

{
  // 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
  }
}

Configuration Benefits:

Code analysis with CodeCop, PerTenantExtensionCop, and UICop
AI suggestions optimized for AL files
Enhanced inline completion

Phase 2: Project Initialization

Choose Project Type

For New Projects:

al_new_project

For Existing Folders:

al_go

Project Structure

Implement feature-based organization:

{{ProjectName}}/
├── .vscode/
│   ├── settings.json          # Workspace settings
│   └── launch.json            # Debug configurations
├── src/
│   ├── Tables/                # Table objects
│   ├── Pages/                 # Page objects
│   ├── Codeunits/             # Codeunit objects
│   ├── Reports/               # Report objects
│   ├── Queries/               # Query objects
│   ├── XMLports/              # XMLport objects
│   ├── PageExtensions/        # Page extensions
│   ├── TableExtensions/       # Table extensions
│   └── Enums/                 # Enum objects
├── test/
│   ├── TestCodeunits/         # Test codeunits
│   └── TestData/              # Test data and helpers
├── app.json                   # Application manifest
├── .gitignore                 # Git ignore rules
└── README.md                  # Project documentation

Download Symbols

Download required symbols:

al_download_symbols

Verify all base application dependencies are available.

Generate Manifest

Create manifest file:

al_generate_manifest

Human Review: Validate manifest contents before proceeding.

Phase 3: Launch Configuration

🔒 Human Gate: Authentication Configuration Review

SECURITY CHECKPOINT - Configuration contains sensitive information

Before creating launch.json:

Review authentication method with stakeholder
Confirm server URLs are correct for target environment
Verify credentials handling follows security policies
Obtain approval before saving configuration

Configure Debugging

Create .vscode/launch.json based on your environment:

For Cloud Sandbox:

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "al",
            "request": "launch",
            "name": "Your own server",
            "server": "https://businesscentral.dynamics.com",
            "serverInstance": "BC",
            "authentication": "AAD",
            "startupObjectType": "Page",
            "startupObjectId": 22,
            "schemaUpdateMode": "Synchronize",
            "tenant": "default"
        }
    ]
}

For On-Premises:

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "al",
            "request": "launch",
            "name": "Local server",
            "server": "http://localhost",
            "serverInstance": "BC210",
            "authentication": "Windows",
            "startupObjectType": "Page",
            "startupObjectId": 22,
            "schemaUpdateMode": "Synchronize"
        }
    ]
}

For Agent Debugging (Copilot features):

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "al",
            "request": "attach",
            "name": "Attach to agent (Sandbox)",
            "clientType": "Agent",
            "environmentType": "Sandbox",
            "environmentName": "{{EnvironmentName}}",
            "breakOnNext": "WebClient"
        }
    ]
}

Phase 4: Best Practices Setup

Create .gitignore

Generate appropriate .gitignore:

# AL Compiler outputs
.alpackages/
.alcache/
.snapshots/
rad.json
*.app

# VS Code settings (optional)
.vscode/launch.json
.vscode/*.log

# Build artifacts
.netFramework/
bin/
obj/

# Test results
TestResults/
*.trx

# Temporary files
*.tmp
*.bak
*~

Documentation Standards

Create comprehensive README.md:

# {{ProjectName}}

## Overview
[Project purpose and business value]

## Key Features
- Feature 1: [Description]
- Feature 2: [Description]

## Architecture
[High-level architecture description]

## Naming Conventions
- Tables: `[BusinessEntity]` (e.g., `CustomerExtended`)
- Pages: `[BusinessEntity][PageType]` (e.g., `CustomerListPage`)
- Codeunits: `[Purpose]` (e.g., `SalesOrderProcessor`)
- ID Range: 50000-50099

## Development Guidelines
- Follow AL coding standards
- Use XML documentation for procedures
- Implement error handling with try-functions
- Write unit tests for business logic

## Dependencies
[List of extension dependencies]

## Setup Instructions
[How to set up the development environment]

XML Documentation Pattern

Demonstrate documentation for procedures:

/// <summary>
/// Calculates the total amount for a sales order including tax
/// </summary>
/// <param name="SalesHeader">The sales header record</param>
/// <returns>The total amount including tax</returns>
procedure CalculateTotalWithTax(var SalesHeader: Record "Sales Header"): Decimal
begin
    // Implementation
end;

Phase 5: Verification

Test Your Setup

Open an AL File
- Navigate to any .al file in the project
- Ensure syntax highlighting is active
Test Code Completion
- Start typing a procedure declaration
- Verify inline suggestions appear from Copilot
Test Copilot Chat
- Open Copilot Chat (Ctrl+Shift+I)
- Ask: "Explain this AL code"
- Verify you receive a response
Verify Code Analysis
- Introduce a small code issue
- Check that warnings appear
Test Build
- Run AL: Download Symbols
- Attempt to compile the project
- Verify no configuration errors

Troubleshooting

Authentication Issues

If authentication fails:

Use al_clear_credentials_cache to clear cached credentials
Re-authenticate when prompted
Verify launch.json authentication method is correct

Symbol Issues

If symbols are missing:

Download symbols: al_download_symbols
If persistent, download source: al_download_source
Verify app.json dependencies match BC version

AI Suggestions Not Appearing

Check:

AI extension is installed and enabled
You're signed in to AI service
editor.inlineSuggest.enabled is true
Restart VS Code if needed

Poor Quality Suggestions

Improvements:

Use descriptive file names
Add code comments and XML documentation
Keep related files open for better context
Follow naming conventions consistently

Success Criteria

Verify the setup is complete:

✅ Visual Studio Code is installed and configured
✅ AL Language extension is active
✅ GitHub Copilot is installed and authenticated
✅ Workspace settings are configured
✅ Project structure is organized
✅ Symbols downloaded successfully
✅ Manifest generated
✅ Launch.json configured
✅ README.md exists with project documentation
✅ Code completion is working
✅ Build succeeds without errors

Next Steps

Once your environment is initialized:

For Development:

@AL Implementation Specialist                    # Implement features (loads page/event skills on demand)
@workspace use al-build          # Build and deploy

For Architecture:

@AL Architecture & Design Specialist                    # Design solutions

For TDD Orchestration:

@AL Development Conductor                    # Plan → Implement → Review → Commit

Security 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 or PII
Security keys or certificates

Best Practices:

Review organization's AI usage policy
Use .gitignore for sensitive files
Use environment variables for credentials
Close files with sensitive information when not needed

Environment Initialization Complete! 🎉

Your AL development environment is ready for Business Central development with optimized AI assistance.

# AL Environment Initialization Your goal is to initialize the AL development environment and workspace for `{{ProjectName}}`. This workflow covers both initial environment setup (VS Code, GitHub Copilot) and AL workspace configuration (project structure, symbols, dependencies). ## Phase 1: Environment Setup ### Prerequisites Check Verify the following are available: **Required Tools:** - [ ] Visual Studio Code (latest version) - [ ] AL Language Extension (Microsoft's official extension) - [ ] GitHub Copilot or compatible AI assistant - [ ] Git for version control **Recommended Tools:** - [ ] AL Test Runner for test management - [ ] Business Central Docker Container for local development - [ ] AL Object Designer for navigation - [ ] GitLens for enhanced git integration ### GitHub Copilot Installation **Step 1: Install VS Code Extensions** - Open Visual Studio Code - Access Extensions marketplace (`Ctrl+Shift+X` or `Cmd+Shift+X`) - Install: - **GitHub Copilot** - Code completion - **GitHub Copilot Chat** - Interactive assistance - **AL Language** - Business Central development **Step 2: Authentication** - Sign in to GitHub when prompted - Authorize the extension - Verify connection is active ### VS Code Workspace Configuration Create or update `.vscode/settings.json` in the workspace root: ```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 } } ``` **Configuration Benefits:** - Code analysis with CodeCop, PerTenantExtensionCop, and UICop - AI suggestions optimized for AL files - Enhanced inline completion ## Phase 2: Project Initialization ### Choose Project Type **For New Projects:** ``` al_new_project ``` **For Existing Folders:** ``` al_go ``` ### Project Structure Implement feature-based organization: ``` {{ProjectName}}/ ├── .vscode/ │ ├── settings.json # Workspace settings │ └── launch.json # Debug configurations ├── src/ │ ├── Tables/ # Table objects │ ├── Pages/ # Page objects │ ├── Codeunits/ # Codeunit objects │ ├── Reports/ # Report objects │ ├── Queries/ # Query objects │ ├── XMLports/ # XMLport objects │ ├── PageExtensions/ # Page extensions │ ├── TableExtensions/ # Table extensions │ └── Enums/ # Enum objects ├── test/ │ ├── TestCodeunits/ # Test codeunits │ └── TestData/ # Test data and helpers ├── app.json # Application manifest ├── .gitignore # Git ignore rules └── README.md # Project documentation ``` ### Download Symbols Download required symbols: ``` al_download_symbols ``` Verify all base application dependencies are available. ### Generate Manifest Create manifest file: ``` al_generate_manifest ``` **Human Review:** Validate manifest contents before proceeding. ## Phase 3: Launch Configuration ### 🔒 Human Gate: Authentication Configuration Review **SECURITY CHECKPOINT - Configuration contains sensitive information** Before creating launch.json: 1. **Review authentication method** with stakeholder 2. **Confirm server URLs** are correct for target environment 3. **Verify credentials handling** follows security policies 4. **Obtain approval** before saving configuration ### Configure Debugging Create `.vscode/launch.json` based on your environment: **For Cloud Sandbox:** ```json { "version": "0.2.0", "configurations": [ { "type": "al", "request": "launch", "name": "Your own server", "server": "https://businesscentral.dynamics.com", "serverInstance": "BC", "authentication": "AAD", "startupObjectType": "Page", "startupObjectId": 22, "schemaUpdateMode": "Synchronize", "tenant": "default" } ] } ``` **For On-Premises:** ```json { "version": "0.2.0", "configurations": [ { "type": "al", "request": "launch", "name": "Local server", "server": "http://localhost", "serverInstance": "BC210", "authentication": "Windows", "startupObjectType": "Page", "startupObjectId": 22, "schemaUpdateMode": "Synchronize" } ] } ``` **For Agent Debugging (Copilot features):** ```json { "version": "0.2.0", "configurations": [ { "type": "al", "request": "attach", "name": "Attach to agent (Sandbox)", "clientType": "Agent", "environmentType": "Sandbox", "environmentName": "{{EnvironmentName}}", "breakOnNext": "WebClient" } ] } ``` ## Phase 4: Best Practices Setup ### Create .gitignore Generate appropriate `.gitignore`: ```gitignore # AL Compiler outputs .alpackages/ .alcache/ .snapshots/ rad.json *.app # VS Code settings (optional) .vscode/launch.json .vscode/*.log # Build artifacts .netFramework/ bin/ obj/ # Test results TestResults/ *.trx # Temporary files *.tmp *.bak *~ ``` ### Documentation Standards Create comprehensive `README.md`: ```markdown # {{ProjectName}} ## Overview [Project purpose and business value] ## Key Features - Feature 1: [Description] - Feature 2: [Description] ## Architecture [High-level architecture description] ## Naming Conventions - Tables: `[BusinessEntity]` (e.g., `CustomerExtended`) - Pages: `[BusinessEntity][PageType]` (e.g., `CustomerListPage`) - Codeunits: `[Purpose]` (e.g., `SalesOrderProcessor`) - ID Range: 50000-50099 ## Development Guidelines - Follow AL coding standards - Use XML documentation for procedures - Implement error handling with try-functions - Write unit tests for business logic ## Dependencies [List of extension dependencies] ## Setup Instructions [How to set up the development environment] ``` ### XML Documentation Pattern Demonstrate documentation for procedures: ```al /// <summary> /// Calculates the total amount for a sales order including tax /// </summary> /// <param name="SalesHeader">The sales header record</param> /// <returns>The total amount including tax</returns> procedure CalculateTotalWithTax(var SalesHeader: Record "Sales Header"): Decimal begin // Implementation end; ``` ## Phase 5: Verification ### Test Your Setup 1. **Open an AL File** - Navigate to any `.al` file in the project - Ensure syntax highlighting is active 2. **Test Code Completion** - Start typing a procedure declaration - Verify inline suggestions appear from Copilot 3. **Test Copilot Chat** - Open Copilot Chat (`Ctrl+Shift+I`) - Ask: "Explain this AL code" - Verify you receive a response 4. **Verify Code Analysis** - Introduce a small code issue - Check that warnings appear 5. **Test Build** - Run AL: Download Symbols - Attempt to compile the project - Verify no configuration errors ## Troubleshooting ### Authentication Issues If authentication fails: - Use `al_clear_credentials_cache` to clear cached credentials - Re-authenticate when prompted - Verify launch.json authentication method is correct ### Symbol Issues If symbols are missing: 1. Download symbols: `al_download_symbols` 2. If persistent, download source: `al_download_source` 3. Verify app.json dependencies match BC version ### AI Suggestions Not Appearing Check: - AI extension is installed and enabled - You're signed in to AI service - `editor.inlineSuggest.enabled` is `true` - Restart VS Code if needed ### Poor Quality Suggestions Improvements: - Use descriptive file names - Add code comments and XML documentation - Keep related files open for better context - Follow naming conventions consistently ## Success Criteria Verify the setup is complete: - ✅ Visual Studio Code is installed and configured - ✅ AL Language extension is active - ✅ GitHub Copilot is installed and authenticated - ✅ Workspace settings are configured - ✅ Project structure is organized - ✅ Symbols downloaded successfully - ✅ Manifest generated - ✅ Launch.json configured - ✅ README.md exists with project documentation - ✅ Code completion is working - ✅ Build succeeds without errors ## Next Steps Once your environment is initialized: **For Development:** ``` @AL Implementation Specialist # Implement features (loads page/event skills on demand) @workspace use al-build # Build and deploy ``` **For Architecture:** ``` @AL Architecture & Design Specialist # Design solutions ``` **For TDD Orchestration:** ``` @AL Development Conductor # Plan → Implement → Review → Commit ``` ## Security 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 or PII - Security keys or certificates **Best Practices:** - Review organization's AI usage policy - Use `.gitignore` for sensitive files - Use environment variables for credentials - Close files with sensitive information when not needed --- **Environment Initialization Complete! 🎉** Your AL development environment is ready for Business Central development with optimized AI assistance.

{ "prompt": "# AL Environment Initialization\n\nYour goal is to initialize the AL development environment and workspace for `{{ProjectName}}`.\n\nThis workflow covers both initial environment setup (VS Code, GitHub Copilot) and AL workspace configuration (project structure, symbols, dependencies).\n\n## Phase 1: Environment Setup\n\n### Prerequisites Check\n\nVerify the following are available:\n\n**Required Tools:**\n- [ ] Visual Studio Code (latest version)\n- [ ] AL Language Extension (Microsoft's official extension)\n- [ ] GitHub Copilot or compatible AI assistant\n- [ ] Git for version control\n\n**Recommended Tools:**\n- [ ] AL Test Runner for test management\n- [ ] Business Central Docker Container for local development\n- [ ] AL Object Designer for navigation\n- [ ] GitLens for enhanced git integration\n\n### GitHub Copilot Installation\n\n**Step 1: Install VS Code Extensions**\n- Open Visual Studio Code\n- Access Extensions marketplace (`Ctrl+Shift+X` or `Cmd+Shift+X`)\n- Install:\n - **GitHub Copilot** - Code completion\n - **GitHub Copilot Chat** - Interactive assistance\n - **AL Language** - Business Central development\n\n**Step 2: Authentication**\n- Sign in to GitHub when prompted\n- Authorize the extension\n- Verify connection is active\n\n### VS Code Workspace Configuration\n\nCreate or update `.vscode/settings.json` in the workspace root:\n\n```json\n{\n // AL Language settings\n \"al.enableCodeAnalysis\": true,\n \"al.codeAnalyzers\": [\"{{CodeCop}}\", \"{{PerTenantExtensionCop}}\", \"{{UICop}}\"],\n\n // GitHub Copilot settings\n \"github.copilot.enable\": {\n \"*\": true,\n \"al\": true\n },\n\n // Editor settings for better AI integration\n \"editor.inlineSuggest.enabled\": true,\n \"editor.quickSuggestions\": {\n \"other\": true,\n \"comments\": true,\n \"strings\": true\n }\n}\n```\n\n**Configuration Benefits:**\n- Code analysis with CodeCop, PerTenantExtensionCop, and UICop\n- AI suggestions optimized for AL files\n- Enhanced inline completion\n\n## Phase 2: Project Initialization\n\n### Choose Project Type\n\n**For New Projects:**\n```\nal_new_project\n```\n\n**For Existing Folders:**\n```\nal_go\n```\n\n### Project Structure\n\nImplement feature-based organization:\n\n```\n{{ProjectName}}/\n├── .vscode/\n│ ├── settings.json # Workspace settings\n│ └── launch.json # Debug configurations\n├── src/\n│ ├── Tables/ # Table objects\n│ ├── Pages/ # Page objects\n│ ├── Codeunits/ # Codeunit objects\n│ ├── Reports/ # Report objects\n│ ├── Queries/ # Query objects\n│ ├── XMLports/ # XMLport objects\n│ ├── PageExtensions/ # Page extensions\n│ ├── TableExtensions/ # Table extensions\n│ └── Enums/ # Enum objects\n├── test/\n│ ├── TestCodeunits/ # Test codeunits\n│ └── TestData/ # Test data and helpers\n├── app.json # Application manifest\n├── .gitignore # Git ignore rules\n└── README.md # Project documentation\n```\n\n### Download Symbols\n\nDownload required symbols:\n```\nal_download_symbols\n```\n\nVerify all base application dependencies are available.\n\n### Generate Manifest\n\nCreate manifest file:\n```\nal_generate_manifest\n```\n\n**Human Review:** Validate manifest contents before proceeding.\n\n## Phase 3: Launch Configuration\n\n### 🔒 Human Gate: Authentication Configuration Review\n\n**SECURITY CHECKPOINT - Configuration contains sensitive information**\n\nBefore creating launch.json:\n1. **Review authentication method** with stakeholder\n2. **Confirm server URLs** are correct for target environment\n3. **Verify credentials handling** follows security policies\n4. **Obtain approval** before saving configuration\n\n### Configure Debugging\n\nCreate `.vscode/launch.json` based on your environment:\n\n**For Cloud Sandbox:**\n```json\n{\n \"version\": \"0.2.0\",\n \"configurations\": [\n {\n \"type\": \"al\",\n \"request\": \"launch\",\n \"name\": \"Your own server\",\n \"server\": \"https://businesscentral.dynamics.com\",\n \"serverInstance\": \"BC\",\n \"authentication\": \"AAD\",\n \"startupObjectType\": \"Page\",\n \"startupObjectId\": 22,\n \"schemaUpdateMode\": \"Synchronize\",\n \"tenant\": \"default\"\n }\n ]\n}\n```\n\n**For On-Premises:**\n```json\n{\n \"version\": \"0.2.0\",\n \"configurations\": [\n {\n \"type\": \"al\",\n \"request\": \"launch\",\n \"name\": \"Local server\",\n \"server\": \"http://localhost\",\n \"serverInstance\": \"BC210\",\n \"authentication\": \"Windows\",\n \"startupObjectType\": \"Page\",\n \"startupObjectId\": 22,\n \"schemaUpdateMode\": \"Synchronize\"\n }\n ]\n}\n```\n\n**For Agent Debugging (Copilot features):**\n```json\n{\n \"version\": \"0.2.0\",\n \"configurations\": [\n {\n \"type\": \"al\",\n \"request\": \"attach\",\n \"name\": \"Attach to agent (Sandbox)\",\n \"clientType\": \"Agent\",\n \"environmentType\": \"Sandbox\",\n \"environmentName\": \"{{EnvironmentName}}\",\n \"breakOnNext\": \"WebClient\"\n }\n ]\n}\n```\n\n## Phase 4: Best Practices Setup\n\n### Create .gitignore\n\nGenerate appropriate `.gitignore`:\n\n```gitignore\n# AL Compiler outputs\n.alpackages/\n.alcache/\n.snapshots/\nrad.json\n*.app\n\n# VS Code settings (optional)\n.vscode/launch.json\n.vscode/*.log\n\n# Build artifacts\n.netFramework/\nbin/\nobj/\n\n# Test results\nTestResults/\n*.trx\n\n# Temporary files\n*.tmp\n*.bak\n*~\n```\n\n### Documentation Standards\n\nCreate comprehensive `README.md`:\n\n```markdown\n# {{ProjectName}}\n\n## Overview\n[Project purpose and business value]\n\n## Key Features\n- Feature 1: [Description]\n- Feature 2: [Description]\n\n## Architecture\n[High-level architecture description]\n\n## Naming Conventions\n- Tables: `[BusinessEntity]` (e.g., `CustomerExtended`)\n- Pages: `[BusinessEntity][PageType]` (e.g., `CustomerListPage`)\n- Codeunits: `[Purpose]` (e.g., `SalesOrderProcessor`)\n- ID Range: 50000-50099\n\n## Development Guidelines\n- Follow AL coding standards\n- Use XML documentation for procedures\n- Implement error handling with try-functions\n- Write unit tests for business logic\n\n## Dependencies\n[List of extension dependencies]\n\n## Setup Instructions\n[How to set up the development environment]\n```\n\n### XML Documentation Pattern\n\nDemonstrate documentation for procedures:\n\n```al\n/// <summary>\n/// Calculates the total amount for a sales order including tax\n/// </summary>\n/// <param name=\"SalesHeader\">The sales header record</param>\n/// <returns>The total amount including tax</returns>\nprocedure CalculateTotalWithTax(var SalesHeader: Record \"Sales Header\"): Decimal\nbegin\n // Implementation\nend;\n```\n\n## Phase 5: Verification\n\n### Test Your Setup\n\n1. **Open an AL File**\n - Navigate to any `.al` file in the project\n - Ensure syntax highlighting is active\n\n2. **Test Code Completion**\n - Start typing a procedure declaration\n - Verify inline suggestions appear from Copilot\n\n3. **Test Copilot Chat**\n - Open Copilot Chat (`Ctrl+Shift+I`)\n - Ask: \"Explain this AL code\"\n - Verify you receive a response\n\n4. **Verify Code Analysis**\n - Introduce a small code issue\n - Check that warnings appear\n\n5. **Test Build**\n - Run AL: Download Symbols\n - Attempt to compile the project\n - Verify no configuration errors\n\n## Troubleshooting\n\n### Authentication Issues\n\nIf authentication fails:\n- Use `al_clear_credentials_cache` to clear cached credentials\n- Re-authenticate when prompted\n- Verify launch.json authentication method is correct\n\n### Symbol Issues\n\nIf symbols are missing:\n1. Download symbols: `al_download_symbols`\n2. If persistent, download source: `al_download_source`\n3. Verify app.json dependencies match BC version\n\n### AI Suggestions Not Appearing\n\nCheck:\n- AI extension is installed and enabled\n- You're signed in to AI service\n- `editor.inlineSuggest.enabled` is `true`\n- Restart VS Code if needed\n\n### Poor Quality Suggestions\n\nImprovements:\n- Use descriptive file names\n- Add code comments and XML documentation\n- Keep related files open for better context\n- Follow naming conventions consistently\n\n## Success Criteria\n\nVerify the setup is complete:\n\n- ✅ Visual Studio Code is installed and configured\n- ✅ AL Language extension is active\n- ✅ GitHub Copilot is installed and authenticated\n- ✅ Workspace settings are configured\n- ✅ Project structure is organized\n- ✅ Symbols downloaded successfully\n- ✅ Manifest generated\n- ✅ Launch.json configured\n- ✅ README.md exists with project documentation\n- ✅ Code completion is working\n- ✅ Build succeeds without errors\n\n## Next Steps\n\nOnce your environment is initialized:\n\n**For Development:**\n```\n@AL Implementation Specialist # Implement features (loads page/event skills on demand)\n@workspace use al-build # Build and deploy\n```\n\n**For Architecture:**\n```\n@AL Architecture & Design Specialist # Design solutions\n```\n\n**For TDD Orchestration:**\n```\n@AL Development Conductor # Plan → Implement → Review → Commit\n```\n\n## Security Considerations\n\n**What Gets Sent to AI Services:**\n- Code snippets from your workspace\n- Currently open files\n- Your prompts and questions\n\n**What You Should NOT Include:**\n- Sensitive credentials or passwords\n- Customer data or PII\n- Security keys or certificates\n\n**Best Practices:**\n- Review organization's AI usage policy\n- Use `.gitignore` for sensitive files\n- Use environment variables for credentials\n- Close files with sensitive information when not needed\n\n---\n\n**Environment Initialization Complete! 🎉**\n\nYour AL development environment is ready for Business Central development with optimized AI assistance.", "variables": [ "ProjectName", "CodeCop", "PerTenantExtensionCop", "UICop", "EnvironmentName" ], "notes": "Initialize AL development environment and workspace for Business Central. Tools: vscode, execute, read, agent, edit, search, web, github/*, github/*, github/*, microsoft-docs/*, upstash/context7/*.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/javiarmesto/SampleDynamicsMinds", "path": ".github/prompts/al-initialize.prompt.md", "ref": "e7c9922321955d86fcbd4d1f1b17488717b93fa3", "url": "https://github.com/javiarmesto/SampleDynamicsMinds/blob/e7c9922321955d86fcbd4d1f1b17488717b93fa3/.github/prompts/al-initialize.prompt.md", "key": "javiarmesto/SampleDynamicsMinds/.github/prompts/al-initialize.prompt.md" } }, "model_hints": [ "Claude Sonnet 4.5" ] }

al-initialize

About