@modootoday/pmcp 0.13.1 → 0.14.0

package/plugins/vite-7/skills/vite/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: vite
+description: Develop and diagnose Vite 7 applications, including React integration, environment variables, asset base paths, production builds and development server lifecycle. Keep Vite 7's Rollup/esbuild configuration separate from Vite 8's Rolldown/Oxc configuration.
+---
+
+# Vite 7 application workflows
+
+Read the installed Vite, Node and plugin versions first. Vite 7 requires Node
+20.19+ or 22.12+. The fixture uses Vite 7.3.6 with @vitejs/plugin-react 5.2.0;
+plugin-react 6 requires Vite 8 and must not be added to a Vite 7 configuration.
+
+## Configure the existing application
+
+Preserve the project's framework plugin, entry HTML and package manager. Vite
+transforms TypeScript syntax but does not perform application typechecking; run
+the project's TypeScript check separately.
+
+```ts
+import { defineConfig } from "vite";
+import react from "@vitejs/plugin-react";
+
+export default defineConfig({
+  plugins: [react()],
+  base: "/app/",
+  build: { target: "es2022" },
+});
+```
+
+Use base for the deployment prefix and verify the built HTML's asset references.
+Do not fix a subpath deployment by hardcoding asset paths throughout components.
+Import assets from application modules when they belong to the build graph; use
+public for files that need their original filename and are copied without bundling.
+
+## Environment and security boundaries
+
+Client code reads import.meta.env. VITE_-prefixed variables are exposed to client
+code and must contain public data only. Values are strings except Vite's built-in
+boolean properties. Changing envPrefix or define can expose additional values;
+do not serialize process.env into a browser bundle.
+
+Mode selects the .env files, while NODE_ENV has a different responsibility.
+Restart the dev server after changing environment files. Test the selected mode
+and production artifact instead of relying on a value seen in a development tab.
+
+## Build, preview and development lifecycle
+
+Use the existing scripts for vite, vite build and vite preview. A preview server
+checks the built application and is not the production web server. Validate the
+application's runtime through its actual browser test runner when behavior,
+accessibility or CSS layout changes.
+
+Programmatic integration must own shutdown:
+
+```ts
+import { createServer } from "vite";
+
+const server = await createServer({
+  server: { host: "127.0.0.1", port: 0, open: false },
+});
+
+try {
+  await server.listen();
+  await server.transformRequest("/src/main.tsx");
+} finally {
+  await server.close();
+}
+```
+
+Use transformIndexHtml in a custom HTML-serving integration so plugin-injected
+scripts, including React's Fast Refresh initialization, are present. Serving the
+original index.html unchanged bypasses this integration.
+
+When running build and dev APIs in one owned process, instantiate plugins
+separately for each configuration. Build resolution can set NODE_ENV to production
+and plugins can retain command-specific state. Restore the intended development
+environment explicitly before creating the dev server and restore the caller's
+environment afterward; changing mode alone does not reset NODE_ENV.
+
+## Diagnose by stage
+
+- Dev succeeds but build fails: inspect build inputs, import resolution, target
+  and Rollup plugin behavior. Do not assume the development dependency optimizer
+  establishes production compatibility.
+- Build succeeds but deployment loses assets: check base, server routing and the
+  produced asset URLs before changing component paths.
+- JSX appears untransformed or Refresh fails: inspect the React plugin, file
+  include filters and transformed HTML. Keep component exports compatible with
+  Fast Refresh instead of disabling updates globally.
+- Types fail but the bundle works: fix the TypeScript project and declaration
+  boundaries; Vite does not replace the compiler check.
+
+Vite 7 uses build.rollupOptions and esbuild-oriented transformation settings.
+Keep Vite 8 migration choices separate. The fixture checks a production build,
+public-variable replacement, base-aware assets, development TSX transformation,
+Refresh HTML injection and shutdown. It does not prove browser rendering or SSR.
+The API fixture disables file watching with server.watch set to null, disables
+dependency discovery and uses an empty optimization include list after framework
+configuration. It does not validate file-change HMR or dependency pre-bundling,
+or claim that these settings are suitable for a browser application. CommonJS
+dependencies normally need optimization during development.
+
+## Sources
+
+- [Vite 7 getting started](https://v7.vite.dev/guide/)
+- [Vite 7 environment variables](https://v7.vite.dev/guide/env-and-mode)
+- [Vite 7 production builds](https://v7.vite.dev/guide/build)
+- [Vite 7 JavaScript API](https://v7.vite.dev/guide/api-javascript)
+- [Dependency optimization options](https://vite.dev/config/dep-optimization-options)
+- [Server file watching](https://vite.dev/config/server-options#server-watch)
+- [Plugin configuration hooks](https://vite.dev/guide/api-plugin#config)
+- [Vite React plugin](https://github.com/vitejs/vite-plugin-react/tree/main/packages/plugin-react)

package/plugins/vite-8/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "vite-8",
+  "version": "8.0.1",
+  "description": "Build React applications with Vite 8 and verify public environment and preview behavior.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/vite-8/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor’s trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion
+of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that
+organization. **control** means ownership of substantially all the assets of an
+entity, or the power to direct its management and policies by vote, contract, or
+otherwise. Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.

package/plugins/vite-8/NOTICE

@@ -0,0 +1,51 @@
+pmcp
+
+Copyright (c) 2026 modootoday. All rights reserved.
+
+Licensor: modootoday
+Licensed under the Elastic License 2.0; see LICENSE.
+
+The licensor is modootoday, the company, not any individual contributor. This
+file names the licensor because the Elastic License 2.0 defines that term rather
+than carrying a copyright line of its own; LICENSE is kept unmodified.
+
+What the licence permits, in short, without replacing the terms in LICENSE:
+
+  - Using this software inside your own company, on any scale.
+  - Embedding it in a product you sell, and modifying or forking it.
+  - Redistributing it, with these notices intact.
+  - Running it locally as an MCP server, which is what it is for. A host
+    process spawning it on your own machine is use, not a hosted service.
+
+What it does not permit:
+
+  - Offering this software to third parties as a hosted or managed service.
+    A remotely hosted MCP endpoint serving other people is the case this
+    forbids.
+  - Circumventing licence key functionality.
+  - Removing or obscuring these notices.
+
+The Elastic License 2.0 is source-available, not an OSI-approved open source
+licence. It grants a patent licence and ends that licence if you assert a patent
+claim against the software; see the Patents section of LICENSE.
+
+LICENSE governs. Where this summary and LICENSE differ, LICENSE is what applies.
+
+---
+
+This software depends on the following packages, which are distributed under
+their own terms and are not covered by the licence above.
+
+  @modelcontextprotocol/server   MIT   Copyright (c) Anthropic, PBC
+  @modelcontextprotocol/core     MIT   Copyright (c) Anthropic, PBC
+  zod                            MIT   Copyright (c) Colin McDonnell
+  semver                         ISC   See the dependency's LICENSE file.
+  smol-toml              BSD-3-Clause   Copyright (c) Squirrel Chat et al.
+  yaml                           ISC   Copyright Eemeli Aro
+
+Full licence texts and copyright notices ship with those packages. Their
+respective licence terms govern distribution of those dependencies.
+
+@huggingface/transformers is an optional peer dependency. It is never
+distributed with this package; a user who wants semantic ranking installs it
+themselves, under its own Apache-2.0 terms.

package/plugins/vite-8/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "vite-8", "version": "8.0.1" }

package/plugins/vite-8/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "vite-8",
+  "version": "8.0.1",
+  "description": "Build React applications with Vite 8 and verify public environment and preview behavior.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/vite-8/skills/vite/SKILL.md

@@ -0,0 +1,267 @@
+---
+name: vite
+description: Develop and diagnose Vite 8 applications with React integration, environment variables, asset base paths and owned dev-server lifecycle. Maintain Rolldown/Oxc configuration and distinguish production builds from standalone programmatic API checks.
+---
+
+Verified against vite@8.2.2 on 2026-09-07. 4 of 4 examples executed.
+
+Those four checks exercise standalone API examples. The application fixture
+separately exercises a build and development server; a successful import or
+configuration helper does not prove an application builds or renders correctly.
+
+# Vite 8 (`^8.0.0`)
+
+Use this skill when writing code against Vite 8's npm API. Vite 8 requires Node `20.19+` or `22.12+`, and uses Rolldown and Oxc instead of Rollup and esbuild.
+
+## Application workflow
+
+Read the installed Vite, Node and framework-plugin versions. Use the project's
+package manager and existing scripts. The fixture pairs Vite 8.2.2 with
+@vitejs/plugin-react 6.1.1, React/React DOM 19.2.8 and Tailwind 4.3.3.
+Do not migrate an existing Vite 7 app merely because this guide covers Vite 8.
+
+```ts
+import { defineConfig } from "vite";
+import react from "@vitejs/plugin-react";
+
+export default defineConfig({
+  plugins: [react()],
+  base: "/app/",
+});
+```
+
+Vite removes TypeScript syntax without application typechecking. Keep the
+project's TypeScript check. Use base to model a deployment prefix and inspect the
+generated HTML's asset URLs. A development server's optimizer and a production
+build are different stages; validate both when changing dependency or plugin
+resolution. Vite preview checks build output and is not a production web server.
+
+VITE_-prefixed environment variables become public browser data. Keep credentials
+outside that prefix, and never define the entire process.env object in a client
+bundle. Mode selects environment files; NODE_ENV is a separate setting. Restart
+the development server when environment files change and verify production
+replacement rather than assuming development values persist.
+
+For custom HTML serving, run transformIndexHtml so framework plugin initialization
+is included. Programmatic consumers must close every dev or preview server in a
+finally block. Bind a fixture to loopback and leave automatic browser opening off.
+The application fixture checks TSX build, base-aware assets, environment exposure,
+React Refresh HTML initialization, Tailwind generation and server shutdown. It
+does not prove browser layout, interactive HMR or SSR behavior.
+
+For sequential build/dev API calls in one owned process, create fresh plugin
+instances for each configuration. Build resolution can retain production
+NODE_ENV and plugin state. Set the intended development environment before dev
+server creation and restore the caller's environment afterward; mode is not a
+reset of NODE_ENV.
+
+## Programmatic API
+
+Import API functions from `vite` in a plain Node/Bun script. The documented APIs include:
+
+- `createServer(inlineConfig?)`: asynchronously creates a development server.
+- `build(inlineConfig?)`: performs a production build and returns Rolldown output or a watcher.
+- `preview(inlineConfig?)`: asynchronously creates a preview server.
+- `resolveConfig(inlineConfig, command, defaultMode?, defaultNodeEnv?, isPreview?)`.
+- `mergeConfig(defaults, overrides, isRoot?)`.
+- `loadEnv(mode, envDir, prefixes?)`.
+- `transformWithOxc(code, filename, options?, inMap?)`.
+- `preprocessCSS(code, filename, config)`.
+- `normalizePath(id)`.
+
+`createServer` returns a server exposing APIs including `listen`, `close`, `transformRequest`, `transformIndexHtml`, `ssrLoadModule`, `reloadModule`, and inspection of its config, middleware, HTTP server, watcher, WebSocket server, plugin container, module graph, and resolved URLs. A server can also print URLs and bind CLI shortcuts after listening.
+
+`preview` returns a preview server exposing its config, middleware, HTTP server, resolved URLs, `printUrls()`, and `bindCLIShortcuts(...)`.
+
+`build()` throws a Vite 8 `BundleError` on failure. It is an `Error` with an optional `.errors` array containing individual `RolldownError` values.
+
+## Configuration utilities
+
+`mergeConfig` accepts object-form configuration. Use it for merging defaults and overrides rather than assuming it accepts a config function.
+
+`loadEnv(mode, envDir, prefixes)` loads matching `.env` variables. Its default prefix is `VITE_`; pass a string or array when using other prefixes.
+
+`resolveConfig` takes an inline config plus a command of `'build'` or `'serve'`. Its optional parameters select the default mode, default `NODE_ENV`, and preview mode.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import { mergeConfig } from "vite";
+
+const result = mergeConfig(
+  { server: { port: 3000 }, define: { A: "1" } },
+  { server: { strictPort: true }, define: { B: "2" } },
+);
+
+assert.equal(result.server.port, 3000);
+assert.equal(result.server.strictPort, true);
+assert.equal(result.define.A, "1");
+assert.equal(result.define.B, "2");
+```
+
+## Oxc JavaScript/TypeScript transforms
+
+Use `transformWithOxc` for standalone JavaScript or TypeScript transformation. It returns the transformed result and exposes warnings separately; the returned shape omits the Oxc `errors` field and includes `warnings`.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import { transformWithOxc } from "vite";
+
+const result = await transformWithOxc(
+  "const answer: number = 42",
+  "example.ts",
+);
+
+assert.equal(typeof result.code, "string");
+assert.equal(result.warnings.length, 0);
+assert.match(result.code, /42/);
+```
+
+## CSS preprocessing
+
+`preprocessCSS(code, filename, config)` handles CSS and supported preprocessor filenames including `.css`, `.scss`, `.sass`, `.less`, `.styl`, and `.stylus`. The corresponding preprocessor must be installed for preprocessor syntaxes. Supply a resolved Vite config.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import { preprocessCSS, resolveConfig } from "vite";
+
+const config = await resolveConfig({}, "serve");
+const result = await preprocessCSS(
+  "body { color: red; }",
+  "example.css",
+  config,
+);
+
+assert.equal(typeof result.code, "string");
+assert.match(result.code, /color:\s*red/);
+```
+
+## Path normalization
+
+`normalizePath` is a standalone helper for normalizing plugin paths. Do not assume it converts backslashes in every environment; on the environment used here, a path that is already slash-normalized is preserved.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import { normalizePath } from "vite";
+
+const normalized = normalizePath("src/components/Button.tsx");
+assert.equal(normalized, "src/components/Button.tsx");
+```
+
+## Dev and preview servers
+
+Create a development server with `createServer`, then call `listen()` yourself. The documented pattern is:
+
+```ts
+import { createServer } from "vite";
+
+const server = await createServer({
+  configFile: false,
+  root: import.meta.dirname,
+  server: { port: 1337 },
+});
+await server.listen();
+server.printUrls();
+server.bindCLIShortcuts({ print: true });
+```
+
+Use `server.close()` when the script is finished. The server API also provides request transformation, HTML transformation, SSR module loading, and module reloading.
+
+Create a preview server with `preview(inlineConfig)`. Its documented pattern is:
+
+```ts
+import { preview } from "vite";
+
+const previewServer = await preview({
+  preview: { port: 8080, open: false },
+});
+previewServer.printUrls();
+previewServer.bindCLIShortcuts({ print: true });
+```
+
+These APIs start HTTP servers and require an owning tool to manage listening, ports, and shutdown. They are described here but are not exercised by the standalone examples because those examples run without network access.
+
+The separate API fixture uses a loopback server with server.watch set to null,
+automatic dependency discovery disabled and an empty optimization include list
+after framework configuration. It verifies HTML injection, TSX transformation
+and actual server shutdown, not file-change HMR, dependency pre-bundling or
+browser execution. Do not copy that optimizer configuration into a browser
+application with CommonJS dependencies.
+See [dependency optimization options](https://vite.dev/config/dep-optimization-options)
+and [server file watching](https://vite.dev/config/server-options#server-watch).
+The [plugin config hook](https://vite.dev/guide/api-plugin#config) can clear an
+include list when ordinary merging preserves framework-injected dependencies.
+
+## Production builds
+
+Call `build(inlineConfig)` for a production build. The documented inline configuration can specify `root`, `base`, and `build.rolldownOptions`:
+
+```ts
+import path from "node:path";
+import { build } from "vite";
+
+await build({
+  root: path.resolve(import.meta.dirname, "./project"),
+  base: "/foo/",
+  build: {
+    rolldownOptions: {
+      // Rolldown options
+    },
+  },
+});
+```
+
+Catch the thrown error as a Vite 8 bundle error and inspect `.errors` when present. A real build also requires a project input, so it is not exercised by the standalone examples, which cannot use filesystem setup.
+
+## Vite 8 configuration migration
+
+Prefer Rolldown/Oxc names:
+
+```ts
+export default {
+  build: { rolldownOptions: {} },
+  worker: { rolldownOptions: {} },
+};
+```
+
+Older Vite 7 examples commonly use `build.rollupOptions` and `worker.rollupOptions`. They remain deprecated aliases in Vite 8, so new code should use the Rolldown names.
+
+Other migration rules:
+
+- `optimizeDeps.esbuildOptions` is deprecated compatibility input and is converted to `optimizeDeps.rolldownOptions`.
+- `esbuild` configuration is converted to Oxc configuration.
+- `build.commonjsOptions` is a no-op.
+- `transformWithEsbuild` is deprecated; use `transformWithOxc`.
+- `esbuild` is optional and must be installed separately if a plugin still calls `transformWithEsbuild`.
+- The object form of `build.rollupOptions.output.manualChunks` is unsupported; the function form is deprecated. Use Rolldown `codeSplitting` instead.
+- `build.rollupOptions.watch.chokidar` was removed; use `build.rolldownOptions.watch.watcher`.
+- The URL form of `import.meta.hot.accept` was removed; pass an id instead.
+- Rolldown does not support the `system` or `amd` output formats, `shouldTransformCachedModule`, `resolveImportMeta`, `renderDynamicImport`, or `resolveFileUrl`.
+
+## CLI and config-file scope
+
+Automatic config discovery, `vite.config.js`/`.ts`, `--config`, `vite`, `vite dev`, `vite serve`, and `vite build` are runner/CLI behavior rather than standalone API calls. Config files can use either an object or `defineConfig`, for example:
+
+```ts
+import { defineConfig } from "vite";
+
+export default defineConfig({
+  // configuration
+});
+```
+
+By default, Vite bundles a config with Rolldown into a temporary file; `--configLoader native` selects native loading.
+
+## Not covered
+
+This skill does not cover framework SSR integration, plugin authoring, the complete
+ResolvedConfig or Rolldown type definitions, browser layout or React Compiler
+adoption. Use the application's actual browser and framework checks for those
+boundaries.
+
+## Sources
+
+- [Vite getting started](https://vite.dev/guide/)
+- [Environment variables](https://vite.dev/guide/env-and-mode)
+- [Production builds](https://vite.dev/guide/build)
+- [JavaScript API](https://vite.dev/guide/api-javascript)
+- [Vite 7 to 8 migration](https://vite.dev/guide/migration)

package/plugins/vitejs-plugin-react-5/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "vitejs-plugin-react-5",
+  "version": "5.0.0",
+  "description": "Configure React transformation with the supported Vite major and verify production output.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/vitejs-plugin-react-5/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor’s trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion
+of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that
+organization. **control** means ownership of substantially all the assets of an
+entity, or the power to direct its management and policies by vote, contract, or
+otherwise. Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.