@goldencomm/create-baseline 0.0.1 → 0.1.0

package/templates/next/.claude/skills/gc-implement-figma-page/SKILL.md

@@ -1,93 +0,0 @@
----
-name: gc-implement-figma-page
-description: Implement a Figma design as a Baseline page — take a figma.com frame/page URL and build it from @goldencomm/ds-react components + DS layout primitives. Use when asked to "implement this Figma design/page/URL", "build this page from Figma", or given a figma.com node link to turn into code.
----
-
-# Implement a Figma page (Baseline)
-
-The "give Claude a Figma URL, get a Baseline page" workflow: read the design
-through the Figma MCP server, trust its Code Connect snippets for component
-choice, and compose the page from DS primitives — never hand-rolled layout.
-
-## 0 · Requirements
-
-- **The Figma MCP server must be connected** (`get_design_context`,
-  `get_screenshot`). If it isn't, STOP and ask the user to connect it (claude.ai
-  Figma connector, or the Figma desktop app's MCP server) — do not attempt to
-  implement from a screenshot alone.
-- Read access to the Design-System library file
-  (`ba28zZ49PAkXhE7PW5kyT9`) so component instances resolve.
-- If the Figma plugin's `figma-design-to-code` skill is available, load it before
-  calling `get_design_context` (it's a declared prerequisite of that tool).
-
-## 1 · Read the design
-
-1. **`get_design_context` on the node URL.** Components mapped via Code Connect
-   come back as **code snippets — TRUST them.** They are the source of truth for
-   which `@goldencomm/ds-react` component and which props/variants to use. Never
-   re-derive a mapped component from raw geometry or invent props the snippet
-   doesn't show.
-2. **`get_screenshot` on the same node** — keep it as the visual reference you
-   verify against in step 4.
-3. Large page (several sections)? Call `get_metadata` first to list the
-   top-level section frames, then `get_design_context` per section so each
-   response stays focused.
-
-## 2 · Assemble the page
-
-Target: the app you're in — for Next.js (App Router) that's
-`app/<route>/page.tsx`. **Server component by default**; no `"use client"` in the
-page — interactivity lives inside the DS components (Dialog, Tabs, …) already.
-
-Compose ONLY from:
-
-- **Components** — `@goldencomm/ds-react`, exactly as the Code Connect snippets
-  dictate (Button, Badge, Card + `Card.Header/Content/…`, Avatar + `Avatar.Group`, …).
-- **Layout primitives** (the Layout module):
-  `import { Section, Container, Flex, Grid, Columns, Box, AspectRatio } from "@goldencomm/ds-react"`
-  - vertical page band → `<Section>` (density-aware fluid padding)
-  - centered max-width + gutter → `<Container>` (`width` narrow|wide|full)
-  - rows/stacks with gaps → `<Flex>`; tile galleries → `<Grid columns={N}>` or
-    fluid `<Grid min="16rem">`
-  - equal columns that stack on mobile (text|image splits) → `<Columns stackAt="md">`
-  - generic padded/flex-basis wrapper → `<Box>`; media crops → `<AspectRatio>`
-- **Typography** — semantic elements + gcds classes: `.gcds-display` (hero h1),
-  `.gcds-eyebrow`, `.gcds-lead`, `.gcds-text-muted`, `.gcds-text-center/-start/-end`,
-  `.gcds-text-balance` / `.gcds-text-pretty`.
-
-Hard rules:
-
-- **NEVER hand-rolled CSS or Tailwind layout utilities for anything a DS
-  primitive expresses** — no `py-24`, `mx-auto max-w-7xl`, `flex gap-8`,
-  `grid-cols-3`, no bespoke stylesheets. Tailwind static values bypass the theme
-  knobs and don't port to WP/Shopify.
-- **Tokens/vars only** — no hardcoded colors, spacing, radii, or font sizes.
-  An inline style value must be a `var(--gcds-*)` token
-  (e.g. `style={{ borderRadius: "var(--gcds-radius-lg)" }}`).
-- **Icons = Lucide via `lucide-react`, composed as children** (explicit numeric
-  `size`, `aria-hidden` when decorative). No other icon sources, no icon props.
-- **Link-ish elements → polymorphic `as`**:
-  `<Button as={Link} href="/pricing">…</Button>`. No `asChild`/Slot.
-- Selfish design: components own themselves; the PAGE owns layout, gaps, and
-  margins between them.
-
-## 3 · Unmapped / custom frames
-
-When a section returns raw frame output (no Code Connect snippet), do **not**
-hand-build it first. Map it to the nearest **copy-to-own section template** in the
-design-system repo under `apps/docs/app/new/patterns/marketing/<category>/pattern-N.tsx`
-(`hero-sections`, `feature-sections`, …): copy the template into the project,
-then reshape its content/structure to match the frame. Hand-compose from layout
-primitives only when no template is close.
-
-If the design needs a component Baseline does not provide, STOP for that piece
-and report `MISSING: <component> — <why>` instead of hand-rolling it.
-
-## 4 · Verify
-
-1. `pnpm typecheck` (monorepo: `pnpm --filter=<app> typecheck`).
-2. Render it — start the dev server (docs app: `pnpm dev:docs` → :3200; Next
-   baseline: `pnpm dev` → :3100) and load the route.
-3. Compare against the `get_screenshot` reference: section order, hierarchy,
-   spacing rhythm, component variants. Fix divergences with DS props/knobs and
-   tokens — never with custom CSS overrides.

package/templates/next/.claude/skills/migrate-ai-sdk-v6-to-v7/SKILL.md

@@ -1,108 +0,0 @@
----
-name: migrate-ai-sdk-v6-to-v7
-description: Migrate applications from AI SDK 6.x to AI SDK 7.0. Use when upgrading Vercel AI SDK packages, fixing v7 migration errors, or when the user mentions AI SDK v6, v7, upgrade, migration, breaking changes, system to instructions, fullStream, telemetry, tool context, or finalStep.
----
-
-## AI SDK 6 to 7 Migration
-
-Use `content/docs/08-migration-guides/23-migration-guide-7-0.mdx` from the AI SDK repo as the source of truth. This skill is the working checklist; read the guide for exact examples or when behavior is unclear.
-
-## Migration Workflow
-
-1. Ensure the user has a clean backup or committed baseline before editing.
-2. Inspect `package.json` and lockfiles to identify installed `ai`, `@ai-sdk/*`, provider, UI, MCP, and telemetry packages.
-3. Upgrade AI SDK packages to latest versions, and add `@ai-sdk/otel` only if the project uses OpenTelemetry spans.
-4. Update runtime and module assumptions: Node.js must be `>=22`, and AI SDK packages are ESM-only. Replace `require()` imports with ESM imports and add `"type": "module"` or use `.mjs` where needed.
-5. Search for the v6 patterns below, migrate only the code that exists, then run typecheck and targeted tests.
-
-Prefer behavior-preserving changes. When v7 changes semantics, decide whether the app wants the new all-steps behavior or the previous final-step-only behavior.
-
-## Core API Changes
-
-- `experimental_customProvider` -> `customProvider`.
-- `experimental_generateImage` -> `generateImage`; `Experimental_GenerateImageResult` -> `GenerateImageResult`.
-- `experimental_transcribe` -> `transcribe`; `Experimental_TranscriptionResult` -> `TranscriptionResult`.
-- `experimental_generateSpeech` -> `generateSpeech`; `Experimental_SpeechResult` -> `SpeechResult`.
-- `experimental_output` option/result -> `output` option/result.
-- `CallSettings` -> `LanguageModelCallOptions & Omit<RequestOptions, 'timeout'>`; `prepareCallSettings` -> `prepareLanguageModelCallOptions`.
-- `stepCountIs` -> `isStepCount`.
-
-## Prompts and Steps
-
-- Rename top-level `system` to `instructions` for `generateText`, `streamText`, `generateObject`, `streamObject`, and `streamUI`.
-- Move `{ role: 'system' }` messages from `prompt` or `messages` into top-level `instructions`. Only use `allowSystemInMessages: true` for trusted persisted messages.
-- Rename `experimental_prepareStep` to `prepareStep`.
-- In `prepareStep`, rename returned `system` to `instructions`.
-- In `experimental_repairToolCall`, use `{ instructions }` instead of `{ system }`.
-- Audit `prepareStep` behavior: returned `instructions` and `messages` now carry forward into later steps. If code depended on one-step-only overrides, rebuild from `initialInstructions`, `initialMessages`, and `responseMessages` explicitly.
-
-## Lifecycle Callbacks
-
-- `experimental_onStart` -> `onStart`.
-- `experimental_onStepStart` -> `onStepStart`.
-- `onFinish` -> `onEnd`.
-- `onStepFinish` -> `onStepEnd`.
-- For `embed`, `embedMany`, and `rerank`, `experimental_onFinish` -> `onEnd`.
-- Callback event fields use `instructions` instead of `system`.
-
-## Usage, Telemetry, and Include Options
-
-- `usage.cachedInputTokens` -> `usage.inputTokenDetails.cacheReadTokens`.
-- `usage.reasoningTokens` -> `usage.outputTokenDetails.reasoningTokens`.
-- OpenTelemetry moved out of `ai`; install `@ai-sdk/otel` and call `registerTelemetry(new OpenTelemetry(...))` at app startup.
-- Telemetry is enabled by default once an integration is registered. Remove redundant `isEnabled: true`; use `isEnabled: false` to opt out per call.
-- Move `experimental_telemetry.tracer` into the `OpenTelemetry` constructor.
-- `experimental_telemetry` -> `telemetry`.
-- Telemetry integration callbacks: `onRerankFinish` -> `onRerankEnd`, `onEmbedFinish` -> `onEmbedEnd`. Update tracing-channel subscribers for the same event type names.
-- `experimental_include` -> `include`.
-- `includeRawChunks` -> `include.rawChunks`.
-- Request and response bodies are excluded by default. If code reads `request.body` or `response.body`, opt in with `include.requestBody` and, for `generateText`, `include.responseBody`.
-
-## Streaming, Messages, and Tools
-
-- `StreamTextResult.fullStream` -> `stream`.
-- `streamText` `onChunk` now receives all stream parts, including lifecycle, boundary, finish, abort, and error parts. Guard by `chunk.type` before assuming text/tool/raw content.
-- `step.response.messages` is no longer accumulated across previous steps. Use `result.responseMessages` for the full response message history, or flatten `result.steps`.
-- Tool execution callbacks: `experimental_onToolCallStart` -> `onToolExecutionStart`, `experimental_onToolCallFinish` -> `onToolExecutionEnd`.
-- Tool callback `experimental_context` -> `context`.
-- Split shared runtime data from tool-specific data: use top-level `runtimeContext` for orchestration state, declare per-tool `contextSchema`, and pass per-tool values through `toolsContext`.
-- Move `needsApproval` from `tool()` / `dynamicTool()` into per-call or agent `toolApproval`.
-- `experimental_activeTools` -> `activeTools`.
-- `ToolCallOptions` -> `ToolExecutionOptions`.
-- `isToolOrDynamicToolUIPart` -> `isToolUIPart`.
-
-## Content Parts and Reasoning
-
-- Tool result `{ type: 'media' }` is removed; use `{ type: 'file-data' }`.
-- Migrate `toModelOutput` `image-*`, `file-*`, `file-id`, and `image-file-id` variants to canonical `{ type: 'file', mediaType, data: { type: 'data' | 'url' | 'reference', ... } }`.
-- User message `{ type: 'image', image, mediaType? }` is deprecated; use `{ type: 'file', mediaType: 'image' | 'image/*', data }`.
-- Add support for the new `reasoning-file` content type in exhaustive switches, renderers, serializers, and validators.
-- When adopting top-level `reasoning`, remove overlapping provider-specific reasoning settings from `providerOptions` unless provider-specific settings intentionally take precedence.
-
-## Multi-Step Result Shape
-
-- `result.usage` now includes all steps; `result.totalUsage` is deprecated. Use `result.finalStep.usage` for final-step-only usage.
-- Top-level `content`, `toolCalls`, `staticToolCalls`, `dynamicToolCalls`, `toolResults`, `staticToolResults`, `dynamicToolResults`, `files`, `sources`, and `warnings` now include all steps. Use `finalStep` for previous final-step-only behavior.
-- Top-level `reasoning`, `reasoningText`, `request`, `response`, and `providerMetadata` are deprecated for final-step data. Use `result.finalStep.*`; for `streamText`, await `result.finalStep`.
-- Apply the same result-shape rules to `onEnd` events.
-
-## Stream Response Helpers
-
-The `streamText` result helper methods are deprecated. Replace result methods with top-level stateless helpers:
-
-- `result.toUIMessageStream(...)` -> `toUIMessageStream({ stream: result.stream, ... })`.
-- `result.toUIMessageStreamResponse(...)` -> `toUIMessageStream(...)` plus `createUIMessageStreamResponse({ stream })`.
-- `result.pipeUIMessageStreamToResponse(response, ...)` -> `toUIMessageStream(...)` plus `pipeUIMessageStreamToResponse({ response, stream })`.
-- `result.toTextStreamResponse()` -> `toTextStream({ stream: result.stream })` plus `createTextStreamResponse({ stream })`.
-- `result.pipeTextStreamToResponse(response)` -> `toTextStream({ stream: result.stream })` plus `pipeTextStreamToResponse({ response, stream })`.
-
-## Package-Specific Checks
-
-- MCP: `MCPTransportConfig.redirect` now defaults to `'error'`. Only set `redirect: 'follow'` for trusted MCP servers that rely on redirects.
-- Vue: `@ai-sdk/vue` `Chat` class is deprecated. Prefer `useChat`, including getter/ref init for reactive chat inputs.
-- Anthropic and `@ai-sdk/google-vertex/anthropic`: `providerMetadata.anthropic.cacheCreationInputTokens` was removed. Use `usage.inputTokenDetails.cacheWriteTokens`; raw Anthropic usage remains at `finalStep.providerMetadata?.anthropic?.usage`.
-- Google: rename `GoogleGenerativeAI*` types, classes, and functions to `Google*`, e.g. `createGoogleGenerativeAI` -> `createGoogle`. The `google` entry point is unchanged.
-
-## Validation
-
-Run the project typecheck after edits, then the smallest relevant test suite. Also smoke-test streaming, chat UI, tool execution, telemetry, and multi-step flows if the migration touched them. If type errors remain, search the migration guide for the exact removed or renamed symbol before inventing a workaround.