[Agent]: Add support for Jerad551/@github.com

[Jerad551]

Agent Name

e.g. Perplexity__> KiT: Royal Naval Ace; 4657ff6

Official Website

https://www.TELECOMM-TriforceTrinity.com

Agent Type

IDE extension/plugin

CLI Command (if applicable)

e.g. Powershell ISE

Installation Method

e.g. GitKraken.com

Command/Workflow Structure

@https://github.com/your-username/dev.oss.git

Argument Passing Pattern

No response

Popularity/Usage

Growing adoption (hundreds of users)

Documentation Links

No response

Use Case

[Motorola]( @url #@url)/) legal.yml.pdf

Example Command File

Contribution

• I can help test the integration
• I can provide example command files
• I can help with documentation
• I can submit a pull request for the integration

Additional Context

No response

[Jerad551]

#https://github.com/github/spec-kit/issues/new/choose

• `[https://github.com/Rename devcontainer.json to devcontainer.jrad Azure/azure-cli#32844#issuecomment-3953483932It looks like you're trying to set up a development environment using GitHub and some specific directories and prompts. Let's break down the steps you might need to follow to set up your development environment.

Step 1: Set Up GitHub Repository

1. Create a GitHub Repository:

   • Go to GitHub and create a new repository.
   • Name it something relevant to your project, e.g., dev.oss.

2. Clone the Repository:

   • Open your terminal or PowerShell.
   • Clone the repository to your local machine:

     git clone https://github.com/your-username/dev.oss.git

Step 2: Set Up Directory Structure

1. Navigate to the Repository:

   cd dev.oss

2. Create Necessary Directories:

   • Create a directory for your test files:

     mkdir src
     mkdir src/test_System32

Step 3: Set Up Prompts

1. Create Prompt Files:

   • In the root directory of your repository (dev.oss), create a file named .prmt_prompt.
   • In the src/test_System32 directory, create a file named .prmt.

2. Add Prompt Content:

   • Open .prmt_prompt in the root directory and add your desired prompt syntax.
   • Open .prmt in the src/test_System32 directory and add your desired prompt syntax.

Step 4: Configure PowerShell Prompt

1. Edit PowerShell Profile:
   • Open your PowerShell profile script. You can do this by running:

     notepad $PROFILE

   • Add the following lines to your profile script to set the prompt:

     function prompt {
         if (Test-Path .prmt_prompt) {
             Get-Content .prmt_prompt
         } elseif (Test-Path src/test_System32/.prmt) {
             Get-Content src/test_System32/.prmt
         } else {
             "PS $($executionContext.SessionState.Path.CurrentLocation)$('>' * ($nestedPromptLevel + 1)) "
         }
     }

Step 5: Test Your Setup

1. Navigate to Different Directories:

   • Open a new PowerShell window and navigate to different directories within your repository to see if the prompts change accordingly.

2. Verify Prompts:

   • Ensure that the prompts display the content of .prmt_prompt when in the root directory and .prmt when in the src/test_System32 directory.

Example Directory Structure

dev.oss/
├── .prmt_prompt
├── src/
│   └── test_System32/
│       └── .prmt

Example Prompt Content

.prmt_prompt:

CND: ps. 1:  test__> __>src/test_System32:  prompt; .prmt_prompt<syntax<.prmt {
}

.prmt:

CND:  ps. 1:  test__> __>src/test_System32:  prompt; .prmt_prompt<syntax<.prmt {
}

By following these steps, you should have a functional development environment with custom prompts set up in PowerShell.](url)`