Vue3 Project Standard

v1.0.0

Vue 3 + TypeScript 项目的完整工程规范,涵盖项目结构、组件设计、Composables、路由、Pinia 状态管理、API 层、错误处理、测试和性能优化。当用户在 Vue 项目中创建、修改组件或模块,涉及架构设计、代码编写时自动激活。

0· 142·0 current·0 all-time
byBovin Phang@bovinphang
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill's name and description describe a coding/architecture standard for Vue 3 + TypeScript projects. The skill requires no binaries, env vars, installs, or config paths — which is consistent for an instruction-only style guide. There are no unexpected credentials or cloud APIs requested.
Instruction Scope
SKILL.md contains project structure, coding conventions, and examples. It does not instruct the agent to read arbitrary system files, harvest environment variables, call external endpoints, or modify unrelated system configuration. The scope is limited to recommending code/structure conventions for a Vue project.
Install Mechanism
There is no install specification and no code files to install or execute. As an instruction-only skill, it does not download or write artifacts to disk, which is proportionate to its purpose.
Credentials
The skill declares no required environment variables, credentials, or config paths. That matches expectations for a project-style guide and is proportionate to its stated functionality.
Persistence & Privilege
Flags show user-invocable true, always false, and model invocation enabled (the platform default). The skill does not request permanent/system-wide presence or elevated privileges. Note: the description mentions automatic activation when users modify Vue code — this is a behavioral trigger description but does not imply it forcibly installs or persists beyond normal skill invocation rules.
Assessment
This skill is an instruction-only coding standard for Vue 3 + TypeScript and appears internally consistent and low-risk: it doesn't request credentials, install code, or access system files. Before enabling, consider: (1) provenance — the source/homepage is unknown, so review the SKILL.md content yourself to ensure the conventions match your team's requirements; (2) autonomous activation — the skill can be invoked by the agent (platform default), so ensure you trust the skill and review any automatic suggestions before applying code changes; (3) review any generated code or recommended templates before committing them into your repository. If you need stronger guarantees, require a human review step or restrict the agent's ability to modify files automatically.

Like a lobster shell, security has layers — review code before you run it.

latestvk973ahzh656fj3mp2brn25pbx583y73w

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments