@wowok/skills 1.1.4 → 1.1.6

package/wowok-safety/SKILL.md

@@ -19,12 +19,35 @@ always: true
 
 ## 1. Core Principles
 
-### 1.1 Security & Safety
+### 1.1 Object Reuse Principle (General Best Practice)
+
+**ALWAYS prefer reusing existing objects over creating new ones** — this enables centralized permission control and reduces management overhead.
+
+| Object Type | Reuse Strategy | Why |
+|-------------|----------------|-----|
+| **Permission** | **Strongly recommended** — ask user for existing Permission name/ID | Centralized permission control across all services |
+| Machine | Reuse if workflow fits | Save design time for similar processes |
+| Guards | Reuse if validation logic matches | Avoid redundant rules |
+| Contact | Reuse existing customer service Contact | Single point of management |
+| Arbitration | Always reuse existing Arbitration services | Customers choose from established arbiters |
+
+**How to Reuse**:
+- Ask user: *"Do you have an existing object you'd like to reuse? Provide the name or ID."*
+- Use string value `"<name_or_id>"` to reference existing objects
+- Use object shape `{ name?, ... }` only when creating new
+
+**CREATE vs MODIFY Pattern**:
+| Format | Meaning | Use When |
+|--------|---------|----------|
+| String `"<name>"` or `"<0x...>"` | **REUSE** existing | Object already exists |
+| Object `{ name?, ... }` | **CREATE** new | Need new object |
+
+### 1.2 Security & Safety
 
 - **Hot Wallet Usage**: WoWok never exposes private keys. Treat it as a spending account for transfers, receipts, and commerce. Flag large transactions for explicit user confirmation.
 - **Amount-Sensitive Operations**: Any token transfer, payment, or reward distribution MUST be verbally confirmed with the user before execution. Use `Payment` objects for commercial transfers when possible (they offer Guard validation and purpose tracking).
 
-### 1.2 LOCAL vs ON-CHAIN
+### 1.3 LOCAL vs ON-CHAIN
 
 | Type | Tools | Gas | Confirmation |
 |------|-------|-----|--------------|
@@ -33,7 +56,7 @@ always: true
 | **QUERY** | `query_toolkit`, `onchain_table_data`, `onchain_events`, `guard2file`, `machineNode2file` | Read-only | Not needed |
 | **ENCRYPTED** | `messenger_operation` (watch/send messages) | Local encryption | Not needed |
 
-### 1.3 Default Account
+### 1.4 Default Account
 
 Empty string `""` means the default account. Always use `""` when the user does not specify an account.
 
@@ -188,7 +211,7 @@ Use `Payment` objects for commercial transfers when possible — they offer Guar
 
 **Tool**: `wowok_buildin_info` with `info: "permissions"`, `info: "guard_instructions"`, or `info: "value types"`.
 
-### 9.1 Value Types — Built-in Type Annotation System
+### 8.1 Value Types — Built-in Type Annotation System
 
 WoWok's value type system is the foundation for type-safe data declarations used across Guards, records, and query instructions. Every data field in a Guard table or Guard submission carries a `value_type` annotation, ensuring the protocol can validate and process data correctly.
 
@@ -239,4 +262,4 @@ For complex objects with many fields (Service, Machine), use **incremental build
 
 **Query Schema**: `schema_query({ action: "get", name: "<schema_name>" })`
 
-**Related Skills**: [wowok-tools](../wowok-tools/SKILL.md) | [wowok-guard](../wowok-guard/SKILL.md) | [wowok-machine](../wowok-machine/SKILL.md)
+**Related Skills**: [wowok-tools](../wowok-tools/SKILL.md) | [wowok-guard](../wowok-guard/SKILL.md) | [wowok-machine](../wowok-machine/SKILL.md) | [wowok-order](../wowok-order/SKILL.md) | [wowok-provider](../wowok-provider/SKILL.md) | [wowok-arbitrator](../wowok-arbitrator/SKILL.md) | [wowok-messenger](../wowok-messenger/SKILL.md)

package/wowok-tools/SKILL.md

@@ -18,7 +18,7 @@ always: true
 
 Quick reference for WoWok MCP tools — patterns, pitfalls, and troubleshooting.
 
-> **Domain Skills**: [wowok-guard](../wowok-guard/SKILL.md) (validation logic), [wowok-messenger](../wowok-messenger/SKILL.md) (encrypted messaging), [wowok-machine](../wowok-machine/SKILL.md) (workflows)
+> **Domain Skills**: [wowok-guard](../wowok-guard/SKILL.md) (validation logic), [wowok-messenger](../wowok-messenger/SKILL.md) (encrypted messaging), [wowok-machine](../wowok-machine/SKILL.md) (workflows), [wowok-safety](../wowok-safety/SKILL.md) (safety & naming)
 > **Business Skills**: [wowok-order](../wowok-order/SKILL.md) (customer), [wowok-provider](../wowok-provider/SKILL.md) (merchant), [wowok-arbitrator](../wowok-arbitrator/SKILL.md) (dispute resolution)
 
 ---
@@ -42,9 +42,11 @@ Quick reference for WoWok MCP tools — patterns, pitfalls, and troubleshooting.
 
 ### CREATE vs MODIFY Pattern
 
+See [wowok-safety](../wowok-safety/SKILL.md) for complete object reuse principles.
+
 | Format | Meaning | Example |
 |--------|---------|---------|
-| **String** | Reference EXISTING | `"my-service"` or `"0x1234..."` |
+| **String** | Reference EXISTING (reuse) | `"my-service"` or `"0x1234..."` |
 | **Object** | CREATE NEW | `{ name: "my-service", permission: "..." }` |
 
 ---