Cosa contiene

Un file SKILL.md (la guida operativa) + un modello di partenza. Un'anteprima:

Silver Robot Product Site

When to use

• You have a robot product — a home assistant, an educational kit, a service robot — and need a site that sells it
• Your current product page is a wall of specs with no clear answer to "what does it do for me?"
• Buyers keep asking the same questions: how big is it, what can it lift, how long does the battery last, is it safe around kids or pets
• You are launching a new robot and need one site for the announcement, the details, and the order
• You have real photos and real specs, and you want the site's look — silver, clean, precise — to match the product

Workflow

1. Gather the real facts (input: specs, photos, safety notes, price → output: fact sheet)
   Write down what is actually true about the robot before any copy is written: dimensions, weight, battery life, payload, sensors, what it can and cannot do, safety certifications or test results, price, and what is in the box. Note every claim's source — a spec sheet, a test report, a manual. Anything without a source stays off the site. Photograph the actual product in silver, from the front, side, and in use; renders are fine only if they are labeled as renders and match the real product.
2. Build the hero (input: fact sheet + photos → output: hero section)
   The hero answers three questions in seconds: what is it, who is it for, and what is the one thing it does best. One strong product photo, one headline stating the main benefit, one line of supporting fact, and one call to action ("See it in action", "Pre-order", or "Read the specs"). No feature list in the hero, no three competing buttons. If a stranger cannot say what the robot does after five seconds on the hero, rewrite the headline before building anything else.
3. Write the sections (input: fact sheet → output: section drafts)
   Build the sections in the order a buyer thinks: what it does (two or three real use cases, each with a photo), how it works (the key features, each tied to a visible part or behavior), the full spec table (every number from the fact sheet, in one table, with units), safety (who it is safe around, what it will not do, how it stops), what's in the box, and price with availability. The spec table is the contract: if a number is approximate, label it approximate; if a feature is coming later, label it "coming" with a date or leave it out.
4. Answer the doubts (input: section drafts + real buyer questions → output: FAQ and trust block)
   Collect the questions real buyers actually ask — from support emails, demo days, or pre-launch inquiries — and answer each in two or three sentences with facts, not reassurance. Add a trust block: warranty length, returns window, support contact, and where the robot is made or serviced, stated plainly. Never invent a review, a customer count, or an award; if you have genuine testimonials, quote them verbatim with the speaker's name and role. A product site that admits one limitation ("not suitable for stairs") is believed about everything else.
5. Launch checks (input: full site → output: verified live site)
   Run six checks before launch: the hero reads correctly on a phone, every spec number matches the fact sheet, every photo shows the real product (or is labeled a render), the price and availability match what buyers will actually be charged, the buy or pre-order button works end to end, and the safety section is complete and accurate. Fix failures before launch. After launch, re-check the price, availability, and safety text every time the product changes — a product site that lags behind the product is a liability.

Anteprima del modello

Silver Robot Product Site — Site Template

One product = one filled-in copy of this template. Facts first, copy second.

Fact sheet (every claim needs a source)

Can do: {…} · Cannot do: {…} · Coming later (with date, or leave out): {…}

Hero

Headline (what it is + who it is for + best capability): {…} Supporting fact (one line): {…} Hero photo: {real product photo file} · Call to action: {e.g. See it in action / Pre-order / Read the specs}

Sections

What it does — use case 1: {…} · Photo: {file} What it does — use case 2: {…} · Photo: {file} What it does — use case 3: {…} · Photo: {file}

Il pacchetto della skill (SKILL.md + modello) è scritto in inglese.

Acquista il pacchetto completo della skill — $4.99 Pro — tutte le 511 skill