Skip to content
Veritas
  • Nothing matches. Try the name of a library or a stack.

Titles, descriptions and sections of every skill.

Veritas

Engineering conventions, one per stack, written inside the project. Your AI assistant reads them before it writes code.

A new project, conventions included

npm create veritas@latest my-app

Or just the skills, in Claude Code

/plugin marketplace add Caiorhcp/veritas
/plugin install veritas@veritas

Included: Ponytail (less code, fewer tokens) and Graphify (a map of your code)

How it works

Install once. Everything else happens inside the project.

Code

Code that already runs

Routes, global state, an HTTP client and a sample form, all working on the first npm run dev.

.veritas/

The rules, in .veritas/

One folder per convention, with the same text as the plugin, and an INDEX.md that says which one applies when.

AGENTS.md

A pointer for every assistant

AGENTS.md and CLAUDE.md get a block telling the assistant to read .veritas/INDEX.md before changing code. Codex, Cursor and Copilot read one; Claude Code, the other.

init

Old projects too

In a repository that already exists, init detects the stack and writes only the conventions. What was already in AGENTS.md stays intact.

One convention per stack

Each one says which libraries to use, which layer everything lives in and what is forbidden. A violation is an error, not a suggestion.

See all skills →
@/

React + Vite

Checked against Vite 8.0.1 · Generates a project with --stack vite

Every screen in src/pages/ with a route in AppRoutes.tsx. An API call becomes a typed service, consumed through TanStack Query.

react-router-dom · Tailwind · Zustand · Axios + TanStack Query · React Hook Form + Zod · lucide-react

'use client'

Next.js

Checked against Next.js 16.2.4 · Generates a project with --stack nextjs

Server Components by default, 'use client' only where there is state or an event. Mutations through Server Actions.

App Router · Tailwind + shadcn/ui · React Hook Form + Zod · SWR / TanStack Query · Prisma / Drizzle

service

Django / DRF

Checked against Django 5.2

View, serializer, service, model. Business logic only in the service; the admin delegates too.

DRF · Django ORM · SimpleJWT · uv

@Module

NestJS

Checked against NestJS 11

DTOs with class-validator and exactly the properties the service needs. Routes protected by a JWT guard.

TypeORM / Prisma · class-validator · @nestjs/jwt · @nestjs/swagger

<View>

React Native

Checked against React Native 0.86.2

No div or span. SafeAreaView, flexbox, and FlatList without heavy inline functions in render.

React Navigation · NativeWind · Zustand · MMKV

uv

Python

Checked against original

Type hints on every signature, PEP 8, Pydantic for structured data and environments managed by uv.

ruff · pytest · Pydantic · uv

bun test

Bun + Hono

Checked against original

Nine prohibitions, among them: HTTP input without Zod, generic errors and refresh tokens stored in the database.

Bun · Hono · Drizzle · Zod · uuidv7 · Biome

Every question has a flag

In a terminal with nobody on the other side (CI, an agent, a script), a missing answer is an error. No default is picked in silence.

--stack vite|nextjs
what to generate
--skills vite,lgpd
exactly these conventions
--dir apps/web
where to write
--yes
confirm init without asking
--no-install
write the files and stop
--lang en
messages in English
Full CLI reference →
--stack
A terminal with nobody there, in CI
$ npx create-veritas new my-app --lang en < /dev/nullMissing answer and the terminal is not interactive. Pass --stack <vite|nextjs>.$ echo $?1$ npx create-veritas new my-app --stack vite --no-install --lang en✓ Done: my-app
npx create-veritas new my-app --stack vite --skills vite,principios,lgpd,atomic-design --no-install

Less code, fewer tokens: Ponytail

Veritas says what to use and where everything lives. Ponytail, by Dietrich Gebert, says how much to write: the smallest change that solves it. Together they are the pair Veritas recommends for every project.

/plugin install ponytail@veritas

Ponytail is a project by Dietrich Gebert, under the MIT license. All credit is his: Veritas only recommends it and makes it easy to install. @DietrichGebert

See Ponytail on GitHub
  • What it doesPuts the agent in lazy senior dev mode: YAGNI, standard library first and no abstraction nobody asked for. Less code to review and fewer tokens spent.
  • How it fits into VeritasInstalling Veritas installs Ponytail, straight from its author's repository. Updates come from there, with no copy of ours in between.
  • When to use itOn any coding task. Veritas skills set the stack and the prohibitions; Ponytail trims what's left. To review a change, /ponytail-review; to audit a whole repository, /ponytail-audit.

A map of your code: Graphify

Graphify, by Graphify Labs, turns a project's code and documents into a graph you can query. Veritas installs it alongside and says when it's worth it: before changing a large or unfamiliar project, and for architecture or impact questions.

/graphify .

Graphify is a project by Graphify Labs, under the Apache-2.0 license. All credit is theirs: Veritas packages the official skill unchanged and makes it easy to install. @Graphify-Labs

See Graphify on GitHub
  • What it doesReads code through its syntax tree, spending no tokens, and builds a graph of files, functions and relationships, with communities and a report. Documents, PDFs and images can be included too, when you allow it.
  • How it fits into VeritasInstalling Veritas installs Graphify. The official skill ships unchanged, from a tagged release of the Graphify Labs repository, and Veritas's mapa-do-codigo skill guides when to query the graph and when a plain search is enough.
  • When to use itFirst contact with a large system: /graphify . builds the code graph. Then /graphify query "what breaks if I change X?". For a one-off task it isn't worth it: a plain search is faster.

They hold in any stack

They load on their own when the topic comes up.

Convention text in Portuguese

MIT licence

It is markdown. Send a PR.

A wrong rule is fixed in the file where it lives. A new skill is a folder copied from docs/modelo-de-skill/, with a name and a description.

Open on GitHub