• Never use methods other than the dws command to operate (prohibit curl, HTTP API, browsers)
• Never fabricate identifiers like UUID or ID; must extract them from command returns
• Never guess field names/parameter values; must query and confirm before operation

• All commands must include

  --format json

  to get parsable output
• Dangerous operations must be confirmed with the user first; add

  --yes

  to execute only after user consent
• Batch operations cannot exceed 30 records at a time
• All commands must strictly follow the parameter formats specified in the corresponding product reference documents (e.g., if there are parameter values, there must be at least one space between the parameter and its value)

aitable

approval

attendance

calendar

chat

contact

devdoc

ding

report

todo

workbench

For more confusing scenarios, see intent-guide.md

dws

1. Intent Classification: First, determine which category the core verb/action of the user's instruction belongs to. This is more important than focusing on nouns.
2. Ambiguity Handling and Information Inquiry: If the user's instruction is ambiguous or contains keywords from multiple products, never guess. You must actively ask the user to clarify the intent. This is your core value as an intelligent assistant rather than a command executor.
3. Precise Product Mapping: After completing the first two steps and clarifying the intent, refer to the Product Overview and Intent Judgment Decision Tree to select the product.
4. Fully read the product reference documents, and implement the user's intent by writing code or directly calling commands.

1. When encountering an error, retry once with

   --verbose

2. If

   RECOVERY_EVENT_ID=<event_id>

   appears in stderr, prioritize executing the recovery closed-loop according to recovery-guide.md
3. If it still fails, report the complete error information to the user; never attempt alternative solutions on your own
4. For authentication failures, refer to the authentication section in global-reference.md for handling
5. High-frequency errors and troubleshooting processes for each product can be found in error-codes.md

• references/products/ — Detailed references for each product's commands
• references/intent-guide.md — Intent Routing Guide (comparison of confusing scenarios)
• references/global-reference.md — Global flags, authentication, output format
• references/field-rules.md — AI Table field type rules
• references/error-codes.md — Error codes + debugging process
• references/recovery-guide.md — Recovery closed-loop,

  RECOVERY_EVENT_ID

  ,

  execute/finalize

  specifications
• scripts/ — Batch operation scripts for each product (AI Table/Calendar/Bot Messages/Address Book/Attendance/Logs/Todo, etc.)