Emphasise mcp use

Author: tkallady

skills/forge-app-builder/SKILL.md

@@ -42,7 +42,7 @@ Continue here when diagnosis or review is incidental to active build work. If th
 
 ## Ground the selected route
 
-Read [references/documentation-routing.md](references/documentation-routing.md) when current platform detail is needed. Use the Forge MCP capabilities actually available in the session; discover them by purpose rather than assuming permanent tool names. Use focused official Atlassian documentation as fallback and for critical verification.
+Read [references/documentation-routing.md](references/documentation-routing.md) when current platform detail is needed. Use Forge MCP as the first preference whenever it is available. Discover its current capabilities by purpose rather than assuming permanent tool names, and call the narrowest relevant capability before relying on web documentation or remembered platform knowledge. Use focused official Atlassian documentation when MCP is unavailable, fails, or lacks the exact coverage needed, and for critical verification.
 
 Call the general Forge development guide when broad orientation is useful. Do not call it merely to satisfy a ritual when the task needs only one known leaf reference. Retrieve the exact module, manifest property, endpoint, scope, or CLI page before relying on it.
 

skills/forge-app-builder/references/custom-ui.md

@@ -4,6 +4,8 @@ Read this reference only for Custom UI or browser content embedded through UI Ki
 
 Confirm that the selected module supports the UI approach. Use current documentation to establish the resource and build boundary, bridge or resolver boundary, and any relevant CSP or egress requirements.
 
+When the implementation uses Atlaskit or Atlassian Design System components, tokens, or icons, use ADS MCP as the first preference when it is available. Use official ADS documentation as fallback. Do not apply ADS or Atlaskit packages to UI Kit.
+
 Preserve a supported existing frontend toolchain. Keep secrets and privileged operations out of browser code. Build production resources before Forge validation and ensure manifest resources point to the intended output. Retrieve current internationalization and accessibility guidance when the requested experience requires them.
 
 Official entries:

skills/forge-app-builder/references/documentation-routing.md

@@ -2,7 +2,11 @@
 
 Read this reference when current Forge platform detail is needed. Keep volatile schemas, commands, versions, packages, limits, and lifecycle labels out of local guidance.
 
-Use the Forge MCP capabilities available in the current session rather than assuming permanent tool names. Choose the narrowest useful source: general guides for orientation, module discovery for candidate extension points, domain guides for architecture, and focused search plus the authoritative page for exact implementation facts.
+Use Forge MCP first whenever it is available for current Forge platform guidance. Discover the capabilities exposed in the current session rather than assuming permanent tool names. Choose the narrowest useful MCP source: general guides for orientation, module discovery for candidate extension points, domain guides for architecture, and focused search for exact implementation facts.
+
+For Atlaskit or Atlassian Design System decisions in Custom UI, use ADS MCP first when it is available. Do not use ADS MCP as a source for UI Kit components.
+
+The skill and its scripts still work without either MCP server. If the preferred MCP server is unavailable, fails, or does not cover the required detail, use the exact official Atlassian documentation as fallback. Report the failed or unavailable lookup and any uncertainty that still affects the implementation.
 
 Check lifecycle, changelog, deprecation, and migration information when using non-GA features or changing observed legacy behavior. Verify critical details against the latest official page even when MCP provides an answer.
 
@@ -24,4 +28,4 @@ Check lifecycle, changelog, deprecation, and migration information when using no
 - Changelog: <https://developer.atlassian.com/platform/forge/changelog/>
 - Deprecation policy: <https://developer.atlassian.com/platform/forge/deprecation-policy/>
 
-Prefer an official Markdown representation when available. If a lookup fails, report what was unavailable, which official source replaced it, and any uncertainty that still affects safe implementation. Never imply that MCP was consulted when it was not.
+Prefer an official Markdown representation when available. Never imply that MCP was consulted when it was not.