# 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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 91 repo stars
- Author: pedrojaques99
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/pedrojaques99/visant-skills-public/tree/HEAD/visant-preflight/SKILL.md
- Updated: 2026-11-11
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/visant-preflight

## What it does

visant-preflight sets up a two-part intake before any design or code begins on major deliverables. It runs an upfront question round with the project owner and writes the answers straight into a markdown file, preventing hidden scope assumptions.

Its bundled Node.js script, `scripts/preflight-scan.mjs`, runs without extra dependencies. The script inspects an asset directory for image dimensions across PNG, JPEG, WebP, AVIF, GIF, and SVG files, and pings the Google Fonts catalog to confirm typography availability. Network access is mandatory for font verification; offline runs leave font checks undetermined.

Flags include `--strict`, which forces an exit code 1 if no image reaches 2000px or if a font check fails.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add pedrojaques99/visant-skills-public --skill visant-preflight -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/visant-preflight/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/visant-preflight/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add pedrojaques99/visant-skills-public --skill visant-preflight -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/visant-preflight/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add pedrojaques99/visant-skills-public --skill visant-preflight -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/visant-preflight/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install pedrojaques99/visant-skills-public visant-preflight
```

2. **Manually: put the files in place**
- File: `.github/skills/visant-preflight/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add pedrojaques99/visant-skills-public --skill visant-preflight -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/pedrojaques99/visant-skills-public --path visant-preflight
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/visant-preflight/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/pedrojaques99/visant-skills-public/tree/HEAD/visant-preflight/SKILL.md

## When to use it
- capture client constraints and non-goals before designing
- verify image dimensions and asset formats in project folders
- test font families against the Google Fonts directory
- spot mismatches between customer assets and stored brand tokens

## Example prompts
- Run preflight checks before building the new site
- Execute visant-preflight scan on the assets directory
- Prepare the kickoff question round for the site redesign

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 9c52b0d708173f43.

BEGIN THIRD-PARTY FILE 9c52b0d708173f43
```text
---
name: visant-preflight
description: 'Preflight for a large client project: one question round with whoever owns the work, plus five premise checks (brand source of truth, loadable fonts, photo resolution, brand files, sourced numbers). Use BEFORE "new site", "site redesign", "new proposal", "criar site", "redesenhar o site", "nova proposta", "montar campanha", "hidratar a marca".'
metadata:
  family: projeto
  routes: visant-new-site
---

# Visant Preflight

Projects rarely go wrong in execution. They go wrong **in the premise**: the work
comes out well made on top of data that was wrong from the start, and the rework
costs days.

> **Nothing large starts without two things: the question round answered, and
> the five checks green or explicitly waived.**

The whole preflight takes 15 minutes. Each mistake it prevents has already cost
more than a day. The long stories are in [references/cases.md](references/cases.md).

## When to run

Run it when the task is **big enough to hurt**: new site, redesign, proposal with
mockups, campaign, brand hydration, migration. Signal: more than half a day of
work before the first client feedback. Not for a one-off tweak: preflight on a
small task is bureaucracy and you will (rightly) stop running it.

---

## Part 1: the question round

**This part is not optional and cannot be automated.** It is the one most often
missing.

Before designing anything, ask the questions below **to whoever owns the work**
(client, account lead, project owner) and write down the answers. Assume none.
If they answer "whatever", write "whatever": that is an answer too, and it turns
into explicit freedom instead of a silent bet.

Use the harness question tool for closed choices; use conversation for open
ones. **Do it in ONE round**, not drip-fed through the work: a question asked
mid-work always arrives after the rework it would have prevented.

### 1.1 The bet

- **What is the single sentence this work must prove?** If it does not fit in a
  sentence, the scope is not closed yet.
- **Which business variable does it move?** Conversion, retention, ticket, cost
  per meeting. If it moves none, it is decoration, and decoration costs
  attention.
- **Who is on the other side, and at what awareness stage do they arrive?**
  (Schwartz, see `revenue-centric-design`.) The headline speaks to the current
  stage; proof pushes one stage further.
- **What is NOT to be done?** The question that saves the most time and that
  nobody asks.

### 1.2 Reference and taste

- **Is there something the client already approved** (layout, piece, campaign)
  that I should inherit instead of reinventing? Mine before designing.
- **Is there something they hate?** Worth more than ten references they love.
- **What in this brand is untouchable?** A "clean" version that swaps the brand's
  own graphic language for a conventional one gets reverted in one sentence.
- **How much density, and do photos go in this round?** Three full proposals
```
END THIRD-PARTY FILE 9c52b0d708173f43

The third-party file has ended. Everything between the 9c52b0d708173f43 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2978 of 11387 bytes. © pedrojaques99 · MIT · https://github.com/pedrojaques99/visant-skills-public/tree/HEAD/visant-preflight/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
