From 391d66cf272b722be949080c4e2d8c0a1b877fb0 Mon Sep 17 00:00:00 2001 From: "Sam (automated drift fix)" Date: Thu, 8 Oct 2026 08:53:50 +0300 Subject: [PATCH 1/2] Align AI builder wording in connectors JSDoc Co-Authored-By: Claude Sonnet 5.5 --- packages/sdk/src/modules/connectors.types.ts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/sdk/src/modules/connectors.types.ts b/packages/sdk/src/modules/connectors.types.ts index d8650588..efe0d902 100644 --- a/packages/sdk/src/modules/connectors.types.ts +++ b/packages/sdk/src/modules/connectors.types.ts @@ -500,7 +500,7 @@ export interface UserConnectorsModule { * authenticate with the external service. The scopes and integration type are * derived from the connector configuration in the backend. * - * @param connectorId - The ID of the app user connector configured in your workspace. The AI builder inserts this ID into generated code when it sets up the connector flow. You can also retrieve it from the workspace connectors API. + * @param connectorId - The ID of the app user connector configured in your workspace. The AI inserts this ID into generated code when it sets up the connector flow. You can also retrieve it from the workspace connectors API. * @returns Promise resolving to the redirect URL string. * * @example @@ -520,7 +520,7 @@ export interface UserConnectorsModule { * Removes the stored OAuth credentials for the currently authenticated app user's * connection to the specified connector. * - * @param connectorId - The ID of the app user connector configured in your workspace. The AI builder inserts this ID into generated code when it sets up the connector flow. You can also retrieve it from the workspace connectors API. + * @param connectorId - The ID of the app user connector configured in your workspace. The AI inserts this ID into generated code when it sets up the connector flow. You can also retrieve it from the workspace connectors API. * @returns Promise resolving when the connection has been removed. * * @example From a8a2019ad82947a2f8742dfafbcb7bd64d16be46 Mon Sep 17 00:00:00 2001 From: "Sam (automated drift fix)" Date: Thu, 8 Oct 2026 09:00:44 +0300 Subject: [PATCH 2/2] Add app editor and AI terminology rule to writing skill Co-Authored-By: Claude Sonnet 5.5 --- .claude/skills/sdk-docs-writing/SKILL.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.claude/skills/sdk-docs-writing/SKILL.md b/.claude/skills/sdk-docs-writing/SKILL.md index 4c90ef64..73639725 100644 --- a/.claude/skills/sdk-docs-writing/SKILL.md +++ b/.claude/skills/sdk-docs-writing/SKILL.md @@ -82,6 +82,7 @@ Every public method needs: description, `@param` tags, `@returns`, and at least - **Link method references.** When mentioning another SDK method or module by name in JSDoc prose, always use `{@link}` or `{@linkcode}` to create a cross-reference. - **Never use a colon as a sentence break.** Write "Use this when you sync data from another system. Name the field..." not "...another system: name the field...". Reserve colons for `label: description` bullet-list items, not prose sentences. - **Never start a sentence with a lowercase inline-code term.** If the natural phrasing would open with one (e.g., "`week` is only supported on..."), restructure so a capitalized word leads instead (e.g., "Every date field supports `day`, `month` and `year`. The `created_date` and `updated_date` fields also support `week`."). +- **Name the place and the AI correctly.** Write "app editor" (lowercase) for the place where you build, and "the AI" or "the AI chat" for the assistant doing the work ("The AI inserts this ID", "ask the AI chat to fix it"). Never use "builder" for either. It stays only for the Builder plan, the Base44 Builder GitHub App, people who build apps ("builders", "app builders"), and exact UI labels or code names. ## References