Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature] Agent-oriented VChart spec authoring workflow

Aperta
  • Qualcosa non va?
#4,648 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
ai, tooling

Direzione di ricerca

Inizia esaminando il workflow esistente di vchart-development-assistant e i formati di output di vchart-mcp-server, quindi chiarisci se questo debba appartenere a un nuovo skill o a un'estensione. Definisci il workflow rivolto all'agente intorno a target, context, result e test; è completato quando può produrre una VChart spec riutilizzabile con mapping dei dati e configurazione verificati, facoltativamente verificata da un renderer reale.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

What problem does this feature solve?

VChart already provides vchart-development-assistant, which is useful for developers building, modifying, or debugging VChart applications.

I think there is a related but different workflow that may be worth supporting explicitly: an autonomous/data agent producing a VChart visualization as part of its own work.

In this case, the agent is not necessarily helping a developer write a VChart application. It may have already analyzed some data and simply needs to decide how to visualize the result, author a valid VChart spec, and pass that spec to a renderer.

For example:

User
↓
"Show these data with an appropriate VChart visualization."
↓
Agent

  • understands the visualization goal
  • inspects the data and runtime constraints
  • chooses an appropriate chart
  • authors a VChart spec
  • validates the result
    ↓
    VChart spec
    ↓
    host / renderer

The VChart spec itself is the useful artifact here. It may be rendered in a browser, embedded into another application, consumed by another tool, or converted to image/HTML later.

I ran a small prototype of this workflow with Feishu Card as the host renderer.

After the host/output constraints had been provided in the earlier conversation context, the later user request was simply natural language plus data:

下面的数据
周一 12
周二 25
周三 18
周四 32

用合适的 vchart 图表展示

The agent chose a bar chart, generated the VChart payload, and the host rendered it directly as a native chart.

Image

In this prototype, Feishu is only the renderer and the transport layer passes the generated payload through unchanged. The VChart authoring itself is done by the agent.

What feels missing is a reusable way to provide that working knowledge. Currently, the prototype relies on conversation history to teach the agent the relevant VChart and renderer constraints. A VChart skill could make this knowledge explicit and reusable, instead of requiring low-level instructions to be repeated in each conversation.

The existing vchart-development-assistant is primarily developer-oriented and currently treats runnable application output such as HTML as the final result. For autonomous/data-agent workflows, I think it may also be useful to treat a reusable VChart spec as a first-class result.

This also seems consistent with vchart-mcp-server, where spec, image, and html are already separate output forms.

What does the proposed API look like?

This may not require a new VChart runtime API.

I think the useful addition is an agent-facing authoring workflow, either as a new skill or as an additional workflow in the existing vchart-development-assistant.

A possible working model is:

Target

  • What should the visualization communicate?

Context

  • What data is available?
  • What VChart/runtime/renderer constraints apply?

Result

  • Produce an appropriate, reusable VChart spec.

Test

  • Check data/field mappings and required configuration.
  • When possible, verify the spec with a real VChart renderer.

The intention is not to turn visualization into a rigid step-by-step pipeline. The agent should still be able to make decisions based on the actual data and task; the skill would provide the domain knowledge, constraints, references, and validation methods needed to do that reliably.

I am not strongly attached to whether this should be a separate skill or an extension of vchart-development-assistant. I would prefer to align on that boundary before implementing it.

If this use case fits the direction of VChart's skill ecosystem, I would be happy to work on the implementation.

Lingua principale
TypeScript
Stelle
1.9k
Fork
221
Merge medio
2g 1h
PR unite (30g)
17

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di VisActor/VChart

Tutte le issue di VisActor/VChart

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.