code: zqyl
name: "ZQYL Spec (中企云链前端规范)"
description: "Yunlian UI spec skills for ZQYL Vue2 projects: one interaction/visual spec entry point plus page-template and component skills for the backend / front / mid platforms"
default_selected: false # Org-specific frontend spec pack, opt-in

# Variables from Core Config inserted:
## user_name
## communication_language
## document_output_language
## output_folder

# All three platform packs install together (96 skills), so the entry skill has to
# know which one this repo targets. Without a recorded answer an agent can only guess
# from the repo name — and the strongest lexical signal is misleading (a repo called
# zqyl-manager collides with the mid-only skill xiaoma-zqyl-manager-title-mid).
# xiaoma-zqyl-ui-spec reads this key first, before any name-based inference.
platform:
  prompt:
    - "Which ZQYL platform does this repo target?"
    - "Pins page/component skill selection; pick 'all' for a repo that spans platforms."
  default: "all"
  result: "{value}"
  single-select:
    - value: "backend"
      label: "backend 后台管理端 (zqyl-manager 等; ylTitle + ylTableSimple)"
    - value: "mid"
      label: "mid 中台 (mps-main 等; ylManagerTitle + ylMpsTable)"
    - value: "front"
      label: "front 前台门户 (zqyl-crclopen 等; ylTitle + ylTableSimple)"
    - value: "all"
      label: "all 不固定 — 每次由 xiaoma-zqyl-ui-spec 判定"

# Note: this module ships reference-only skills (specs, page skeletons, component
# APIs). It generates no artifacts of its own — code lands wherever the user's
# Vue2 project already keeps pages — so it declares no output folder and no
# `directories:` to create at install time.

# No agents: these are reference skills consumed by whichever agent is active.