Usually you can describe the business requirement without selecting a Skill manually each time. Your Coding Agent must support skill discovery and be able to read the project's skills. Automatic selection is not guaranteed. If the agent misses project conventions, explicitly ask it to read the project’s AGENTS.md and the relevant Skill, and check its execution record.
V3 applications use the project-local nocobase-app-development as the main development entry. No-code platform skills such as nocobase-data-modeling and nocobase-ui-builder must not be applied directly to a V3 Core application. The current application template explicitly excludes globally installed NocoBase 2 Skills. See Develop your first app.
Your own Skills can add business rules, design conventions, and acceptance criteria. When instructions conflict, check their versions and task scopes, then follow your agent's instruction hierarchy. There is no universal rule that NocoBase Skills always take precedence. Maintain agreed team rules in project-owned guidance rather than editing Skills generated by dependency synchronization.
In Studio, global, project, and repository skills are combined, with the more specific scope taking precedence for the same skill name. This mounting rule does not automatically resolve contradictions between different skills. See Studio skills.