@windypro-rourou/dsh-eda 0.1.0 → 0.1.1

package/skill/guide/ancillary-projects.md

@@ -0,0 +1,10 @@
+# Ancillary Projects
+
+The current EasyEDA Professional Edition Extension API provides the following helper items that you can use for a more complete development experience:
+
+| Project                                                      | Type              | Badges                                                       | License                                                      | Description                    |
+| ------------------------------------------------------------ | ----------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------ |
+| [pro-api-sdk](./ancillary-projects/pro-api-sdk)              | Git Repo          | <a href="https://github.com/easyeda/pro-api-sdk" style="vertical-align: inherit;" target="_blank"><img src="https://img.shields.io/github/stars/easyeda/pro-api-sdk" alt="GitHub Repo Stars" class="not-medium-zoom-image" style="display: inline; vertical-align: inherit;" /></a> <a href="https://github.com/easyeda/pro-api-sdk/issues" style="vertical-align: inherit;" target="_blank"><img src="https://img.shields.io/github/issues/easyeda/pro-api-sdk" alt="GitHub Issues" class="not-medium-zoom-image" style="display: inline; vertical-align: inherit;" /></a> | <a href="https://choosealicense.com/licenses/apache-2.0/" style="vertical-align: inherit;" target="_blank"><img src="https://img.shields.io/github/license/easyeda/pro-api-sdk" alt="GitHub License" class="not-medium-zoom-image" style="display: inline; vertical-align: inherit;" /></a> | Extension Development SDK      |
+| [pro-api-types](./ancillary-projects/pro-api-types)          | npm Package       | <a href="https://www.npmjs.com/package/@jlceda/pro-api-types" style="vertical-align: inherit;" target="_blank"><img src="https://img.shields.io/npm/v/%40jlceda%2Fpro-api-types" alt="NPM Version" class="not-medium-zoom-image" style="display: inline; vertical-align: inherit;" /></a> | <a href="https://choosealicense.com/licenses/apache-2.0/" style="vertical-align: inherit;" target="_blank"><img src="https://img.shields.io/npm/l/%40jlceda%2Fpro-api-types" alt="NPM License" class="not-medium-zoom-image" style="display: inline; vertical-align: inherit;" /></a> | Extension API Type Definitions |
+| [eext-run-api-gateway](https://jlcext.com/item/oshwhub-official/run-api-gateway) | EasyEDA Extension | <a href="https://github.com/easyeda/eext-run-api-gateway" style="vertical-align: inherit;" target="_blank"><img src="https://img.shields.io/github/stars/easyeda/eext-run-api-gateway" alt="GitHub Repo Stars" class="not-medium-zoom-image" style="display: inline; vertical-align: inherit;" /></a> <a href="https://github.com/easyeda/eext-run-api-gateway/issues" style="vertical-align: inherit;" target="_blank"><img src="https://img.shields.io/github/issues/easyeda/eext-run-api-gateway" alt="GitHub Issues" class="not-medium-zoom-image" style="display: inline; vertical-align: inherit;" /></a> | <a href="https://choosealicense.com/licenses/apache-2.0/" style="vertical-align: inherit;" target="_blank"><img src="https://img.shields.io/github/license/easyeda/eext-run-api-gateway" alt="GitHub License" class="not-medium-zoom-image" style="display: inline; vertical-align: inherit;" /></a> | EDA \<-\> AI Gateway Extension |
+| [easyeda-api-skill](https://clawhub.ai/yanranxiaoxi/easyeda-api) | AI Skill          | <a href="https://github.com/easyeda/easyeda-api-skill" style="vertical-align: inherit;" target="_blank"><img src="https://img.shields.io/github/stars/easyeda/easyeda-api-skill" alt="GitHub Repo Stars" class="not-medium-zoom-image" style="display: inline; vertical-align: inherit;" /></a> <a href="https://github.com/easyeda/easyeda-api-skill/issues" style="vertical-align: inherit;" target="_blank"><img src="https://img.shields.io/github/issues/easyeda/easyeda-api-skill" alt="GitHub Issues" class="not-medium-zoom-image" style="display: inline; vertical-align: inherit;" /></a> | <a href="https://github.com/aws/mit-0" style="vertical-align: inherit;" target="_blank"><img src="https://img.shields.io/github/license/easyeda/easyeda-api-skill" alt="GitHub License" class="not-medium-zoom-image" style="display: inline; vertical-align: inherit;" /></a> | Extension API AI Skill         |

package/skill/guide/error-handling.md

@@ -0,0 +1,38 @@
+# Error Handling
+
+## Disable Extensions and Scripting Systems Globally
+
+When you encounter an exception caused by an extension that prevents you from removing the extension through the normal route (such as corrupted or masked data in the top menu bar, or an uninstall returning an error), you can globally disable the extension and the scripting system by adding the `safetyMode=true` parameter within the URL of the EasyEDA Professional editor:
+
+```diff
+- https://pro.easyeda.com/editor
++ https://pro.easyeda.com/editor?safetyMode=true
+```
+
+::: tip
+
+If you wish to enter debug mode at the same time, you can add the `cll=debug` parameter again:
+
+```diff
+- https://pro.easyeda.com/editor?safetyMode=true
++ https://pro.easyeda.com/editor?safetyMode=true&cll=debug
+```
+
+:::
+
+## Remove All Extensions Globally
+
+::: danger
+
+**DANGEROUS!** All your installed extensions and standalone scripts will be removed and cannot be recovered. This method should only be used if a serious error is confirmed to be caused by an extension and cannot be resolved by conventional means.
+
+:::
+
+::: details Thanos mode switch
+
+```diff
+- https://pro.easyeda.com/editor
++ https://pro.easyeda.com/editor?DANGEROUS_OPERATION_DeleteExtensionStorage=true
+```
+
+:::

package/skill/guide/extension-json.md

@@ -0,0 +1,135 @@
+# Extension Configuration File
+
+In order to define the properties of an extension and the various functions that an extension can invoke, each extension should have an extension configuration file named `extension.json` in the root directory with the following default contents:
+
+<<< @/private/pro-api-sdk/extension.json{json}
+
+## name <Badge type="tip" text="string" />
+
+Extension name. It can only contain lowercase English characters `a-z`, numbers `0-9`, and underscores `-`, and is `5-30` characters long.
+
+## uuid <Badge type="tip" text="string" />
+
+UUID. A unique ID for the extension that can contain only lowercase English characters `a-z`, numbers `0-9`, and is `32` characters long.
+
+## displayName <Badge type="tip" text="string" />
+
+Display name.
+
+## description <Badge type="tip" text="string" />
+
+Description.
+
+## version <Badge type="tip" text="string" />
+
+Version number. The format is `major.minor.patch`.
+
+## publisher <Badge type="tip" text="string" />
+
+Developer Information.
+
+## engines <Badge type="tip" text="Object" /> <Badge type="warning" text="feature" />
+
+The engine to which the extension applies.
+
+### engines.eda <Badge type="tip" text="string" /> <Badge type="warning" text="feature" />
+
+Extended adapted version of EasyEDA Professional (online).
+
+## license <Badge type="tip" text="string" />
+
+Open-source licensing terms. It is recommended to go to [Choose a License](https://choosealicense.com/) to select the appropriate open source license for your project.
+
+## repository <Badge type="tip" text="Object" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
+
+Repository information for the source code of the extension.
+
+### repository.type <Badge type="tip" text="string" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
+
+The type of source code repository. Optional values are `extension-store` `git` `mercurial` `svn` `ftp` `github` `gitlab` `gitlab-selfhosted` `gitee` `gitea` `bitbucket` `coding` `gnu-savannah` ` gitbucket` `gogs`.
+
+### repository.url <Badge type="tip" text="string" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
+
+Source code repository URL.
+
+## categories <Badge type="tip" text="string | Array<string>" />
+
+The extension's classification. Optional values are `Schematic` `Symbol` `PCB` `Footprint` `Panel` `Library` `Project` `Other`.
+
+## keywords <Badge type="tip" text="Array<string>" />
+
+Keywords.
+
+## images <Badge type="tip" text="Object" />
+
+Images.
+
+### images.logo <Badge type="tip" text="string" />
+
+Logo. Size `1:1`, PNG/JPEG format. Logos can be drawn using an AI generation tool such as [AutoDraw](https://www.autodraw.com/) and a minimum size of `500×500` is recommended.
+
+### images.banner <Badge type="tip" text="string" /> <Badge type="warning" text="feature" />
+
+Banner. Size `64:27`, for presentation of extension's store page, JPEG format.
+
+## homepage <Badge type="tip" text="string" />
+
+Project homepage.
+
+## bugs <Badge type="tip" text="string" />
+
+Vulnerability feedback channel. Please fill in a correct URI.
+
+## activationEvents <Badge type="tip" text="Object" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
+
+Extension's activation event.
+
+## entry <Badge type="tip" text="string" />
+
+Entry file. No modification is recommended, it is correctly defined within the SDK.
+
+## dependentExtensions <Badge type="tip" text="Object" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
+
+Dependencies on other extensions. Supports the use of 32-bit UUIDs of extensions in the Extension Store (automatic pulling supported), or user-defined extension names (manual upload required).
+
+## headerMenus <Badge type="tip" text="Object" />
+
+The header menu registered when the extension is initialized.
+
+The header menu is currently supported to be configured separately according to the following pages:
+
+```json
+{
+	"headerMenus": {
+		"home": [], // [!code focus:9]
+		"blank": [],
+		"sch": [],
+		"symbol": [],
+		"pcb": [],
+		"footprint": [],
+		"pcbView": [],
+		"panel": [],
+		"panelView": []
+	}
+}
+```
+
+### headerMenus[].id <Badge type="tip" text="string" />
+
+Menu item ID. must be unique.
+
+### headerMenus[].title <Badge type="tip" text="string" />
+
+Menu item title.
+
+### headerMenus[].menuItems <Badge type="tip" text="Object" />
+
+Menu item subitems. Up to two levels of subitems can be nested.
+
+`menuItems` conflicts with `registerFn`, only one of them is allowed to exist in the same level.
+
+### headerMenus[].registerFn <Badge type="tip" text="string" />
+
+Menu associated registered method. The method here is associated with a method exported within the code of this extension, you need to export the specified method as an `ES Module` using `export` and fill in its method name here.
+
+`registerFn` conflicts with `menuItems`, only one of them is allowed to exist in the same level.

package/skill/guide/extensions-marketplace.md

@@ -0,0 +1,61 @@
+# Extensions Marketplace
+
+EasyEDA Extensions Marketplace site [https://jlcext.com](https://jlcext.com), which is a professional platform for users to download and share extensions.
+
+If you want to learn how to develop extensions, please refer to the [how-to-start](./how-to-start), which describes in detail how to install the development environment and build your own EasyEDA Pro extension from scratch.
+
+## Publishing Your Extension
+
+When you have fully verified the functionality of the extension you have developed and wish to share it with other users, please visit the [EasyEDA Extensions Marketplace](https://jlcext.com/) and click the **Extension Management** button in the upper right corner:
+
+![图 0](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260617_210219.jpg)
+
+
+Enter the extension management page, which supports uploading, publishing and versioning of extensions.
+
+Click the **Extension Upload** button to upload your first extension that meets the following requirements:
+
+1. The extension `extension.json` should contain the following attributes: `name`, `uuid`, `displayName`, `description`, `version`, and `license`;
+2. select and fill in at least one or more of the required extension types (`categories`);
+3. the extension must provide a custom icon and must not use the default `logo` provided in the SDK, the recommended icon size ratio is `1:1`, the format must be PNG or JPEG, the content must be clear without risk of infringement, and the file size must not exceed `5 MiB`;
+4. make sure that the entry file (`entry`) of the extension exists and is valid;
+5. the value of the `name` attribute must not be duplicated across extensions with different `uuid`;
+6. include a detailed description of the extension's functionality and usage in the `README.md` file;
+7. if necessary, keep an change log for the extension in the `CHANGELOG.md` file;
+8. the extension **DOESN'T** contain private information, such as your phone numbers.
+
+![图 0](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260603_163928.png)
+
+Select your compiled `.eext` file in the upload pop-up window and upload it. The first uploaded extension will automatically create a namespace into which all subsequent uploads of the extension (identified by `uuid`) will be grouped.
+
+You can view the extension's name, description, version, install count, updated time, and other information on the namespace cover:
+
+![图 4](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172246.png)
+
+
+After the extension is uploaded, it will automatically enter the review process. After approval, it will be listed in the marketplace:
+
+![图 5](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172309.png)
+
+
+After waiting for the review to complete, the review status will change to **Passed**. If there is a case that the review is not passed, please check the reason in the message notification in time and check the non-compliant content in the extension:
+
+![图 6](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172321.png)
+
+After approval, other users will be able to view your extension details and download the uploaded version:
+
+![图 7](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172403.png)
+
+You can view the extension's detail page, where the `README.md` and `CHANGELOG.md` contents of the extension file will be displayed:
+
+![图 8](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172447.png)
+
+All published versions of the extension are listed in the history:
+
+![图 9](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172548.png)
+
+You can leave ratings and reviews of the extension in the comments section:
+
+![图 10](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172603.png)
+
+You can also downgrade the namespace of an extension at any time on the extension management page. This does not affect the status of uploaded versions, and you can also individually unpublish a specific version in the versioning management.

package/skill/guide/how-to-start.md

@@ -0,0 +1,301 @@
+# How to Get Started <Badge type="tip" text="Intro" />
+
+In the EasyEDA Professional extension engine, all extensions are independent JavaScript scripts running under their own scope chains.
+
+Each extension requires a UUID as the uniquely identifiable name of the extension, and this UUID exists in two cases:
+
+1. the extension has been included and referenced from the EasyEDA Pro Extension Store, or the extension developer has requested a UUID for the extension and filled in the `uuid` field in `extension.json`, in this case, the UUID is an auto-generated 32-bit string, and you can find it on the Extension Store page for the extension;
+2. if the extension is not included and does not fill in the `uuid` field, then the UUID is the `name` field defined by the extension developer in `extension.json`, please be careful about using this field as the name of the extension's interdependent references as it is always variable and may be renamed.
+
+::: info
+
+If you are using [pro-api-sdk](./ancillary-projects/pro-api-sdk), a new UUID will be automatically generated for you the first time you run `npm run build`.
+
+If you wish to build the full development environment manually, you can also safely use <code id="generatedUuid"></code> as the UUID for the new extension, which is randomly generated when you visit the current page.
+
+:::
+
+All user extensions run locally on the client, which means you can write them in JavaScript according to the [ECMAScript Next](https://262.ecma-international.org/) specification, but note that in the main thread, there are limitations on accessing the DOM, external requests, local file system, and other browser APIs. However, it should be noted that in the main thread, calls to the DOM, external requests, local filesystem, and other browser APIs will be limited, and we will provide predefined interfaces in the extension APIs to address the need for this type of access.
+
+::: tip
+
+EasyEDA offers a wide range of extension examples, allowing users to view the source code and compile it for use:
+Extensions source code: [https://github.com/easyeda](https://github.com/easyeda)
+Extensions marketplace : [https://jlcext.com/](https://jlcext.com/)
+
+:::
+
+## Development Environment (Computer)
+
+In order to facilitate the environment configuration, we provide [pro-api-sdk](https://gitee.com/jlceda/pro-api-sdk), and we recommend all developers to use this SDK for development, and this document will be based on this SDK to explain. You can get and configure the SDK environment in the following ways:
+
+### I. Install Visual Studio Code
+
+Visual Studio Code is the most recommended IDE for novice developers, hereafter referred to as **VSCode**, and you can download it from its [official website](https://code.visualstudio.com/#alt-downloads).
+
+If you don't understand the difference between the versions, please download the version indicated in the figure below (Windows System Installer x64):
+
+![VS Code Windows System Installer x64](/storage/images/cn/api/guide/how-to-start/how-to-start_20240729_170651.png)
+
+### II. Install Git
+
+Git is the recommended tool for pulling SDKs, and you can download it from its [official website](https://git-scm.com/download).
+
+On the right side of the official download page, click `Download for Windows`:
+
+![Git Download for Windows](/storage/images/cn/api/guide/how-to-start/how-to-start_20240729_170746.png)
+
+### III. Install Node.js
+
+Node.js is the runtime software necessary to build TypeScript natively, and you can download it from its [official website](https://nodejs.org/en/download/prebuilt-installer).
+
+The official download page is a guided interactive page, so if you don't need it, just follow the instructions below:
+
+I want `Current` version of Node.js for `Windows` running `x64`
+
+Then click the `Download Node.js` button to download the Node.js installer.
+
+::: warning
+
+If you wish to use a customized version of Node.js, make sure it is no lower than `20.5.0`, which is the minimum version required for this project.
+
+:::
+
+::: tip
+
+You can check the version of Node.js you have installed by typing `node -v` in the console, if the version is lower than `20.5.0`, follow the steps above to install Node.js.
+
+:::
+
+### IV. Getting SDK Locally
+
+Now you can choose either of the following two ways to get the SDK, you can choose one according to your preference:
+
+::: details Initialize using npx command
+
+1. Before you start, you need to first create a subfolder on your local disc where you will keep all your development materials. For example, you can create a subfolder named `easyeda-extension` under the `D:` disc.
+
+    ::: warning
+
+    Please try not to include `spaces` `non-ASCII characters` in the path to avoid surprises in subsequent operations.
+
+    :::
+
+2. Once created, open the Windows PowerShell tool (right-click on the `Windows Logo Key` and select the `Windows PowerShell (Administrator)` option).
+
+3. Navigate within Windows PowerShell to the folder you just created, in this case the `D:\easyeda-extension` folder, and execute `cd "D:\easyeda-extension"`:
+
+    ![PowerShell cd](/storage/images/en/api/guide/how-to-start/how-to-start_20240802_154933.png)
+
+    ::: tip
+
+    The double quotes `""` here are half-width characters, and they cannot be omitted when the path contains `spaces`.
+
+    :::
+
+4. Execute the following command:
+
+    ```shell
+    npx github:easyeda/pro-api-sdk my-extension
+    ```
+
+:::
+
+::: details Initialize using git command
+
+1. Before you start, you need to first create a subfolder on your local disc where you will keep all your development materials. For example, you can create a subfolder named `easyeda-extension` under the `D:` disc.
+
+    ::: warning
+
+    Please try not to include `spaces` `non-ASCII characters` in the path to avoid surprises in subsequent operations.
+
+    :::
+
+2. Once created, open the Windows PowerShell tool (right-click on the `Windows Logo Key` and select the `Windows PowerShell (Administrator)` option).
+
+3. Navigate within Windows PowerShell to the folder you just created, in this case the `D:\easyeda-extension` folder, and execute `cd "D:\easyeda-extension"`:
+
+    ![PowerShell cd](/storage/images/en/api/guide/how-to-start/how-to-start_20240802_154933.png)
+
+    ::: tip
+
+    The double quotes `""` here cannot be omitted when the path contains `spaces`.
+
+    :::
+
+4. Depending on your network environment, execute one of the following commands:
+
+    ```shell
+    git clone --depth=1 https://github.com/easyeda/pro-api-sdk.git my-extension
+    ```
+
+:::
+
+### V. Get VS Code Extension
+
+1. First you need to start VS Code and open the folder of the project you pulled in the previous stage inside it (e.g. `D:\easyeda-extension\my-extension`).
+
+    ![VS Code Open Folder](/storage/images/en/api/guide/how-to-start/how-to-start_20240802_155144.png)
+
+2. Then switch to the Extensions page (shortcut <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>X</kbd>) and search for and install the following apps in the search box at the top:
+
+    1. `Code Spell Checker` by Street Side Software
+    2. `ESLint` by Microsoft
+    3. `EditorConfig for VS Code` by EditorConfig
+
+    ![VS Code Search Extensions](/storage/images/en/api/guide/how-to-start/how-to-start_20240802_155249.png)
+
+3. All extensions are pre-configured within the SDK and saved in their corresponding configuration files, and you don't need to do any additional configuration on them unless you understand what you're doing.
+
+## Build the First EasyEDA Professional Extension
+
+### I. List of Files
+
+The SDK comes pre-configured with all the necessary components of the development environment, so you can refer to the following list of files to see what each one does:
+
+```
+├───.husky              Auto Script Directory
+├───.vscode             VS Code Configuration File Directory
+│   ├───extensions.json Recommended Extensions
+│   └───settings.json   Extension Configuration
+├───build               Extension Pack Compilation Directory
+│   ├───dist            Extension Pack Compilation Result Directory
+│   └───packaged.ts     Compile Scripts
+├───config              ESBuild Configuration Directory
+├───dist                Compilation Results Directory
+├───iframe              IFrame Inline Frame Directory
+├───images              Extension Preview Image Directory
+│   ├───banner.png      Extension Banner Image
+│   └───logo.png        Extension Logo Image
+├───locales             Extended Multilingual Directory
+│   ├───en.json         English Language Translation File
+│   └───zh-Hans.json    Simplified Chinese Language Translation File
+├───node_modules        NPM Dependency Module Directory
+├───src                 Extension's Main Source Code Directory
+├───.edaignore          EDA Ignore File Configuration
+├───.editorconfig       Editor Base Format Configuration
+├───.eslintrc.js        ESLint Automatic Code Constraint Configuration
+├───.gitattributes      Git Attribute Configuration
+├───.gitignore          Git Ignores File Configuration
+├───.prettierignore     Prettier Ignores File Configuration
+├───.prettierrc.js      Prettier Auto Format Configuration
+├───LICENSE             Open Source License
+├───README.md           Project Introduction
+├───extension.json      EasyEDA Professional Extension Configuration
+├───package.json        NPM Package Configuration
+├───package-lock.json   NPM Package Dependency Locking Configuration
+└───tsconfig.json       TypeScript Compilation Configuration
+```
+
+### II. Extension Configuration
+
+EasyEDA Professional has a custom configuration file, i.e. `extension.json` file in the root directory of the SDK, the contents of which will be fully read by EasyEDA Professional and will be shown in the display and running process of the extension package, the following is the default contents of this file:
+
+<<< @/private/pro-api-sdk/extension.json{2,4-5,7,11 json}
+
+Now, we only need to change a few of the key values:
+
+| Property    | Type     | Example                                                 | Description                                                                                 |
+| ----------- | -------- | ------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
+| name        | `string` | `run-api-gateway`                                       | Extension name. It can only contain lowercase English letters `a-z`, digits `0-9`, and hyphens `-`, and must be `5-30` characters long. |
+| displayName | `string` | `Run API Gateway`                                       | Display name. It can be in Chinese.                                                        |
+| description | `string` | `Provides WebSocket gateway bridging for AI coding tools` | Description.                                                                                |
+| publisher   | `string` | `JLCEDA`                                                | Developer information.                                                                      |
+| license     | `string` | `Apache-2.0`                                            | Open-source licensing terms. It is recommended to go to [Choose a License](https://choosealicense.com/) to select the appropriate open source license for your project. |
+
+### III. Initialization Environment
+
+Initializing the environment and starting the build are very simple single commands, in order to execute these commands you first need to start a VS Code terminal:
+
+![New VS Code Terminal](/storage/images/en/api/guide/how-to-start/how-to-start_20240802_155359.png)
+
+The terminal will appear below by default, and you can execute all the next commands from within the terminal. Now, we need to initialize the environment for the SDK project, including installing all the dependent libraries, initializing the runtime hooks, and more things that can be automated, and you'll need to execute the following commands from within the terminal:
+
+```shell
+npm install
+```
+
+::: tip
+
+If you encounter an error like this:
+
+```
+File C:\example.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
+```
+
+You need to run the following command in PowerShell with administrator privileges:
+
+```powershell
+Set-ExecutionPolicy RemoteSigned
+```
+
+This changes the execution policy to allow script execution. It is required to run NPM via Node.js on the device, but be aware that changing the execution policy may affect the security of the system.
+
+If you are developing within an organization, you may need to consult your IT department, because the organization may have its own security policies.
+
+:::
+
+### IV. Modify the Code File
+
+In the default environment provided by the SDK, your entry code file is `/src/index.ts`.
+
+If the file has the same suffix, we highly recommend and support writing EasyEDA Pro extensions in TypeScript by default, relying on the type system provided by TypeScript and our [pro-api-types](https://www.npmjs.com/package/@jlceda/pro-api-types) type definition file, you can easily get complete support for type inference and syntax hints.
+
+::: info
+
+If you still want to code in native JavaScript, you can rename `/src/index.ts` to `/src/index.js` and remove anything inside that doesn't conform to JavaScript syntax.
+
+:::
+
+### V. Build
+
+After each code change, you should perform a build to get the latest extension package, and you may need to change the version number within the `extension.json` file before doing the build:
+
+| Property | Type     | Description                                      |
+| -------- | -------- | ------------------------------------------------ |
+| version  | `string` | Semantic version number in `major.minor.patch` format |
+
+Then, execute the following command in the terminal to build the extension package:
+
+```shell
+npm run build
+```
+
+The extension packages you build will be generated in the `/build/dist/` directory.
+
+::: tip
+
+The build will read the `.edaignore` file in the root directory, which controls what will be excluded from the package at build time, and has the same syntax as `.gitignore`.
+
+:::
+
+## Import Extensions to EasyEDA Pro
+
+The import operation currently has a different location:
+
+::: details EasyEDA Pro V2
+
+**Top Menu Bar** -\> **Settings** -\> **Extensions** -\> **Extension Manager...** -\> **Import Extensions**
+
+![Import Extension](/storage/images/cn/api/guide/how-to-start/how-to-start_20260209_133454.png)
+
+Import the `.eext` file you generated in the `/build/dist/` directory during the last build.
+
+:::
+
+::: details EasyEDA Pro V3
+
+**Top Menu Bar** -\> **Advanced** -\> **Extension Manager...** -\> **Import**
+
+![Import Extension](/storage/images/cn/api/guide/how-to-start/how-to-start_20260209_133418.png)
+
+Import the `.eext` file you generated in the `/build/dist/` directory during the last build.
+
+:::
+
+<script setup>
+    import { onMounted } from 'vue'
+    onMounted(() => {
+        document.getElementById('generatedUuid').innerHTML = crypto.randomUUID().replaceAll('-', '');
+    })
+</script>

package/skill/guide/i18n.md

@@ -0,0 +1,57 @@
+# Multi-language Support
+
+## Multi-language Configuration
+
+The extension supports multi-language configuration, you can create a `<IANA Language Tags>.json` file in the `./locales/` folder, you can create a `<IANA language tag>.json` file, which will be automatically associated with the corresponding language and called when appropriate.
+
+::: code-group
+
+```json [zh-Hans.json]
+{
+	"Enter": "确定",
+	"Cancel": "取消"
+}
+```
+
+```json [en.json]
+{
+	"Enter": "Enter",
+	"Cancel": "Cancel"
+}
+```
+
+:::
+
+If you need to get all the language labels supported by the current extension, you can call the [SYS_I18n.getAllSupportedLanguages()](../reference/pro-api.sys_i18n.getallsupportedlanguages) method, which will return an array of strings.
+
+::: warning
+
+Note that if your extension has two or more languages, it must include at least one of `en` or `zh-Hans` as a fallback language, otherwise you may encounter unexpected display errors.
+
+:::
+
+## Use of Multiple Languages within the Code
+
+To use a multilingual system to display different text in different language environments, use the [SYS_I18n.text()](../reference/pro-api.sys_i18n.text) method.
+
+[SYS_I18n.text()](../reference/pro-api.sys_i18n.text) method has a mandatory argument `tag`, which corresponds to the key name in the multilingual file, and the key value matched by that key name is the final displayed text.
+
+You can specify the `namespace` parameter as the `uuid` of other extensions to call the multilingual configuration of other extensions.
+
+Currently, EasyEDA Professional only supports a few languages by default, while the extension API supports a lot of additional languages, you can use the `language` parameter to adapt more languages for your extension, but you need to design your own logic and method to switch languages.
+
+When translating a language, it is very likely that we will encounter a situation where we need to embed parameters into the text, because the syntax of each language is different and the position of the parameters in the text of the language may vary greatly, you can use a placeholder in the `${1}` format to indicate the parameters that need to be embedded and pass the parameters into the `arg` of the [SYS_I18n.text()](../reference/pro-api.sys_i18n.text) method within `arg`, so that when the specified text is displayed, the corresponding argument will be embedded in the text at the specified location.
+
+::: tip
+
+Language priority: current display language > system default language > the first language in the dataset that contains the text tag > text label (tag)
+
+In addition to the above steps, you may need to know other [SYS_I18n](../reference/pro-api.sys_i18n) APIs to work more freely with multilingual content.
+
+:::
+
+## Translating Fields in extension.json
+
+If you need to translate fields in `extension.json`, create a `<IANA language tag>.json` file in the `./locales/extensionJson/` folder.
+
+Within that file, each `key` must be a `value` from `extension.json`, and each `value` in the translation file is the translated result.

package/skill/guide/index.md

@@ -0,0 +1,7 @@
+# What is Extension API?
+
+EasyEDA Professional Extension API (hereinafter referred to as "Extension API") is a set of JS API interfaces built on the front-end, which is used to develop various custom functions of EasyEDA Professional Editor. In short, the Extension API uses the basic syntax of JavaScript to write source code that highly encapsulates many EasyEDA Pro features and algorithms, together with a comprehensive [SDK](./ancillary-projects/pro-api-sdk), [type constraints](./ancillary-projects/pro-api-types), the development of custom extensions can be completed with very little effort, effectively reducing the mental burden on developers and designers.
+
+Next, you can go to the [How to Get Started](./how-to-start) section to learn how to install the environment from scratch and build your own EasyEDA Pro Edition extension.
+
+If you are an extension user, see the [Getting and Using Extensions](../user-guide/using-extension) section.

package/skill/guide/inline-frame.md

@@ -0,0 +1,20 @@
+# Inline Frame Support
+
+In some application scenarios where extensions want to have fully customized windows that are not limited to the popups and controls provided by EasyEDA, we provide a way to build windows using inline frames.
+
+To use inline frames, you need to save all files in the extension's `/iframe/` directory and use [SYS_IFrame.openIFrame()](../reference/pro-api.sys_iframe.openiframe) method to load the specified `html` file as the content of the inline frame.
+
+```typescript
+// This example loads the index.html file in the /iframe/ directory with a window of 500px in height and width
+eda.sys_IFrame.openIFrame('/iframe/index.html', 500, 500);
+```
+
+::: tip
+Files can be loaded and indexed without being stored in the `/iframe/` directory, but it is recommended that the `/iframe/` directory be used as the storage directory for inline frame files for a more intuitive organization of the files.
+
+The URI referred to by the `htmlFileName` parameter starts at the root path of the extension package, you can use `/` or start directly with the `iframe/` folder name.
+:::
+
+The extension API will automatically read the specified `html` file and other files associated with it, but will not continue to recursively parse it, due to the limitations of our secure resource access rules.
+
+To open multiple IFrame windows within a single extension, specify an ID for each IFrame.