Skip to main content
skill CX Codex

visant-copy — Claude Code skill: pt-BR copy and how to install

visant-copy is a Claude Code skill that writes and audits pt-BR copy in Visant's voice, with a linter for AI tics in PT and EN. It fires on requests about headlines or tone of voice.

MIT ★ 91 updated 2026-11-11

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add pedrojaques99/visant-skills-public --skill visant-copy -a claude-code
Open on GitHub

What visant-copy does

The skill keeps Brazilian Portuguese copy in Visant's voice, from a landing page to a signed post. Register comes first: signed, where a named person argues; house, where the company speaks as “a gente”; interface, where only the verb is left.

Ten rules are absolute across headline, body, CTA, FAQ, alt text and error copy. Dashes and the middle dot are out. So is the “não é X, é Y” frame, a negation left hanging at the end, emoji, semicolons, guru openings and urgency clichés. Credibility words such as “real” or “de verdade” get one use per page.

scripts/copy-lint.mjs is plain Node with no dependencies. It walks folders, skips generated files, and wants the files of one page in a single call, which is how a sentence repeated in two of them surfaces. Length warnings sit outside the exit code, so a headline that wraps to three lines on mobile does not fail the run. Anything the linter did not flag comes back as a proposal table with key, before and after, and the author picks the rows to apply.

What it helps with

  • rewrite a landing hero so it stops sounding like AI
  • check an article against the banned constructions before it ships
  • keep headlines and CTAs speaking in one voice
  • spot the same sentence repeated across a page's files
  • hand back a proposal table instead of a silent rewrite

Example prompts for the agent

  • Audit the copy in page.tsx and give me a table of proposed edits.
  • Rewrite the hero headline in the house register.
  • Run copy-lint on copy.json and walk me through each failure.

How to install visant-copy

1Skills CLI (Vercel)

npx skills add pedrojaques99/visant-skills-public --skill visant-copy -a claude-code

2Manually: put the files in place

~/.claude/skills/visant-copy/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/visant-copy/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about visant-copy

How do I install visant-copy in Claude Code?

Run npx skills add pedrojaques99/visant-skills-public --skill visant-copy -a claude-code. The files land at ~/.claude/skills/visant-copy/SKILL.md.

What does visant-copy do?

It writes and reviews Brazilian Portuguese copy in Visant's voice, from a landing page to a signed post, and runs copy-lint for AI tics in Portuguese and English.

What does visant-copy need to run?

Node, to run scripts/copy-lint.mjs; the linter pulls in no dependencies. An audit returns a table of rows and leaves the files alone until rows are picked.

Source text

SKILL.md · MIT
---
name: visant-copy
description: 'Writes, audits and reviews Brazilian Portuguese copy in Visant''s voice, from landing to signed post, and runs copy-lint, which catches AI tics in PT and English. Use on "copy", "headline", "landing copy", "audit the copy", "auditar o copy", "reescrever a dobra", "tirar cara de IA", "burilar a copy", "artigo", "newsletter", "tom de voz".'
metadata:
  family: texto
  routes: visant-headlines
---

# Visant Copy

Two things live here: **how Visant copy sounds** (valid in any repo) and **how it
is operated**, which depends on where the text lives. The voice below is for
Brazilian Portuguese; **for English copy read [english.md](references/english.md)**.
The linter runs a PT and an English rule set on every input.

- **The repo uses Visant's pipeline** (`copy*.json` at the root and
  `copy:build`/`copy:check` scripts in `package.json`): the JSON is the SSoT and
  the HTML is a generated view, so never edit text directly in the `.html`. See
  "If the repo uses Visant's pipeline".
- **Any other repo** (copy inside the component, `.md`, exported CMS): the
  component is the SSoT, and the risk is echo, the same sentence in four files.

Find out which one before touching text:

```bash
ls copy*.json 2>/dev/null; grep -nE '"copy:(lint|build|check)"' package.json
```

Either way, never write Visant copy without going through the prohibitions
below. **Asked to audit a page?** A clean linter says little: follow
[references/audit.md](references/audit.md).

## Pick the register first

The voice is one; who is speaking changes. Decide before the first sentence.

| register | pieces | who speaks | rhythm |
|---|---|---|---|
| **Signed** | essay, newsletter, post, thread, personal invitation | "eu", a named person with an opinion | ~17 words on average, room for a long sentence and a story |
| **House** | landing, product line, CTA, FAQ, sales email | "a gente" or "nossa", speaking for Visant | ~12 words, punch after the long sentence |
| **Interface** | button, label, error, caption | nobody, just the verb | as short as it stays clear |

Signed is where the voice comes from, so read
[the signed register](references/voice.md#8-signed-register-from-the-originals)
before writing anything longer than a section, in any register.

## Rule zero: propose, never apply

**Only the tic fixes the linter points out go into the file.** A headline, lead
or sentence that passes clean stays untouched, even if you think it sounds flat.

Style improvements go as a **proposal table in the report** (key, before, after),
and the user picks row by row. Rewriting what was already good burns trust and
makes the user review the reviewer.

**An audit changes nothing yet.** Asked to audit or review, deliver the table, tics
included, and ask which rows to apply.

**The exception is an explicit request.** "Essa copy tá confusa, tem que ser na
pegada X" is a work order, not an invitation to debate: apply it, show the
before/after table, and leave **one or two ONE-line alternatives** at the end, so
a swap costs one Edit and not a new round. Returning only options when the user
already gave the direction pushes the work back to them.

## The prohibitions

Absolute. They apply to headline, body, CTA, FAQ, email, caption, alt text,
error message, meta description. No "but here it worked" exception. The only
one is rule 3, and context decides it: [a real reversal is not the AI tic](references/voice.md#the-one-exception-a-real-reversal).

1. **Dash (— or –) never.** Period, comma, colon or parentheses.
2. **Separator dot (`·`, alt+7) never.** Not in metadata lists, not in a CTA with
   a price, not in a phase label, not on the social card. In a list it becomes
   period and comma ("34 páginas. 9 etapas, 1 case inteiro"), in a label a colon
   ("Fase 1: A Estratégia"), in a CTA a preposition ("Quero o e-book por R$ 47").
3. **"Não é X, é Y" never.** Not split in two sentences ("Não é uma lista. É uma
   cascata."). Not the sentence that defines by negation ("Não é slogan.").
4. **"É sobre X" never.** It asserts nothing. Swap it for the verb of what the
   thing does.
5. **"Não é apenas X, é X e Y" never.** Nor "mais que apenas", "menos X e mais
   Y", "não se trata de".
6. **Negation dangling at the end never.** "Feito pra ler, não pra arquivar."
   Delete the tail and the sentence gets stronger.
7. **Emoji never. Semicolon never.** (`©`, `®`, `™` are trademarks and stay.)
8. **Guru openings never.** "Imagine que", "E se eu te dissesse", "Prepare-se
   pra", "Chegou a hora de". Start with the fact or the scene.
9. **Cliché urgency never.** "Últimas vagas", "corre que acaba", "por tempo
   limitado". Scarcity must be countable: say the number ("este lote tem 30
   vagas", "a cota sobe a cada compra").
10. **Credibility seal at most once per page.** "real", "de verdade", "na
    prática", "de fato", "genuíno", "autêntico", "honesto". One passes. With two, the reader
    counts and posts a screenshot ("trajetória real, projeto real, técnica real,
    processo real"). An adjective does not prove; numbers and scenes do.
    `Sete anos de projeto real` → `Sete anos entregando marca`.

**The rule that solves 3 to 6: cut the negative half.** The sentence that remains
is almost always the right one. If the contrast really is the argument, show the
**consequence** instead of negating: instead of "não é falta de talento, é falta
de ordem", write "Talento você já tem. O que falta é ordem."

## The linter

Running it before delivering copy is mandatory. Plain node, no dependencies, runs
in any repo:

```bash
L=<skill-dir>/scripts/copy-lint.mjs
node $L copy.json                       # copy JSON
node $L hero.tsx page.tsx og.tsx        # components, passed TOGETHER
node $L README.md docs/landing.md       # markdown or plain text
npm run copy:lint                       # if the repo uses Visant's pipeline
```

Folders are walked, generated files skipped. Inputs, flags and rule ids: [references/linter.md](references/linter.md).

Exit 1 with the key, the excerpt and the fix. Two warnings come **outside the
exit code**, because good copy cannot fail on a detail:

- **length per line type** (headline 60, CTA 28, lead 180, body 280, SEO title
  60, meta description 160), inferred from the key suffix, so `.json` only; it
  flags the headline that breaks into three lines on mobile;
- **echo**, when the same sentence lives in two of the files passed in the same
  call. That is why you **pass the files together**, never one at a time.

In code files **comments are not linted** on purpose: a JSDoc is not copy.

### Repetition budget is per PIECE, and the file is not always the piece

`credibility-seal` (limit 1, PT and EN words share it) counts per piece: in JSON
the first key segment (`onboarding.*`), in a component the file. Money (`R$ 47`)
is not a seal; the rest is semantic, so confirm at `file:line`. [Why](references/cases.md).

## The voice

Pattern taken from Visant's e-book landing and from what the studio publishes
under its own name. In order of importance:

1. **Spoken Brazilian, by ear.** "para" and "pra" both live here: written lines
   lean "para", spoken beats take "pra", "tá", "tô". Never swap one for the other
   mechanically. No "cê", "mano", "tá ligado". Short imperative: "Lê e julga".
2. **Short sentence after short sentence.** Average 12 words. **A verbless
   fragment is a device**, always as a punch after the long sentence: "…e a marca
   se comporta de outro jeito três meses depois. Toda vez."
3. **Scene instead of adjective.** Never "inconsistência de marca". Write what is
   seen: "Um post fala uma coisa, o atendimento fala outra, o site parece de
   outra empresa."
4. **Blame starts with the author, and only if it happened.** Never invent a
   scene, memory or confession: [ask, or mark the place](references/voice.md#never-invent-the-personal-part). Confess before charging: "A gente começava
   pelo logo também. Perdeu semanas assim, até inverter a ordem." Accusing the
   reader directly ("você começa pelo logo porque é a parte divertida") only
   after the confession, if at all.
5. **Raw numbers, not rounded to impress.** `R$450k`, `160+ lives`,
   `34 páginas`, `7 dias`.
6. **Admit limits.** "Se algo não funcionou pra gente, tá escrito que não
   funcionou." It is what most separates the voice from AI text.
7. **Humor by mocking the market**, dry and unsignposted: "Sem aula de 40 horas
   ensinando a centralizar retângulo." It targets the practice, never the person.
8. **Mild swearing, at most one per page**, and only where the argument hurts:
   "porcaria", "cagada". Never in the CTA or the main headline.
9. **Objections in the reader's voice.** The FAQ is what the person thinks, in
   their words: "Já faço branding há anos. Vou ver algo novo?". The answer opens
   by answering ("Serve.", "É."), never with "Ótima pergunta".
10. **Takes a position and owns it.** "Eu acho triste", then "mas não importa se
    eu acho isso bom ou ruim". Grant the best counterargument before answering it.
11. **The specific analogy, announced.** "Um exemplo meio tosco": the Subway order
    with "exatamente 12 azeitonas pretas". Detail too exact to be invented is what
    AI text lacks.

For a long signed piece, follow the skeleton in
[voice.md §9](references/voice.md#9-structure-of-a-signed-piece-the-skeleton). For text that passes the
linter and still reads like AI, hunt the tells in [§10](references/voice.md#10-linguistics-what-makes-it-sound-brazilian).
For a script that will be read aloud, [§11](references/voice.md#11-spoken-scripts-video-narration).

Line-by-line detail, vocabulary, anglicisms, money, CTA, and the before/after
table: [references/voice.md](references/voice.md). Read it before writing a new
piece or rewriting a whole section.

### The fold and the product line: two mistakes invisible to every linter

**The fold (H1, `<title>`, social card) names the TASK, not the state.** State
copy describes the reader's world and leaves them to work out the gain; task
copy names the verb they came to do. Test: **which verb would the reader type
into Google?** Full test, examples and the wrong-task trap:
[voice.md → The fold names the task](references/voice.md#the-fold-names-the-task-not-the-state).

**The product line says what the reader gets**, not the mechanism from inside,
a list of nouns, or a promise the demo beside it contradicts. Full failure
modes: [voice.md → The product line](references/voice.md#the-product-line-says-what-the-reader-gets).

Visant's own brand terms: [glossary](references/voice.md#brand-glossary-visants-own-copy-only). In client copy, the glossary is the client's.

## If the repo uses Visant's pipeline (`copy.json`)

**Copy lives in the JSON. HTML and Markdown are generated views.** Editing text
in the `.html` is always wrong: the next build overwrites it and the check breaks
the deploy. Flow: edit the JSON, `npm run copy:lint`, `npm run copy:build`,
commit json + html + md together (`copy:check` in the gate catches drift). SEO
(`meta.title`, `meta.description`, `meta.og_*`) lives in the JSON too, injected
via `data-copy-attr="content"`.

Full mechanics (new key, new page, `data-copy-attr`, `\n` becoming `<br>`, orphan
key error, setting it up in a new repo): [references/pipeline.md](references/pipeline.md).

## When there is no `copy.json` (any other repo)

**The component is the SSoT.** Do not set up a `copy.json` in the middle of a text
task. The risk changes shape: the same sentence lives in three or four places, so
**after changing the headline, hunt the echoes** with `rg`. The social card and the
`<title>` get forgotten most. Where they hide, and why the `<title>` keeps the search
noun: [references/pipeline.md](references/pipeline.md#without-copyjson-echoes-in-a-component-repo).

## Work order on "review/write the copy"

1. Read the page's whole JSON (or the whole component) before touching any key.
   Including comments: they hold the WHY of the current line, and copy that
   contradicts the decision documented there is rework.
2. Run `copy-lint` to get the map of tics.
3. **Apply only the tic fixes**, and the rewrite the user asked for with a
   direction. Everything else becomes a proposal in a table.
4. Check every number against the source of truth (server-side price, client
   count, member count). The skill does not store those values on purpose: they
   age. When in doubt, ask before publishing.
5. **Hunt the echo** of the old sentence (`rg`, or the linter's echo warning with
   the files passed together) and update the social card, `<title>`, description
   and `alt`.
6. If you touched a code comment, update what it explains: a comment defending
   the old copy lies to the next dev.
7. Run `copy-lint` again. With Visant's pipeline, also `copy:build` and
   `copy:check`. In a React/TS repo, `tsc --noEmit`.
8. Report the before/after of the changed lines. The user approves text by
   reading text, never by reading a summary of the text.

## Neighbors

- **Feedback**: when the work is delivered, ask once per session, in one line, what helped and what was missing; it goes to https://ui.visantlabs.com/skills#feedback
- **[[visant-design]]**: the layout around the words
- **[[visant-killer]]**: a screen that looks AI-made; this skill handles text that reads AI-made
- **[[visant-headlines]]** (Visant internal): a client brand's voice; this skill is Visant's voice
- **[[visant-new-site]]** (Visant internal): the copy of a whole client site
- **[[revenue-centric-design]]**: the lever behind the message; this skill writes the sentence

© pedrojaques99 · MIT · pedrojaques99/visant-skills-public

Similar skills

All skills for Writing and docs →

From the same set12

The whole set →
visant-mcp-connect visant-mcp-connect is a Claude Code skill that connects the agent to Visant Labs over MCP. It activates for requests to set up Visant, use its tools, or extract information from a PDF. CX Codex +1 ★ 91repo stars visant-preflight visant-preflight is a Claude Code skill that runs a stakeholder questionnaire and validates brand assets, fonts, and images before new site builds or redesigns. CX Codex +1 ★ 91repo stars visant-video-editor visant-video-editor is a Claude Code skill that turns raw footage into an edited video by preparing a cut list and assembling approved cuts. It activates for requests to edit a vlog, lesson, or silence in a recording. CX Codex +1 ★ 91repo stars visant-premiere-editor visant-premiere-editor is a Claude Code skill that builds rough cuts in Adobe Premiere Pro from a JSON plan. It transfers timelines through FCP7 XML and MCP without dropping frames. CX Codex +1 ★ 91repo stars visant-refine visant-refine is a Claude Code skill for styling charts, gauges, sparklines, and control panels as parts of one interface. It activates for requests to add a chart, build a simulator slider, or polish a screen. CX Codex +1 ★ 91repo stars visant-frontend visant-frontend is a Claude Code skill that ties interface decisions to business variables and requires a route classification table. It activates for requests to redesign a screen, critique a UI, or assess visual hierarchy. CX Codex +1 ★ 91repo stars visant-killer visant-killer is a Claude Code skill that audits React JSX interfaces before pull requests. Catches AI generation tells, broken layout spacing, and forbidden CSS rules. CX Codex +1 ★ 91repo stars visant-motion visant-motion is a Claude Code skill for interface animation and micro-interactions. It activates on requests about transitions, loading states, skeletons, or smoother motion. CX Codex +1 ★ 91repo stars

Project sponsors

Companies that keep this analytics open