arm-pz

Site Prompt — Development skill for Claude Code

Development community

Agent skill that turns a website topic or landing-page brief into one self-contained build prompt: subject-native concept, final copy, every source file embedded verbatim, and a replay check that comp.

How to install Site Prompt

This entry records only its repository, not the path inside it, so there is no exact command to give. Open arm-pz/site-prompt and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Site Prompt does

Alternatives in Development

Om Meeting — Prep for any meeting by topic — subject-forward briefing with open tasks, blockers, and brainstormed considera 4.6k ★
15 — Build a Next.js 14 portfolio landing page with a full-screen hero section and an animated loading screen 152 ★
Little Agent — A lightweight embedded agent framework (similar to Claude Code and OpenAI Codex) 95 ★

README

site-prompt

An agent skill that turns a website topic into one self-contained, paste-and-build prompt. Give it "cargo ship", "a ferry between Athens and the Cyclades" or "a marine insurance broker", and it returns one markdown file with the concept, final copy, complete source for every file, and the checks that were actually run — enough for a fresh agent to rebuild the site without seeing the session that produced it.

It does not stop at an outline or a list of sections. It narrows a category to one concrete subject, derives the page from that subject's world, builds and verifies the site in a scratch folder first, then embeds each file verbatim under a `## File:` heading. The included replay verifier materialises the prompt into a clean directory and compares it against the built site, so "complete source" is tested rather than claimed.

Install

npx skills add arm-pz/site-prompt --skill site-prompt

Or clone this repository into `~/.qoder/skills/site-prompt` (Qoder) or `~/.claude/skills/site-prompt` (Claude Code), then start a new session. The skills CLI resolves this repo; `--list` reports one skill.

Ask it things like

"Write a one-shot build prompt for a cargo-ship company landing page."
"Here's a SELENE-style prompt. Make one like it for a ferry between Athens and the Cyclades."
"I need a mega-prompt that rebuilds a tugboat charter site — every file, no placeholders."
"Produce a prompt for a marine insurance broker whose design could only belong to that subject."

What a run produces

One markdown file, in this order: the subject brief and the page's job; the load-bearing behaviours with their contracts; hard build constraints; a pinned stack with exact versions; code-native asset rules; the steps and verify commands; one `## File:` section per file with the complete contents; design notes; and the checks that ran, with the remainder listed as not verified.

Every prompt has to pass two tests before it ships: