Clean up for review

* fix: clear scene and bust cache if rust panics

* fix: pr clean up

* fix: huh? cargo fmt doesn't do this?

.codespellrc

@@ -1,3 +1,4 @@
 [codespell]
 ignore-words-list: crate,everytime,inout,co-ordinate,ot,nwo,atleast,ue,afterall,ser,fromM,FromM
-skip: **/target,node_modules,build,dist,./out,**/Cargo.lock,./docs/kcl/*.md,./e2e/playwright/lib/console-error-whitelist.ts,.package-lock.json,**/package-lock.json,./openapi/*.json,./packages/codemirror-lang-kcl/test/all.test.ts,./public/kcl-samples,./rust/kcl-lib/tests/kcl_samples,tsconfig.tsbuildinfo,./src/lib/machine-api.d.ts
+skip: **/target,node_modules,build,dist,./out,**/Cargo.lock,./docs/**/*.md,./e2e/playwright/lib/console-error-whitelist.ts,.package-lock.json,**/package-lock.json,./openapi/*.json,./packages/codemirror-lang-kcl/test/all.test.ts,./public/kcl-samples,./rust/kcl-lib/tests/kcl_samples,tsconfig.tsbuildinfo,./src/lib/machine-api.d.ts,./test-results,./playwright-report,./kcl-book/book
+

.env.development

@@ -1,3 +1,5 @@
+# DO NOT commit secrets, overrides go in the ignored `.env.development.local`
+
 NODE_ENV=development
 DEV=true
 
@@ -7,7 +9,11 @@ VITE_KC_SITE_BASE_URL=https://dev.zoo.dev
 VITE_KC_SITE_APP_URL=https://app.dev.zoo.dev
 VITE_KC_SKIP_AUTH=false
 VITE_KC_CONNECTION_TIMEOUT_MS=5000
-# ONLY add your token in .env.development.local if you want to skip auth, otherwise this token takes precedence!
-#VITE_KC_DEV_TOKEN="your token from dev.zoo.dev should go in .env.development.local"
+#VITE_KC_DEV_TOKEN="optional token to skip auth in the app"
+#token="required token for playwright. TODO: clean up env vars in #3973"
+
+RUST_BACKTRACE=1
+PYO3_PYTHON=/usr/local/bin/python3
+#KITTYCAD_API_TOKEN="required token for engine testing"
 
 FAIL_ON_CONSOLE_ERRORS=true

.eslintrc.json

@@ -87,6 +87,14 @@
       {
         "selector": "CallExpression[callee.object.name='TOML'][callee.property.name='parse']",
         "message": "Do not use TOML.parse directly. Use the wrappers in test-utils instead like tomlToSettings."
+      },
+      {
+        "selector": "CallExpression[callee.property.name='split'] > Literal[value='/']",
+        "message": "Avoid using split with '/'."
+      },
+      {
+        "selector": "CallExpression[callee.property.name='join'] > Literal[value='/']",
+        "message": "Avoid using join with '/'."
       }
     ],
     "no-restricted-imports": [

.github/ci-cd-scripts/upload-results.sh

@@ -0,0 +1,41 @@
+#!/bin/bash
+set -euo pipefail
+
+if [ -z "${TAB_API_URL:-}" ] || [ -z "${TAB_API_KEY:-}" ]; then
+    exit 0
+fi
+
+project="https://github.com/KittyCAD/modeling-app"
+branch="${GITHUB_HEAD_REF:-${GITHUB_REF_NAME:-}}"
+commit="${CI_COMMIT_SHA:-${GITHUB_SHA:-}}"
+
+echo "Uploading batch results"
+curl --silent --request POST \
+  --header "X-API-Key: ${TAB_API_KEY}" \
+  --form "project=${project}" \
+  --form "branch=${branch}" \
+  --form "commit=${commit}" \
+  --form "tests=@test-results/junit.xml" \
+  --form "CI_COMMIT_SHA=${CI_COMMIT_SHA:-}" \
+  --form "CI_PR_NUMBER=${CI_PR_NUMBER:-}" \
+  --form "GITHUB_BASE_REF=${GITHUB_BASE_REF:-}" \
+  --form "GITHUB_EVENT_NAME=${GITHUB_EVENT_NAME:-}" \
+  --form "GITHUB_HEAD_REF=${GITHUB_HEAD_REF:-}" \
+  --form "GITHUB_REF_NAME=${GITHUB_REF_NAME:-}" \
+  --form "GITHUB_REF=${GITHUB_REF:-}" \
+  --form "GITHUB_SHA=${GITHUB_SHA:-}" \
+  --form "GITHUB_WORKFLOW=${GITHUB_WORKFLOW:-}" \
+  --form "RUNNER_ARCH=${RUNNER_ARCH:-}" \
+  ${TAB_API_URL}/api/results/bulk
+
+echo
+echo "Sharing updated report"
+curl --silent --request POST \
+  --header "Content-Type: application/json" \
+  --header "X-API-Key: ${TAB_API_KEY}" \
+  --data "{
+    \"project\": \"${project}\",
+    \"branch\": \"${branch}\",
+    \"commit\": \"${commit}\"
+  }" \
+  ${TAB_API_URL}/api/share

.github/workflows/build-apps.yml

@@ -7,11 +7,10 @@ on:
       - main
     tags:
       - 'v[0-9]+.[0-9]+.[0-9]+'
-      - 'nightly-v[0-9]+.[0-9]+.[0-9]+'
 
 env:
   IS_RELEASE: ${{ github.ref_type == 'tag' && startsWith(github.ref_name, 'v') }}
-  IS_NIGHTLY: ${{ github.ref_type == 'tag' && startsWith(github.ref_name, 'nightly-v') }}
+  IS_STAGING: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }}
 
 concurrency:
   group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }}
@@ -92,12 +91,16 @@ jobs:
         if: ${{ steps.wasm.outputs.should-build-wasm == 'true' }}
         run: "npm run build:wasm"
 
-      - name: Set nightly version, product name, release notes, and icons
-        if: ${{ env.IS_NIGHTLY == 'true' }}
+      - name: Set staging version, product name, release notes, and icons
+        if: ${{ env.IS_STAGING == 'true' }}
         run: |
-          export VERSION=${GITHUB_REF_NAME#nightly-v}
+          COMMIT=$(git rev-parse --short HEAD)
+          DATE=$(date +'%-y.%-m.%-d')
+          # TODO: add commit count today on main
+          OFFSET=$(date +'%H%M')
+          export VERSION=$DATE-staging.$OFFSET+$COMMIT
           npm run files:set-version
-          npm run files:flip-to-nightly
+          npm run files:flip-to-staging
 
       - name: Set release version
         if: ${{ env.IS_RELEASE == 'true' }}
@@ -117,7 +120,7 @@ jobs:
             assets/icon.png
 
       - id: export_version
-        run: echo "version=`cat package.json | jq -r '.version'`" >> "$GITHUB_OUTPUT"
+        run: echo "version=`cat package.json | jq -r '.version' | cut -f1 -d"+"`" >> "$GITHUB_OUTPUT"
 
       - id: export_notes
         run: echo "notes=`cat release-notes.md`" >> "$GITHUB_OUTPUT"
@@ -177,7 +180,7 @@ jobs:
       - run: npm install
 
       - name: Prepare certificate and variables (Windows only)
-        if: ${{ (env.IS_RELEASE == 'true' || env.IS_NIGHTLY == 'true') && matrix.os == 'windows-2022' }}
+        if: ${{ (env.IS_RELEASE == 'true' || env.IS_STAGING == 'true') && matrix.os == 'windows-2022' }}
         run: |
           echo "${{secrets.SM_CLIENT_CERT_FILE_B64 }}" | base64 --decode > /d/Certificate_pkcs12.p12
           cat /d/Certificate_pkcs12.p12
@@ -192,7 +195,7 @@ jobs:
         shell: bash
 
       - name: Setup certicate with SSM KSP (Windows only)
-        if: ${{ (env.IS_RELEASE == 'true' || env.IS_NIGHTLY == 'true') && matrix.os == 'windows-2022' }}
+        if: ${{ (env.IS_RELEASE == 'true' || env.IS_STAGING == 'true') && matrix.os == 'windows-2022' }}
         run: |
           curl -X GET  https://one.digicert.com/signingmanager/api-ui/v1/releases/smtools-windows-x64.msi/download -H "x-api-key:%SM_API_KEY%" -o smtools-windows-x64.msi
           msiexec /i smtools-windows-x64.msi /quiet /qn
@@ -201,22 +204,17 @@ jobs:
           C:\Windows\System32\certutil.exe -csp "DigiCert Signing Manager KSP" -key -user
           smksp_cert_sync.exe
           smctl windows certsync
-        # This last line `smctl windows certsync` was added after windows codesign failures started happening
-        # with nightly-v25.4.10. It looks like `smksp_cert_sync.exe` used to do the sync to the local cert store,
-        # but stopped doing it overnight. This extra call that I randomly got from this azure-related doc page
-        # https://docs.digicert.com/en/digicert-keylocker/code-signing/sign-with-third-party-signing-tools/windows-applications/sign-azure-apps-with-signtool-using-ksp-library.html#sync-certificates--windows-only--618365
-        # seems to be doing that extra sync that we need for scripts/sign-win.js to work.
         # TODO: we still need to make sign-win.js errors fail the workflow, see issue #6276
         shell: cmd
 
       - name: Build the app (debug)
-        if: ${{ env.IS_RELEASE == 'false' && env.IS_NIGHTLY == 'false' }}
+        if: ${{ env.IS_RELEASE == 'false' && env.IS_STAGING == 'false' }}
         # electron-builder doesn't have a concept of release vs debug,
         # this is just not doing any codesign or release yml generation, and points to dev infra
         run: npm run tronb:package:dev
 
       - name: Build the app (release)
-        if: ${{ env.IS_RELEASE == 'true' || env.IS_NIGHTLY == 'true' }}
+        if: ${{ env.IS_RELEASE == 'true' || env.IS_STAGING == 'true' }}
         env:
           APPLE_ID: ${{ secrets.APPLE_ID }}
           APPLE_PASSWORD: ${{ secrets.APPLE_PASSWORD }}
@@ -226,7 +224,7 @@ jobs:
           CSC_KEY_PASSWORD: ${{ secrets.APPLE_CERTIFICATE_PASSWORD }}
           CSC_KEYCHAIN: ${{ secrets.APPLE_SIGNING_IDENTITY }}
           WINDOWS_CERTIFICATE_THUMBPRINT: ${{ secrets.WINDOWS_CERTIFICATE_THUMBPRINT }}
-        run: npm run tronb:package:prod
+        run: npm run tronb:package:${{ env.IS_RELEASE == 'true' && 'prod' || 'dev' }}
 
       - name: List artifacts in out/
         run: ls -R out
@@ -250,13 +248,13 @@ jobs:
             out/*-x86_64-linux.*
 
       - uses: actions/upload-artifact@v4
-        if: ${{ env.IS_RELEASE == 'true' || env.IS_NIGHTLY == 'true' }}
+        if: ${{ env.IS_RELEASE == 'true' || env.IS_STAGING == 'true' }}
         with:
           name: out-yml-${{ matrix.platform }}
           path: |
             out/latest*.yml
 
-      # TODO: add the 'Build for Mac TestFlight (nightly)' stage back
+      # TODO: add the 'Build for Mac TestFlight' stage back
 
       # The steps below are for updater-test builds, only on release
 
@@ -306,7 +304,8 @@ jobs:
     runs-on: ubuntu-22.04
     permissions:
       contents: write
-    if: ${{ github.ref_type == 'tag' }}
+    # Equivalent to IS_RELEASE || IS_STAGING (but we can't access those env vars here)
+    if: ${{ github.ref_type == 'tag' || (github.event_name == 'push' && github.ref == 'refs/heads/main') }}
     env:
       VERSION_NO_V: ${{ needs.prepare-files.outputs.version }}
       VERSION: ${{ format('v{0}', needs.prepare-files.outputs.version) }}
@@ -363,8 +362,8 @@ jobs:
         env:
           NOTES: ${{ needs.prepare-files.outputs.notes }}
           PUB_DATE: ${{ github.event.repository.updated_at }}
-          WEBSITE_DIR: ${{ env.IS_NIGHTLY == 'true' && 'dl.zoo.dev/releases/modeling-app/nightly' || 'dl.zoo.dev/releases/modeling-app' }}
-          URL_CODED_NAME: ${{ env.IS_NIGHTLY == 'true' && 'Zoo%20Design%20Studio%20%28Nightly%29' || 'Zoo%20Design%20Studio' }}
+          WEBSITE_DIR: ${{ env.IS_STAGING == 'true' && 'dl.zoo.dev/releases/modeling-app/staging' || 'dl.zoo.dev/releases/modeling-app' }}
+          URL_CODED_NAME: ${{ env.IS_STAGING == 'true' && 'Zoo%20Design%20Studio%20%28Staging%29' || 'Zoo%20Design%20Studio' }}
         run: |
           RELEASE_DIR=https://${WEBSITE_DIR}
           jq --null-input \
@@ -412,38 +411,27 @@ jobs:
       - name: List artifacts
         run: "ls -R out"
 
-      - name: Set more complete nightly release notes
-        if: ${{ env.IS_NIGHTLY == 'true' }}
-        run: |
-          # Note: preferred going this way instead of a full clone in the checkout step,
-          # see https://github.com/actions/checkout/issues/1471
-          git fetch --prune --unshallow --tags
-          export TAG="nightly-${VERSION}"
-          export PREVIOUS_TAG=$(git tag --list --sort=-committerdate "nightly-v[0-9]*" | head -n2 | tail -n1)
-          export NOTES=$(./scripts/get-nightly-changelog.sh)
-          npm run files:set-notes
-
       - name: Authenticate to Google Cloud
-        if: ${{ env.IS_NIGHTLY == 'true' }}
+        if: ${{ env.IS_STAGING == 'true' }}
         uses: 'google-github-actions/auth@v2.1.8'
         with:
           credentials_json: '${{ secrets.GOOGLE_CLOUD_DL_SA }}'
 
       - name: Set up Google Cloud SDK
-        if: ${{ env.IS_NIGHTLY == 'true' }}
+        if: ${{ env.IS_STAGING == 'true' }}
         uses: google-github-actions/setup-gcloud@v2.1.4
         with:
           project_id: ${{ env.GOOGLE_CLOUD_PROJECT_ID }}
 
-      - name: Upload nightly files to public bucket
-        if: ${{ env.IS_NIGHTLY == 'true' }}
+      - name: Upload staging files to public bucket
+        if: ${{ env.IS_STAGING == 'true' }}
         uses: google-github-actions/upload-cloud-storage@v2.2.2
         with:
           path: out
           glob: '*'
           parent: false
-          destination: 'dl.kittycad.io/releases/modeling-app/nightly'
+          destination: 'dl.kittycad.io/releases/modeling-app/staging'
 
       - name: Invalidate bucket cache on latest*.yml and last_download.json files
-        if: ${{ env.IS_NIGHTLY == 'true' }}
-        run: npm run files:invalidate-bucket:nightly
+        if: ${{ env.IS_STAGING == 'true' }}
+        run: npm run files:invalidate-bucket:staging

.github/workflows/cargo-test.yml

@@ -2,7 +2,6 @@ on:
   push:
     branches:
       - main
-
   pull_request:
   workflow_dispatch:
 permissions:
@@ -84,7 +83,7 @@ jobs:
         run: |
           set -euo pipefail
           cd rust
-          cargo nextest run --workspace --features artifact-graph --retries=2 --no-fail-fast --profile ci simulation_tests::kcl_samples 2>&1 | tee /tmp/github-actions.log
+          cargo nextest run --workspace --features artifact-graph --retries=10 --no-fail-fast --profile ci simulation_tests::kcl_samples 2>&1 | tee /tmp/github-actions.log
         env:
           KITTYCAD_API_TOKEN: ${{secrets.KITTYCAD_API_TOKEN_DEV}}
           ZOO_HOST: https://api.dev.zoo.dev
@@ -99,9 +98,7 @@ jobs:
           popd
           git add \
             rust/kcl-lib/tests \
-            public/kcl-samples/manifest.json \
-            public/kcl-samples/README.md \
-            public/kcl-samples/screenshots
+            public/kcl-samples
           git config --local user.email "github-actions[bot]@users.noreply.github.com"
           git config --local user.name "github-actions[bot]"
           git remote set-url origin https://${{ github.actor }}:${{ secrets.GITHUB_TOKEN }}@github.com/${{ github.repository }}.git
@@ -131,7 +128,6 @@ jobs:
         with:
           name: nextest-archive
           path: rust/nextest-archive.tar.zst
-
   run-test-artifacts:
     name: cargo test (shard ${{ matrix.partitionIndex}})
     runs-on:
@@ -179,11 +175,55 @@ jobs:
           cp nextest-archive.tar.zst rust/nextest-archive.tar.zst
           ls -lah
           cd rust
-          cargo nextest run\
-           --retries=2 --no-fail-fast -P ci --archive-file nextest-archive.tar.zst \
+          cargo nextest run \
+           --retries=10 --no-fail-fast --profile=ci --archive-file nextest-archive.tar.zst \
            --partition count:${{ matrix.partitionIndex}}/${{ matrix.partitionTotal }} \
            2>&1 | tee /tmp/github-actions.log
         env:
           KITTYCAD_API_TOKEN: ${{secrets.KITTYCAD_API_TOKEN_DEV}}
           ZOO_HOST: https://api.dev.zoo.dev
-
+      - name: Upload results
+        if: always()
+        run: .github/ci-cd-scripts/upload-results.sh
+        env:
+          TAB_API_URL: ${{ secrets.TAB_API_URL }}
+          TAB_API_KEY: ${{ secrets.TAB_API_KEY }}
+          CI_COMMIT_SHA: ${{ github.event.pull_request.head.sha }}
+          CI_PR_NUMBER: ${{ github.event.pull_request.number }}
+  run-wasm-tests:
+    name: Run wasm tests
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+      fail-fast: false
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+      - name: Use correct Rust toolchain
+        shell: bash
+        run: |
+          [ -e rust-toolchain.toml ] || cp rust/rust-toolchain.toml ./
+      - name: Install rust
+        uses: actions-rust-lang/setup-rust-toolchain@v1
+        with:
+          cache: false # Configured below.
+      - uses: taiki-e/install-action@d4635f2de61c8b8104d59cd4aede2060638378cc
+        with:
+          tool: wasm-pack
+      - name: Rust Cache
+        uses: Swatinem/rust-cache@v2
+        with:
+          workspaces: './rust'
+      - name: Build Wasm
+        shell: bash
+        run: |
+          npm install
+          npm run build:wasm
+      - name: Run wasm tests
+        run: |
+          cd rust
+          cd kcl-wasm-lib
+          #wasm-pack test --headless --chrome
+        env:
+          KITTYCAD_API_TOKEN: ${{ secrets.KITTYCAD_API_TOKEN_DEV }}
+          NODE_ENV: development

.github/workflows/e2e-tests.yml

@@ -229,7 +229,6 @@ jobs:
           max_attempts: 5
         env:
           token: ${{ secrets.KITTYCAD_API_TOKEN_DEV }}
-          snapshottoken: ${{ secrets.KITTYCAD_API_TOKEN }}
           TAB_API_URL: ${{ secrets.TAB_API_URL }}
           TAB_API_KEY: ${{ secrets.TAB_API_KEY }}
           CI_COMMIT_SHA: ${{ github.event.pull_request.head.sha }}

.github/workflows/generate-website-docs.yml

@@ -38,17 +38,13 @@ jobs:
         run: |
           mkdir -p documentation/content/pages/docs/kcl/
           # cleanup old
-          rm -rf documentation/content/pages/docs/kcl/*.md
-          rm -rf documentation/content/pages/docs/kcl/types
-          rm -rf documentation/content/pages/docs/kcl/functions
-          rm -rf documentation/content/pages/docs/kcl/consts
+          rm -rf documentation/content/pages/docs/kcl-std
+          rm -rf documentation/content/pages/docs/kcl-lang
           # move new
-          mv -f docs/kcl/*.md documentation/content/pages/docs/kcl/
-          mv -f docs/kcl/types documentation/content/pages/docs/kcl/
-          mv -f docs/kcl/functions documentation/content/pages/docs/kcl/
-          mv -f docs/kcl/consts documentation/content/pages/docs/kcl/
+          mv -f docs/kcl-std documentation/content/pages/docs
+          mv -f docs/kcl-lang documentation/content/pages/docs
           # We don't need the README
-          rm documentation/content/pages/docs/kcl/README.md
+          rm documentation/content/pages/docs/kcl-std/README.md
       - name: move kcl-samples
         shell: bash
         run: |

.github/workflows/static-analysis.yml

@@ -171,13 +171,8 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v4
-      - name: Set up Python
-        uses: actions/setup-python@v5
-      - name: Install codespell
-        run: |
-            python -m pip install codespell
       - name: Run codespell
-        run: codespell --config .codespellrc # Edit this file to tweak the typo list and other configuration.
+        uses: crate-ci/typos@v1.32.0
 
   npm-unit-test-kcl-samples:
     runs-on: ubuntu-latest

.github/workflows/tag-nightly.yml

@@ -1,39 +0,0 @@
-name: tag-nightly
-
-permissions:
-  contents: write
-on:
-  schedule:
-    - cron: '0 4 * * *'
-  # Daily at 04:00 AM UTC
-  # Will checkout the last commit from the default branch (main as of 2023-10-04)
-  
-jobs:
-  tag-nightly:
-    runs-on: ubuntu-22.04
-    steps:
-      - uses: actions/create-github-app-token@v1
-        id: app-token
-        with:
-          app-id: ${{ secrets.MODELING_APP_GH_APP_ID }}
-          private-key: ${{ secrets.MODELING_APP_GH_APP_PRIVATE_KEY }}
-          owner: ${{ github.repository_owner }}
-
-      - uses: actions/checkout@v4
-        with:
-          token: ${{ steps.app-token.outputs.token }}
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version-file: '.nvmrc'
-
-      - run: npm install
-
-      - name: Push tag
-        run: |
-          VERSION_NO_V=$(date +'%-y.%-m.%-d')
-          TAG="nightly-v$VERSION_NO_V"
-          git config --local user.email "github-actions[bot]@users.noreply.github.com"
-          git config --local user.name "github-actions[bot]"
-          git tag $TAG
-          git push origin tag $TAG

CONTRIBUTING.md

@@ -63,7 +63,7 @@ If you're not a Zoo employee you won't be able to access the dev environment, yo
 
 ### Development environment variables
 
-The Copilot LSP plugin in the editor requires a Zoo API token to run. In production, we authenticate this with a token via cookie in the browser and device auth token in the desktop environment, but this token is inaccessible in the dev browser version because the cookie is considered "cross-site" (from `localhost` to `dev.zoo.dev`). There is an optional environment variable called `VITE_KC_DEV_TOKEN` that you can populate with a dev token in a `.env.development.local` file to not check it into Git, which will use that token instead of other methods for the LSP service.
+The Copilot LSP plugin in the editor requires a Zoo API token to run. In production, we authenticate this with a token via cookie in the browser and device auth token in the desktop environment, but this token is inaccessible in the dev browser version because the cookie is considered "cross-site" (from `localhost` to `zoo.dev`). There is an optional environment variable called `VITE_KC_DEV_TOKEN` that you can populate with a dev token in a `.env.development.local` file to not check it into Git, which will use that token instead of other methods for the LSP service.
 
 ### Developing in Chrome
 
@@ -97,7 +97,7 @@ The following will need to be run when checking out a new commit and guarantees
 ```bash
 npm install
 npm run build:wasm
-npm start # or npm run build:local && npm run serve for slower but more production-like build
+npm start
 ```
 
 ## Before submitting a PR
@@ -198,15 +198,9 @@ For more information on fuzzing you can check out
 
 ### Playwright tests
 
-You will need a `./e2e/playwright/playwright-secrets.env` file:
+Prepare these system dependencies:
 
-```bash
-$ touch ./e2e/playwright/playwright-secrets.env
-$ cat ./e2e/playwright/playwright-secrets.env
-token=<dev.zoo.dev/account/api-tokens>
-snapshottoken=<zoo.dev/account/api-tokens>
-```
-or use `export` to set the environment variables `token` and `snapshottoken`.
+- Set $token from https://zoo.dev/account/api-tokens
 
 #### Snapshot tests (Google Chrome on Ubuntu only)
 
@@ -300,131 +294,17 @@ Which will run our suite of [Vitest unit](https://vitest.dev/) and [React Testin
 
 ### Rust tests
 
-**Dependencies**
+Prepare these system dependencies:
 
-- `KITTYCAD_API_TOKEN`
-- `cargo-nextest`
-- `just`
+- Set `$KITTYCAD_API_TOKEN` from https://zoo.dev/account/api-tokens
+- Install `just` following [these instructions](https://just.systems/man/en/packages.html)
 
-#### Setting KITTYCAD_API_TOKEN
-
-Use the production zoo.dev token, set this environment variable before running the tests
-
-#### Installing cargonextest
+then run tests that target the KCL language:
 
 ```
-cd rust
-cargo search cargo-nextest
-cargo install cargo-nextest
+npm run test:rust
 ```
 
-#### just
-
-install [`just`](https://github.com/casey/just?tab=readme-ov-file#pre-built-binaries)
-
-#### Running the tests
-
-```bash
-# With just
-# Make sure KITTYCAD_API_TOKEN=<prod zoo.dev token> is set
-# Make sure you installed cargo-nextest
-# Make sure you installed just
-cd rust
-just test
-```
-
-```bash
-# Without just
-# Make sure KITTYCAD_API_TOKEN=<prod zoo.dev token> is set
-# Make sure you installed cargo-nextest
-cd rust
-export RUST_BRACKTRACE="full" && cargo nextest run --workspace --test-threads=1
-```
-
-Where `XXX` is an API token from the production engine (NOT the dev environment).
-
-We recommend using [nextest](https://nexte.st/) to run the Rust tests (its faster and is used in CI). Once installed, run the tests using
-
-```
-cd rust
-KITTYCAD_API_TOKEN=XXX cargo run nextest
-```
-
-### Mapping CI CD jobs to local commands
-
-When you see the CI CD fail on jobs you may wonder three things
-
-- Do I have a bug in my code?
-- Is the test flaky?
-- Is there a bug in `main`?
-
-To answer these questions the following commands will give you confidence to locate the issue.
-
-#### Static Analysis
-
-Part of the CI CD pipeline performs static analysis on the code. Use the following commands to mimic the CI CD jobs.
-
-The following set of commands should get us closer to one and done commands to instantly retest issues.
-
-```
-npm run test-setup
-```
-
-> Gotcha, are packages up to date and is the wasm built?
-
-```
-npm run tsc
-npm run fmt:check
-npm run lint
-npm run test:unit:local
-```
-
-> Gotcha: Our unit tests have integration tests in them. You need to run a localhost server to run the unit tests.
-
-#### E2E Tests
-
-**Playwright Electron**
-
-These E2E tests run in electron. There are tests that are skipped if they are ran in a windows, linux, or macos environment. We can use playwright tags to implement test skipping.
-
-```
-npm run test:playwright:electron:local
-npm run test:playwright:electron:windows:local
-npm run test:playwright:electron:macos:local
-npm run test:playwright:electron:ubuntu:local
-```
-
-> Why does it say local? The CI CD commands that run in the pipeline cannot be ran locally. A single command will not properly setup the testing environment locally.
-
-#### Some notes on CI
-
-The tests are broken into snapshot tests and non-snapshot tests, and they run in that order, they automatically commit new snap shots, so if you see an image commit check it was an intended change. If we have non-determinism in the snapshots such that they are always committing new images, hopefully this annoyance makes us fix them asap, if you notice this happening let Kurt know. But for the odd occasion `git reset --hard HEAD~ && git push -f` is your friend.
-
-How to interpret failing playwright tests?
-If your tests fail, click through to the action and see that the tests failed on a line that includes `await page.getByTestId('loading').waitFor({ state: 'detached' })`, this means the test fail because the stream never started. It's you choice if you want to re-run the test, or ignore the failure.
-
-We run on ubuntu and macos, because safari doesn't work on linux because of the dreaded "no RTCPeerConnection variable" error. But linux runs first and then macos for the same reason that we limit the number of parallel tests to 1 because we limit stream connections per user, so tests would start failing we if let them run together.
-
-If something fails on CI you can download the artifact, unzip it and then open `playwright-report/data/<UUID>.zip` with https://trace.playwright.dev/ to see what happened.
-
-#### Getting started writing a playwright test in our app
-
-Besides following the instructions above and using the playwright docs, our app is weird because of the whole stream thing, which means our testing is weird. Because we've just figured out this stuff and therefore docs might go stale quick here's a 15min vid/tutorial
-
-https://github.com/KittyCAD/modeling-app/assets/29681384/6f5e8e85-1003-4fd9-be7f-f36ce833942d
-
-<details>
-
-<summary>
-PS: for the debug panel, the following JSON is useful for snapping the camera
-</summary>
-
-```JSON
-{"type":"modeling_cmd_req","cmd_id":"054e5472-e5e9-4071-92d7-1ce3bac61956","cmd":{"type":"default_camera_look_at","center":{"x":15,"y":0,"z":0},"up":{"x":0,"y":0,"z":1},"vantage":{"x":30,"y":30,"z":30}}}
-```
-
-</details>
-
 ### Logging
 
 To display logging (to the terminal or console) set `ZOO_LOG=1`. This will log some warnings and simple performance metrics. To view these in test runs, use `-- --nocapture`.

Makefile

@@ -1,5 +1,5 @@
 .PHONY: all
-all: install build check
+all: install check build
 
 ###############################################################################
 # INSTALL
@@ -49,14 +49,9 @@ REACT_SOURCES := $(wildcard src/*.tsx) $(wildcard src/**/*.tsx)
 TYPESCRIPT_SOURCES := tsconfig.* $(wildcard src/*.ts) $(wildcard src/**/*.ts)
 VITE_SOURCES := $(wildcard vite.*) $(wildcard vite/**/*.tsx)
 
+
 .PHONY: build
-build: build-web build-desktop
-
-.PHONY: build-web
-build-web: install public/kcl_wasm_lib_bg.wasm build/index.html
-
-.PHONY: build-desktop
-build-desktop: install public/kcl_wasm_lib_bg.wasm .vite/build/main.js
+build: install public/kcl_wasm_lib_bg.wasm .vite/build/main.js
 
 public/kcl_wasm_lib_bg.wasm: $(CARGO_SOURCES) $(RUST_SOURCES)
 ifdef WINDOWS
@@ -65,9 +60,6 @@ else
 	npm run build:wasm:dev
 endif
 
-build/index.html: $(REACT_SOURCES) $(TYPESCRIPT_SOURCES) $(VITE_SOURCES)
-	npm run build:local
-
 .vite/build/main.js: $(REACT_SOURCES) $(TYPESCRIPT_SOURCES) $(VITE_SOURCES)
 	npm run tronb:vite:dev
 
@@ -95,11 +87,11 @@ TARGET ?= desktop
 run: run-$(TARGET)
 
 .PHONY: run-web
-run-web: install build-web ## Start the web app
+run-web: install build ## Start the web app
 	npm run start
 
 .PHONY: run-desktop
-run-desktop: install build-desktop ## Start the desktop app
+run-desktop: install build ## Start the desktop app
 	npm run tron:start
 
 ###############################################################################
@@ -114,6 +106,7 @@ test: test-unit test-e2e
 
 .PHONY: test-unit
 test-unit: install ## Run the unit tests
+	npm run test:rust
 	@ curl -fs localhost:3000 >/dev/null || ( echo "Error: localhost:3000 not available, 'make run-web' first" && exit 1 )
 	npm run test:unit
 
@@ -121,7 +114,7 @@ test-unit: install ## Run the unit tests
 test-e2e: test-e2e-$(TARGET)
 
 .PHONY: test-e2e-web
-test-e2e-web: install build-web ## Run the web e2e tests
+test-e2e-web: install build ## Run the web e2e tests
 	@ curl -fs localhost:3000 >/dev/null || ( echo "Error: localhost:3000 not available, 'make run-web' first" && exit 1 )
 ifdef E2E_GREP
 	npm run chrome:test -- --headed --grep="$(E2E_GREP)" --max-failures=$(E2E_FAILURES)
@@ -130,7 +123,7 @@ else
 endif
 
 .PHONY: test-e2e-desktop
-test-e2e-desktop: install build-desktop ## Run the desktop e2e tests
+test-e2e-desktop: install build ## Run the desktop e2e tests
 ifdef E2E_GREP
 	npm run test:playwright:electron -- --grep="$(E2E_GREP)" --max-failures=$(E2E_FAILURES)
 else

README.md

@@ -42,8 +42,6 @@ The 3D view in Design Studio is just a video stream from our hosted geometry eng
 
 We recommend downloading the latest application binary from our [releases](https://github.com/KittyCAD/modeling-app/releases) page. If you don't see your platform or architecture supported there, please file an issue.
 
-If you'd like to try out upcoming changes sooner, you can also download those from our [nightly releases](https://zoo.dev/modeling-app/download/nightly) page.
-
 ## Developing
 
 Finally, if you'd like to run a development build or contribute to the project, please visit our [contributor guide](CONTRIBUTING.md) to get started.

_typos.toml

@@ -0,0 +1,39 @@
+[files]
+extend-exclude = [
+  "**/target",
+  "node_modules",
+  "build",
+  "dist",
+  "out",
+  "**/Cargo.lock",
+  "docs/**/*.md",
+  "docs/**/*.json",
+  "e2e/playwright/lib/console-error-whitelist.ts",
+  ".package-lock.json",
+  "**/package-lock.json",
+  "openapi/*.json",
+  "packages/codemirror-lang-kcl/test/all.test.ts",
+  "public/kcl-samples",
+  "rust/kcl-lib/tests/kcl_samples",
+  "tsconfig.tsbuildinfo",
+  "src/lib/machine-api.d.ts",
+  "kcl-book/book",
+]
+
+[default.extend-words]
+metalness = "metalness" # appearance API 
+Hom = "Hom" # short for homogenous
+typ = "typ" # used to declare a variable named 'type' which is a reserved keyword in Rust
+ue = "ue" # short for UnaryExpression
+THRE = "THRE" # Weird bug that wrongly detects THREEjs as a typo
+nwo = "nwo" # don't know what this is about tbh
+"ot" = "ot" # some abbreviation, idk what
+"oe" = "oe" # some abbreviation, idk what
+
+[default]
+extend-ignore-identifiers-re = [
+    "\\dnd", # e.g. 2nd
+]
+extend-ignore-re = [
+  "@xstate-layout .*",
+]

docs/kcl-lang/arithmetic.md

@@ -0,0 +1,53 @@
+---
+title: "Arithmetic and logic"
+excerpt: "Documentation of the KCL language for the Zoo Design Studio."
+layout: manual
+---
+
+KCL supports the usual arithmetic operators on numbers and logic operators on booleans:
+
+| Operator | Meaning |
+|----------|---------|
+| `+` | Addition |
+| `-` | Subtraction or unary negation |
+| `*` | Multiplication |
+| `/` | Division |
+| `%` | Modulus aka remainder |
+| `^` | Power, e.g., `x ^ 2` means `x` squared |
+| `&` | Logical 'and' |
+| `|` | Logical 'or' |
+| `!` | Unary logical 'not' |
+
+KCL also supports comparsion operators which operate on numbers and produce booleans:
+
+| Operator | Meaning |
+|----------|---------|
+| `==` | Equal |
+| `!=` | Not equal |
+| `<` | Less than |
+| `>` | Greater than |
+| `<=` | Less than or equal |
+| `>=` | Greater than or equal |
+
+Arithmetics and logic expressions can be arbitrairly combined with the usual rules of associativity and precedence, e.g.,
+
+```
+myMathExpression = 3 + 1 * 2 / 3 - 7
+```
+
+You can also nest expressions in parenthesis:
+
+```
+myMathExpression = 3 + (1 * 2 / (3 - 7))
+```
+
+KCL numbers are implemented using [floating point numbers](https://en.wikipedia.org/wiki/Floating-point_arithmetic). This means that there are occasionally representation and rounding issues, and some oddities such as supporting positive and negative zero.
+
+Some operators can be applied to other types:
+
+- `+` can be used to concatenate strings, e.g., `'hello' + ' ' + 'world!'`
+- Unary `-` can be used with planes or line-like objects such as axes to produce an object with opposite orientation, e.g., `-XY` is a plain which is aligned with `XY` but whose normal aligns with the negative Z axis.
+- The following operators can be used with solids as shorthand for CSG operations:
+  - `+` or `|` for [`union`](/docs/kcl-std/union).
+  - `-` for [`subtract`](/docs/kcl-std/subtract).
+  - `&` for [`intersect`](/docs/kcl-std/intersect)

docs/kcl-lang/attributes.md

@@ -0,0 +1,30 @@
+---
+title: "Attributes"
+excerpt: "Documentation of the KCL language for the Zoo Design Studio."
+layout: manual
+---
+
+Attributes are syntax which affects the language item they annotate. In KCL they are indicated using `@`. For example, `@settings` affects the file in which it appears.
+
+There are two kinds of attributes: named and unnamed attributes. Named attributes (e.g., `@settings`) have a name immediately after the `@` (e.g., `settings`) and affect their surrounding scope. Unnamed attributes have no name and affect the following item, e.g.,
+
+```kcl,norun
+@(lengthUnit = ft, coords = opengl)
+import "tests/inputs/cube.obj"
+```
+
+has an unnamed attribute on the `import` statement.
+
+Named and unnamed attributes may take a parenthesized list of arguments (like a function). Named attributes may also appear without any arguments (e.g., `@no_std`).
+
+## Named attributes
+
+The `@settings` attribute affects the current file and accepts the following arguments: `defaultLengthUnit`, `defaultAngleUnit`, and `kclVersion`. See [settings](/docs/kcl-lang/settings) for details.
+
+The `@no_std` attribute affects the current file, takes no arguments, and causes the standard library to not be implicitly available. It can still be used by being explicitly imported.
+
+## Unnamed attributes
+
+Unnamed attributes may be used on `import` statements when importing non-KCL files. See [projects, modules, and imports](/docs/kcl-lang/modules) for details.
+
+Other unnamed attributes are used on functions inside the standard library, but these are not available in user code.

docs/kcl-lang/foreign-imports.md

@@ -0,0 +1,99 @@
+---
+title: "Importing geometry from other CAD systems"
+excerpt: "Documentation of the KCL language for the Zoo Design Studio."
+layout: manual
+---
+
+`import` can also be used to import files from other CAD systems. The format of the statement is the
+same as for KCL files. You can only import the whole file, not items from it. E.g.,
+
+```norun
+import "tests/inputs/cube.obj"
+
+// Use `cube` just like a KCL object.
+```
+
+```kcl
+import "tests/inputs/cube.sldprt" as cube
+
+// Use `cube` just like a KCL object.
+```
+
+For formats lacking unit data (such as STL, OBJ, or PLY files), the default
+unit of measurement is millimeters. Alternatively you may specify the unit
+by using an attribute. Likewise, you can also specify a coordinate system. E.g.,
+
+```kcl
+@(lengthUnit = ft, coords = opengl)
+import "tests/inputs/cube.obj"
+```
+
+When importing a GLTF file, the bin file will be imported as well.
+
+Import paths are relative to the current project directory. Imports currently only work when
+using the native Design Studio, not in the browser.
+
+### Supported values
+
+File formats: `fbx`, `gltf`/`glb`, `obj`+, `ply`+, `sldprt`, `step`/`stp`, `stl`+. (Those marked with a
+'+' support customising the length unit and coordinate system).
+
+Length units: `mm` (the default), `cm`, `m`, `inch`, `ft`, `yd`.
+
+Coordinate systems:
+
+- `zoo` (the default), forward: -Y, up: +Z, handedness: right
+- `opengl`, forward: +Z, up: +Y, handedness: right
+- `vulkan`, forward: +Z, up: -Y, handedness: left
+
+---
+
+## Performance deep‑dive for foreign‑file imports
+
+Parallelized foreign‑file imports now let you overlap file reads, initialization,
+and rendering. To maximize throughput, you need to understand the three distinct
+stages—reading, initializing (background render start), and invocation (blocking)
+—and structure your code to defer blocking operations until the end.
+
+### Foreign import execution stages
+
+1. **Import (Read / Initialization) Stage**
+   ```kcl
+   import "tests/inputs/cube.step" as cube
+   ```
+   - Reads the file from disk and makes its API available.
+   - Starts engine rendering but **does not block** your script.
+   - This kick‑starts the render pipeline while you keep executing other code.
+
+2. **Invocation (Blocking) Stage**
+   ```kcl
+   import "tests/inputs/cube.step" as cube
+
+   cube
+     |> translate(z=10) // ← blocks here only
+   ```
+   - Any method call (e.g., `translate`, `scale`, `rotate`) waits for the background render to finish before applying transformations.
+
+### Best practices
+
+#### 1. Defer blocking calls
+
+```kcl
+import "tests/inputs/cube.step" as cube     // 1) Read / Background render starts
+
+
+// --- perform other operations and calculations here ---
+
+
+cube
+  |> translate(z=10)                        // 2) Blocks only here
+```
+
+#### 2. Split heavy work into separate modules
+
+Place computationally expensive or IO‑heavy work into its own module so it can render in parallel while `main.kcl` continues.
+
+#### Future improvements
+
+Upcoming releases will auto‑analyse dependencies and only block when truly necessary. Until then, explicit deferral will give you the best performance.
+

docs/kcl-lang/functions.md

@@ -0,0 +1,46 @@
+---
+title: "Functions"
+excerpt: "Documentation of the KCL language for the Zoo Design Studio."
+layout: manual
+---
+
+We have support for defining your own functions. Functions can take in any
+type of argument. Below is an example of the syntax:
+
+```
+fn myFn(x) {
+  return x
+}
+```
+
+As you can see above `myFn` just returns whatever it is given.
+
+KCL uses keyword arguments:
+
+```
+// If you declare a function like this
+fn add(left, right) {
+  return left + right
+}
+
+// You can call it like this:
+total = add(left = 1, right = 2)
+```
+
+Functions can also declare one *unlabeled* arg. If you do want to declare an unlabeled arg, it must
+be the first arg declared.
+
+```
+// The @ indicates an argument is used without a label.
+// Note that only the first argument can use @.
+fn increment(@x) {
+  return x + 1
+}
+
+fn add(@x, delta) {
+  return x + delta
+}
+
+two = increment(1)
+three = add(1, delta = 2)
+```

docs/kcl-lang/index.md

@@ -0,0 +1,21 @@
+---
+title: "KCL Language Reference"
+excerpt: "Documentation of the KCL language for the Zoo Design Studio."
+layout: manual
+---
+
+This is a reference for KCL. If you are learning KCL, you may prefer the [guide]() which explains
+things in a more tutorial fashion. See also our documentation of the [standard library](/docs/kcl-std).
+
+## Topics
+
+* [Pipelines](/docs/kcl-lang/pipelines)
+* [Arithmetic and logic](/docs/kcl-lang/arithmetic)
+* [Values and types](/docs/kcl-lang/types)
+* [Numeric types and units](/docs/kcl-lang/numeric)
+* [Functions](/docs/kcl-lang/functions)
+* [Projects and modules](/docs/kcl-lang/modules)
+* [Attributes](/docs/kcl-lang/attributes)
+* [Importing geometry from other CAD systems](/docs/kcl-lang/foreign-imports)
+* [Settings](/docs/kcl-lang/settings)
+* [Known Issues](/docs/kcl-lang/known-issues)

docs/kcl-lang/known-issues.md

@@ -1,5 +1,5 @@
 ---
-title: "KCL Known Issues"
+title: "Known Issues"
 excerpt: "Known issues with the KCL standard library for the Zoo Design Studio."
 layout: manual
 ---
@@ -15,12 +15,6 @@ once fixed in engine will just start working here with no language changes.
 - **Import**: Right now you can import a file, even if that file has brep data
     you cannot edit it, after v1, the engine will account for this. 
 
-- **Fillets**: Fillets cannot intersect, you will get an error. Only simple fillet
-    cases work currently.
-
-- **Chamfers**: Chamfers cannot intersect, you will get an error. Only simple
-    chamfer cases work currently.
-
 - **Appearance**: Changing the appearance on a loft does not work. 
 
 - **CSG Booleans**: Coplanar (bodies that share a plane) unions, subtractions, and intersections are not currently supported.

docs/kcl-lang/modules.md

@@ -1,6 +1,6 @@
 ---
-title: "KCL Modules"
-excerpt: "Documentation of modules for the KCL language for the Zoo Design Studio."
+title: "Projects and modules"
+excerpt: "Documentation of the KCL language for the Zoo Design Studio."
 layout: manual
 ---
 
@@ -264,102 +264,3 @@ cube
 clone(cube)
   |> translate(x=20)
 ```
-
----
-
-## Importing files from other CAD systems
-
-`import` can also be used to import files from other CAD systems. The format of the statement is the
-same as for KCL files. You can only import the whole file, not items from it. E.g.,
-
-```norun
-import "tests/inputs/cube.obj"
-
-// Use `cube` just like a KCL object.
-```
-
-```kcl
-import "tests/inputs/cube.sldprt" as cube
-
-// Use `cube` just like a KCL object.
-```
-
-For formats lacking unit data (such as STL, OBJ, or PLY files), the default
-unit of measurement is millimeters. Alternatively you may specify the unit
-by using an attribute. Likewise, you can also specify a coordinate system. E.g.,
-
-```kcl
-@(lengthUnit = ft, coords = opengl)
-import "tests/inputs/cube.obj"
-```
-
-When importing a GLTF file, the bin file will be imported as well.
-
-Import paths are relative to the current project directory. Imports currently only work when
-using the native Design Studio, not in the browser.
-
-### Supported values
-
-File formats: `fbx`, `gltf`/`glb`, `obj`+, `ply`+, `sldprt`, `step`/`stp`, `stl`+. (Those marked with a
-'+' support customising the length unit and coordinate system).
-
-Length units: `mm` (the default), `cm`, `m`, `inch`, `ft`, `yd`.
-
-Coordinate systems:
-
-- `zoo` (the default), forward: -Y, up: +Z, handedness: right
-- `opengl`, forward: +Z, up: +Y, handedness: right
-- `vulkan`, forward: +Z, up: -Y, handedness: left
-
----
-
-## Performance deep‑dive for foreign‑file imports
-
-Parallelized foreign‑file imports now let you overlap file reads, initialization,
-and rendering. To maximize throughput, you need to understand the three distinct
-stages—reading, initializing (background render start), and invocation (blocking)
-—and structure your code to defer blocking operations until the end.
-
-### Foreign import execution stages
-
-1. **Import (Read / Initialization) Stage**
-   ```kcl
-   import "tests/inputs/cube.step" as cube
-   ```
-   - Reads the file from disk and makes its API available.
-   - Starts engine rendering but **does not block** your script.
-   - This kick‑starts the render pipeline while you keep executing other code.
-
-2. **Invocation (Blocking) Stage**
-   ```kcl
-   import "tests/inputs/cube.step" as cube
-
-   cube
-     |> translate(z=10) // ← blocks here only
-   ```
-   - Any method call (e.g., `translate`, `scale`, `rotate`) waits for the background render to finish before applying transformations.
-
-### Best practices
-
-#### 1. Defer blocking calls
-
-```kcl
-import "tests/inputs/cube.step" as cube     // 1) Read / Background render starts
-
-
-// --- perform other operations and calculations here ---
-
-
-cube
-  |> translate(z=10)                        // 2) Blocks only here
-```
-
-#### 2. Split heavy work into separate modules
-
-Place computationally expensive or IO‑heavy work into its own module so it can render in parallel while `main.kcl` continues.
-
-#### Future improvements
-
-Upcoming releases will auto‑analyse dependencies and only block when truly necessary. Until then, explicit deferral will give you the best performance.
-
-

docs/kcl-lang/numeric.md

@@ -0,0 +1,48 @@
+---
+title: "Numeric types and units"
+excerpt: "Documentation of the KCL language for the Zoo Design Studio."
+layout: manual
+---
+
+Numbers and numeric types in KCL include information about the units of the numbers. So rather than just having a number like `42`, we always have information about the units so we don't confuse 42 mm with 42 inches.
+
+
+## Numeric literals
+
+When writing a number literal, you can use a unit suffix to explicitly state the unit, e.g., `42mm`. The following units are available:
+
+- Length units:
+  - metric: `mm`, `cm`, `m`
+  - imperial: `in`, `ft`, `yd`
+- Angle units: `deg`, `rad`
+- `_` to indicate a unitless number such as a count or ratio.
+
+If you write a numeric literal without a suffix, then the defaults for the current file are used. These defaults are specified using the `@settings` attribute, see [settings](/docs/kcl-lang/settings) for details. Note that if using the defaults, the KCL interpreter won't know whether you intend the number to be a length, angle, or count and will treat it as being possibly any of them.
+
+
+## Numeric types
+
+Just like numbers carry units information, the `number` type also includes units information. Units are written in parentheses after the type, e.g., `number(mm)`.
+
+Any of the suffixes described above can be used meaning that values with that type have the supplied units. E.g., `number(mm)` is the type of number values with mm units and `number(_)` is the type of number values with no units.
+
+You can also use `number(Length)`, `number(Angle)`, or `number(Count)`. These types mean a number with any length, angle, or unitless (count) units, respectively (note that `number(_)` and `number(Count)` are equivalent since there is only one kind of unitless-ness).
+
+Using just `number` means accepting any kind of number, even where the units are unknown by KCL.
+
+
+## Function calls
+
+When calling a function with an argument with numeric type, the declared numeric type in the function signature and the units of the argument value used in the function call must be compatible. Units are adjusted automatically. For example, if a function requires an argument with type `number(mm)`, then you can call it with `2in` and the units will be automatically adjusted, but calling it with `90deg` will cause an error.
+
+
+## Mixing units with arithmetic
+
+When doing arithmetic or comparisons, units will be adjusted as necessary if possible. However, often arithmetic expressions exceed the ability of KCL to accurately choose units which can result in warnings in your code or sometimes errors. In these cases, you will need to give KCL more information. Sometimes this can be done by making units explicit using suffixes. If not, then you will need to use *type ascription*, which asserts that an expression has the supplied type. For example, `(x * y): number(mm)` tells KCL that the units of `x * y` is mm. Note that type ascription does not do any adjustment of the numbers, e.g., `2mm: number(in)` has the value `2in` (note that this would be a very non-idiomatic way to use numeric type ascription, you could simply write `2in`. Usually type ascription is only necessary for supplying type information about the result of computation).
+
+KCL has no support for area, volume, or other higher dimension units. When internal unit tracking requires multiple dimensions, KCL essentially gives up. This is usually where the extra type information described above is needed. If doing computation with higher dimensioned units, you must ensure that all adjustments occur before any computation. E.g., if you want to compute an area with unknown units, you must convert all numbers to the same unit before starting.
+
+
+## Explicit conversions
+
+You might sometimes need to convert from one unit to another for some calculation. You can do this implicitly when calling a function (see above), but if you can't or don't want to, then you can use the explicit conversion functions in the [`std::units`](/docs/kcl-std/modules/std-units) module.

docs/kcl-lang/pipelines.md

@@ -0,0 +1,66 @@
+---
+title: "Pipelines"
+excerpt: "Documentation of the KCL language for the Zoo Design Studio."
+layout: manual
+---
+
+It can be hard to read repeated function calls, because of all the nested brackets.
+
+```norun
+i = 1
+x = h(g(f(i)))
+```
+
+You can make this easier to read by breaking it into many declarations, but that is a bit annoying.
+
+```norun
+i  = 1
+x0 = f(i)
+x1 = g(x0)
+x  = h(x1)
+```
+
+Instead, you can use the pipeline operator (`|>`) to simplify this.
+
+Basically, `x |> f(%)` is a shorthand for `f(x)`. The left-hand side of the `|>` gets put into
+the `%` in the right-hand side.
+
+So, this means `x |> f(%) |> g(%)` is shorthand for `g(f(x))`. The code example above, with its
+somewhat-clunky `x0` and `x1` constants could be rewritten as
+
+```norun
+i = 1
+x = i
+  |> f(%)
+  |> g(%)
+  |> h(%)
+```
+
+This helps keep your code neat and avoid unnecessary declarations.
+
+## Pipelines and keyword arguments
+
+Say you have a long pipeline of sketch functions, like this:
+
+```norun
+startSketchOn(XZ)
+  |> line(%, end = [3, 4])
+  |> line(%, end = [10, 10])
+  |> line(%, end = [-13, -14])
+  |> close(%)
+```
+
+In this example, each function call outputs a sketch, and it gets put into the next function call via
+the `%`, into the first (unlabeled) argument.
+
+If a function call uses an unlabeled first parameter, it will default to `%` if it's not given. This
+means that `|> line(%, end = [3, 4])` and `|> line(end = [3, 4])` are equivalent! So the above
+could be rewritten as 
+
+```norun
+startSketchOn(XZ)
+ |> line(end = [3, 4])
+ |> line(end = [10, 10])
+ |> line(end = [-13, -14])
+ |> close()
+```

docs/kcl-lang/settings.md

@@ -1,6 +1,6 @@
 ---
-title: "KCL Settings"
-excerpt: "Documentation of settings for the KCL language and Zoo Design Studio."
+title: "Settings"
+excerpt: "Documentation of the KCL language for the Zoo Design Studio."
 layout: manual
 ---
 
@@ -8,16 +8,16 @@ layout: manual
 
 There are three levels of settings available in Zoo Design Studio:
 
-1. [User Settings](/docs/kcl/settings-user): Global settings that apply to all projects, stored in `user.toml`
-2. [Project Settings](/docs/kcl/settings-project): Settings specific to a project, stored in `project.toml`
+1. [User Settings](/docs/kcl-lang/settings/user): Global settings that apply to all projects, stored in `user.toml`
+2. [Project Settings](/docs/kcl-lang/settings/project): Settings specific to a project, stored in `project.toml`
 3. Per-file Settings: Settings that apply to a single KCL file, specified using the `@settings` attribute
 
 ## Configuration Files
 
 Zoo Design Studio uses TOML files for configuration:
 
-* **User Settings**: `user.toml` - See [complete documentation](/docs/kcl/settings-user)
-* **Project Settings**: `project.toml` - See [complete documentation](/docs/kcl/settings-project)
+* **User Settings**: `user.toml` - See [complete documentation](/docs/kcl-lang/settings/user)
+* **Project Settings**: `project.toml` - See [complete documentation](/docs/kcl-lang/settings/project)
 
 ## Per-file settings
 

docs/kcl-lang/types.md

@@ -1,6 +1,6 @@
 ---
-title: "KCL Types"
-excerpt: "Documentation of types for the KCL standard library for the Zoo Design Studio."
+title: "Values and types"
+excerpt: "Documentation of the KCL language for the Zoo Design Studio."
 layout: manual
 ---
 
@@ -52,131 +52,6 @@ their internal components. See the [modules and imports docs](modules) for more
 detail on importing geometry.
 
 
-## Binary expressions
-
-You can also do math! Let's show an example below:
-
-```
-myMathExpression = 3 + 1 * 2 / 3 - 7
-```
-
-You can nest expressions in parenthesis as well:
-
-```
-myMathExpression = 3 + (1 * 2 / (3 - 7))
-```
-
-## Functions
-
-We also have support for defining your own functions. Functions can take in any
-type of argument. Below is an example of the syntax:
-
-```
-fn myFn(x) {
-  return x
-}
-```
-
-As you can see above `myFn` just returns whatever it is given.
-
-KCL's early drafts used positional arguments, but we now use keyword arguments:
-
-```
-// If you declare a function like this
-fn add(left, right) {
-  return left + right
-}
-
-// You can call it like this:
-total = add(left = 1, right = 2)
-```
-
-Functions can also declare one *unlabeled* arg. If you do want to declare an unlabeled arg, it must
-be the first arg declared.
-
-```
-// The @ indicates an argument can be used without a label.
-// Note that only the first argument can use @.
-fn increment(@x) {
-  return x + 1
-}
-
-fn add(@x, delta) {
-  return x + delta
-}
-
-two = increment(1)
-three = add(1, delta = 2)
-```
-
-## Pipelines
-
-It can be hard to read repeated function calls, because of all the nested brackets.
-
-```norun
-i = 1
-x = h(g(f(i)))
-```
-
-You can make this easier to read by breaking it into many declarations, but that is a bit annoying.
-
-```norun
-i  = 1
-x0 = f(i)
-x1 = g(x0)
-x  = h(x1)
-```
-
-Instead, you can use the pipeline operator (`|>`) to simplify this.
-
-Basically, `x |> f(%)` is a shorthand for `f(x)`. The left-hand side of the `|>` gets put into
-the `%` in the right-hand side.
-
-So, this means `x |> f(%) |> g(%)` is shorthand for `g(f(x))`. The code example above, with its
-somewhat-clunky `x0` and `x1` constants could be rewritten as
-
-```norun
-i = 1
-x = i
-  |> f(%)
-  |> g(%)
-  |> h(%)
-```
-
-This helps keep your code neat and avoid unnecessary declarations.
-
-## Pipelines and keyword arguments
-
-Say you have a long pipeline of sketch functions, like this:
-
-```norun
-startSketchOn(XZ)
-  |> line(%, end = [3, 4])
-  |> line(%, end = [10, 10])
-  |> line(%, end = [-13, -14])
-  |> close(%)
-```
-
-In this example, each function call outputs a sketch, and it gets put into the next function call via
-the `%`, into the first (unlabeled) argument.
-
-If a function call uses an unlabeled first parameter, it will default to `%` if it's not given. This
-means that `|> line(%, end = [3, 4])` and `|> line(end = [3, 4])` are equivalent! So the above
-could be rewritten as 
-
-```norun
-startSketchOn(XZ)
- |> line(end = [3, 4])
- |> line(end = [10, 10])
- |> line(end = [-13, -14])
- |> close()
-```
-
-Note that we are still in the process of migrating KCL's standard library to use keyword arguments. So some
-functions are still unfortunately using positional arguments. We're moving them over, so keep checking back.
-Some functions are still using the old positional argument syntax.
-Check the docs page for each function and look at its examples to see.
-
 ## Tags
 
 Tags are used to give a name (tag) to a specific path.
@@ -210,7 +85,7 @@ As per the example above you can use the tag identifier to get a reference to th
 tagged object. The syntax for this is `myTag`.
 
 In the example above we use the tag identifier to get the angle of the segment
-`segAng(rectangleSegmentA001, %)`.
+`segAng(rectangleSegmentA001)`.
 
 ### `Start`
 
@@ -291,7 +166,6 @@ See how we use the tag `rectangleSegmentA001` in the `fillet` function outside
 the `rect` function. This is because the `rect` function is returning the
 sketch group that contains the tags.
 
-
 ---
 
 If you find any issues using any of the above expressions or syntax,

docs/kcl-src/known-issues.md

@@ -1,26 +0,0 @@
----
-title: "KCL Known Issues"
-excerpt: "Known issues with the KCL standard library for the Zoo Design Studio."
-layout: manual
----
-
-The following are bugs that are not in modeling-app or kcl itself. These bugs
-once fixed in engine will just start working here with no language changes.
-
-- **Sketch on Face**: If your sketch is outside the edges of the face (on which you
-    are sketching) you will get multiple models returned instead of one single
-    model for that sketch and its underlying 3D object.
-    If you see a red line around your model, it means this is happening.
-
-- **Import**: Right now you can import a file, even if that file has brep data
-    you cannot edit it, after v1, the engine will account for this. 
-
-- **Fillets**: Fillets cannot intersect, you will get an error. Only simple fillet
-    cases work currently.
-
-- **Chamfers**: Chamfers cannot intersect, you will get an error. Only simple
-    chamfer cases work currently.
-
-- **Appearance**: Changing the appearance on a loft does not work. 
-
-- **CSG Booleans**: Coplanar (bodies that share a plane) unions, subtractions, and intersections are not currently supported.

docs/kcl-src/settings.md

@@ -1,45 +0,0 @@
----
-title: "KCL Settings"
-excerpt: "Documentation of settings for the KCL language and Zoo Design Studio."
-layout: manual
----
-
-# KCL Settings
-
-There are three levels of settings available in Zoo Design Studio:
-
-1. [User Settings](/docs/kcl/settings-user): Global settings that apply to all projects, stored in `user.toml`
-2. [Project Settings](/docs/kcl/settings-project): Settings specific to a project, stored in `project.toml`
-3. Per-file Settings: Settings that apply to a single KCL file, specified using the `@settings` attribute
-
-## Configuration Files
-
-Zoo Design Studio uses TOML files for configuration:
-
-* **User Settings**: `user.toml` - See [complete documentation](/docs/kcl/settings-user)
-* **Project Settings**: `project.toml` - See [complete documentation](/docs/kcl/settings-project)
-
-## Per-file settings
-
-Settings which affect a single file are configured using the settings attribute.
-This must be at the top of the KCL file (comments before the attribute are permitted).
-For example:
-
-```kcl
-// The settings attribute.
-@settings(defaultLengthUnit = in)
-
-// The rest of your KCL code goes below...
-
-x = 42 // Represents 42 inches.
-```
-
-The settings attribute may contain multiple properties separated by commas.
-Valid properties are:
-
-- `defaultLengthUnit`: the default length unit to use for numbers declared in this file.
-  - Accepted values: `mm`, `cm`, `m`, `in` (inches), `ft` (feet), `yd` (yards).
-- `defaultAngleUnit`: the default angle unit to use for numbers declared in this file.
-  - Accepted values: `deg` (degrees), `rad` (radians).
-
-These settings override any project-wide settings (configured in project.toml or via the UI).

docs/kcl-std/angledLine.md

@@ -1,16 +1,15 @@
 ---
 title: "angledLine"
+subtitle: "Function in std::sketch"
 excerpt: "Draw a line segment relative to the current origin using the polar measure of some angle and distance."
 layout: manual
 ---
 
 Draw a line segment relative to the current origin using the polar measure of some angle and distance.
 
-
-
 ```kcl
 angledLine(
-  sketch: Sketch,
+  @sketch: Sketch,
   angle: number,
   length?: number,
   lengthX?: number,
@@ -22,22 +21,23 @@ angledLine(
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `sketch` | [`Sketch`](/docs/kcl/types/std-types-Sketch) | Which sketch should this path be added to? | Yes |
-| `angle` | [`number`](/docs/kcl/types/std-types-number) | Which angle should the line be drawn at? | Yes |
-| `length` | [`number`](/docs/kcl/types/std-types-number) | Draw the line this distance along the given angle. Only one of `length`, `lengthX`, `lengthY`, `endAbsoluteX`, `endAbsoluteY` can be given. | No |
-| `lengthX` | [`number`](/docs/kcl/types/std-types-number) | Draw the line this distance along the X axis. Only one of `length`, `lengthX`, `lengthY`, `endAbsoluteX`, `endAbsoluteY` can be given. | No |
-| `lengthY` | [`number`](/docs/kcl/types/std-types-number) | Draw the line this distance along the Y axis. Only one of `length`, `lengthX`, `lengthY`, `endAbsoluteX`, `endAbsoluteY` can be given. | No |
-| `endAbsoluteX` | [`number`](/docs/kcl/types/std-types-number) | Draw the line along the given angle until it reaches this point along the X axis. Only one of `length`, `lengthX`, `lengthY`, `endAbsoluteX`, `endAbsoluteY` can be given. | No |
-| `endAbsoluteY` | [`number`](/docs/kcl/types/std-types-number) | Draw the line along the given angle until it reaches this point along the Y axis. Only one of `length`, `lengthX`, `lengthY`, `endAbsoluteX`, `endAbsoluteY` can be given. | No |
-| [`tag`](/docs/kcl/types/std-types-tag) | [`TagDeclarator`](/docs/kcl/types#TagDeclarator) | Create a new tag which refers to this line | No |
+| `sketch` | [`Sketch`](/docs/kcl-std/types/std-types-Sketch) | Which sketch should this path be added to? | Yes |
+| `angle` | [`number`](/docs/kcl-std/types/std-types-number) | Which angle should the line be drawn at? | Yes |
+| `length` | [`number`](/docs/kcl-std/types/std-types-number) | Draw the line this distance along the given angle. Only one of `length`, `lengthX`, `lengthY`, `endAbsoluteX`, `endAbsoluteY` can be given. | No |
+| `lengthX` | [`number`](/docs/kcl-std/types/std-types-number) | Draw the line this distance along the X axis. Only one of `length`, `lengthX`, `lengthY`, `endAbsoluteX`, `endAbsoluteY` can be given. | No |
+| `lengthY` | [`number`](/docs/kcl-std/types/std-types-number) | Draw the line this distance along the Y axis. Only one of `length`, `lengthX`, `lengthY`, `endAbsoluteX`, `endAbsoluteY` can be given. | No |
+| `endAbsoluteX` | [`number`](/docs/kcl-std/types/std-types-number) | Draw the line along the given angle until it reaches this point along the X axis. Only one of `length`, `lengthX`, `lengthY`, `endAbsoluteX`, `endAbsoluteY` can be given. | No |
+| `endAbsoluteY` | [`number`](/docs/kcl-std/types/std-types-number) | Draw the line along the given angle until it reaches this point along the Y axis. Only one of `length`, `lengthX`, `lengthY`, `endAbsoluteX`, `endAbsoluteY` can be given. | No |
+| [`tag`](/docs/kcl-std/types/std-types-tag) | [`TagDeclarator`](/docs/kcl-lang/types#TagDeclarator) | Create a new tag which refers to this line | No |
 
 ### Returns
 
-[`Sketch`](/docs/kcl/types/std-types-Sketch)
+[`Sketch`](/docs/kcl-std/types/std-types-Sketch) - A sketch is a collection of paths.
 
 
 ### Examples

docs/kcl-std/angledLineThatIntersects.md

@@ -1,16 +1,15 @@
 ---
 title: "angledLineThatIntersects"
+subtitle: "Function in std::sketch"
 excerpt: "Draw an angled line from the current origin, constructing a line segment such that the newly created line intersects the desired target line segment."
 layout: manual
 ---
 
 Draw an angled line from the current origin, constructing a line segment such that the newly created line intersects the desired target line segment.
 
-
-
 ```kcl
 angledLineThatIntersects(
-  sketch: Sketch,
+  @sketch: Sketch,
   angle: number,
   intersectTag: TagIdentifier,
   offset?: number,
@@ -19,19 +18,20 @@ angledLineThatIntersects(
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `sketch` | [`Sketch`](/docs/kcl/types/std-types-Sketch) | Which sketch should this path be added to? | Yes |
-| `angle` | [`number`](/docs/kcl/types/std-types-number) | Which angle should the line be drawn at? | Yes |
-| `intersectTag` | [`TagIdentifier`](/docs/kcl/types#TagIdentifier) | The tag of the line to intersect with | Yes |
-| `offset` | [`number`](/docs/kcl/types/std-types-number) | The offset from the intersecting line. Defaults to 0. | No |
-| [`tag`](/docs/kcl/types/std-types-tag) | [`TagDeclarator`](/docs/kcl/types#TagDeclarator) | Create a new tag which refers to this line | No |
+| `sketch` | [`Sketch`](/docs/kcl-std/types/std-types-Sketch) | Which sketch should this path be added to? | Yes |
+| `angle` | [`number`](/docs/kcl-std/types/std-types-number) | Which angle should the line be drawn at? | Yes |
+| `intersectTag` | [`TagIdentifier`](/docs/kcl-lang/types#TagIdentifier) | The tag of the line to intersect with | Yes |
+| `offset` | [`number`](/docs/kcl-std/types/std-types-number) | The offset from the intersecting line. Defaults to 0. | No |
+| [`tag`](/docs/kcl-std/types/std-types-tag) | [`TagDeclarator`](/docs/kcl-lang/types#TagDeclarator) | Create a new tag which refers to this line | No |
 
 ### Returns
 
-[`Sketch`](/docs/kcl/types/std-types-Sketch)
+[`Sketch`](/docs/kcl-std/types/std-types-Sketch) - A sketch is a collection of paths.
 
 
 ### Examples

docs/kcl-std/arc.md

@@ -1,18 +1,15 @@
 ---
 title: "arc"
+subtitle: "Function in std::sketch"
 excerpt: "Draw a curved line segment along an imaginary circle."
 layout: manual
 ---
 
 Draw a curved line segment along an imaginary circle.
 
-The arc is constructed such that the current position of the sketch is placed along an imaginary circle of the specified radius, at angleStart degrees. The resulting arc is the segment of the imaginary circle from that origin point to angleEnd, radius away from the center of the imaginary circle.
-
-Unless this makes a lot of sense and feels like what you're looking for to construct your shape, you're likely looking for tangentialArc.
-
 ```kcl
 arc(
-  sketch: Sketch,
+  @sketch: Sketch,
   angleStart?: number,
   angleEnd?: number,
   radius?: number,
@@ -22,22 +19,25 @@ arc(
 ): Sketch
 ```
 
+The arc is constructed such that the current position of the sketch is placed along an imaginary circle of the specified radius, at angleStart degrees. The resulting arc is the segment of the imaginary circle from that origin point to angleEnd, radius away from the center of the imaginary circle.
+
+Unless this makes a lot of sense and feels like what you're looking for to construct your shape, you're likely looking for tangentialArc.
 
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `sketch` | [`Sketch`](/docs/kcl/types/std-types-Sketch) | Which sketch should this path be added to? | Yes |
-| `angleStart` | [`number`](/docs/kcl/types/std-types-number) | Where along the circle should this arc start? | No |
-| `angleEnd` | [`number`](/docs/kcl/types/std-types-number) | Where along the circle should this arc end? | No |
-| `radius` | [`number`](/docs/kcl/types/std-types-number) | How large should the circle be? | No |
-| `interiorAbsolute` | [`Point2d`](/docs/kcl/types/std-types-Point2d) | Any point between the arc's start and end? Requires `endAbsolute`. Incompatible with `angleStart` or `angleEnd` | No |
-| `endAbsolute` | [`Point2d`](/docs/kcl/types/std-types-Point2d) | Where should this arc end? Requires `interiorAbsolute`. Incompatible with `angleStart` or `angleEnd` | No |
-| [`tag`](/docs/kcl/types/std-types-tag) | [`TagDeclarator`](/docs/kcl/types#TagDeclarator) | Create a new tag which refers to this line | No |
+| `sketch` | [`Sketch`](/docs/kcl-std/types/std-types-Sketch) | Which sketch should this path be added to? | Yes |
+| `angleStart` | [`number`](/docs/kcl-std/types/std-types-number) | Where along the circle should this arc start? | No |
+| `angleEnd` | [`number`](/docs/kcl-std/types/std-types-number) | Where along the circle should this arc end? | No |
+| `radius` | [`number`](/docs/kcl-std/types/std-types-number) | How large should the circle be? | No |
+| `interiorAbsolute` | [`Point2d`](/docs/kcl-std/types/std-types-Point2d) | Any point between the arc's start and end? Requires `endAbsolute`. Incompatible with `angleStart` or `angleEnd` | No |
+| `endAbsolute` | [`Point2d`](/docs/kcl-std/types/std-types-Point2d) | Where should this arc end? Requires `interiorAbsolute`. Incompatible with `angleStart` or `angleEnd` | No |
+| [`tag`](/docs/kcl-std/types/std-types-tag) | [`TagDeclarator`](/docs/kcl-lang/types#TagDeclarator) | Create a new tag which refers to this line | No |
 
 ### Returns
 
-[`Sketch`](/docs/kcl/types/std-types-Sketch)
+[`Sketch`](/docs/kcl-std/types/std-types-Sketch) - A sketch is a collection of paths.
 
 
 ### Examples

docs/kcl-std/assert.md

@@ -1,16 +1,15 @@
 ---
 title: "assert"
+subtitle: "Function in std"
 excerpt: "Check a value meets some expected conditions at runtime. Program terminates with an error if conditions aren't met. If you provide multiple conditions, they will all be checked and all must be met."
 layout: manual
 ---
 
 Check a value meets some expected conditions at runtime. Program terminates with an error if conditions aren't met. If you provide multiple conditions, they will all be checked and all must be met.
 
-
-
 ```kcl
 assert(
-  actual: number,
+  @actual: number,
   isGreaterThan?: number,
   isLessThan?: number,
   isGreaterThanOrEqual?: number,
@@ -22,18 +21,19 @@ assert(
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `actual` | [`number`](/docs/kcl/types/std-types-number) | Value to check. It will be compared with one of the comparison arguments. | Yes |
-| `isGreaterThan` | [`number`](/docs/kcl/types/std-types-number) | Comparison argument. If given, checks the `actual` value is greater than this. | No |
-| `isLessThan` | [`number`](/docs/kcl/types/std-types-number) | Comparison argument. If given, checks the `actual` value is less than this. | No |
-| `isGreaterThanOrEqual` | [`number`](/docs/kcl/types/std-types-number) | Comparison argument. If given, checks the `actual` value is greater than or equal to this. | No |
-| `isLessThanOrEqual` | [`number`](/docs/kcl/types/std-types-number) | Comparison argument. If given, checks the `actual` value is less than or equal to this. | No |
-| `isEqualTo` | [`number`](/docs/kcl/types/std-types-number) | Comparison argument. If given, checks the `actual` value is less than or equal to this. | No |
-| `tolerance` | [`number`](/docs/kcl/types/std-types-number) | If `isEqualTo` is used, this is the tolerance to allow for the comparison. This tolerance is used because KCL's number system has some floating-point imprecision when used with very large decimal places. | No |
-| `error` | [`string`](/docs/kcl/types/std-types-string) | If the value was false, the program will terminate with this error message | No |
+| `actual` | [`number`](/docs/kcl-std/types/std-types-number) | Value to check. It will be compared with one of the comparison arguments. | Yes |
+| `isGreaterThan` | [`number`](/docs/kcl-std/types/std-types-number) | Comparison argument. If given, checks the `actual` value is greater than this. | No |
+| `isLessThan` | [`number`](/docs/kcl-std/types/std-types-number) | Comparison argument. If given, checks the `actual` value is less than this. | No |
+| `isGreaterThanOrEqual` | [`number`](/docs/kcl-std/types/std-types-number) | Comparison argument. If given, checks the `actual` value is greater than or equal to this. | No |
+| `isLessThanOrEqual` | [`number`](/docs/kcl-std/types/std-types-number) | Comparison argument. If given, checks the `actual` value is less than or equal to this. | No |
+| `isEqualTo` | [`number`](/docs/kcl-std/types/std-types-number) | Comparison argument. If given, checks the `actual` value is less than or equal to this. | No |
+| `tolerance` | [`number`](/docs/kcl-std/types/std-types-number) | If `isEqualTo` is used, this is the tolerance to allow for the comparison. This tolerance is used because KCL's number system has some floating-point imprecision when used with very large decimal places. | No |
+| `error` | [`string`](/docs/kcl-std/types/std-types-string) | If the value was false, the program will terminate with this error message | No |
 
 ### Returns
 

docs/kcl-std/assertIs.md

@@ -1,27 +1,27 @@
 ---
 title: "assertIs"
+subtitle: "Function in std"
 excerpt: "Asserts that a value is the boolean value true."
 layout: manual
 ---
 
 Asserts that a value is the boolean value true.
 
-
-
 ```kcl
 assertIs(
-  actual: bool,
+  @actual: bool,
   error?: string,
 ): ()
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `actual` | [`bool`](/docs/kcl/types/std-types-bool) | Value to check. If this is the boolean value true, assert passes. Otherwise it fails. | Yes |
-| `error` | [`string`](/docs/kcl/types/std-types-string) | If the value was false, the program will terminate with this error message | No |
+| `actual` | [`bool`](/docs/kcl-std/types/std-types-bool) | Value to check. If this is the boolean value true, assert passes. Otherwise it fails. | Yes |
+| `error` | [`string`](/docs/kcl-std/types/std-types-string) | If the value was false, the program will terminate with this error message | No |
 
 ### Returns
 

docs/kcl-std/bezierCurve.md

@@ -1,16 +1,15 @@
 ---
 title: "bezierCurve"
+subtitle: "Function in std::sketch"
 excerpt: "Draw a smooth, continuous, curved line segment from the current origin to the desired (x, y), using a number of control points to shape the curve's shape."
 layout: manual
 ---
 
 Draw a smooth, continuous, curved line segment from the current origin to the desired (x, y), using a number of control points to shape the curve's shape.
 
-
-
 ```kcl
 bezierCurve(
-  sketch: Sketch,
+  @sketch: Sketch,
   control1: Point2d,
   control2: Point2d,
   end: Point2d,
@@ -19,19 +18,20 @@ bezierCurve(
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `sketch` | [`Sketch`](/docs/kcl/types/std-types-Sketch) | Which sketch should this path be added to? | Yes |
-| `control1` | [`Point2d`](/docs/kcl/types/std-types-Point2d) | First control point for the cubic | Yes |
-| `control2` | [`Point2d`](/docs/kcl/types/std-types-Point2d) | Second control point for the cubic | Yes |
-| `end` | [`Point2d`](/docs/kcl/types/std-types-Point2d) | How far away (along the X and Y axes) should this line go? | Yes |
-| [`tag`](/docs/kcl/types/std-types-tag) | [`TagDeclarator`](/docs/kcl/types#TagDeclarator) | Create a new tag which refers to this line | No |
+| `sketch` | [`Sketch`](/docs/kcl-std/types/std-types-Sketch) | Which sketch should this path be added to? | Yes |
+| `control1` | [`Point2d`](/docs/kcl-std/types/std-types-Point2d) | First control point for the cubic | Yes |
+| `control2` | [`Point2d`](/docs/kcl-std/types/std-types-Point2d) | Second control point for the cubic | Yes |
+| `end` | [`Point2d`](/docs/kcl-std/types/std-types-Point2d) | How far away (along the X and Y axes) should this line go? | Yes |
+| [`tag`](/docs/kcl-std/types/std-types-tag) | [`TagDeclarator`](/docs/kcl-lang/types#TagDeclarator) | Create a new tag which refers to this line | No |
 
 ### Returns
 
-[`Sketch`](/docs/kcl/types/std-types-Sketch)
+[`Sketch`](/docs/kcl-std/types/std-types-Sketch) - A sketch is a collection of paths.
 
 
 ### Examples

docs/kcl-std/circleThreePoint.md

@@ -1,16 +1,15 @@
 ---
 title: "circleThreePoint"
+subtitle: "Function in std::sketch"
 excerpt: "Construct a circle derived from 3 points."
 layout: manual
 ---
 
 Construct a circle derived from 3 points.
 
-
-
 ```kcl
 circleThreePoint(
-  sketchSurfaceOrGroup: Sketch | Plane | Face,
+  @sketchSurfaceOrGroup: Sketch | Plane | Face,
   p1: Point2d,
   p2: Point2d,
   p3: Point2d,
@@ -19,19 +18,20 @@ circleThreePoint(
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `sketchSurfaceOrGroup` | [`Sketch`](/docs/kcl/types/std-types-Sketch) or [`Plane`](/docs/kcl/types/std-types-Plane) or [`Face`](/docs/kcl/types/std-types-Face) | Plane or surface to sketch on. | Yes |
-| `p1` | [`Point2d`](/docs/kcl/types/std-types-Point2d) | 1st point to derive the circle. | Yes |
-| `p2` | [`Point2d`](/docs/kcl/types/std-types-Point2d) | 2nd point to derive the circle. | Yes |
-| `p3` | [`Point2d`](/docs/kcl/types/std-types-Point2d) | 3rd point to derive the circle. | Yes |
-| [`tag`](/docs/kcl/types/std-types-tag) | [`TagDeclarator`](/docs/kcl/types#TagDeclarator) | Identifier for the circle to reference elsewhere. | No |
+| `sketchSurfaceOrGroup` | [`Sketch`](/docs/kcl-std/types/std-types-Sketch) or [`Plane`](/docs/kcl-std/types/std-types-Plane) or [`Face`](/docs/kcl-std/types/std-types-Face) | Plane or surface to sketch on. | Yes |
+| `p1` | [`Point2d`](/docs/kcl-std/types/std-types-Point2d) | 1st point to derive the circle. | Yes |
+| `p2` | [`Point2d`](/docs/kcl-std/types/std-types-Point2d) | 2nd point to derive the circle. | Yes |
+| `p3` | [`Point2d`](/docs/kcl-std/types/std-types-Point2d) | 3rd point to derive the circle. | Yes |
+| [`tag`](/docs/kcl-std/types/std-types-tag) | [`TagDeclarator`](/docs/kcl-lang/types#TagDeclarator) | Identifier for the circle to reference elsewhere. | No |
 
 ### Returns
 
-[`Sketch`](/docs/kcl/types/std-types-Sketch)
+[`Sketch`](/docs/kcl-std/types/std-types-Sketch) - A sketch is a collection of paths.
 
 
 ### Examples

docs/kcl-std/close.md

@@ -1,31 +1,31 @@
 ---
 title: "close"
+subtitle: "Function in std::sketch"
 excerpt: "Construct a line segment from the current origin back to the profile's origin, ensuring the resulting 2-dimensional sketch is not open-ended."
 layout: manual
 ---
 
 Construct a line segment from the current origin back to the profile's origin, ensuring the resulting 2-dimensional sketch is not open-ended.
 
-
-
 ```kcl
 close(
-  sketch: Sketch,
+  @sketch: Sketch,
   tag?: TagDeclarator,
 ): Sketch
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `sketch` | [`Sketch`](/docs/kcl/types/std-types-Sketch) | The sketch you want to close | Yes |
-| [`tag`](/docs/kcl/types/std-types-tag) | [`TagDeclarator`](/docs/kcl/types#TagDeclarator) | Create a new tag which refers to this line | No |
+| `sketch` | [`Sketch`](/docs/kcl-std/types/std-types-Sketch) | The sketch you want to close | Yes |
+| [`tag`](/docs/kcl-std/types/std-types-tag) | [`TagDeclarator`](/docs/kcl-lang/types#TagDeclarator) | Create a new tag which refers to this line | No |
 
 ### Returns
 
-[`Sketch`](/docs/kcl/types/std-types-Sketch)
+[`Sketch`](/docs/kcl-std/types/std-types-Sketch) - A sketch is a collection of paths.
 
 
 ### Examples

docs/kcl-std/consts/std-END.md

@@ -1,15 +1,16 @@
 ---
-title: "std::END"
+title: "END"
+subtitle: "Constant in std"
 excerpt: "Identifies the ending face of an extrusion. I.e., the new face created by an extrusion."
 layout: manual
 ---
 
 Identifies the ending face of an extrusion. I.e., the new face created by an extrusion.
 
-
-
 ```kcl
-std::END: string = 'end'
+END: string = 'end'
 ```
 
 
+
+

docs/kcl-std/consts/std-START.md

@@ -1,15 +1,16 @@
 ---
-title: "std::START"
+title: "START"
+subtitle: "Constant in std"
 excerpt: "Identifies the starting face of an extrusion. I.e., the face which is extruded."
 layout: manual
 ---
 
 Identifies the starting face of an extrusion. I.e., the face which is extruded.
 
-
-
 ```kcl
-std::START: string = 'start'
+START: string = 'start'
 ```
 
 
+
+

docs/kcl-std/consts/std-X.md

@@ -0,0 +1,16 @@
+---
+title: "X"
+subtitle: "Constant in std"
+excerpt: "The X-axis (can be used in both 2d and 3d contexts)."
+layout: manual
+---
+
+The X-axis (can be used in both 2d and 3d contexts).
+
+```kcl
+X
+```
+
+
+
+

docs/kcl-std/consts/std-XY.md

@@ -0,0 +1,16 @@
+---
+title: "XY"
+subtitle: "Constant in std"
+excerpt: "An abstract 3d plane aligned with the X and Y axes. Its normal is the positive Z axis."
+layout: manual
+---
+
+An abstract 3d plane aligned with the X and Y axes. Its normal is the positive Z axis.
+
+```kcl
+XY
+```
+
+
+
+

docs/kcl-std/consts/std-XZ.md

@@ -0,0 +1,16 @@
+---
+title: "XZ"
+subtitle: "Constant in std"
+excerpt: "An abstract 3d plane aligned with the X and Z axes. Its normal is the negative Y axis."
+layout: manual
+---
+
+An abstract 3d plane aligned with the X and Z axes. Its normal is the negative Y axis.
+
+```kcl
+XZ
+```
+
+
+
+

docs/kcl-std/consts/std-Y.md

@@ -0,0 +1,16 @@
+---
+title: "Y"
+subtitle: "Constant in std"
+excerpt: "The Y-axis (can be used in both 2d and 3d contexts)."
+layout: manual
+---
+
+The Y-axis (can be used in both 2d and 3d contexts).
+
+```kcl
+Y
+```
+
+
+
+

docs/kcl-std/consts/std-YZ.md

@@ -0,0 +1,16 @@
+---
+title: "YZ"
+subtitle: "Constant in std"
+excerpt: "An abstract 3d plane aligned with the Y and Z axes. Its normal is the positive X axis."
+layout: manual
+---
+
+An abstract 3d plane aligned with the Y and Z axes. Its normal is the positive X axis.
+
+```kcl
+YZ
+```
+
+
+
+

docs/kcl-std/consts/std-Z.md

@@ -0,0 +1,16 @@
+---
+title: "Z"
+subtitle: "Constant in std"
+excerpt: "The 3D Z-axis."
+layout: manual
+---
+
+The 3D Z-axis.
+
+```kcl
+Z
+```
+
+
+
+

docs/kcl-std/consts/std-turns-HALF_TURN.md

@@ -0,0 +1,16 @@
+---
+title: "turns::HALF_TURN"
+subtitle: "Constant in std::turns"
+excerpt: "A half turn, 180 degrees or π radians."
+layout: manual
+---
+
+A half turn, 180 degrees or π radians.
+
+```kcl
+turns::HALF_TURN: number(deg) = 180deg
+```
+
+
+
+

docs/kcl-std/consts/std-turns-QUARTER_TURN.md

@@ -0,0 +1,16 @@
+---
+title: "turns::QUARTER_TURN"
+subtitle: "Constant in std::turns"
+excerpt: "A quarter turn, 90 degrees or π/2 radians."
+layout: manual
+---
+
+A quarter turn, 90 degrees or π/2 radians.
+
+```kcl
+turns::QUARTER_TURN: number(deg) = 90deg
+```
+
+
+
+

docs/kcl-std/consts/std-turns-THREE_QUARTER_TURN.md

@@ -0,0 +1,16 @@
+---
+title: "turns::THREE_QUARTER_TURN"
+subtitle: "Constant in std::turns"
+excerpt: "Three quarters of a turn, 270 degrees or 1.5*π radians."
+layout: manual
+---
+
+Three quarters of a turn, 270 degrees or 1.5*π radians.
+
+```kcl
+turns::THREE_QUARTER_TURN: number(deg) = 270deg
+```
+
+
+
+

docs/kcl-std/consts/std-turns-ZERO.md

@@ -0,0 +1,16 @@
+---
+title: "turns::ZERO"
+subtitle: "Constant in std::turns"
+excerpt: "No turn, zero degrees/radians."
+layout: manual
+---
+
+No turn, zero degrees/radians.
+
+```kcl
+turns::ZERO: number = 0
+```
+
+
+
+

docs/kcl-std/extrude.md

@@ -1,16 +1,15 @@
 ---
 title: "extrude"
+subtitle: "Function in std::sketch"
 excerpt: "Extend a 2-dimensional sketch through a third dimension in order to create new 3-dimensional volume, or if extruded into an existing volume, cut into an existing solid."
 layout: manual
 ---
 
 Extend a 2-dimensional sketch through a third dimension in order to create new 3-dimensional volume, or if extruded into an existing volume, cut into an existing solid.
 
-You can provide more than one sketch to extrude, and they will all be extruded in the same direction.
-
 ```kcl
 extrude(
-  sketches: [Sketch],
+  @sketches: [Sketch],
   length: number,
   symmetric?: bool,
   bidirectionalLength?: number,
@@ -19,21 +18,22 @@ extrude(
 ): [Solid]
 ```
 
+You can provide more than one sketch to extrude, and they will all be extruded in the same direction.
 
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `sketches` | [`[Sketch]`](/docs/kcl/types/std-types-Sketch) | Which sketch or sketches should be extruded | Yes |
-| `length` | [`number`](/docs/kcl/types/std-types-number) | How far to extrude the given sketches | Yes |
-| `symmetric` | [`bool`](/docs/kcl/types/std-types-bool) | If true, the extrusion will happen symmetrically around the sketch. Otherwise, the | No |
-| `bidirectionalLength` | [`number`](/docs/kcl/types/std-types-number) | If specified, will also extrude in the opposite direction to 'distance' to the specified distance. If 'symmetric' is true, this value is ignored. | No |
-| `tagStart` | [`TagDeclarator`](/docs/kcl/types#TagDeclarator) | A named tag for the face at the start of the extrusion, i.e. the original sketch | No |
-| `tagEnd` | [`TagDeclarator`](/docs/kcl/types#TagDeclarator) | A named tag for the face at the end of the extrusion, i.e. the new face created by extruding the original sketch | No |
+| `sketches` | [`[Sketch]`](/docs/kcl-std/types/std-types-Sketch) | Which sketch or sketches should be extruded | Yes |
+| `length` | [`number`](/docs/kcl-std/types/std-types-number) | How far to extrude the given sketches | Yes |
+| `symmetric` | [`bool`](/docs/kcl-std/types/std-types-bool) | If true, the extrusion will happen symmetrically around the sketch. Otherwise, the extrusion will happen on only one side of the sketch. | No |
+| `bidirectionalLength` | [`number`](/docs/kcl-std/types/std-types-number) | If specified, will also extrude in the opposite direction to 'distance' to the specified distance. If 'symmetric' is true, this value is ignored. | No |
+| `tagStart` | [`TagDeclarator`](/docs/kcl-lang/types#TagDeclarator) | A named tag for the face at the start of the extrusion, i.e. the original sketch | No |
+| `tagEnd` | [`TagDeclarator`](/docs/kcl-lang/types#TagDeclarator) | A named tag for the face at the end of the extrusion, i.e. the new face created by extruding the original sketch | No |
 
 ### Returns
 
-[`[Solid]`](/docs/kcl/types/std-types-Solid)
+[`[Solid]`](/docs/kcl-std/types/std-types-Solid)
 
 
 ### Examples

docs/kcl-std/functions/std-math-atan.md

@@ -1,27 +1,27 @@
 ---
-title: "std::math::atan"
+title: "atan"
+subtitle: "Function in std::math"
 excerpt: "Compute the arctangent of a number."
 layout: manual
 ---
 
 Compute the arctangent of a number.
 
-Consider using `atan2()` instead for the true inverse of tangent.
-
 ```kcl
 atan(@num: number(_)): number(rad)
 ```
 
+Consider using `atan2()` instead for the true inverse of tangent.
 
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `num` | `number(_)` |  | Yes |
+| `num` | [`number(_)`](/docs/kcl-std/types/std-types-number) | A number. | Yes |
 
 ### Returns
 
-`number(rad)`
+[`number(rad)`](/docs/kcl-std/types/std-types-number) - A number.
 
 
 ### Examples

docs/kcl-std/functions/std-units-toCentimeters.md

@@ -1,27 +1,27 @@
 ---
-title: "std::units::toCentimeters"
+title: "units::toCentimeters"
+subtitle: "Function in std::units"
 excerpt: "Convert a number to centimeters from its current units."
 layout: manual
 ---
 
 Convert a number to centimeters from its current units.
 
-
-
 ```kcl
-units::toCentimeters(@num: number(cm)): number(cm)
+units::toCentimeters(@num: number(Length)): number(cm)
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `num` | `number(cm)` |  | Yes |
+| `num` | [`number(Length)`](/docs/kcl-std/types/std-types-number) | A number. | Yes |
 
 ### Returns
 
-`number(cm)`
+[`number(cm)`](/docs/kcl-std/types/std-types-number) - A number.
 
 
 

docs/kcl-std/functions/std-units-toFeet.md

@@ -1,27 +1,27 @@
 ---
-title: "std::units::toFeet"
+title: "units::toFeet"
+subtitle: "Function in std::units"
 excerpt: "Convert a number to feet from its current units."
 layout: manual
 ---
 
 Convert a number to feet from its current units.
 
-
-
 ```kcl
-units::toFeet(@num: number(ft)): number(ft)
+units::toFeet(@num: number(Length)): number(ft)
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `num` | `number(ft)` |  | Yes |
+| `num` | [`number(Length)`](/docs/kcl-std/types/std-types-number) | A number. | Yes |
 
 ### Returns
 
-`number(ft)`
+[`number(ft)`](/docs/kcl-std/types/std-types-number) - A number.
 
 
 

docs/kcl-std/functions/std-units-toInches.md

@@ -1,27 +1,27 @@
 ---
-title: "std::units::toInches"
+title: "units::toInches"
+subtitle: "Function in std::units"
 excerpt: "Convert a number to inches from its current units."
 layout: manual
 ---
 
 Convert a number to inches from its current units.
 
-
-
 ```kcl
-units::toInches(@num: number(in)): number(in)
+units::toInches(@num: number(Length)): number(in)
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `num` | `number(in)` |  | Yes |
+| `num` | [`number(Length)`](/docs/kcl-std/types/std-types-number) | A number. | Yes |
 
 ### Returns
 
-`number(in)`
+[`number(in)`](/docs/kcl-std/types/std-types-number) - A number.
 
 
 

docs/kcl-std/functions/std-units-toMeters.md

@@ -1,27 +1,27 @@
 ---
-title: "std::units::toMeters"
+title: "units::toMeters"
+subtitle: "Function in std::units"
 excerpt: "Convert a number to meters from its current units."
 layout: manual
 ---
 
 Convert a number to meters from its current units.
 
-
-
 ```kcl
-units::toMeters(@num: number(m)): number(m)
+units::toMeters(@num: number(Length)): number(m)
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `num` | `number(m)` |  | Yes |
+| `num` | [`number(Length)`](/docs/kcl-std/types/std-types-number) | A number. | Yes |
 
 ### Returns
 
-`number(m)`
+[`number(m)`](/docs/kcl-std/types/std-types-number) - A number.
 
 
 

docs/kcl-std/functions/std-units-toMillimeters.md

@@ -1,27 +1,27 @@
 ---
-title: "std::units::toMillimeters"
+title: "units::toMillimeters"
+subtitle: "Function in std::units"
 excerpt: "Convert a number to millimeters from its current units."
 layout: manual
 ---
 
 Convert a number to millimeters from its current units.
 
-
-
 ```kcl
-units::toMillimeters(@num: number(mm)): number(mm)
+units::toMillimeters(@num: number(Length)): number(mm)
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `num` | `number(mm)` |  | Yes |
+| `num` | [`number(Length)`](/docs/kcl-std/types/std-types-number) | A number. | Yes |
 
 ### Returns
 
-`number(mm)`
+[`number(mm)`](/docs/kcl-std/types/std-types-number) - A number.
 
 
 

docs/kcl-std/functions/std-units-toYards.md

@@ -1,27 +1,27 @@
 ---
-title: "std::units::toYards"
+title: "units::toYards"
+subtitle: "Function in std::units"
 excerpt: "Converts a number to yards from its current units."
 layout: manual
 ---
 
 Converts a number to yards from its current units.
 
-
-
 ```kcl
-units::toYards(@num: number(yd)): number(yd)
+units::toYards(@num: number(Length)): number(yd)
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `num` | `number(yd)` |  | Yes |
+| `num` | [`number(Length)`](/docs/kcl-std/types/std-types-number) | A number. | Yes |
 
 ### Returns
 
-`number(yd)`
+[`number(yd)`](/docs/kcl-std/types/std-types-number) - A number.
 
 
 

docs/kcl-std/getCommonEdge.md

@@ -1,23 +1,23 @@
 ---
 title: "getCommonEdge"
+subtitle: "Function in std::sketch"
 excerpt: "Get the shared edge between two faces."
 layout: manual
 ---
 
 Get the shared edge between two faces.
 
-
-
 ```kcl
 getCommonEdge(faces: [TagIdentifier]): Uuid
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `faces` | [`[TagIdentifier]`](/docs/kcl/types#TagIdentifier) | The tags of the faces you want to find the common edge between | Yes |
+| `faces` | [`[TagIdentifier]`](/docs/kcl-lang/types#TagIdentifier) | The tags of the faces you want to find the common edge between | Yes |
 
 ### Returns
 

docs/kcl-std/getNextAdjacentEdge.md

@@ -1,23 +1,23 @@
 ---
 title: "getNextAdjacentEdge"
+subtitle: "Function in std::sketch"
 excerpt: "Get the next adjacent edge to the edge given."
 layout: manual
 ---
 
 Get the next adjacent edge to the edge given.
 
-
-
 ```kcl
-getNextAdjacentEdge(edge: TagIdentifier): Uuid
+getNextAdjacentEdge(@edge: TagIdentifier): Uuid
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `edge` | [`TagIdentifier`](/docs/kcl/types#TagIdentifier) | The tag of the edge you want to find the next adjacent edge of. | Yes |
+| `edge` | [`TagIdentifier`](/docs/kcl-lang/types#TagIdentifier) | The tag of the edge you want to find the next adjacent edge of. | Yes |
 
 ### Returns
 

docs/kcl-std/getOppositeEdge.md

@@ -1,23 +1,23 @@
 ---
 title: "getOppositeEdge"
+subtitle: "Function in std::sketch"
 excerpt: "Get the opposite edge to the edge given."
 layout: manual
 ---
 
 Get the opposite edge to the edge given.
 
-
-
 ```kcl
-getOppositeEdge(edge: TagIdentifier): Uuid
+getOppositeEdge(@edge: TagIdentifier): Uuid
 ```
 
 
+
 ### Arguments
 
 | Name | Type | Description | Required |
 |----------|------|-------------|----------|
-| `edge` | [`TagIdentifier`](/docs/kcl/types#TagIdentifier) | The tag of the edge you want to find the opposite edge of. | Yes |
+| `edge` | [`TagIdentifier`](/docs/kcl-lang/types#TagIdentifier) | The tag of the edge you want to find the opposite edge of. | Yes |
 
 ### Returns