Skill

edit-site

Edit a Flint website using a background AI agent. Use when the user wants to modify, update, or add content to their Flint managed website.

Install

npx claudepluginhub anthropics/claude-plugins-official --plugin flint

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Help the user modify a Flint website by running a background AI agent.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.0k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-distillator

7 files

Compresses source documents into lossless, LLM-optimized distillates preserving all facts and relationships. Use for 'distill documents' or 'create distillate' requests.

bmad-pro-skills

43.8k

Stats

Stars0

Forks0

Last CommitMar 24, 2026

Actions

View Source View Plugin View on GitHub View README

Edit a Flint Site

Help the user modify a Flint website by running a background AI agent.

Workflow

Find the site: Call list_sites to get the user's available sites. If $ARGUMENTS contains a site name, match it. If there are multiple sites and the user didn't specify, ask which one.

Run the agent: Call run_background_agent with the site ID and a prompt describing the changes.

Describe goals and intent, not implementation details
If the user provided code, examples, or reference material, pass them through as-is
Do NOT generate HTML, CSS, or markup — Flint is an expert designer and produces better results with creative freedom

Monitor progress: Call check_background_agent_status to track the agent.

Wait 90-120 seconds between status checks
A single agent typically finishes in 4-5 minutes
Multiple concurrent agents take longer (10 agents may take ~15 minutes)

Report results: When complete, share the summary of changes and the preview URL.

Important guidelines

Flint is an expert web designer. Describe what you want, not how to build it.

Always honor the user's explicit requests (e.g., "make the header black", "use a three-column grid") — pass that intent through.

Only use publish_site if the user explicitly asks to publish or deploy. It deploys the entire site.

Edit a Flint Site

Help the user modify a Flint website by running a background AI agent.

Workflow

Find the site: Call list_sites to get the user's available sites. If $ARGUMENTS contains a site name, match it. If there are multiple sites and the user didn't specify, ask which one.
Run the agent: Call run_background_agent with the site ID and a prompt describing the changes.
- Describe goals and intent, not implementation details
- If the user provided code, examples, or reference material, pass them through as-is
- Do NOT generate HTML, CSS, or markup — Flint is an expert designer and produces better results with creative freedom
Monitor progress: Call check_background_agent_status to track the agent.
- Wait 90-120 seconds between status checks
- A single agent typically finishes in 4-5 minutes
- Multiple concurrent agents take longer (10 agents may take ~15 minutes)
Report results: When complete, share the summary of changes and the preview URL.

Important guidelines

Flint is an expert web designer. Describe what you want, not how to build it.
Always honor the user's explicit requests (e.g., "make the header black", "use a three-column grid") — pass that intent through.
Only use publish_site if the user explicitly asks to publish or deploy. It deploys the entire site.