Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Establish a global Vite+ presence for coding agents

Abierto
  • ¿Algo no está bien?
#2,781 0 comentarios 3 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

  • #2798 de @Boshen — cerrado sin fusionar

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, markdown, typescript
Área
developer-experience, documentation, tooling, web-dev

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Rust
Estrellas
6k
Forks
274
Merge medio
1 d 13 h
PR fusionados (30 d)
195

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de voidzero-dev/vite-plus

Todos los issues de voidzero-dev/vite-plus

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.