mirror of
https://github.com/webstudio-is/webstudio.git
synced 2026-10-28 23:57:17 +09:00
This PR expands Webstudio MCP and CLI into a more complete agent authoring interface. Agents can discover project capabilities, edit real Webstudio content, use data/resources, verify visual output, and report useful issues when workflows fail. ## MCP User Capabilities - Create, update, duplicate, reorder, and delete pages. - Create pages from templates and manage reusable page templates. - Inspect project pages, instances, props, styles, assets, variables, resources, and metadata. - Insert Webstudio components and authored JSX fragments into pages. - Edit text, props, styles, breakpoints, design tokens, and CSS variables. - Update page metadata, SEO fields, redirects, marketplace metadata, and project settings. - Create and use static data variables. - Create and use dynamic resources fetched over HTTP. - Use REST, GraphQL, and built-in system resources in authored pages. - Bind data variables and resources to visible page content. - Create resource-backed pages such as sitemap XML, structured SEO data, and API-driven content sections. - Preview current project state without requiring a publish step. - Capture screenshots for visual verification. - Verify responsive designs across desktop, tablet, and mobile breakpoints. - Use screenshot diff and OCR-style checks to inspect rendered output. - Reset and refresh local MCP project state when needed. - Discover available CLI/MCP commands from generated manuals. - Use clearer examples for resources, data variables, JSX authoring, previewing, and visual checks. - Read marketplace product metadata without requiring a full project snapshot. - Get safer guidance when using low-level patch tools. - Get a ready-to-copy Discord report template when MCP/CLI behavior is confusing or broken.
40 lines
1.1 KiB
TypeScript
40 lines
1.1 KiB
TypeScript
const metrics: Array<{ phase: string; duration: number }> = [];
|
|
|
|
export const logPerf = (phase: string, startedAt: number) => {
|
|
const duration = Date.now() - startedAt;
|
|
metrics.push({ phase, duration });
|
|
console.info(`[e2e:perf] phase="${phase}" duration=${duration}ms`);
|
|
};
|
|
|
|
export const printPerfSummary = () => {
|
|
if (metrics.length === 0) {
|
|
return;
|
|
}
|
|
|
|
console.info("[e2e:perf:summary] begin");
|
|
for (const { phase, duration } of metrics) {
|
|
console.info(`[e2e:perf:summary] phase="${phase}" duration=${duration}ms`);
|
|
}
|
|
console.info("[e2e:perf:slowest] begin");
|
|
for (const { phase, duration } of [...metrics]
|
|
.sort((left, right) => right.duration - left.duration)
|
|
.slice(0, 30)) {
|
|
console.info(`[e2e:perf:slowest] phase="${phase}" duration=${duration}ms`);
|
|
}
|
|
console.info("[e2e:perf:slowest] end");
|
|
console.info("[e2e:perf:summary] end");
|
|
};
|
|
|
|
export const measure = async <Result>(
|
|
phase: string,
|
|
task: () => Promise<Result>
|
|
) => {
|
|
const startedAt = Date.now();
|
|
|
|
try {
|
|
return await task();
|
|
} finally {
|
|
logPerf(phase, startedAt);
|
|
}
|
|
};
|