From 30ff360cca53f33688fa15e3160be310d16a535e Mon Sep 17 00:00:00 2001 From: Michael Ramos Date: Wed, 2 Sep 2026 11:55:31 -0700 Subject: [PATCH] feat(site): refine landing page agent setup --- apps/site/src/pages/index.astro | 94 ++++----- apps/site/src/styles/landing.css | 317 +++++++++++-------------------- 2 files changed, 160 insertions(+), 251 deletions(-) diff --git a/apps/site/src/pages/index.astro b/apps/site/src/pages/index.astro index e5a47f2..691b1b7 100644 --- a/apps/site/src/pages/index.astro +++ b/apps/site/src/pages/index.astro @@ -33,6 +33,28 @@ const agents = [ { name: "Pi", tier: "native", light: piLight.src, dark: piDark.src }, { name: "OpenCode", tier: "native", light: opencodeLight.src, dark: opencodeDark.src }, ]; + +const setupPrompt = `Install and configure Artifact Server for me. Do the work, not only explain the steps. + +Use these pages as the source of truth: +- https://artifactserver.com/docs/get-started/ +- https://artifactserver.com/docs/deploy/ +- https://artifactserver.com/docs/mcp/ +- https://artifactserver.com/docs/agents/ + +First, ask me exactly one question: “Do you want to run Artifact Server locally on this machine, or deploy it for a team?” Wait for my answer before you continue. + +Then complete the matching setup: + +- Inspect the system before you make changes. Follow the current documentation and do not invent commands. +- For a local setup, verify that Node.js 24.12 or later and pnpm 10.34.3 are available. Use the current source checkout when one exists. Otherwise, clone https://github.com/plannotator/artifact-server.git, install its dependencies, and run \`pnpm dev\`. Keep the server on loopback only and use the URL printed by the process. +- For a team deployment, ask only for choices or credentials that are still missing. Explain the current qualification status of the available deployment targets. Follow the selected deployment guide, keep secrets out of source control, use HTTPS for the trusted application origin, configure an isolated wildcard content domain, and configure backups. Do not describe AWS or Google Cloud as live-qualified deployments. +- Install the Artifact Server skill with \`npx skills add plannotator/artifact-server\`. +- Connect this agent to Artifact Server through MCP as part of the setup. From a source checkout, run \`pnpm artifactserver connect --data .artifact-server\`. With an installed CLI, run \`artifactserver connect\`. For a team deployment, configure the exact HTTPS \`/mcp\` endpoint and complete browser authorization. Never print or paste bootstrap URLs, tokens, or credentials into chat. +- Verify the server health, the review application, the installed skill, and MCP tool discovery. Fix failures that are within the setup scope. +- Do not stop after producing a plan. Complete the setup unless you need a credential or a deployment choice from me. + +When the setup is complete, begin your final response with “Artifact Server is running at .” State whether it is local or deployed for a team, where its data is stored, whether the skill is installed, whether this agent is connected through MCP, and what you verified. Link to https://artifactserver.com/docs/ for operating guidance. If anything is incomplete, list the exact blocker instead of claiming success.`; --- @@ -66,21 +88,28 @@ const agents = [ -
-

- artifactserver connect - connect your agent - -

-

- npx skills add plannotator/artifact-server - install the skill - -

+ + + + Connect MCP + +
@@ -150,7 +179,7 @@ const agents = [

Why Artifact Server

-

Own your team's development process outputs

+

Own your team's SDLC outputs

Product teams create plans, mockups, prototypes, and code reviews as HTML, images, and video. These files often end up scattered across tools. @@ -162,7 +191,7 @@ const agents = [

01 -

Publish from where the work happens.

+

Integrated with Agents

Agents publish through MCP or the Agent Skill. People use the CLI or browser. Each upload can contain one file or a complete site.

/artifact-server upload that HTML design doc
@@ -234,33 +263,6 @@ const agents = [ -
-
-

Security model

-

Untrusted artifacts stay isolated.

-

- Artifact Server serves untrusted content from an isolated host for each - version. The trusted application host handles authentication, metadata, - comments, the API, and MCP. Private content uses browser sessions scoped to - one version. Untrusted paths cannot select storage locations. -

- Understand the two-origin model -
- -
-

Yours to run

@@ -330,16 +332,18 @@ const agents = [