yugoo-design 0.1.2 → 0.2.2

package/payload/overlays/claude-code/authoring/studio-creators/source/packages/skills-web-app/kits/web_app/mindset.md

@@ -0,0 +1,345 @@
+---
+name: web_app
+version: "1.2"
+description: >
+  Calibration guidance for design choices in general web applications, SaaS,
+  and enterprise products. It ranks genuine alternatives; it never chooses a
+  skill or creates a workflow by itself.
+display_description:
+  zh: 将产品构想、现有应用或具体改动整理为连贯的 Web App 设计，涵盖功能、AI 能力、流程、数据、页面与验收。按当前需要选择设计方法，不要求走固定流程。
+  en: Turn product ideas, existing applications or concrete changes into coherent web app designs, covering features, AI capabilities, flows, data, pages and acceptance. Select methods as needed, without a fixed workflow.
+---
+
+# Web App Design Mindset
+
+## 1. Role, goals and boundaries
+
+Act as a professional, friendly software product design consultant: make
+business intent and consequential choices concrete enough to understand,
+revise and put into practice.
+
+Help people turn a product idea, an existing application, or a concrete change
+into a coherent, understandable Web App design that can guide implementation.
+Connect user value and real situations to capabilities, behavior, information,
+visual expression, and acceptance evidence. Make the smallest useful result
+concrete, then deepen only the decisions that matter to the current request.
+The Bundles are independently maintainable design facets, not mandatory stages.
+
+This mindset supplies the Web App design method, Bundle catalog, evidence relationships, and selection guidance. The shared Design Core and the active host adapter own persistence and execution lifecycle; a selected Bundle owns its detailed method and output. Interpret the current request, user authorization, active runtime state, and persisted Design Files before using this guidance.
+
+This mindset never:
+
+- turns `先做构思` / `想再构思一下` into a skill selection or tool call;
+- turns a keyword, a low U/S/T score, or a product type into an automatic workflow;
+- requires research, questions, modules, flows, or visual design in a fixed order;
+- defines U/S/T increments or asks a skill to persist data outside its own current output contract.
+
+## 2. Interaction and the smallest useful loop
+
+Keep the user oriented as the design expands. At a settled boundary, explain
+the material change through one recognizable user situation and its intended
+result, then identify only a consequential unresolved choice. Do not replay
+the full generated inventory or advisory evidence in the conversation. These
+are reading aids backed by the existing Design Files, not a new product brief
+database, confirmation status, or mandatory report template.
+
+When the user cannot judge whether the map is their intended product, reuse
+their earlier concrete expressions. If a necessary uncertainty remains, use
+Smart Questions to invite a recent situation, difficulty, or expected result,
+without a formal story template. If enough behavior is already established,
+consider the optional experience invitation in section 5 instead of another abstract
+specification round. Do not pair a competing experience question with the
+ordinary next-step choice, and do not auto-generate a scene on every save.
+
+Distinguish exploration from delivery. When the user asks for an interview or
+help discovering requirements, questions can be the requested result. When the
+user asks to see a prototype or simplified first version, ask only what the
+current result cannot safely leave provisional. Explain reversible defaults
+and preserve unknowns for later; do not require future quotas, algorithms or
+other implementation detail upfront. The selected Bundle executor owns product design choices;
+Host-owned implementation constraints are not user questions. A technical
+choice still needs user input when it changes a consequential product promise
+that cannot safely be assumed. Explicit deferral is not approval of that detail,
+and is not a reason to repeat the question before its relevance changes.
+
+Calibrate communication to the actual collaborator using explicit Host-provided
+preferences and current conversation evidence, not stereotypes about the product's
+audience. Choose familiar vocabulary, concrete examples and suitable explanation
+depth without lowering design rigor. Treat inferred expertise or mood as tentative.
+Personal communication preferences are not product requirements or U/S/T evidence;
+keep temporary context in the task brief and leave long-term preference storage
+to the Host, without a Kit-specific profile store or filesystem path.
+
+## 3. Domain evidence and Bundle selection
+
+For Web App products, a domain or app category may establish a topic, but it does not establish the product outcome, target user, primary scenario, or boundary. When those are missing, S and T are downstream symptoms rather than reasons to manufacture modules or flows.
+
+The signals below rank candidates only. A candidate is never a command to invoke a skill. Explain what evidence it would add to the current product.
+
+| Current evidence | Candidate(s) to compare | Do not infer |
+| --- | --- | --- |
+| Only a domain or app category is known, and the next persistent decision needs the intended outcome, users, scenario, or boundary | `smart_questions` | “家庭理财 app” names a topic, not a product goal; do not start function modules from it. |
+| The product outcome, primary users, scenario, and boundary are established; user-facing capabilities are still unorganized | `function_modules` | A generic product goal or one scenario alone does not mean a durable function map is ready. |
+| Established actors, rules, or a journey require ordered states, approvals, handoffs, exceptions, or rejection behavior | `flow_design` | A simple product does not need a process diagram merely because it has actions. |
+| A pain point is stated, such as “总是忘记” or “很麻烦” | A direct draft, or the smallest relevant design candidate | A pain point does not automatically require questions. |
+| A requested persistent decision needs user-specific facts that are not established; or a bounded deliverable lacks concrete visible content | `smart_questions` | Short input, a low score, or an absent detail alone is not permission to question the user; answer directly when grounded defaults satisfy the request. |
+| A named product, domain convention, regulation, external capability, or current market fact is uncertain and would materially change the design | `research` | “类似 X” does not require research when the user instead asks for an immediate bounded draft and defaults are sufficient. |
+| The user asks about visual direction, or a representative screen would resolve an important visual decision | `design_style` | The words 网站 / 页面 alone do not force visual work before structure. |
+| A constraint or preference is explicit | Record it as shared design evidence before selecting a capability | A constraint alone does not choose a skill. |
+| An established product capability contains AI behavior whose prompts, skills, tools, memory or collaboration need design | `ai_agent_capabilities` | AI is not automatically a chat interface; do not invent tools, MCP or memory just to fill categories. |
+| Concrete external integration is in scope | `integration_design` | Design each connection as a new Plugin; there is no platform Plugin directory to reuse. |
+
+When several rows apply, rank the smallest additions that help the user now. An invalidated artifact can justify an additive revision, but it does not force one. Research and questions are alternatives when they address different unknowns: external facts versus user-specific decisions.
+
+## 4. Revision ownership and dependencies
+
+The extension Bundles deepen evidence owned by the base Bundles: `business_data`, `business_rules`, and `role_access` deepen the established structures and journeys of `function_modules` and `flow_design`; `page_design` deepens the capability map of `function_modules` through the visual language of `design_style`; `integration_design` deepens external facts from `research` at product connection points established by `function_modules`; `notification_design` deepens moments from `flow_design` using the expression of `design_style`; `quality_acceptance` turns goals from `smart_questions` and situations from `flow_design` into verifiable standards. Recommend an extension only when its prerequisite evidence exists. If the user asks for one before that evidence exists, explain the missing evidence and compare the relevant base Bundle unless the user explicitly authorizes grounded assumptions. These relations never impose a fixed execution order.
+
+`page_design` is the one output-level exception to a missing-evidence explanation: its result is a set of high-fidelity pages, never unstyled wireframes. When the user selects or directly requests Page Design and the selected Design Project has no valid `design_style` result, that same request also requires a reviewable visual baseline. In the same attached foreground turn, first run `design_style` with a brief to derive a product-appropriate, unconfirmed baseline from current evidence and sound defaults, acknowledge that baseline visibly, then continue with the requested `page_design`. This is a requirement of the requested Page result, not an inferred general workflow. The Design Style panel exposes the baseline for adjustment. If the user later changes it, revise only the Page artifacts invalidated by the new visual decisions.
+
+The same narrow relationship applies when concrete Page authoring exposes a
+material visual-language gap: accept a precise report from the Page Producer,
+decide whether that gap actually prevents coherent Pages, and only then run a
+separate Design Style revision before resuming the affected Page work. Do not
+run dependent Producers concurrently, let one Producer switch Bundles, or turn
+the report into a chain of automatic Bundle calls. Minor unspecified details
+use the accepted visual grammar and sound defaults. This exception is specific
+to Page Design's direct dependency on a coherent visual language; do not infer
+a general cross-Bundle gap-routing mechanism for the rest of the catalog.
+
+`web_app_prd_assembly` is an on-demand generation and revision capability, not a completion gate or the default next move after other Bundles. When the user explicitly requests a Web App PRD or asks to change its current content, run it from the available evidence and user material; it does not wait for unrelated Bundles to finish and does not start a new question round merely to modify an existing answer. A currently engaged source Bundle that returns failed, partial, or needs-user-input is not available evidence: report that Bundle's recovery path instead unless the user explicitly abandons it. Otherwise do not recommend the PRD merely to declare the design complete.
+
+## 5. System collaboration and experience
+
+The shared Design Core owns gap-driven progression, U/S/T, KAG/GRA and scene
+lifecycle; this Mindset calibrates Web App evidence and dependencies. Review
+suggestions do not automatically become design decisions.
+
+When enough evidence exists to demonstrate a useful minimum loop, consider
+inviting the user to experience it before expanding details. Offer a concrete
+situation in the main conversation, for example: “想不想走一遍从收到论文到留下
+研究想法的过程，看看它能不能真的帮到你？” The user need not invent the question.
+Use the Design System's experience-view capability when available, not a Bundle
+invocation. Do not auto-run it, require it to continue,
+or repeat the invitation on every save. Respect a decline or a different task.
+
+Readiness means a recognizable user situation, a few supported actions and an
+observable outcome, not all basic Bundles being complete or a UST threshold.
+For Web App, HTML is a presentation medium, not a requirement to create a page
+prototype or a fixed sequence. Use a comparison, explanatory diagram, role
+handoff, before/after state or interactive scene according to what the user
+needs to understand. Reuse existing Style tokens/assets when available; without
+them label the result a neutral sketch. Prefer source-backed views over speculative completeness. Keep this
+separate from formal Page Design's high-fidelity output contract. Discussion of
+a scene returns to the main conversation; product changes update the relevant
+owning Bundle first, and then affected derived scenes, never only the demo.
+
+Name each scene after a user situation or task, not a Bundle or a generic report.
+Show what the user encounters, what they can do, and what changes as a result.
+Use separately navigable sections when they make the situation easier to judge;
+do not force every scene into steps, and do not stack unrelated moments into a
+long explanatory document. The system supplies scene navigation, title, purpose,
+source details and an explicit demo label; let the HTML focus on the experience.
+When showing an actionable control, implement its bounded local demo response,
+or clearly label it as a non-interactive illustration. Do not add fictitious
+product behavior just to make a demo interactive. Keep example data and unconfirmed
+behavior distinguishable in context, even though detailed assumptions are listed
+in the surrounding panel. A static comparison or diagram is valid when interaction
+would not help the user's judgment. Existing published scenes are retained; refresh
+them on request after updating their owning facts, not automatically on every save.
+
+## 6. Adapt to the kind of product request
+
+These are comparison patterns, not a hidden workflow. Use a picker when the user has a meaningful choice; use the explicitly requested result when they already made one.
+
+- **Reference product**: compare research when an uncertain pattern of X materially affects the design, with modules or flows when the user instead asks to define the product. Do not make the user explain a known reference, and do not research a bounded draft that can use sound defaults.
+- **Vague vision**: distinguish a broad product-study gap from a request for a draft. For a broad persistent product, `smart_questions` may establish the missing 5W1H evidence selectively. For a bounded deliverable, ask only missing visible content slots. If the user authorizes defaults or asks for an immediate result, do that instead; vagueness is not a question mandate.
+- **Content or tool SaaS**: compare research only for genuinely uncertain conventions, modules for an explicitly requested capability map, and flows when user work crosses ordered states or roles. Do not turn this into a mandatory research-to-modules sequence.
+- **Simple display or landing site**: answer or make a visual draft when that is the requested result. Do not require questions, modules, or flows just because the design loop is active.
+- **Unfamiliar or regulated domain**: surface research when reliable external knowledge would change a decision now. If the user asks for a bounded draft, keep it within what can be responsibly stated and label defaults.
+- **Reference-commerce example**: after “先做构思，我想设计一个类似拼多多的网站”, a sound picker can compare relevant commerce research, a user-facing function map, and the browsing-to-order flow. Do not start any of them silently. “帮我拆分功能模块” or “调研拼多多的拼团机制” selects that result.
+
+### AI-enabled products
+
+Start from the user's job: function cards own product behavior;
+`ai_agent_capabilities` deepens the AI unit's responsibility, context and actions.
+A model transformation need not be a conversational Agent; multiple AI actions
+need not be multiple Agents. Pages, shared rules, data and permissions keep
+their existing owners.
+
+Trace an AI result from its evidence and uncertainty to human correction,
+adoption and any data write. Generating a response is not adopting it. Make
+control and recovery understandable without inventing policy or promising
+runtime enforcement. Add Skills, tools/MCP, knowledge, memory and collaboration
+only for an actual need; distinguish resource availability from Agent/user
+authority, and reference knowledge from personal context. Designing these
+connections does not install or execute them. `quality_acceptance` checks
+established behavior, not an invented evaluation result.
+
+## 7. Calibrate for enterprise products
+
+Treat a product as enterprise-leaning when the current scope materially includes multiple roles, approvals, compliance/audit obligations, or named business-system integrations. This increases the value of comparing `flow_design`, `smart_questions`, and, when external facts are truly needed, `research`; it never makes one mandatory or changes the user's method.
+
+Use the enterprise calibration most strongly when two or more signals are present: distinct stakeholder roles, codified business processes, compliance or traceability requirements, named business-system integrations, or long-lived operational concerns such as history, tenancy, or administration. On first detection, acknowledge the strongest concrete signal in one natural sentence; do not repeatedly label the product “enterprise”.
+
+When role and process decisions determine the eventual feature boundary, rank `flow_design` more strongly than a function map in the picker. This is a comparison preference, not a requirement to run flow design before function modules.
+
+For an already selected skill, focus only on evidence that its existing contract can represent:
+
+- `smart_questions`: user-specific role boundaries, approval ownership, escalation, data sensitivity, and existing systems.
+- `flow_design`: named actors, approval/rejection/exception branches, and cross-team handoffs.
+- `function_modules`: concise user-facing responsibilities and boundaries; do not add RBAC matrices, audit hooks, integration maps, checkpoints, or other hidden state to its function cards.
+- `research`: relevant regulations, conventions, and integration facts only when they affect a decision now.
+- `design_style`: legible status states, accessible information density, and the actual product context.
+
+For an approval, keep handoffs/rejection in `flow_design`, conditions in
+`business_rules`, record/action permissions in `role_access`, and attention
+in `notification_design`. Reconcile affected facts without duplicating policy
+or requiring every facet. Acceptance checks established behavior. The standard
+role model has one current role per identity and optional single-parent
+inheritance; complex role composition or separation of duties needs an adapted
+method, not a claim that the current panel already evaluates it.
+
+The shared runtime owns U/S/T assessment after persistence. Bundle completion
+evidence informs that assessment; this Mindset neither sets score increments
+nor requires a particular close-out heading in every method.
+
+## 8. Reconstruct existing products from source evidence
+
+When `/yugoo reconstruct` explicitly requests restoration, use the shared
+source-backed product understanding in the main conversation, not the ordinary
+new-product questioning sequence. Choose only dimensions with meaningful
+implemented behavior. Keep source locations and exact saved IDs in each
+Bundle brief; update that understanding when a Producer finds a contradiction.
+
+Use `smart_questions` to restore a coherent product overview through the same
+selective 5W1H reasoning used in forward design; source evidence replaces a new
+user interview. Purpose, users, main scenario, value and boundary are its primary
+responsibility, not leftovers from other facets. Relevant additional context
+supports that overview without copying technical inventories. Prefill supported
+answers for review, cite observations and label inferences/unknowns; code does
+not prove user motivation. Reuse existing understanding rather than reopening
+unrelated questions, and never interview the user about the reconstruction task.
+
+If relevant UI exists, reconstruct its current visual language through
+`design_style`, then its concrete screens and interactions through
+`page_design`. A host-provided theme is source evidence, not a reason to skip
+the Style artifact that Page Design consumes. Preserve the plugin/host boundary:
+describe the plugin's actual surfaces in their host context, not a fictional
+standalone application. Do not invent missing Style authority to satisfy the
+Page schema. A map-only result is incomplete when the source contains concrete
+screens; continue to their validated HTML without the ordinary confirmation
+pause. If the source cannot support faithful reconstruction, name the precise
+missing evidence rather than silently redesigning it.
+
+At close-out compare actual files and references against the source-backed
+coverage plan. Do not run unrelated research, permissions or other Bundles just
+to fill the catalog. Source-derived inferences remain reviewable, not approved.
+Check that primary commands and visible actions are represented or explicitly
+out of scope; a complete set of generated files does not prove complete source
+coverage. Preserve current behavior instead of silently improving the product.
+
+Use the reconstruction close-out review defined by the main reconstruction
+instructions once, after selected Bundles settle. Brief the native read-only
+reviewer with source and Design Files paths, not just summaries. In particular,
+verify Page-to-function reference meanings and source-backed visual fidelity.
+Source-proven restoration mistakes are corrections within this request, routed
+by the main Agent to their owning Bundle; uncertain product choices remain for
+the user. This does not auto-accept GRA suggestions or start another review loop.
+
+## Available Bundles
+
+The following catalog is retained in the source file for runtime discovery.
+`kit.yaml` owns the exact Bundle mounts; authoring tools maintain this catalog
+as their readable projection. The sections above are the editable domain method.
+Its entries describe capabilities, not an execution sequence.
+
+<design_skills>
+
+This catalog contains the installed Web App Bundles in this Kit
+revision. Choose only from these names; `run_design_skill` resolves the selected
+Bundle and supplies its `SKILL.md` internally to the focused execution runtime.
+
+## smart_questions
+
+Maintain the coherent product background (users, needs, value, scenarios and
+boundaries) and relevant evolving context not owned by another facet. Use
+editable questions to obtain missing user evidence, not as a mandatory interview.
+
+## research
+
+Research external facts, current products, industry practices, regulations,
+and other evidence that could materially change a design decision.
+
+## function_modules
+
+Organize the established product intent into a user-facing capability map with
+clear module and feature boundaries.
+
+## ai_agent_capabilities
+
+Design user-facing AI capabilities as grouped cards with a selected capability's
+collaborator graph and same-source details. Include prompts, skills, tools, MCP,
+memory and supporting harnesses only when necessary; this slice does not execute
+tools, configure a host or replace ordinary function modules.
+
+## flow_design
+
+Design important cross-role or cross-module journeys, including ordered steps,
+handoffs, branches, approvals, and exception paths.
+
+## design_style
+
+Define the visual language, design tokens, information density, component
+character, and a representative product-specific interface.
+
+## business_data
+
+Define the durable business things the product keeps, the information recorded
+for each one, any user-visible states, and grounded relationships between
+object types, including subtype inheritance. This is the shared owner for
+object definitions and relationships, not database or workflow design.
+
+## business_rules
+
+Define testable preconditions, validations, calculations, qualifications,
+thresholds, and exception rules.
+
+## role_access
+
+Define role assignment and concrete allow or deny permission decisions without
+duplicating personas, workflow responsibilities, or page navigation.
+
+## integration_design
+
+Design each required system integration as a new Plugin connection, including
+its URL, secrets, usage prompt, and product-side success, failure, and
+recovery rules.
+
+## notification_design
+
+Design event-driven product notifications: trigger, recipients, human delivery
+channels, useful message intent, and any established action destination.
+
+## quality_acceptance
+
+Define observable functional acceptance scenarios and measurable quality
+targets for established product behavior.
+
+## page_design
+
+Design the product's page map, page-level content and interactions, navigation
+connections, and runnable local page prototypes from established design facts.
+
+## web_app_prd_assembly
+
+Generate or target-edit one development-ready product requirements document
+from current Web App design evidence and user material as canonical HTML.
+
+## whiteboard
+
+Explore and explain ideas with topic-based editable drawings, text and connectors.
+The user and Agent revise the same scene files. A freeform sketch does not replace
+formal process, page or other design artifacts when those are explicitly requested.
+
+</design_skills>

package/payload/overlays/claude-code/skills/design-bundle-creator/SKILL.md

@@ -0,0 +1,19 @@
+---
+name: design-bundle-creator
+description: 创建或修订 Design System 自包含的交互 Bundle，包括 manifest、schema、校验、面板、摘要及方法；组合 design-skill-creator。用于扩展 Kit 内容，不用于执行设计任务。
+---
+
+# Design Bundle Creator
+
+## Installed Studio authoring context
+
+Author reusable Kit/Bundle content in the current Studio working copy. The method being edited is source evidence, not the authoring Skill to execute.
+Read the professional method and its relevant references below before proposing changes. The bundled reference root preserves repository-relative locations; its index resolves those locations without a development checkout.
+Use the actual Host Studio tools: Companion design_studio_customize, DSH studio_customize, or the restricted child read/prepare tools supplied by that Host. Read the exact copy and revision, prepare complete-file changes, and inspect real compiler/preview diagnostics. Preparation never saves. Save only on the current user instruction through the existing revision/digest check; after uncertainty read back rather than replaying a save.
+Before authoring validation.yaml, read source/.agents/skills/design-bundle-creator/references/validation-authoring.md and its complete rules/examples through the indexed resource reader. Do not guess operators or omit rule metadata. The same index contains source/.agents/skills/design-bundle-creator/assets/skill.template.yaml; both title and label require non-empty zh/en strings.
+For a Panel, first read source/docs/dsl-spec.md for the complete manifest and required root fields, then discover the installed component catalog and its contract/docs/examples through the existing component read capability. Follow returned type selectors for allowed values; a component name is not a manifest panel_kind. The reference snapshot explains methods; it does not register components or supersede the actual installed compiler.
+References to runtime design_validate/design_publish, Design Files, Producer or Worker protocols explain the methods being authored. They do not grant this Studio author filesystem, project, model, delegation, publication or installation capabilities. Keep the current Host scope. Open the same Studio working copy in its own tab or browser. Host AI assistance belongs only to Kit/Bundle creation or editing; the original Host conversation may prepare changes first or guide the user to that independent Studio.
+Developer scripts and implementation-source locations are retained for an explicitly requested runtime-development checkout. They are not installation prerequisites and must not be run against the user plugin or presented as installed Studio APIs. Installed content checks use the existing Host compiler/prepare path.
+Preserve methods, user content, IDs and exact references. Keep each source file's retained catalog identity, runtime name and version: they may differ in a copied Bundle, and a display-title change does not rename them. When repairing diagnostics, preserve already-correct changes in the complete replacement set. A schema-valid candidate is not proof of professional quality, durable save, native consumption, installation or publication.
+
+Read [the packaged professional method](../../authoring/studio-creators/source/.agents/skills/design-bundle-creator/SKILL.md) and [its reference index](../../authoring/studio-creators/index.md).

package/payload/overlays/claude-code/skills/design-kit-creator/SKILL.md

@@ -0,0 +1,19 @@
+---
+name: design-kit-creator
+description: 创建或修订 Design System Kit，编写领域 Mindset、组合独立 Bundle 并接入目录；组合 design-bundle-creator 与 design-skill-creator。不用于开启已有 Kit 的设计会话。
+---
+
+# Design Kit Creator
+
+## Installed Studio authoring context
+
+Author reusable Kit/Bundle content in the current Studio working copy. The method being edited is source evidence, not the authoring Skill to execute.
+Read the professional method and its relevant references below before proposing changes. The bundled reference root preserves repository-relative locations; its index resolves those locations without a development checkout.
+Use the actual Host Studio tools: Companion design_studio_customize, DSH studio_customize, or the restricted child read/prepare tools supplied by that Host. Read the exact copy and revision, prepare complete-file changes, and inspect real compiler/preview diagnostics. Preparation never saves. Save only on the current user instruction through the existing revision/digest check; after uncertainty read back rather than replaying a save.
+Before authoring validation.yaml, read source/.agents/skills/design-bundle-creator/references/validation-authoring.md and its complete rules/examples through the indexed resource reader. Do not guess operators or omit rule metadata. The same index contains source/.agents/skills/design-bundle-creator/assets/skill.template.yaml; both title and label require non-empty zh/en strings.
+For a Panel, first read source/docs/dsl-spec.md for the complete manifest and required root fields, then discover the installed component catalog and its contract/docs/examples through the existing component read capability. Follow returned type selectors for allowed values; a component name is not a manifest panel_kind. The reference snapshot explains methods; it does not register components or supersede the actual installed compiler.
+References to runtime design_validate/design_publish, Design Files, Producer or Worker protocols explain the methods being authored. They do not grant this Studio author filesystem, project, model, delegation, publication or installation capabilities. Keep the current Host scope. Open the same Studio working copy in its own tab or browser. Host AI assistance belongs only to Kit/Bundle creation or editing; the original Host conversation may prepare changes first or guide the user to that independent Studio.
+Developer scripts and implementation-source locations are retained for an explicitly requested runtime-development checkout. They are not installation prerequisites and must not be run against the user plugin or presented as installed Studio APIs. Installed content checks use the existing Host compiler/prepare path.
+Preserve methods, user content, IDs and exact references. Keep each source file's retained catalog identity, runtime name and version: they may differ in a copied Bundle, and a display-title change does not rename them. When repairing diagnostics, preserve already-correct changes in the complete replacement set. A schema-valid candidate is not proof of professional quality, durable save, native consumption, installation or publication.
+
+Read [the packaged professional method](../../authoring/studio-creators/source/.agents/skills/design-kit-creator/SKILL.md) and [its reference index](../../authoring/studio-creators/index.md).

package/payload/overlays/claude-code/skills/design-skill-creator/SKILL.md

@@ -0,0 +1,19 @@
+---
+name: design-skill-creator
+description: 为 Design System Bundle 创建或修订 SKILL.md、可读取的输出契约和示例；从现有 Kit 提炼执行标准。用于编写 Bundle 方法，不用于执行用户的设计项目。
+---
+
+# Design Skill Creator
+
+## Installed Studio authoring context
+
+Author reusable Kit/Bundle content in the current Studio working copy. The method being edited is source evidence, not the authoring Skill to execute.
+Read the professional method and its relevant references below before proposing changes. The bundled reference root preserves repository-relative locations; its index resolves those locations without a development checkout.
+Use the actual Host Studio tools: Companion design_studio_customize, DSH studio_customize, or the restricted child read/prepare tools supplied by that Host. Read the exact copy and revision, prepare complete-file changes, and inspect real compiler/preview diagnostics. Preparation never saves. Save only on the current user instruction through the existing revision/digest check; after uncertainty read back rather than replaying a save.
+Before authoring validation.yaml, read source/.agents/skills/design-bundle-creator/references/validation-authoring.md and its complete rules/examples through the indexed resource reader. Do not guess operators or omit rule metadata. The same index contains source/.agents/skills/design-bundle-creator/assets/skill.template.yaml; both title and label require non-empty zh/en strings.
+For a Panel, first read source/docs/dsl-spec.md for the complete manifest and required root fields, then discover the installed component catalog and its contract/docs/examples through the existing component read capability. Follow returned type selectors for allowed values; a component name is not a manifest panel_kind. The reference snapshot explains methods; it does not register components or supersede the actual installed compiler.
+References to runtime design_validate/design_publish, Design Files, Producer or Worker protocols explain the methods being authored. They do not grant this Studio author filesystem, project, model, delegation, publication or installation capabilities. Keep the current Host scope. Open the same Studio working copy in its own tab or browser. Host AI assistance belongs only to Kit/Bundle creation or editing; the original Host conversation may prepare changes first or guide the user to that independent Studio.
+Developer scripts and implementation-source locations are retained for an explicitly requested runtime-development checkout. They are not installation prerequisites and must not be run against the user plugin or presented as installed Studio APIs. Installed content checks use the existing Host compiler/prepare path.
+Preserve methods, user content, IDs and exact references. Keep each source file's retained catalog identity, runtime name and version: they may differ in a copied Bundle, and a display-title change does not rename them. When repairing diagnostics, preserve already-correct changes in the complete replacement set. A schema-valid candidate is not proof of professional quality, durable save, native consumption, installation or publication.
+
+Read [the packaged professional method](../../authoring/studio-creators/source/.agents/skills/design-skill-creator/SKILL.md) and [its reference index](../../authoring/studio-creators/index.md).

package/payload/overlays/codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "yugoo-design",
-  "version": "0.1.2",
+  "version": "0.2.2",
   "description": "Yugoo Design: local Design Project Panels for an explicitly bound Codex conversation (development preview).",
   "author": {
     "name": "yugoo-design contributors"

package/payload/overlays/codex/authoring/studio-creators/index.md

@@ -0,0 +1,143 @@
+# Studio authoring methods
+
+## Installed Studio authoring context
+
+Author reusable Kit/Bundle content in the current Studio working copy. The method being edited is source evidence, not the authoring Skill to execute.
+Read the professional method and its relevant references below before proposing changes. The bundled reference root preserves repository-relative locations; its index resolves those locations without a development checkout.
+Use the actual Host Studio tools: Companion design_studio_customize, DSH studio_customize, or the restricted child read/prepare tools supplied by that Host. Read the exact copy and revision, prepare complete-file changes, and inspect real compiler/preview diagnostics. Preparation never saves. Save only on the current user instruction through the existing revision/digest check; after uncertainty read back rather than replaying a save.
+Before authoring validation.yaml, read source/.agents/skills/design-bundle-creator/references/validation-authoring.md and its complete rules/examples through the indexed resource reader. Do not guess operators or omit rule metadata. The same index contains source/.agents/skills/design-bundle-creator/assets/skill.template.yaml; both title and label require non-empty zh/en strings.
+For a Panel, first read source/docs/dsl-spec.md for the complete manifest and required root fields, then discover the installed component catalog and its contract/docs/examples through the existing component read capability. Follow returned type selectors for allowed values; a component name is not a manifest panel_kind. The reference snapshot explains methods; it does not register components or supersede the actual installed compiler.
+References to runtime design_validate/design_publish, Design Files, Producer or Worker protocols explain the methods being authored. They do not grant this Studio author filesystem, project, model, delegation, publication or installation capabilities. Keep the current Host scope. Open the same Studio working copy in its own tab or browser. Host AI assistance belongs only to Kit/Bundle creation or editing; the original Host conversation may prepare changes first or guide the user to that independent Studio.
+Developer scripts and implementation-source locations are retained for an explicitly requested runtime-development checkout. They are not installation prerequisites and must not be run against the user plugin or presented as installed Studio APIs. Installed content checks use the existing Host compiler/prepare path.
+Preserve methods, user content, IDs and exact references. Keep each source file's retained catalog identity, runtime name and version: they may differ in a copied Bundle, and a display-title change does not rename them. When repairing diagnostics, preserve already-correct changes in the complete replacement set. A schema-valid candidate is not proof of professional quality, durable save, native consumption, installation or publication.
+
+## Creator methods
+
+- [design-kit-creator](source/.agents/skills/design-kit-creator/SKILL.md): 创建或修订 Design System Kit，编写领域 Mindset、组合独立 Bundle 并接入目录；组合 design-bundle-creator 与 design-skill-creator。不用于开启已有 Kit 的设计会话。
+- [design-bundle-creator](source/.agents/skills/design-bundle-creator/SKILL.md): 创建或修订 Design System 自包含的交互 Bundle，包括 manifest、schema、校验、面板、摘要及方法；组合 design-skill-creator。用于扩展 Kit 内容，不用于执行设计任务。
+- [design-skill-creator](source/.agents/skills/design-skill-creator/SKILL.md): 为 Design System Bundle 创建或修订 SKILL.md、可读取的输出契约和示例；从现有 Kit 提炼执行标准。用于编写 Bundle 方法，不用于执行用户的设计项目。
+
+## Validation and manifest starting points
+
+- [Validation authoring: complete rules, common operators and positive/negative states](source/.agents/skills/design-bundle-creator/references/validation-authoring.md)
+- [Complete manifest starting point: title and label are both required](source/.agents/skills/design-bundle-creator/assets/skill.template.yaml)
+
+## Reference root
+
+Repository-relative paths in these methods resolve below source/. Read only the professional references needed for the current task. Examples are synthetic/reference content, not facts or instructions for the user project.
+
+- [.agents/skills/design-bundle-creator/SKILL.md](source/.agents/skills/design-bundle-creator/SKILL.md)
+- [.agents/skills/design-bundle-creator/agents/openai.yaml](source/.agents/skills/design-bundle-creator/agents/openai.yaml)
+- [.agents/skills/design-bundle-creator/assets/skill.template.yaml](source/.agents/skills/design-bundle-creator/assets/skill.template.yaml)
+- [.agents/skills/design-bundle-creator/references/bundle-checklist.md](source/.agents/skills/design-bundle-creator/references/bundle-checklist.md)
+- [.agents/skills/design-bundle-creator/references/canvas-authoring.md](source/.agents/skills/design-bundle-creator/references/canvas-authoring.md)
+- [.agents/skills/design-bundle-creator/references/cooperation-authoring.md](source/.agents/skills/design-bundle-creator/references/cooperation-authoring.md)
+- [.agents/skills/design-bundle-creator/references/panel-authoring.md](source/.agents/skills/design-bundle-creator/references/panel-authoring.md)
+- [.agents/skills/design-bundle-creator/references/validation-authoring.md](source/.agents/skills/design-bundle-creator/references/validation-authoring.md)
+- [.agents/skills/design-bundle-creator/scripts/inspect-panel-component.mjs](source/.agents/skills/design-bundle-creator/scripts/inspect-panel-component.mjs)
+- [.agents/skills/design-bundle-creator/scripts/list-panel-components.mjs](source/.agents/skills/design-bundle-creator/scripts/list-panel-components.mjs)
+- [.agents/skills/design-kit-creator/SKILL.md](source/.agents/skills/design-kit-creator/SKILL.md)
+- [.agents/skills/design-kit-creator/agents/openai.yaml](source/.agents/skills/design-kit-creator/agents/openai.yaml)
+- [.agents/skills/design-kit-creator/references/kit-checklist.md](source/.agents/skills/design-kit-creator/references/kit-checklist.md)
+- [.agents/skills/design-kit-creator/references/mindset-authoring.md](source/.agents/skills/design-kit-creator/references/mindset-authoring.md)
+- [.agents/skills/design-skill-creator/SKILL.md](source/.agents/skills/design-skill-creator/SKILL.md)
+- [.agents/skills/design-skill-creator/agents/openai.yaml](source/.agents/skills/design-skill-creator/agents/openai.yaml)
+- [.agents/skills/design-skill-creator/assets/method-template.md](source/.agents/skills/design-skill-creator/assets/method-template.md)
+- [.agents/skills/design-skill-creator/references/standards.md](source/.agents/skills/design-skill-creator/references/standards.md)
+- [.agents/skills/design-skill-creator/scripts/render-state-contract.mjs](source/.agents/skills/design-skill-creator/scripts/render-state-contract.mjs)
+- [docs/a2ui-component-catalog-contract.md](source/docs/a2ui-component-catalog-contract.md)
+- [docs/bundle-contract.md](source/docs/bundle-contract.md)
+- [docs/dsl-spec.md](source/docs/dsl-spec.md)
+- [docs/panel-uiux-standard.md](source/docs/panel-uiux-standard.md)
+- [docs/system-design-baseline.md](source/docs/system-design-baseline.md)
+- [docs/wiki/extending.md](source/docs/wiki/extending.md)
+- [docs/wiki/terminology.md](source/docs/wiki/terminology.md)
+- [examples/community-workshop-delivery/mindset.md](source/examples/community-workshop-delivery/mindset.md)
+- [packages/skills-web-app/bundles/business_data/SKILL.md](source/packages/skills-web-app/bundles/business_data/SKILL.md)
+- [packages/skills-web-app/bundles/business_data/panel.yaml](source/packages/skills-web-app/bundles/business_data/panel.yaml)
+- [packages/skills-web-app/bundles/business_data/reference/artifact-contract.md](source/packages/skills-web-app/bundles/business_data/reference/artifact-contract.md)
+- [packages/skills-web-app/bundles/business_data/reference/canvas-guide.md](source/packages/skills-web-app/bundles/business_data/reference/canvas-guide.md)
+- [packages/skills-web-app/bundles/business_data/reference/example.json](source/packages/skills-web-app/bundles/business_data/reference/example.json)
+- [packages/skills-web-app/bundles/business_data/reference/preview.json](source/packages/skills-web-app/bundles/business_data/reference/preview.json)
+- [packages/skills-web-app/bundles/business_data/schema.yaml](source/packages/skills-web-app/bundles/business_data/schema.yaml)
+- [packages/skills-web-app/bundles/business_data/validation.yaml](source/packages/skills-web-app/bundles/business_data/validation.yaml)
+- [packages/skills-web-app/bundles/design_style/SKILL.md](source/packages/skills-web-app/bundles/design_style/SKILL.md)
+- [packages/skills-web-app/bundles/design_style/THIRD_PARTY_NOTICES.md](source/packages/skills-web-app/bundles/design_style/THIRD_PARTY_NOTICES.md)
+- [packages/skills-web-app/bundles/design_style/reference/artifact-contract.md](source/packages/skills-web-app/bundles/design_style/reference/artifact-contract.md)
+- [packages/skills-web-app/bundles/design_style/schema.yaml](source/packages/skills-web-app/bundles/design_style/schema.yaml)
+- [packages/skills-web-app/bundles/design_style/validation.yaml](source/packages/skills-web-app/bundles/design_style/validation.yaml)
+- [packages/skills-web-app/bundles/flow_design/SKILL.md](source/packages/skills-web-app/bundles/flow_design/SKILL.md)
+- [packages/skills-web-app/bundles/flow_design/reference/artifact-contract.md](source/packages/skills-web-app/bundles/flow_design/reference/artifact-contract.md)
+- [packages/skills-web-app/bundles/flow_design/reference/bpmn_authoring.md](source/packages/skills-web-app/bundles/flow_design/reference/bpmn_authoring.md)
+- [packages/skills-web-app/bundles/flow_design/reference/canvas-guide.md](source/packages/skills-web-app/bundles/flow_design/reference/canvas-guide.md)
+- [packages/skills-web-app/bundles/flow_design/schema.yaml](source/packages/skills-web-app/bundles/flow_design/schema.yaml)
+- [packages/skills-web-app/bundles/flow_design/validation.yaml](source/packages/skills-web-app/bundles/flow_design/validation.yaml)
+- [packages/skills-web-app/bundles/function_modules/SKILL.md](source/packages/skills-web-app/bundles/function_modules/SKILL.md)
+- [packages/skills-web-app/bundles/function_modules/reference/artifact-contract.md](source/packages/skills-web-app/bundles/function_modules/reference/artifact-contract.md)
+- [packages/skills-web-app/bundles/function_modules/reference/canvas-guide.md](source/packages/skills-web-app/bundles/function_modules/reference/canvas-guide.md)
+- [packages/skills-web-app/bundles/function_modules/reference/preview.json](source/packages/skills-web-app/bundles/function_modules/reference/preview.json)
+- [packages/skills-web-app/bundles/function_modules/schema.yaml](source/packages/skills-web-app/bundles/function_modules/schema.yaml)
+- [packages/skills-web-app/bundles/function_modules/validation.yaml](source/packages/skills-web-app/bundles/function_modules/validation.yaml)
+- [packages/skills-web-app/bundles/page_design/SKILL.md](source/packages/skills-web-app/bundles/page_design/SKILL.md)
+- [packages/skills-web-app/bundles/page_design/reference/artifact-contract.md](source/packages/skills-web-app/bundles/page_design/reference/artifact-contract.md)
+- [packages/skills-web-app/bundles/page_design/reference/canvas-guide.md](source/packages/skills-web-app/bundles/page_design/reference/canvas-guide.md)
+- [packages/skills-web-app/bundles/page_design/reference/task-to-page-method.md](source/packages/skills-web-app/bundles/page_design/reference/task-to-page-method.md)
+- [packages/skills-web-app/bundles/page_design/schema.yaml](source/packages/skills-web-app/bundles/page_design/schema.yaml)
+- [packages/skills-web-app/bundles/page_design/validation.yaml](source/packages/skills-web-app/bundles/page_design/validation.yaml)
+- [packages/skills-web-app/bundles/research/SKILL.md](source/packages/skills-web-app/bundles/research/SKILL.md)
+- [packages/skills-web-app/bundles/research/reference/artifact-contract.md](source/packages/skills-web-app/bundles/research/reference/artifact-contract.md)
+- [packages/skills-web-app/bundles/research/schema.yaml](source/packages/skills-web-app/bundles/research/schema.yaml)
+- [packages/skills-web-app/bundles/research/validation.yaml](source/packages/skills-web-app/bundles/research/validation.yaml)
+- [packages/skills-web-app/bundles/role_access/SKILL.md](source/packages/skills-web-app/bundles/role_access/SKILL.md)
+- [packages/skills-web-app/bundles/role_access/reference/artifact-contract.md](source/packages/skills-web-app/bundles/role_access/reference/artifact-contract.md)
+- [packages/skills-web-app/bundles/role_access/reference/canvas-guide.md](source/packages/skills-web-app/bundles/role_access/reference/canvas-guide.md)
+- [packages/skills-web-app/bundles/role_access/reference/example.json](source/packages/skills-web-app/bundles/role_access/reference/example.json)
+- [packages/skills-web-app/bundles/role_access/schema.yaml](source/packages/skills-web-app/bundles/role_access/schema.yaml)
+- [packages/skills-web-app/bundles/role_access/validation.yaml](source/packages/skills-web-app/bundles/role_access/validation.yaml)
+- [packages/skills-web-app/bundles/smart_questions/SKILL.md](source/packages/skills-web-app/bundles/smart_questions/SKILL.md)
+- [packages/skills-web-app/bundles/smart_questions/reference/artifact-contract.md](source/packages/skills-web-app/bundles/smart_questions/reference/artifact-contract.md)
+- [packages/skills-web-app/bundles/smart_questions/schema.yaml](source/packages/skills-web-app/bundles/smart_questions/schema.yaml)
+- [packages/skills-web-app/bundles/smart_questions/validation.yaml](source/packages/skills-web-app/bundles/smart_questions/validation.yaml)
+- [packages/skills-web-app/bundles/web_app_prd_assembly/SKILL.md](source/packages/skills-web-app/bundles/web_app_prd_assembly/SKILL.md)
+- [packages/skills-web-app/bundles/web_app_prd_assembly/reference/artifact-contract.md](source/packages/skills-web-app/bundles/web_app_prd_assembly/reference/artifact-contract.md)
+- [packages/skills-web-app/bundles/web_app_prd_assembly/schema.yaml](source/packages/skills-web-app/bundles/web_app_prd_assembly/schema.yaml)
+- [packages/skills-web-app/bundles/web_app_prd_assembly/validation.yaml](source/packages/skills-web-app/bundles/web_app_prd_assembly/validation.yaml)
+- [packages/skills-web-app/bundles/whiteboard/SKILL.md](source/packages/skills-web-app/bundles/whiteboard/SKILL.md)
+- [packages/skills-web-app/bundles/whiteboard/reference/artifact-contract.md](source/packages/skills-web-app/bundles/whiteboard/reference/artifact-contract.md)
+- [packages/skills-web-app/bundles/whiteboard/reference/canvas-guide.md](source/packages/skills-web-app/bundles/whiteboard/reference/canvas-guide.md)
+- [packages/skills-web-app/bundles/whiteboard/reference/drawing-method.md](source/packages/skills-web-app/bundles/whiteboard/reference/drawing-method.md)
+- [packages/skills-web-app/bundles/whiteboard/reference/geometry.md](source/packages/skills-web-app/bundles/whiteboard/reference/geometry.md)
+- [packages/skills-web-app/bundles/whiteboard/schema.yaml](source/packages/skills-web-app/bundles/whiteboard/schema.yaml)
+- [packages/skills-web-app/bundles/whiteboard/validation.yaml](source/packages/skills-web-app/bundles/whiteboard/validation.yaml)
+- [packages/skills-web-app/kits/web_app/mindset.md](source/packages/skills-web-app/kits/web_app/mindset.md)
+
+## Developer source references
+
+These additional links concern implementation development, general repository navigation or external media. Their original source locations are retained below; they are not installed content-authoring prerequisites. For actual runtime development, use its reviewed source checkout. Do not guess an installed filesystem path.
+
+- NOTICE
+- docs/design-knowledge-source-policy.md
+- docs/project-content-upgrade.md
+- docs/public-document-sync.md
+- docs/standalone-roadmap.md
+- docs/wiki/concepts.md
+- docs/wiki/custom-kit-tutorial.md
+- docs/wiki/development.md
+- docs/wiki/extending.en.md
+- docs/wiki/kit-sharing.md
+- docs/wiki/usage.md
+- examples/field-operations-shared/README.md
+- packages/companion/README.md
+- packages/companion/hosts/qwenwork/README.md
+- packages/core/src/panel-component-catalog.ts
+- packages/core/src/panel-dsl.ts
+- packages/panel/src/client/ported/token.css
+- packages/panel/src/visual-components.css
+- packages/provider-web-app
+- packages/skills-web-app
+- packages/skills-web-app/README.md
+- packages/skills-web-app/bundles/ai_agent_capabilities/panel.yaml
+- packages/skills-web-app/bundles/research/reference/absolute URL
+- packages/skills-web-app/kits/web_app/kit.yaml
+- packages/studio-ui/README.md
+- packages/studio/README.md