9529360-cpu/veteran-engineering-studio
v1.14.27
Repository-first primary full-stack engineering owner for online repositories: architecture, frontend/backend/data/runtime implementation, CI/PR/release closure, and evidence-bound delivery with UI work delegated only as a bounded specialist phase.
MCP servers
Declared in a file that clients do not read
This package ships a
.mcp.json. Agent Plugins reads MCP configuration from mcp.json, so a client installing this plugin finds no servers. The directory does not read the file either, and shows nothing from it.What this package declares
The file a client reads when it loads this plugin, exactly as this revision carries it.
plugin.json
{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "veteran-engineering-studio",
"version": "1.14.27",
"description": "Repository-first primary full-stack engineering owner for online repositories: architecture, frontend/backend/data/runtime implementation, CI/PR/release closure, and evidence-bound delivery with UI work delegated only as a bounded specialist phase.",
"keywords": [
"full-stack",
"full-stack-engineer",
"primary-full-stack-owner",
"software-engineering",
"frontend",
"backend",
"data",
"runtime",
"infrastructure",
"debugging",
"architecture",
"repository-takeover",
"vertical-slice",
"end-to-end-delivery",
"design-system",
"release",
"visual-qa",
"figma",
"design-to-code",
"responsive",
"accessibility",
"code-connect",
"storybook",
"visual-regression",
"mobbin",
"design-research",
"design-tokens",
"component-library",
"ux-audit",
"ux-research",
"prototyping",
"design-qa",
"design-system-sync",
"token-sync",
"component-api",
"context-routing",
"progressive-loading",
"figjam",
"swiftui",
"motion-design",
"code-to-design",
"url-to-code",
"live-reference",
"visual-reconstruction",
"python-agent",
"tool-calling",
"multi-agent",
"design-system-discovery",
"repo-probe",
"design-action-fabric",
"design-provider",
"asset-sync",
"visual-design-authority",
"concept-competition",
"design-quality-gate",
"anti-generic-ui",
"implementation-first-ui",
"runtime-visual-proof",
"ui-pattern-library",
"test-self-check",
"visual-shotgun",
"designer-critique",
"ui-slop-scan",
"optical-alignment",
"image-first-design",
"github",
"repository",
"pull-request",
"ci",
"exact-head",
"release-engineering",
"repository-closure",
"foreground-continuation"
],
"extensions": {
"com.openai": {
"interface": {
"displayName": "Veteran Engineering Studio",
"shortDescription": "End-to-end full-stack engineering with primary repository ownership and bounded UI specialist delegation",
"longDescription": "Veteran Full-Stack Engineer is the primary owner for substantial online repository work: takeover, architecture, backend/data/runtime changes, frontend integration, debugging, review, exact-head CI, PR/merge convergence, release/operations, and mixed product delivery. It treats the hosted repository/control plane as the default authority for repository work. When a user asks for the full-stack engineer, 全栈工程师, repository development, CI/PR/release closure, or codebase ownership, route to this full-stack owner first. Veteran Frontend Design Builder remains a bounded UI/frontend specialist for design-system discovery, visual direction, responsive polish, accessibility, and rendered QA; it does not become the whole-repository owner when backend, data, runtime, release, or cross-layer product behavior is material. The full-stack owner retains cross-layer integration and final repository delivery authority. Local desktop or machine execution is optional evidence only when explicitly available and materially required.",
"developerName": "Veteran Engineer Project",
"category": "Developer Tools",
"capabilities": [
"Read",
"Write"
],
"defaultPrompt": [
"Take ownership of this online repository task as the primary full-stack engineer: recover current repo/PR truth, implement the change, validate the exact head, reconcile review, and carry it through the requested merge/release boundary.",
"Continue improving the Full-Stack Engineer plugin itself in the online GitHub repository: update the smallest authoritative owner, add eval/test coverage, validate exact-head CI, and close the PR/merge/release boundary requested by the user.",
"After a merged or main-validated repository slice, continue with the next evidence-backed reversible improvement from the refreshed default branch when the user asks to continue; do not stop at status-only reporting while safe material work remains.",
"Audit this repository and product surface, implement the highest-value evidence-backed full-stack fixes, delegate only bounded UI/frontend phases when visual quality is material, and close the work through current PR/CI/release state.",
"Build this feature as a production-quality vertical slice across frontend, backend, data, runtime, and release surfaces as needed, using the frontend design specialist only for bounded visual/product UI phases, then verify the current repository head and delivery state."
],
"brandColor": "#4F46E5"
}
}
},
"author": {
"name": "Veteran Engineer Project"
}
}What else this package ships
These files come with the package and this site does not publish them. They are listed so you know what is there before you install it.
- 348JavaScript files
- 97Python files
- 12JSON files
- 2YAML files
- requirements-ci.txt
- icon.svg
Client extensions
Data this package carries for particular clients. The directory lists the clients named and never reads what is addressed to them.
- com.openai