Skip to content
Skills Library
Programming · Building & coding

add

/add

Generate a vexana INetworkModel (with nested classes), a sendRequest service method and a round-trip model test from a JSON sample, a JSON file or an existing model, for a Flutter project using vexana 6.x. Use when the user says "vexana add", "bu JSON'dan model yap", "model oluştur", "servise endpoint ekle", "create a model from this JSON", or pastes a JSON response and wants it in the app.

Author
vb10 ↗
Repository
vexana ↗
Licence
MIT
Last repository change
19.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Generate a vexana INetworkModel (with nested classes), a sendRequest service method and a round-trip model test from a JSON sample, a JSON file or an existing model, for a Flutter project using vexana 6.x. Use when the user says "vexana add", "bu JSON'dan model yap", "model oluştur", "servise endpoint ekle", "create a model from this JSON", or pastes a JSON response and wants it in the app.

Triggers from the description

vexana addbu JSONmodel oluşturservise endpoint eklecreate a model from this JSON
Original author description

Generate a vexana INetworkModel (with nested classes), a sendRequest service method and a round-trip model test from a JSON sample, a JSON file or an existing model, for a Flutter project using vexana 6.x. Use when the user says "vexana add", "bu JSON'dan model yap", "model oluştur", "servise endpoint ekle", "create a model from this JSON", or pastes a JSON response and wants it in the app.

How it works

  1. 0. Preconditions
  2. 1. Inputs
  3. 2. Infer types
  4. 3. Check for collisions
  5. 4. Write files
  6. 5. Verify
  7. 6. Report
Original SKILL.md headings · 49 lines, 496 words
SKILL.md preview
---
name: add
description: Generate a vexana INetworkModel (with nested classes), a sendRequest service method and a round-trip model test from a JSON sample, a JSON file or an existing model, for a Flutter project using vexana 6.x. Use when the user says "vexana add", "bu JSON'dan model yap", "model oluştur", "servise endpoint ekle", "create a model from this JSON", or pastes a JSON response and wants it in the app.
---

# vexana add

Targets vexana `^6.0.0`. Read `references/vexana-api.md` and `references/templates.md` first; generate code only from those templates.

## 0. Preconditions

- Find the network setup (`AppNetworkManager` or a `NetworkManager<` construction in `lib/`). If there is none, stop and tell the user to run `/vexana:init`.
- Take `{{E}}` from that setup (`EmptyModel` or the generated error model), `{{networkPath}}` from its folder, and `{{package}}` from `pubspec.yaml` `name`.
- Features root: the first of `lib/features/`, `lib/feature/`, `lib/src/features/` that exists, even if it is empty; if none exists, `lib/features/`. `{{featurePath}}` is that root without `lib/`, plus the feature name: `features/post`.
- If the project uses json_serializable or freezed, still generate from the "Model" template, and tell the user the model was written by hand so they can convert it to their generator.
- Write every file under the project root you are working in, using paths relative to it.

## 1. Inputs

- JSON: pasted text, a file path, or an existing Dart model class to convert to `INetworkModel`.
- Read large JSON files only as far as needed to infer types (e.g. the first elements plus a key scan); do not echo them back.
- Optional: endpoint(s) as `METHOD /path` (`GET /posts`, `GET /posts/{id}`), feature name (default: the model name in snake_case), model name (default: from the path's last static segment, singular UpperCamel: `/posts` → `Post`).
- Invalid JSON → stop and show the parse error position. Do not guess.

## 2. Infer types

Apply the "Type inference" table and naming rules in `templates.md`. For a top-level array, infer from all elements. Collect every `Object?` and `List<Object?>?` field, and every key whose Dart field name differs from the key, for the report.

## 3. Check for collisions

If a class with the same name exists anywhere in `lib/`, or a target file exists, ask the user (reuse, rename, or skip) before writing anything. Do not write files for that input until they answer.

## 4. Write files

1. Model file (+ nested classes in the same file) from "Model".
2. If endpoints were given: create `<feature>_service.dart` from "Service" with only those methods, or add the methods (and interface entries) to the existing service.
3. Save the JSON sample to `test/fixtures/<model_snake>.json`, values unchanged:
   - input is a file → copy it with `cp <input> test/fixtures/<model_snake>.json`. Never re-type a file's contents: a large API response would be regenerated token by token.
   - input was pasted → write it as given.
4. Model test from "Model test" (array form for array samples). Make sure `test/helpers/fixture_reader.dart` has `dropNulls`.

## 5. Verify

```bash
dart analyze
flutter test test/{{featurePath}}/
```
Fix and retry at most twice; then report failures verbatim. Never edit a fixture or weaken an assertion to make a test pass.

## 6. Report

Files created/changed, the service methods added, values replaced in a fake sample, fields typed `Object?` / `List<Object?>?` (the sample did not show their type — ask the user to tighten them), and renamed keys (JSON key → Dart field).
Files in this package (3)
  • SKILL.md 4 KB
  • references/templates.md 12 KB
  • references/vexana-api.md 2 KB

Versions

RepositoryScoreLicence
This page · vb10/vexana100MIT
pilotspace/ADD100MIT
xhluca/agent-talk100MIT
ramonclaudio/skills100MIT
remocn/remocn96MIT
ArthurgLeonida/paperscout96MIT
pilotspace/ADD95MIT
pilotspace/ADD95MIT
pilotspace/ADD95MIT

Database snapshot: 13.11.2026 · package version eb5ddbb578c8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100multiple-add
    Generate vexana models, services, fake services, mocktail service tests and model tests for several JSON samples at once (a folder, several files or a pasted list), deduplicating shared nested types. Use when the user says "vexana multiple add", "bu JSON'ların hepsini ekle",…
  • 100refactor
    Migrate a Flutter project that already uses an older vexana (4.x or 5.x) to vexana 6.x — bumps the dependency, rewrites removed imports and immutable-model mutations, and flags call sites whose behaviour changed (removeAll, sendPrimitive, downloadFileSimple, cache keys). Use…
  • 100generate-tests
    Use when the user asks to generate, create, write, or add unit tests for existing code, or to cover a class, method, or file with tests — including Java targets using JUnit 5, Mockito, or AssertJ. Not for analysis-only requests that stop at listing test cases.
  • 100flutter-handling-http-and-json
    Executes HTTP requests and handles JSON serialization in a Flutter app. Use when integrating with REST APIs or parsing structured data from external sources.
  • 100add-test
    Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
  • 100add-test
    Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.