Goal

Turn a user's business request into a coherent, production-shaped AI Portal application. Own both product design and source implementation: do not stop at a mechanical CRUD example when the user has not supplied detailed information architecture, page composition, copy, or visual direction.

Entry Contract

• Use this skill for every development request after a Portal record has been resolved with portalType === "ai".
• Consume the resolved Portal name, environment, and local source path from nocobase-portal-manage when available. Do not resolve a different Portal inside this skill.
• Do not begin source edits without a real local source directory. If the selected AI Portal's developmentPath / localPath / local source path is empty in nb portal list -j or nb portal info <portal> -j, run nb portal pull <portal> first through the Portal workflow, read the Portal info/list again, then enter the pulled development directory before applying this skill.
• Reject source storage configuration as a working directory. sourceStorage, git_repo, git_branch, git_path, --git-path, repository subdirectories, and deployment/storage paths identify where Portal source is stored for pull/push/deploy; they are not the local development directory for source edits unless nb portal pull readback explicitly returns the same path as developmentPath / localPath.
• When the user is already working in a recognizable AI Portal source project, use that project directly unless the request identifies another Portal.
• Treat @nocobase/portal-template-default as the canonical base-template package. Unless the user explicitly narrows the request, upgrading a Portal means safely applying the latest base-template source changes to the user project, together with required @nocobase/portal-sdk and installed Registry migrations; it never means only changing package or compatibility versions.
• Treat the original build request as authorization to edit and verify that Portal source. Do not ask for a second code-edit confirmation.
• Read the project's AGENTS.md and applicable local instructions before changing files.
• Preserve unrelated worktree changes. Do not push or deploy unless the user requests it.

Required Workflow

1. Inspect the current application