Add basic project description and template

Author: aiqlcom

.github/FUNDING.yml

@@ -0,0 +1,4 @@
+# These are supported funding model platforms
+
+github: AI-QL
+custom: ["https://www.aiql.com"]

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,38 @@
+name: 'Bug report'
+description: Report a bug in this project.
+labels: ['bug']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Before creating an issue, please read the following:
+
+        - Read the `README.md` file on the project page or the documentation file and compare your code to the intent of the project.
+        - Search to see if the same issue already exists, and keep the title concise and accurate so that it's easy for others to understand and search for.
+        - Please create a separate issue for each type of issue.
+        - For modular projects, make sure you're using the latest version of the module.
+        - Please be as detailed as possible and write in English so that we can handle your issue quickly.
+  - type: textarea
+    attributes:
+      label: Describe the bug
+      description: |
+        For the issue you are experiencing, please describe in detail what you are seeing, the error message, and the impact of the issue. If you are able to reproduce the issue, please list the steps in order. You can attach an image or video if necessary.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected behavior
+      description: Describe how it should be handled when it's normal behavior or what needs to be fixed.
+    validations:
+  - type: input
+    attributes:
+      label: Your environment - System OS
+      description: Please describe the full range of OSes you are experiencing the issue with, preferably including the version.
+      placeholder: Windows 11, macOS 15.x, Linux Ubuntu 24.04...
+    validations:
+  - type: input
+    attributes:
+      label: Your environment - Node.js
+      description: If relevant, please describe the version of Node.js you are currently using.
+      placeholder: 20.19.4, 22.17.0, 24.4.0...
+    validations:

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,18 @@
+name: 'Feature request'
+description: Report a feature request in this project.
+labels: ['enhancement']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Before creating an issue, please read the following:
+
+        - Search to see if the same issue already exists, and keep the title concise and accurate so that it's easy for others to understand and search for.
+        - Please create a separate issue for each type of issue.
+        - Please be as detailed as possible and write in English so that we can handle your issue quickly.
+  - type: textarea
+    attributes:
+      label: Describe the feature
+      description: Feel free to describe any features or improvements you would like to see. You can attach text or images of examples, behavior, etc. from other projects to elaborate.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/fix_typo.yml

@@ -0,0 +1,18 @@
+name: 'Fix typo request'
+description: Request to fix a typo or bad translation in this project
+labels: ['typo']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Before creating an issue, please read the following:
+
+        - Search to see if the same issue already exists, and keep the title concise and accurate so that it's easy for others to understand and search for.
+        - Please create a separate issue for each type of issue.
+        - Please be as detailed as possible and write in English so that we can handle your issue quickly.
+  - type: textarea
+    attributes:
+      label: Describe the issue
+      description: Please describe where the typo occurs and a list of text that needs to be corrected.
+    validations:
+      required: true

.github/pull_request_template.md

@@ -0,0 +1,24 @@
+<!--
+Thank you for contributing to the project. Your contribution will be reviewed and approved after appropriate review.
+
+Please read the caveats below to ensure a fast merge.
+-->
+
+## Pull request checklist
+
+You should familiarize yourself with the files `README.md`, `CONTRIBUTING.md`, and `CODE_OF_CONDUCT.md` in the root of your project.
+
+- If an issue has been created for this, add `(fixes #{ISSUE_NUMBER})` to the end of the commit description. In `{ISSUE_NUMBER}`, please include the relevant issue number.
+- If you need to update or add to the article, please update the relevant content. If a multilingual article exists, you should update all relevant content in your own language, except for translations.
+- Add or update test code if it exists and is needed. Also, verify that the tests pass.
+- If this PR is not yet complete, keep the PR in draft status. If it's no longer valid, close the PR with an explanation.
+
+<!--
+Below is a template for describing this PR. It's not required, so please delete the content below if you don't need it.
+-->
+
+### What did you change?
+
+### Why did you make the change?
+
+### How does this work?

.github/workflows/build-test.yml

@@ -0,0 +1,55 @@
+name: Build Test
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - '**'
+      - '!LICENSE'
+      - '!*.md'
+      - '!docs/**'
+      - '!.github/**'
+      - '.github/workflows/build-test.yml'
+  pull_request:
+    branches: [main]
+  workflow_dispatch:
+
+jobs:
+  build-test:
+    runs-on: ${{ matrix.os }}
+    name: Test Node.js ${{ matrix.node_version }} on ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        node_version: ['20', '22']
+        os: [windows-latest, macos-latest, ubuntu-latest]
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js ${{ matrix.node_version }}
+        uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node_version }}
+          cache: npm
+          cache-dependency-path: '**/package-lock.json'
+
+      - name: Cache dependencies
+        uses: actions/cache@v4
+        id: npm-cache
+        with:
+          path: |
+            **/node_modules
+          key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-npm-
+
+      - name: Install dependencies
+        if: steps.npm-cache.outputs.cache-hit != 'true'
+        run: npm i
+
+      - name: Test module script
+        run: |
+          npm run build

CODE_OF_CONDUCT.md

@@ -0,0 +1,79 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at https://www.aiql.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,122 @@
+# Contributing to Project
+
+Thank you for contributing to the project. Your contributions will help us take the project to the next level.
+
+This project adheres to the Contributor Covenant code of conduct. Your contribution implies that you have read and agree to this policy. Any behavior that undermines the quality of the project community, including this policy, will be warned or restricted by the maintainers.
+
+## Issues
+
+Issues can be created on the following page: https://github.com/AI-QL/mcp-devcontainers/issues
+
+Alternatively, you can email the package maintainer. However, we prefer to track progress via GitHub Issues.
+
+When creating an issue, keep the following in mind:
+
+- Please specify the correct category selection based on the format of the issue (e.g., bug report, feature request).
+- Check to see if there are duplicate issues.
+- Describe in detail what is happening and what needs to be fixed. You may need additional materials such as images or video.
+- Use appropriate keyword titles to make it easy for others to search and understand.
+- Please use English in all content.
+- You may need to describe the environment in which the issue occurs.
+
+## How to contribute (Pull Requests)
+
+### Write the code you want to change
+
+Here's the process for contributing to the project:
+
+1. Clone the project (or rebase to the latest commit in the main branch)
+2. Install the package (if the package manager exists)
+3. Setting up lint or code formatter in the IDE (if your project includes a linter) and installing the relevant plugins. Some projects may use specific commands to check rules and perform formatting after module installation and before committing.
+4. Write the code that needs to be fixed
+5. Update the documentation (if it exists) or create a new one. If your project supports multilingual documentation, update the documentation for all languages. You can fill in the content in your own language and not translate it.
+6. Add or modify tests as needed (if test code exists). You should also verify that existing tests pass.
+
+### Write a commit message
+
+While we don't have strict restrictions on commit messages, we recommend that you follow the recommendations below whenever possible:
+
+- Write in English.
+- Use the ` symbol to name functions, variables, or folders and files.
+- Use a format like `xxx: message (fixes #1)`. The content in parentheses is optional.
+- The message includes a summary of what was modified.
+- It's a good idea to separate multiple modifications into their own commit messages.
+
+It is recommended that you include a tag at the beginning of the commit message. Between the tag and the message, use `: ` between the tag and the message.
+
+tags conform to the ["Udacity Git Commit Message Style Guide"](https://udacity.github.io/git-styleguide). However, you are welcome to use tags not listed here for additional situations.
+
+- `feat`: A new feature
+- `fix`: A bug fix
+- `docs`: Changes to documentation
+- `style`: Formatting, missing semicolons, etc.; no code change
+- `refactor`: Refactoring production code
+- `test`: Adding tests, refactoring test; no production code change
+- `chore`: Updating build tasks, package manager configs, etc.; no production code change
+
+Informal tags:
+
+- `package`: Modifications to package settings, modules, or GitHub projects
+- `typo`: Fix typos
+
+### Create a pull request
+
+When creating a pull request, keep the following in mind:
+
+- Include a specific description of what the modification is, why it needs to be made, and how it works.
+- Check to see if there are duplicate pull requests.
+- Please use English in all content.
+
+Typically, a project maintainer will review and test your code before merging it into the project. This process can take some time, and they may ask you for further edits or clarifications in the comments.
+
+## Development Guide
+
+### Prerequisites
+
+The following software is required to work on the spec:
+
+- Node.js 20 or above
+- TypeScript
+
+## Getting Started
+
+1. Fork the repository
+2. Clone your fork:
+
+```bash
+git clone https://github.com/YOUR-USERNAME/mcp-devcontainers.git
+cd mcp-devcontainers
+```
+
+3. Install dependencies:
+
+```bash
+npm install  # install dependencies
+```
+
+## Making Changes
+
+1. Create a new branch:
+
+```bash
+git checkout -b feature/your-feature-name
+```
+
+2. Make your changes
+3. Lint your changes:
+
+```bash
+npm run lint:fix    # perform lint validation/fixing
+```
+
+4. Run build locally:
+
+```bash
+npm run build
+```
+
+5. Test MCP servers:
+
+```bash
+npm run start
+```