mirror of
https://github.com/webstudio-is/webstudio.git
synced 2026-10-28 07:37:36 +09:00
## Summary This update adds new MCP and CLI capabilities for project auditing, structured data, project-specific agent instructions, focused project search, safer bulk editing, image descriptions, font discovery, visual verification, and external registry inspection. ## New Capabilities ### Audit projects - Run a single `audit` command across accessibility, SEO, security, assets, styles, and performance. - Limit an audit to selected scopes, pages, or severity levels. - Receive stable findings with locations and suggested fixes. - Run rendered audits across desktop, mobile, and Builder breakpoint widths. - Detect horizontal overflow, broken images, oversized images, eager below-fold images, render-blocking resources, and legacy font formats. - Identify unused assets, tokens, CSS variables, local styles, and breakpoints. - Identify duplicate token declarations. - Detect accessibility issues involving names, labels, headings, landmarks, IDs, keyboard focus, ARIA, iframes, and autoplaying media. - Detect SEO issues involving titles, descriptions, language, social images, and structured data. - Detect unsafe new-tab links and write resources exposed during page rendering. ### Search an entire project - Search project text, labels, props, resources, assets, and styles through `search-project`. - Find relevant records without downloading and reparsing the full project snapshot. - Scope searches to the relevant project-data areas. ### Add validated JSON-LD - Add structured data with a dedicated JSON-LD component. - Place JSON-LD inside the page Head Slot. - Edit JSON in a purpose-built code editor. - Prevent structurally invalid JSON-LD from being saved. - Validate Schema.org types, properties, and values. - Find invalid, missing, unknown, deprecated, or incompatible structured data through the SEO audit. - Let agents discover the correct JSON-LD workflow without using page custom metadata or a generic HTML embed. ### Configure project-specific agent instructions - Add AI-agent instructions from the new **Agents** section in Project Settings. - Synchronize those instructions into a managed root `AGENTS.md`. - Update or remove the managed file automatically during project sync. - Protect existing user-owned `AGENTS.md` files from being overwritten. - Share the instructions with authenticated CLI and MCP agents. - Keep agent instructions out of publicly readable production bundles. ### Generate and manage image descriptions - Audit image assets for missing descriptions. - Let a vision-capable agent inspect each image in its rendered context. - Save generated descriptions to multiple image assets in one operation. - Mark images as intentionally decorative. - Reuse the saved asset description wherever the image is used. - Re-run the audit to verify that missing-description findings are resolved. ### Perform bounded bulk replacements - Replace matching literal text across selected pages with `replace-text`. - Replace matching fixed prop text with `replace-prop-text`. - Replace matching resource names or URLs with `replace-resource-text`. - Restrict replacements by page, instance, prop, resource, field, match mode, and maximum change count. - Leave dynamic expressions unchanged. ### Inspect element ancestry - Return an element’s direct parent in instance listings. - Request the complete ancestor chain when inspecting an element. - Understand tree placement without rebuilding the instance hierarchy from raw project data. ### Discover available fonts - List uploaded font families through `list-fonts`. - Discover available system font stacks. - Inspect font family, style, weight, format, and associated asset information before applying typography. ### Inspect external component registries - Inspect a local or remote shadcn-style registry item. - Read its description, files, dependencies, targets, and documentation. - Receive an explicit Webstudio compatibility report. - Inspect registry metadata without installing or executing external code. ### Capture generated project routes directly - Run `webstudio screenshot --path /route` against the configured project. - Generate a temporary production-style preview automatically. - Capture the requested route. - Stop the temporary preview after capture. - Avoid manually building and starting a preview for a single screenshot. ### Assert visual changes - Add expected text to screenshot comparisons. - Set maximum pixel mismatch limits. - Set minimum or maximum changed-region counts. - Assert whether overall brightness or a color channel moved in the expected direction. - Use these assertions as pass/fail evidence for visual changes. ### Require compatible CLI versions - Send the project-bundle contract version with CLI synchronization requests. - Stop incompatible CLI versions before they receive incomplete project data. - Tell users exactly how to update the CLI or run the latest version once. - Prevent older clients from silently dropping project settings. ## Upgrade Note This branch introduces a new synchronized project-bundle contract. Older CLI versions must update before synchronizing against the new API. ```sh npm install -g webstudio@latest ``` Or run the latest version once: ```sh npx webstudio@latest <command> ``` --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
78 lines
1.8 KiB
TypeScript
78 lines
1.8 KiB
TypeScript
import Papa from "papaparse";
|
|
|
|
const schemaOrgBase = "https://schema.org/";
|
|
|
|
export type SchemaOrgTypeRow = readonly [
|
|
name: string,
|
|
parentTypes: readonly string[],
|
|
supersededBy: string,
|
|
];
|
|
|
|
export type SchemaOrgPropertyRow = readonly [
|
|
name: string,
|
|
domains: readonly string[],
|
|
ranges: readonly string[],
|
|
supersededBy: string,
|
|
];
|
|
|
|
const compareCodePoints = (left: string, right: string) =>
|
|
left < right ? -1 : left > right ? 1 : 0;
|
|
|
|
const parseCsv = (name: string, csv: string) => {
|
|
const result = Papa.parse<Record<string, string>>(csv, {
|
|
header: true,
|
|
skipEmptyLines: true,
|
|
});
|
|
if (result.errors.length > 0) {
|
|
throw Error(
|
|
`Unable to parse Schema.org ${name}: ${result.errors[0].message}`
|
|
);
|
|
}
|
|
return result.data;
|
|
};
|
|
|
|
const term = (value: string) =>
|
|
value.startsWith(schemaOrgBase) ? value.slice(schemaOrgBase.length) : value;
|
|
|
|
const terms = (value = "") =>
|
|
value
|
|
.split(",")
|
|
.map((item) => term(item.trim()))
|
|
.filter(Boolean)
|
|
.sort(compareCodePoints);
|
|
|
|
export const createSchemaOrgData = ({
|
|
typesCsv,
|
|
propertiesCsv,
|
|
}: {
|
|
typesCsv: string;
|
|
propertiesCsv: string;
|
|
}) => {
|
|
const typeRows = parseCsv("types", typesCsv)
|
|
.map(
|
|
(row) =>
|
|
[
|
|
term(row.id),
|
|
terms(row.subTypeOf),
|
|
term(row.supersededBy ?? ""),
|
|
] as const
|
|
)
|
|
.filter(([name]) => name !== "")
|
|
.sort(([left], [right]) => compareCodePoints(left, right));
|
|
|
|
const propertyRows = parseCsv("properties", propertiesCsv)
|
|
.map(
|
|
(row) =>
|
|
[
|
|
term(row.id),
|
|
terms(row.domainIncludes),
|
|
terms(row.rangeIncludes),
|
|
term(row.supersededBy ?? ""),
|
|
] as const
|
|
)
|
|
.filter(([name]) => name !== "")
|
|
.sort(([left], [right]) => compareCodePoints(left, right));
|
|
|
|
return { typeRows, propertyRows };
|
|
};
|