ShareCRM AI intelligent configuration development kit

1. What is the ShareCRM AI intelligent configuration development kit

Environment preparation → Requirement understanding → Skill orchestration → Configuration generation → Code development → Review and validation → Release confirmation

• Create or modify objects, fields, layouts, and layout rules.
• Develop APL buttons, flows, scheduled tasks, custom controllers, or event listeners.
• Develop PWC components or plugins.
• Parse requirements from Word documents or pasted content.
• Generate PRDs, technical solutions, implementation plans, and code review reports.
• Run compilation, static analysis, manual validation reminders, and risk confirmation before release.

2. AI intelligent implementation scenarios

3. Quick start

1. Install a local AI agent (WorkBuddy / Trae SOLO Desktop / Codex / Claude Code)
2. Install the CLI tool
3. Download and install sharedev-init
4. Call the sharedev-init skill in the AI agent to initialize the project
5. Quick experience

3.1 Step 1: Install a local AI agent

• WorkBuddy: Visit codebuddy.cn/work, download the installer for your system (Windows / macOS), and log in with your Tencent account after installation.
• Trae SOLO Desktop: Chinese users can download the China version from trae.com.cn, supporting Windows / macOS / Linux; international users can visit trae.ai.
• Codex: We recommend the CLI method npm install -g @openai/codex, or get the desktop app from chatgpt.com/codex; requires ChatGPT Plus / Pro or higher subscription.
• Claude Code: For macOS / Linux, run curl -fsSL https://claude.ai/install.sh | bash; on Windows, run irm https://claude.ai/install.ps1 | iex in PowerShell; you can also download the desktop app or use the Web version; requires Claude Pro or higher subscription.

• WorkBuddy and Trae SOLO Desktop recommend: Deepseek V4 Pro, GLM-5.1, KIMI-K2.6.
• Codex and Claude Code can use their official corresponding models.

3.2 Step 2: CLI tool installation

Environment requirements

• Node.js: >= 22.0.0
• Package manager: npm 8+, pnpm 8+, or Yarn 2+

1. Download Node.js — Visit the Node.js official website to download the latest stable version and follow the installation wizard (usually keeping the default settings).
2. Environment ready — After completing the above steps, you can install the CLI.

Command-line installation

npm install -g @share-crm/sharedev-cli

curl -fsSL http://developer.fxiaoke.com/sharedev/install.sh | bash

irm https://developer.fxiaoke.com/sharedev/install.ps1 | iex

Verify installation

sharedev -v

3.3 Step 3: Download and install sharedev-init

{
  "enterpriseEA": "fktest001",
  "domain": "https://www.fxiaoke.com",
  "certificate": "ZXlKaGJHY2lPaUpJVXpJMU5pSXNJblI1Y0NJNklrcFhWQ0o5LmV5SnpkV0lpT2lKU1pYRjFaWE4wVkc5clpXNGlMQ0pwYzNNaU9pSkRSVkF0VTJWeWRtVnlJaXdpWlc1MFpYSndjbWx6WlVGalkyOTFiblFpT2lKbWEzUmxjM1E0TlRBM0lpd2laVzUwWlhKd2NtbHpaVWxrSWpvNE1qUXpNRElzSW5ObGMzTnBiMjVKWkNJNklqWTNNemN6WmpjM0xUSXdPVFV0TkdJMVpTMDVZbVU0TFdOaE16VXpZV0k1T0dVME5pSXNJbVY0Y0NJNk16ZzNNelV4TURVeE9Dd2lkWE5sY2tsa0lqb3hNREF3TENKcFlYUWlPakUzTnprd056UTVOVGw5Lm9Sbjdfc1FJSmtsVlAxUGQy"
}

/                           # Project root
└──  settings.json                          # Initialization input: tenant connection info

For specific content settings, see the “Environment initialization content” section.

3.4 Step 4: Example initialization

1. Install the skill from <path where skill package is stored>/sharedev-init.zip
2. After installation, call the sharedev-init skill in the AI agent as follows

/sharedev-init initialize current <workspace>

/                           # Project root
├── settings.json                          # Tenant connection info
├──.sharedev/                             # Local metadata
│   ├── dev-metadata/objects/              # Object dictionary
│   ├── apl-docs/                          # APL documents
│   └── pwc-docs/                          # PWC documents
├── <enterpriseRoot>/                    # Enterprise project directory
│   ├──.trae/skills/                      # Target platform skills
│   ├── specs/apl/                         # APL specifications and references
│   ├── package/fx/custom/apl/script/      # APL source code
│   │   ├── <namespace>.function.groovy
│   │   └── <namespace>.class.groovy
│   ├── pwc/                               # PWC component/plugin resources
│   │   └── components/
│   │       └── <componentName>/
│   │           ├── source/
│   │           ├──.sharedev-meta.json
│   │           └── mateXml.xml
│   └── tenant-config/                     # CRM configuration directory
│       ├── objects/<objectApiName>/
│       │   ├── <objectApiName>.object-meta.xml
│       │   ├── fields/<fieldApiName>.field-meta.xml
│       │   ├── layouts/<layoutApiName>.layout-meta.xml
│       │   ├── layout-rules/<ruleApiName>.layout-rule-meta.xml
│       │   ├── validation-rules/<ruleApiName>.validation-rule-meta.xml
│       │   ├── scenes/<sceneApiName>.scene-meta.xml
│       │   └── buttons/<buttonApiName>.button-meta.xml
│       ├── option-sets/<optionSetApiName>.option-set-meta.xml
│       ├── mapping-rules/<ruleApiName>.mapping-rule-meta.xml
│       ├── convert-rules/<ruleApiName>.convert-rule-meta.xml
│       ├── global-variables/<variableApiName>.global-variable-meta.xml
│       ├── currencies/currency.currency-meta.xml
│       ├── approval/<workflowApiName>/
│       │   ├── workflow.json
│       │   ├── rule.json
│       │   └── execution.json
│       ├── stage/<workflowApiName>/
│       │   ├── workflow.json
│       │   └── rule.json
│       └── bpm/
└──.trae/skills/                          # Global skill directory (installed during initialization)

Note: The <enterpriseRoot> directory is the enterprise root. All sharedev remote operation commands (such as apl push, pwc deploy, object-dev push) should be executed in this directory, not in <projectRoot>.

3.5 Step 5: Hands-on experience

Scenario 1: One-sentence end-to-end development

/sharedev-auto [requirement description]

/sharedev-auto Parse and orchestrate the skill chain based on this Word requirement document: /path/to/requirement.docx

We recommend using WorkBuddy, Codex, or Trae SOLO Desktop locally for Word document recognition. These tools will automatically install the corresponding plugins or Python extractors for your environment.

• Input source recognition result: one sentence, file path, Word document, or pasted content
• Structured requirement summary: objects, fields, pages, rules, APL, PWC, release targets, etc.
• Complexity level: L1 to L5
• Recommended skill chain: configuration, APL, PWC, or mixed orchestration path
• Phase Gate: hard stop points requiring user confirmation
• Execution plan for specialized skills after user confirmation

Scenario 2: Create a business object from scratch

/sharedev-object Create a "Competitor Profile" object with API Name Competitor__c

/sharedev-field Add fields Competitor Name, Industry, Official Website, and Active Status to Competitor__c

/sharedev-layout Configure the detail page, new page, and list page layouts for Competitor__c

/sharedev-layout-rule On the Competitor__c new page, hide the Official Website field when Active Status is "Inactive"

• tenant-config/objects/<objectApiName>/<objectApiName>.object-meta.xml — Object definition
• tenant-config/objects/<objectApiName>/fields/<fieldApiName>.field-meta.xml — Field definition
• tenant-config/objects/<objectApiName>/layouts/<layoutApiName>.layout-meta.xml — Page layout
• tenant-config/objects/<objectApiName>/layout-rules/<ruleApiName>.layout-rule-meta.xml — Layout rule

Note: New fields do not automatically appear on the page. To display fields, you need to configure layouts. Layout rules can only control fields already in the target layout. If a field is not placed in the layout, adjust the layout first, then configure the rule.

Scenario 3: Develop an APL flow function

/sharedev-apl-implement Develop a flow function: when a sales order is approved, automatically update the customer's latest transaction time. Please follow the complete APL development process.

/sharedev-apl-lite Quickly write a customer detail page button function to check whether Customer Level is empty. PRD/ARCH/TASKS are not needed.

/sharedev-apl-code-review Review this APL function for me, confirm compile/analyze and release risks, and output REVIEW.md.

• package/fx/custom/apl/script/<namespace>.function.groovy — Function source code
• package/fx/custom/apl/script/<namespace>.class.groovy — Class source code
• deliverables/<requirementDir>/PRD.md, ARCH.md, TASKS.md — Full process documents
• deliverables/<requirementDir>/REVIEW.md — Code review report
• Results of sharedev apl compile <namespace> and sharedev apl analyze <namespace>

• Full development: Requirement confirmation → PRD/ARCH/TASKS → Code implementation → compile/analyze → Code review → Release confirmation
• Lite development: Requirement confirmation → Code implementation → compile/analyze → Code review → Release confirmation
• Code review: Confirm scope → compile/analyze → Rule review → REVIEW.md → Review conclusion

The Lite process only skips PRD/ARCH/TASKS, not compile/analyze, code review, and release authorization.

Scenario 4: Develop a PWC plugin

/sharedev-pwc-write-prd-spec Develop a customer new/edit page plugin that automatically checks whether a mobile phone number is duplicated and prompts. Please write the PRD first.

1. Use the sharedev-pwc-write-prd-spec skill to clarify requirements and output prd.md
2. After the user approves the PRD, use the sharedev-pwc-write-arch skill to output arch.md
3. After the user approves the technical solution, use the sharedev-pwc-write-plans skill to output plan.md
4. Use the sharedev-pwc-execute-plans or sharedev-pwc-subagent-driven-development skill to execute the plan
5. After the main functions are completed, use the sharedev-pwc-review-code skill to review
6. Use the sharedev-pwc-finish-development skill to output configuration instructions and request manual testing
7. Only after manual testing passes and the user explicitly authorizes, execute release

Scenario 5: Configure a common option set

/sharedev-option-set Create a "Industry" common option set with API Name option_industry__c, including Internet, Finance, Manufacturing, and Healthcare options, with Internet marked blue.

1. The skill checks tenant-config/option-sets/ to confirm no API Name conflict
2. Generate the option_industry__c.option-set-meta.xml configuration file
3. Deploy: sharedev object-dev option-set push --apiNames option_industry__c
4. Then use sharedev-field to reference this option set for fields

Note: The option set value is the data primary key. After creation, existing values cannot be deleted or modified. Unused values should be set to not_usable=true to disable them.

Scenario 6: Configure validation rules

/sharedev-validation-rule Add a validation rule to LeadsObj: Mobile Phone cannot be empty. When Mobile Phone is empty, block save and prompt "Mobile phone number is required".

1. The skill confirms the target object exists and loads the field list
2. Confirm with the user the rule name, block/non-block, trigger timing (new/edit)
3. Generate the formula expression (returns Boolean)
4. Output validation-rules/<ruleApiName>.validation-rule-meta.xml
5. Deploy: sharedev object-dev validate-rule push --objectApiName LeadsObj --apiName <ruleApiName>

Note: The validation rule expression must ultimately be Boolean (true = trigger prompt). In master-detail simultaneous creation scenarios, non-blocking rules on child objects do not take effect.

Scenario 7: Configure mapping rules (field backfill)

/sharedev-mapping-rule Configure the lead-to-account mapping rule: Company Name → Account Name, Phone → Account Phone, Address → Account Address.

1. The skill confirms the source object (LeadsObj) and target object (AccountObj) exist
2. Load both sides’ field lists to validate field references
3. Generate the mapping-rules/<ruleApiName>.mapping-rule-meta.xml configuration file (including main rule + paired button)
4. Deploy: sharedev object-dev object-mapping push --ruleApiNames <ruleApiName>

Note: Mapping rules are a simplified version of convert rules and do not support scenarios/strategies/merge/rollback/close/excess checks. For complete push/pull document capabilities, use sharedev-convert-rule.

Scenario 8: Configure an approval process

/sharedev-approval Configure a two-level approval process for the Purchase Request document: Department Manager → General Manager. After approval, automatically update the document status to "Approved".

1. The skill collects node structure, approver configuration, post actions, etc.
2. Generate the tenant-config/approval/<workflowApiName>/workflow.json approval flow body
3. Deploy: sharedev approval def deploy -f tenant-config/approval/<workflowApiName>/ --updateType "create"
4. After successful deployment, fill back the workflowId

Note: New and updated uses different data structures — when creating, workflow.id is an empty string; when updating, you must use the real ID obtained from detail. sharedev-approval is for approval flows, sharedev-bpm-def is for BPM business processes, and sharedev-stage-def is for stage advancers.

4. Intelligent orchestration details (sharedev-auto)

4.1 Overview

4.2 Input source detection

4.3 Requirement analysis and product line classification

4.4 Skill chain templates

Template A: Pure PWC development chain

write-prd-spec → write-arch → write-plans → implement → review-code → finish-development

Template B: Pure APL development chain

prd → arch → plan → apl-init → apl-implement → apl-code-review → (push)

Template C: Object configuration chain

prd → plan → object → option-set → field → layout → scene → layout-rule → validation-rule → mapping-rule → global-variable → (push)

Template D: PWC+APL mixed chain

prd → arch → plan → [APL ∥ PWC] → review → deploy

Template E: Full-stack development chain

prd → arch → plan → [Object ∥ APL ∥ PWC] → review → deploy

Template F: Flow definition chain

[prd → arch → plan →] flow-def → <workflowApiName> → deploy

Flow Definition deployment is independently controlled by the flow-skill internal HARD-GATE and user confirmation flow.

4.5 Document generation flow

4.6 Review execution flow

4.7 Multi-sub-agent parallel execution

4.8 Phase Gate coordination — three major hard stops

4.9 Mandatory deployment order

Object → Option Set → Field → Layout → Scene → Layout Rule → Validation Rule → Mapping Rule → Global Variable → Button → APL → PWC

5. Skill details

5.0 Quick skill reference table

Configuration skills

APL backend development skills

PWC frontend development skills

Flow definition skills

5.1 Configuration skills

sharedev-object — Object definition configuration

• Input: Object API Name, display name, feature switches (such as approval flow, stage advancer, etc.)
• Output path: tenant-config/objects/<objectApiName>/<objectApiName>.object-meta.xml
• Constraints: Custom objects end with __c; content.release_version is fixed to "6.4"; define_type=custom prohibits short_name
• Example:

  /sharedev-object Create a "Competitor Profile" object with API Name Competitor__c
  

sharedev-option-set — Common option set configuration

• Input: API Name (format option___c), option list (label/value/color/enable status)
• Output path: tenant-config/option-sets/<optionSetApiName>.option-set-meta.xml
• Constraints: Deleting or modifying existing values is prohibited (breaks historical data); only add new values or disable them; cannot create option sets for platform system fields
• Example:

  /sharedev-option-set Create an "Industry" common option set with API Name option_industry__c, including Internet, Finance, Manufacturing, Healthcare
  

sharedev-field — Field definition configuration

• Input: Object API Name, field name, type (text/number/date/select_one, etc.), option values, default value, required/read-only
• Output path: tenant-config/objects/<objectApiName>/fields/<fieldApiName>.field-meta.xml
• Constraints: Confirm the object exists and the API Name does not conflict; formula type requires referring to the formula generation guide; cascade fields require referring to the cascade specification
• Example:

  /sharedev-field Add a "Competitor Name" text field to Competitor__c, API Name competitor_name__c, required
  

sharedev-layout — Page layout configuration

• Input: Object API Name, layout type, field grouping and arrangement, PWC plugin mounting
• Output path: tenant-config/objects/<objectApiName>/layouts/<layoutApiName>.layout-meta.xml
• Constraints: Detail layout must contain name and owner fields; edit layout requires the server to enable independent edit page first; list and list_layout cannot be confused
• Example:

  /sharedev-layout Configure the detail page layout for Competitor__c, placing Competitor Name, Industry, and Official Website in the basic information section
  

sharedev-layout-rule — Layout rule configuration

• Input: Object API Name, target layout, main field, condition tree, action (show/hide/required/read-only)
• Output path: tenant-config/objects/<objectApiName>/layout-rules/<ruleApiName>.layout-rule-meta.xml
• Constraints: Maximum 10 rules per layout; condition field and leaf field cannot be the same; main fields cannot be repeated in the same layout
• Example:

  /sharedev-layout-rule On the Competitor__c new page, hide the Official Website field when Active Status is "Inactive"
  

sharedev-validation-rule — Validation rule configuration

• Input: Object API Name, rule name, formula expression (returns Boolean), error message, block/non-block, trigger timing
• Output path: tenant-config/objects/<objectApiName>/validation-rules/<ruleApiName>.validation-rule-meta.xml
• Constraints: Formula return value must be Boolean; in master-detail simultaneous creation scenarios, non-blocking rules on child objects do not take effect
• Example:

  /sharedev-validation-rule Add a validation rule to LeadsObj: Mobile Phone cannot be empty, block save, prompt "Mobile phone number is required"
  

sharedev-scene — Tenant scene configuration

• Input: Object API Name, scene name, filter conditions (wheres), scope (ranges), display columns
• Output path: tenant-config/objects/<objectApiName>/scenes/<sceneApiName>.scene-meta.xml
• Constraints: Must check whether API Name conflicts; default fields are used when display columns are not provided
• Example:

  /sharedev-scene Create a "My Accounts" scene for AccountObj with filter condition Owner equals current user
  

sharedev-mapping-rule — Mapping rule configuration

• Input: Source object, target object, field mapping (field_mapping), option mapping (option_mapping), child object mapping
• Output path: tenant-config/mapping-rules/<ruleApiName>.mapping-rule-meta.xml
• Constraints: Source/target objects must exist; unsupported field types for mapping (reference/calculated/statistics/auto-number, etc.); Contract/Refund/Invoice objects cannot be mapping targets
• Example:

  /sharedev-mapping-rule Configure the lead-to-account mapping rule: Company Name → Account Name, Phone → Account Phone
  

sharedev-convert-rule — Convert rule configuration (push/pull)

• Input: Source object, target object, scenario type, strategy, field mapping, rollback logic, close logic
• Output path: tenant-config/convert-rules/<ruleApiName>.convert-rule-meta.xml
• Constraints: More complex than mapping-rule; suitable for complete push/pull document processes
• Example:

  /sharedev-convert-rule Configure a one-to-one simple scenario convert rule from Purchase Request to Purchase Order
  

sharedev-button — Custom button configuration

• Input: Object API Name, button API Name, type, post actions (post_actions), display conditions (wheres), input form
• Output path: tenant-config/objects/<objectApiName>/buttons/<buttonApiName>.button-meta.xml
• Constraints: Missing APL function blocks and points to sharedev-apl-implement; jump buttons cannot configure post actions; mapping buttons cannot configure input form and post actions
• Example:

  /sharedev-button Configure a "Sync WeCom" normal button for AccountObj, calling an APL function
  

sharedev-global-variable — Global variable configuration

• Input: API Name (format var___g), type (string/number/date, etc.), default value, remark
• Output path: tenant-config/global-variables/<variableApiName>.global-variable-meta.xml
• Constraints: api_name cannot be changed after creation; __c suffix is not applicable (use __g); 4 system preset variables (currentTime__g, etc.) cannot be modified
• Example:

  /sharedev-global-variable Create a "Minimum Discount" global variable, type number, default value 0.8
  

sharedev-currency — Currency and exchange rate configuration

• Input: Currency code (ISO standard), currency name, exchange rate, base currency flag
• Output path: tenant-config/currencies/currency.currency-meta.xml (single file for the whole tenant)
• Constraints: Base currency is set only once and cannot be modified; currencyCode must come from the ISO standard list; cannot add an existing currency repeatedly
• Example:

  /sharedev-currency Add USD currency, exchange rate 7.24
  

5.2 APL backend development skills

sharedev-apl-implement — APL full development

• Execution flow: Phase 0 (Requirement confirmation) → Phase 1 (PRD/ARCH/TASKS) → Phase 2 (Code implementation) → Phase 3 (Compile + Analyze) → Phase 4 (Code review) → Phase 5 (Release confirmation)
• Hard stops: Before code review (Phase 5-6 transition) and before release (Phase 6-7 transition)
• Example:

  /sharedev-apl-implement Develop a flow function: when a sales order is approved, automatically update the customer's latest transaction time
  

sharedev-apl-lite — APL lightweight development

• Execution flow: Phase 0 (Requirement confirmation) → Phase 1 (Code implementation) → Phase 2 (Compile + Analyze) → Phase 3 (Code review) → Phase 4 (Release)
• Constraints: Does not skip compile/analyze, code review, and release authorization
• Example:

  /sharedev-apl-lite Quickly write a customer detail page button function to check whether Customer Level is empty
  

sharedev-apl-code-review — APL code review

• Review output: Findings (sorted by severity), Review Decision (pass/conditional pass/fail), REVIEW.md
• Constraints: Must compile/static analyze before manual review; cannot enter release recommendation when blocking issues are found
• Example:

  /sharedev-apl-code-review Review my APL function, confirm compile/analyze and release risks
  

5.3 PWC frontend development skills

sharedev-pwc — PWC basic commands

• Subcommands: pull (pull source), push (upload files), deploy (push + build + release), create (create resource)
• Example:

  sharedev pwc pull --all --type component
  

sharedev-pwc-write-prd-spec — PWC requirement document

• Flow: Explore project background → Ask clarification questions → Propose solution → Present design → User approval → Write PRD
• Constraints: Cannot write code or call technical design skills before user approval
• Example:

  /sharedev-pwc-write-prd-spec Develop a customer new/edit page plugin that automatically checks whether a mobile phone number is duplicated
  

sharedev-pwc-write-arch — PWC technical solution

• Constraints: Must first load the skill and read reference documents (spec + feature)
• Example:

  /sharedev-pwc-write-arch Design a PWC plugin technical solution based on the approved PRD
  

sharedev-pwc-write-plans — PWC implementation plan

• Output path: deliverables/YYYY-MM-DD-<featureName>/plan.md
• Example:

  /sharedev-pwc-write-plans Break down the PWC technical solution into executable task plans
  

sharedev-pwc-implement — PWC plan execution

• Flow: Load and review plan → Sync PWC resources (create/pull) → Implement code task by task
• Example:

  /sharedev-pwc-implement Implement PWC code task by task according to plan.md
  

sharedev-pwc-subagent-driven-development — PWC sub-agent-driven development

• Constraints: Maximum 8 parallel sub-agents
• Example:

  /sharedev-pwc-subagent-driven-development Use sub-agents to develop multiple independent PWC tasks in parallel
  

sharedev-pwc-review-code — PWC code review

• Review content: Source code quality check, PRD verification, output REVIEW.md
• Example:

  /sharedev-pwc-review-code Review the PWC plugin code and confirm it meets the PRD requirements
  

sharedev-pwc-finish-development — PWC delivery wrap-up

• Flow: Generate configuration instructions → Request manual testing → Release after test passes
• Example:

  /sharedev-pwc-finish-development PWC plugin development is complete, request manual testing and prepare release
  

sharedev-pwc-fix-bug — PWC bug fix

• Flow: Reproduce problem → Locate code → Fix → Manual verification
• Example:

  /sharedev-pwc-fix-bug Fix the bug in the PWC plugin where mobile phone number duplicate check does not take effect
  

5.4 Flow definition skills

sharedev-approval — Approval flow definition

• Output path: tenant-config/approval/<workflowApiName>/workflow.json (approval flow body), rule.json (instance post actions), execution.json (process post actions)
• Deployment: New passes --updateType "create", update passes --updateType "update"
• Example:

  /sharedev-approval Configure a two-level approval for Purchase Request: Department Manager → General Manager, and automatically update status after approval
  

sharedev-bpm-def — BPM business process definition

• Deployment: Through the sharedev bpm def create-definition command
• Example:

  /sharedev-bpm-def Create a customer approval BPM process including Sales Manager review and Finance review nodes
  

sharedev-stage-def — Stage advancer definition

• Output path: tenant-config/stage/<workflowApiName>/workflow.json, rule.json
• Deployment: New uses sharedev stage def deploy, update uses sharedev stage def update
• Difference from approval flow: No execution.json; post actions are reflected in stage tasks
• Example:

  /sharedev-stage-def Configure a stage advancer for Opportunity: Prospect → Needs Analysis → Solution Quote → Negotiation → Closed Won
  

sharedev-oneflow-def — OneFlow process definition

sharedev-flow-def — Flow common data structure specification

6. Usage boundaries and precautions

• AI can help analyze requirements, generate configurations, develop code, run checks, and organize deliverables, but remote release requires explicit user authorization.
• Before referencing objects and fields, prefer reading .sharedev/dev-metadata/objects/<objectApiName>.md.
• APL and configuration development cannot guess object API Names, field API Names, or option values.
• APL must pass sharedev apl compile <namespace> and sharedev apl analyze <namespace> before release.
• PWC must complete code review, configuration instructions, and manual testing confirmation before release.
• push, deploy, and configuration push commands cannot be automatically executed just because the user says “continue”.
• When a Word document cannot be read, prompt the user to paste the body or provide readable text.
• When requirement descriptions conflict with document content, list the conflicts and wait for user confirmation.
• Custom object configuration can only reference other custom objects, not preset objects (such as ContactObj).
• PWC prohibits using the document.querySelector global selector.
• APL prohibits for loops, Range expressions, the owner reserved word, and multi-argument log.error.
• Layout rules are limited to 10 rules per layout, and condition fields and leaf fields cannot be the same.
• Mapping rule source/target objects must exist; Contract/Refund/Invoice/Marketing Activity/Visit cannot be mapping targets.
• All CLI commands must be executed under the <enterpriseRoot> directory, and running directly from <projectRoot> is prohibited.

7. Frequently asked questions

Q1: Why can’t the target platform be determined by directory?

Q2: The initialization command succeeded, so why can’t we say it’s complete?

Q3: Does sharedev-auto directly implement requirements?

Q4: Only new fields were added, why are they not visible on the page?

Q5: Why can’t we hand-write XML directly?

Q6: Can field API Names be in Chinese or named arbitrarily?

Q7: Why must manual testing be done before release?

Q8: Why must all CLI commands be executed under the enterpriseRoot directory?

Q9: What are the configuration restrictions for layout rules?

Q10: What is the difference between mapping rules and convert rules?

Q11: What should I do if Windows PowerShell reports “cannot load file” when running the installation script?

If you want to restore a stricter policy, you can run Set-ExecutionPolicy Restricted -Scope CurrentUser after installation.