$ loading_
分析业务需求并推荐 Power Pages 最合适的后端集成方案与实施路径。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "integrate-backend" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/integrate-backend/SKILL.md 2. 保存为 ~/.claude/skills/integrate-backend/SKILL.md 3. 装好后重载技能，告诉我可以用了
我正在做一个 Power Pages 门户，用户提交表单后需要校验数据、写入外部系统，并在部分场景触发审批。请分析应该用 Web API、Server Logic、Cloud Flows 还是组合方案，并说明原因。
给出适合该场景的后端集成架构建议，并说明各方案的适用性、优缺点与推荐组合。
我想让 Power Pages 连接公司内部 CRM 和订单系统，需要考虑身份验证、实时读写、失败重试和维护成本。请帮我判断最合适的后端集成方式。
输出面向内部系统集成的方案建议，涵盖认证方式、数据流设计、可靠性与运维考虑。
我还不确定该怎么给 Power Pages 做后端能力：既要读取 Dataverse 数据，也可能要接第三方 API，还想做自动化通知。请先帮我拆解需求并判断后续应该优先走哪个专项方向。
先完成需求分析与技术路径判断，再明确应转向的专项方案方向与下一步实施重点。
Plugin check: Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"— if it outputs a message, show it to the user before proceeding.
Analyze the user's business problem and recommend the right backend integration approach — Web API, Server Logic, Cloud Flows, or a combination — then route to the appropriate skill(s) to implement the solution.
Initial request: $ARGUMENTS
Goal: Locate the Power Pages project root and confirm prerequisites
Actions:
Look for powerpages.config.json in the current directory or immediate subdirectories.
If not found: Tell the user to create a site first with /create-site.
Use the Explore agent to quickly scan the site for existing backend integrations:
"Analyze this Power Pages code site for existing backend integrations:
- Check
.powerpages-site/server-logic/— list any existing server logic endpoints- Check
.powerpages-site/cloud-flow-consumer/— list any registered cloud flows- Search frontend code (
src/**/*.{ts,tsx,js,jsx,vue,astro}) for calls to/_api/(Web API) and/_api/serverlogics/(Server Logic) and/_api/cloudflow/(Cloud Flows)- Check for existing service layers or API utilities in
src/services/,src/shared/, or similar- List available web roles from
.powerpages-site/web-roles/*.webrole.ymlReport what backend integrations already exist so we can build on them."
Check whether the user's Dataverse environment has existing custom actions that could be leveraged in the integration:
node "${CLAUDE_PLUGIN_ROOT}/scripts/list-custom-actions.js" "<ENV_URL>"
The script returns Custom APIs (modern) and Custom Process Actions (legacy) with their names, descriptions, binding types, and parameters. If custom actions are found, note them — they will be factored into the recommendation in Phase 3.
Output: Project root confirmed, existing backend integrations identified, Dataverse custom actions discovered
Goal: Analyze the user's request to understand the underlying business problem, not just the technical ask
Actions:
From the user's request and the existing site state, determine:
…
为 Power Apps 代码应用接入 Azure DevOps 连接器，便于查询工单、提报缺陷与管理流水线。
为 Power Pages 编写、配置并部署安全的服务器端逻辑与接口。