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

Establish a global Vite+ presence for coding agents

Aperta
  • Qualcosa non va?
#2,781 0 commenti 3 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

  • #2798 di @Boshen — chiusa senza merge

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, markdown, typescript
Ambito
developer-experience, documentation, tooling, web-dev

Direzione di ricerca

Read Cloudflare's linked agent setup prompt, then inspect the homepage and Getting Started CTA and determine where the canonical Markdown endpoint should live. Verify the bootstrap instructions against the listed macOS/Linux and Windows, idempotence, supported-agent, restart, and skill update/removal acceptance criteria; done means the endpoint is fetchable and the global skill is loaded after setup.

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

Descrizione

pending triage
Description

Vite+ project instructions are currently created after running vp create or vp migrate. Before a project exists, coding agents may still default to npm create, npx, and direct package-manager commands.

Vite+ should have a global presence in supported coding agents so they know to use vp when creating projects and managing frontend workflows.

Suggested solution

  • Publish setup instructions at https://viteplus.dev/agent-setup/prompt.md.

  • Make the homepage and Getting Started CTA copy:

    Fetch and execute the appropriate instructions to set me up for Vite+ from https://viteplus.dev/agent-setup/prompt.md

  • Have the fetched instructions:

    • Keep an existing global vp installation or install it with the official platform installer when missing.
    • Verify it with vp --version and vp help.
    • Install an official Vite+ Agent Skill globally for the active agent, preferably through vpx.
    • Report the installed path and whether the agent must restart.

  • Add a global vite-plus skill that:

    • Activates for new JavaScript, TypeScript, and web projects even when Vite+ is not explicitly mentioned.
    • Prefers vp create over npm create and npx create-*.
    • Prefers vp install, vp add, vp remove, vp update, vp run, and vpx over direct package-manager equivalents.
    • Uses npm, pnpm, Yarn, or Bun directly only when explicitly requested or when vp has no equivalent.
    • Reads current Vite+ documentation or command help before selecting options.

Project-local agent instructions generated by vp create and vp migrate should remain unchanged and complement the global skill.

Acceptance criteria
  • The website copies the short bootstrap prompt above.
  • The Markdown endpoint is directly fetchable and is the canonical setup source.
  • Setup works on macOS/Linux and Windows.
  • Re-running setup is idempotent and preserves unrelated global agent configuration.
  • Supported agents load the Vite+ skill after restarting.
  • A request such as “create a new React project” results in a vp create workflow instead of npm create.
  • Global skill update and removal instructions are documented.
Additional context

Cloudflare's agent setup prompt demonstrates this remotely maintained bootstrap pattern.

This also revisits the earlier agent-skill discussions in #560 and #665. The project-local skill and MCP implementation removed in #1440 served a different purpose; this proposal is specifically about global, pre-project guidance.

Lingua principale
Rust
Stelle
6k
Fork
271
Merge medio
1g 12h
PR unite (30g)
198

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

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 voidzero-dev/vite-plus

Tutte le issue di voidzero-dev/vite-plus

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.