new-bundle

原文涵盖的主题

• New Bundle
• Behavior
• Addon flows
• Safety
• References

Create a version-controlled project-local bundle under .aiwg/. 1. Determine the bundle name and type. 2. Select an optional starter artifact. 3. Preview when requested, then run: 4. Deploy the completed bundle with aiwg use . 5. Validate project-local health with aiwg doctor. 6. When the bundle is ready to graduate, use aiwg promote --dry-run. The default type is extension; the default starter is skill. The aliases new-extension, new-addon, new-framework, new-plugin, and new-provider select their corresponding type. After aiwg new-bundle ux-studio --type addon, add a flows/ directory and set addonConfig.entry.flows to "flows/" in its manifest. Each flows/ .yaml uses the existing flow.aiwg.io/v1 metalanguage with kind: FlowCapability, metadata.name, and a schema-valid spec including description, version, inputs, and outputs. Custom relative entry directories and .yml files are also supported. Optionally declare a top-level flows: [" "] inventory; legacy addonConfig.flows is also accepted. A skill alone remains type skill. Rebuild and inspect the authored flow from the project root: The flow card shows Owner: addon:ux-studio; the project-local list reports flow names and counts. Use

这里只展示节选，请以完整原文和当前要求为准。