Agentic Site Building

Community

divyanshu-iitian

agentic-site-building

Design, implement, or harden an AI website-building agent that turns natural-language requests into scoped code changes with planning, structured edits, deterministic verification, bounded repair, safe previewing, version history, and token-aware model routing.

Overview

Publisher	divyanshu-iitian
Repository	`agent-website-design-skills`
Skill name	`agentic-site-building`
Stars	4
Forks	0
Bundled files	2
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by divyanshu-iitian on GitHub. Read the source before you install it.

Installation

Install the Agentic Site Building AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/divyanshu-iitian/agent-website-design-skills/tree/main/agentic-site-building
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/divyanshu-iitian/agent-website-design-skills/tree/main/agentic-site-building

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/divyanshu-iitian/agent-website-design-skills.git /tmp/agent-website-design-skills
mkdir -p .claude/skills
cp -r /tmp/agent-website-design-skills/agentic-site-building .claude/skills/agentic-site-building

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agentic Site Building in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Agentic Site Building on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Agentic Site Building is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Agentic Site Building

Build editing systems that can prove a requested change happened without rewriting unrelated work or claiming success on a no-op.

Workflow

Map the editable artifact, source of truth, preview boundary, model providers, persistence, and rollback path.
Compile each request into an explicit contract: mode, target surface, allowed change radius, acceptance criteria, and risk.
Prefer a structured patch for an existing artifact. Require exact, unique anchors and a bounded change budget.
Apply patches locally, then validate syntax, structure, requested-surface change, and collateral-change limits.
If validation fails, give the verifier evidence to one bounded repair attempt. Escalate to a full rewrite only when scope requires it or patching is unsafe.
For redesigns, reject the current composition deliberately while preserving factual content and product constraints.
Render generated code in an isolated preview. Keep authentication, storage, parent DOM, and privileged network access outside the generated runtime.
Save only accepted outputs. Keep restorable revisions with prompt, mode, verifier result, and prompt/model version.
Expose honest progress and failure states. Never label an unchanged or unverified preview as updated.
Measure patch success, no-op rate, repair rate, latency, token cost, rollback rate, and user acceptance.

Decision Rules

Deterministic code owns safety and common runtime contracts; the model owns interpretation and creative composition.
A small edit should not receive the full site unless the patch path fails safely.
Verification must inspect the requested surface, not only whole-file similarity.
Retries must use new evidence and stop after a fixed budget.
Provider fallback handles availability; it must not silently weaken required structured-output or context capabilities.
Keep generated code facts grounded in user data. Do not invent projects, metrics, employers, or media.

Delivery Contract

Provide or implement:

Execution contract - modes, scope, acceptance criteria, and escalation rules.
Orchestration path - plan, patch or build, validate, repair, persist, preview, rollback.
Verifier design - deterministic checks and evidence returned to repair attempts.
Safety boundary - generated-code sandbox and authorization limits.
Efficiency budget - context selection, model routing, retries, and stopping conditions.
Operational proof - tests for no-op, collateral edit, failed patch, retry, rollback, and preview isolation.

Reference

Read references/orchestration-contract.md when defining schemas, retry policy, or production metrics.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Agentic Site Building AI skill do?

Why use Agentic Site Building on TypingMind?

Because you install it once and use it with any model. Agentic Site Building is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Agentic Site Building in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/divyanshu-iitian/agent-website-design-skills/tree/main/agentic-site-building. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Agentic Site Building?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Agentic Site Building?

As many as you like. As long as a model supports skills, you can use Agentic Site Building with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Agentic Site Building AI skill free?

Yes. It is published on GitHub by divyanshu-iitian under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Writing For Agents

mattpocock

CommunityPopular

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Auteur

Design and build cinematic, award-level web pages.

Excalidraw

Hand-drawn Excalidraw JSON diagrams (arch, flow, seq).

Simple English

Rewrite text to ASD-STE100 Simplified Technical English.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Agentic Site Building

Workflow

Decision Rules

Delivery Contract

Reference

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now