Cosa contiene

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

Fintech Landing

When to use

• You are launching a fintech product — payments, savings, lending, investing, or business money tools — and need a landing page that earns trust
• Your current page leads with growth claims and hides the fees, the regulator, and the security details in a footer link
• Cautious visitors bounce because they cannot tell whether your product is legitimate, safe, and fairly priced
• You need a page structure that puts compliance, security, and fees where a skeptical reader looks first
• You are preparing for a launch where journalists, partners, or regulators will read the page as closely as customers do

Workflow

1. Write the plain-language job (input: what the product does → output: hero headline)
   State what the product does with money in one line, using words a non-finance person would use: "Send money abroad for a flat fee" beats "Next-generation cross-border payment infrastructure." Follow it with one subline naming who it is for and what it costs in the simplest honest terms. If the headline needs the word "revolutionary," "disruptive," or "seamless," it is hiding a missing fact — replace the adjective with the fact.
2. Build the trust-first hero (input: headline → output: hero section with trust proof)
   In the hero, next to the headline, place the three facts a cautious visitor checks first: who operates the product (legal entity name), who regulates or licenses it (regulator and license type, in plain words), and how customer money is protected (segregated accounts, insurance, or equivalent — stated exactly, never exaggerated). Add one primary action and one quieter secondary action ("Read how fees work"). Everything in this step must be verifiable; if you cannot state it plainly and truly, it does not go on the page.
3. Explain the fees in plain language (input: hero → output: fees section)
   Give fees their own section, above the fold or one scroll down, with a short table or list: each fee, what triggers it, and the exact amount or percentage. Include the "zero" cases too — what is free, and under what conditions — and one worked example with real numbers ("Sending $500 costs $4.50 total. The recipient gets $495.50."). Never write "no fees" if any fee exists anywhere in the journey, and never bury a fee in a footnote that the table contradicts.
4. Show security and compliance proof (input: fees section → output: proof section)
   Below the fees, place the proof a careful reader checks: security practices in plain words (encryption, two-factor sign-in, fraud monitoring), the license or registration details with the regulator's name, and links to the terms, privacy policy, and complaints process. State plainly what the product is not — not a bank, not insured the same way as a bank, or whatever applies — because the reader who discovers that later will never trust you again.
5. Close with a calm decision path (input: proof section → output: complete page with footer)
   End with a short summary of the three things that matter — what it does, what it costs, how money is protected — and one primary action, plus a link to the full fee schedule and a way to contact a human. Add a footer with the legal entity name, registration numbers, and the date the page was last reviewed. Re-check every regulatory claim, fee figure, and link before publishing — a fintech page with one wrong number is worse than no page at all.

Anteprima del modello

Fintech Landing — Template

A landing page a cautious visitor can trust. Fill in the blanks with verifiable facts only.

Hero

• Headline (plain-language job): {what the product does with money, in ordinary words}
• Subline: {who it is for} + {what it costs, in the simplest honest terms}
• Operator: {legal entity name}
• Regulator / license: {regulator name, license type and number, plain words}
• Money protection: {segregated accounts / insurance / equivalent — stated exactly}
• Primary action: {action} | Secondary action: {Read how fees work}

Fees (own section, plain language)

Worked example: {Sending $X costs $Y total. The recipient gets $Z.}

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

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