wpvc
Skill0 starsChanged 3 months agoMITView on GitHub
Use when working in an app that consumes @wgalleti/primevue-components (Vue 3 + PrimeVue 4) — first-time setup, building CRUD screens/forms with useCrudManager + FieldDef, using the W* components (WCrudView, WFormRenderer, WDatePicker, WAutoCompleteFK, WMoneyInput...), or migrating ad-hoc date/form/table code to the library. Trigger on tasks like 'add a CRUD', 'novo cadastro', 'formulário', 'campo de data', 'substituir DatePicker'.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- site-docsSkill
- documentoSkill
- frontend-kickstartSkill
- geojsonSkill
- manual-docSkill
- mrSkill
- novo-projetoSkill
- portal-frontendSkill
- projetoSkill
- prototipo-apiSkill
- prototipo-portalSkill
- sddSkill
- ui-ricaSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Datas: use WDatePicker (v-model string YYYY-MM-DD).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
wPrimeVueComponents (wpvc)
Biblioteca interna de componentes Vue 3 + PrimeVue 4 para CRUD, formulários e UI padronizada em pt-BR. O objetivo é escrever telas por configuração (ColumnDef/FieldDef), não por composição manual de inputs.
Escopo: esta skill cobre a API da suite. As regras de como se trabalha no app (padrões de tela, tokens, o que fica no app × o que vai para a suite) estão na skill
portal-frontend; para montar um frontend do zero com esse padrão,frontend-kickstart.
Quando usar esta skill
- Setup inicial da lib num app novo (plugin, dataProvider, CSS).
- Criar uma tela de CRUD, um formulário, ou um campo específico (data, FK, moeda).
- Migrar código ad-hoc (DatePicker solto, tabela manual, helpers copiados) para os componentes W*.
Regra de ouro
- Não componha inputs à mão. Descreva a tela com
useCrudManager({ endpoint, columns, form })+<WCrudView>, ouFieldDef[]+<WFormRenderer>. - axios/dataProvider vêm do plugin (injetados). Nunca crie instância axios dentro da tela nem importe axios direto.
- Endpoints são strings; a resposta paginada esperada é
{ data, page, page_size, rows }. - Datas: use
WDatePicker(v-model stringYYYY-MM-DD). NuncaparseDate/toISOStringà mão. - Antes de inventar prop, confirme a API nos tipos publicados:
node_modules/@wgalleti/primevue-components/dist/*.d.ts(FieldDef,ColumnDef,CrudManagerConfig, props dos componentes).
Fluxo rápido
Setup (uma vez por projeto) → references/setup.md. Ou rode npx @wgalleti/primevue-components init.
CRUD completo (tabela + form + toast + confirm):
<script setup lang="ts">
import { useCrudManager, WCrudView } from '@wgalleti/primevue-components'
import type { ColumnDef, FieldDef } from '@wgalleti/primevue-components'
const columns: ColumnDef[] = [
{ field: 'nome', header: 'Nome' },
{ field: 'preco', header: 'Preço', type: 'currency' },
{ field: 'data', header: 'Data', type: 'date' },
]
const form: FieldDef[] = [
{ field: 'nome', label: 'Nome', required: true },
{ field: 'preco', label: 'Preço', type: 'currency', colSpan: 0.5 },
{ field: 'data', label: 'Data', type: 'date', autonow: true, colSpan: 0.5 },
]
const crud = useCrudManager({ endpoint: '/api/v1/produtos/', columns, form })
</script>
<template>
<WCrudView :crud="crud" title="Produtos" />
</template>Detalhes de useCrudManager, ColumnDef, FieldDef (todos os tipos e props): references/crud.md.
Formulário standalone (sem dialog, dentro de Card/Dialog seu): WFormRenderer com FieldDef[] — ver references/crud.md.
Campos específicos e componentes W* (WDatePicker, WAutoCompleteFK, WMoneyInput, WTransferList, UI): references/components.md.
Migrar código existente (DatePicker→WDatePicker, tabela manual→WCrudView, apagar helpers copiados): references/migration.md.
Gotchas (leia antes de debugar)
- Registre o
WPrimeVuePlugindepois dePrimeVue,ToastServiceeConfirmationService— os componentes usam Toast/Confirm. - O
axiospassado ao plugin deve já terbaseURLe auth configurados. - Importe o CSS uma vez:
import '@wgalleti/primevue-components/style.css'. - "No PrimeVue Toast provided" / inject quebrado em monorepo com a lib aliased pra source: adicione
resolve.dedupe: ['vue', 'primevue']novite.config. (Instalação normal via npm não precisa.) - Resposta da API precisa ser
{ data, page, page_size, rows }. Erros no formato DRF ({ detail },{ campo: [erros] }).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

