메뉴
Navigation and NowDev-specific guardrails for ServiceNow Fluent SDK development. Use when a task involves Fluent `.now.ts` metadata, SDK project layout, NowDev agent handoffs, or local patterns that are not covered by `now-sdk explain`.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | nowdev-ai-toolbox-fluent-development |
| user-invocable | false |
| description | Navigation and NowDev-specific guardrails for ServiceNow Fluent SDK development. Use when a task involves Fluent `.now.ts` metadata, SDK project layout, NowDev agent handoffs, or local patterns not covered by installed SDK documentation. |
Use this skill for NowDev workflow conventions around Fluent SDK projects. Do not use it as API reference for constructors, parameters, imports, enums, CLI flags, or examples.
Load nowdev-ai-toolbox-servicenow-sdk before using now-sdk. It is the sole authority for CLI command construction, flags, documentation and query discovery, authentication, output handling, pagination, and troubleshooting; this skill does not duplicate those mechanics.
Always ask the canonical SDK skill to retrieve the relevant installed documentation topic before writing or reviewing Fluent code. Installed SDK documentation takes absolute precedence and is the sole authority on all SDK APIs; local pattern files or prior knowledge do not apply to SDK API syntax or shapes.
If the canonical SDK skill cannot retrieve the installed documentation, halt and inform the user that SDK verification is required before proceeding. Let that skill classify the CLI failure; do not fall back to local pattern docs or prior knowledge as a substitute for current SDK shape.
Use these local docs ONLY for workflows and patterns not covered by the SDK. Always prioritize installed SDK guides retrieved by nowdev-ai-toolbox-servicenow-sdk, and consult these files only for the specific non-API topics they cover:
| Need | Local Reference |
|---|---|
| Build/runtime troubleshooting workflow | TROUBLESHOOTING.md |
| Multi-agent handoff sequencing, artifact naming conventions, and NowDev-specific anti-patterns not addressable by SDK explain topics | ADVANCED-PATTERNS.md |
The following used to be local files but are now fully covered by installed SDK documentation. Ask the canonical SDK skill to retrieve these topics:
| Need | SDK Topic |
|---|---|
| JavaScript modules, module/string-only decision support | module-guide |
| Script Include bridges (module-to-Script Include pattern) | script-include-guide |
$override risk policy and gotchas | override-guide |
| React UI Page build model, dirty state, service layer, CSS constraints | ui-page-patterns-guide |
| Work Type | Agent |
|---|---|
| Tables, Roles, ACLs, Data Policies, Properties, Menus, Lists, Form layouts, Instance Scan checks | NowDev-AI-Fluent-Schema-Developer |
| Business Rules, Script Includes, Script Actions, REST APIs, Email Notifications, SLAs, Scheduled Scripts | NowDev-AI-Fluent-Logic-Developer |
| Flows, Subflows, custom actions/triggers, Playbooks | NowDev-AI-Fluent-Automation-Developer |
| UI Pages, React client code, Client Scripts, UI Policies, UI Actions, Catalog, Portal, Workspaces, Dashboards | NowDev-AI-Fluent-UI-Developer |
| AiAgent, AiAgenticWorkflow | NowDev-AI-AI-Agent-Developer |
| NowAssistSkillConfig | NowDev-AI-NowAssist-Developer |
Automated Test Framework Test() definitions | NowDev-AI-ATF-Developer |
| SDK build/install/release | NowDev-AI-Fluent-Release |
| Code review | NowDev-AI-Fluent-Reviewer |
nowdev-ai-toolbox-servicenow-sdk before writing or reviewing code.now.config.json, .vscode/nowdev-ai-config.json, generated schema types, and session artifact state.table.name or record.$id; use Now.ref() for metadata outside the current application.Now.include() for files only where the current SDK topic says the property accepts string content or file inclusion.module-guide, and use topic now-include-guide only to confirm file-inclusion syntax. The artifact-specific topic takes precedence over the general guides.nowdev-ai-toolbox-servicenow-sdk.Table() / BusinessRule() / Record() definition from a .now.ts file without confirming with the user first — the deletion may need to propagate as an upgrade-time delete via keys.ts, which the code alone can't reveal. See the required Fluent orientation (keys-file topic) in nowdev-ai-toolbox-servicenow-sdk.Prefer existing project layout when present. For new Fluent projects, use clear ownership folders such as:
src/fluent/tables/
src/fluent/script-includes/
src/fluent/business-rules/
src/fluent/ui-pages/
src/fluent/flows/
src/client/
src/tests/
Use this layout as a convention only; API correctness still comes from installed documentation retrieved through nowdev-ai-toolbox-servicenow-sdk and the current workspace.
Explains exactly why a ServiceNow user lacks access or permissions to view/edit a record, view/modify a field, or execute an action/UI Action, and provides a precise remedy. Triggers when the user mentions "I can't see/edit X", "insufficient rights", "why is this field read-only", "access denied", "user can't run this action/UI action", "ACL failure", "no write access", "cannot view", or similar permission and access restriction issues. It uses read-only `now-sdk` retrieval delegated to `nowdev-ai-toolbox-servicenow-sdk` to trace ACL evaluations and identify failing roles or conditions.
Surfaces and correlates recent configuration and code changes in a single live ServiceNow instance to explain a sudden regression ("this used to work"). Trigger this skill whenever a user mentions a regression or asks "what changed recently", "started failing after...", "did someone break this", "regression since last week", or says something was working but is now broken. The skill delegates read-only `now-sdk` retrieval to `nowdev-ai-toolbox-servicenow-sdk`, then maps Customer Updates into a chronological, risk-annotated timeline.
Safely and systematically audits configuration drift between two or more ServiceNow environments/instances that share the same Fluent application scope. Use this skill for environment comparison, drift audits, alignment checks, or pre-deployment safety checks. It delegates read-only `now-sdk` retrieval to `nowdev-ai-toolbox-servicenow-sdk` and aggregates configuration differences into high, medium, and low risk categories.
Symptom-first root-cause triage when something in the live ServiceNow instance is broken or erroring and the user has no known file/script to point at. Use for unexpected UI/session crashes, background job exceptions, flow failures, email delivery issues, integration errors, and general instance triage. It delegates read-only `now-sdk` retrieval to `nowdev-ai-toolbox-servicenow-sdk` across operational diagnostic tables.
Review and cross-check generated ServiceNow artifacts and code against relevant connected instance Knowledge Base articles for organizational guidelines, development standards, and forbidden patterns. Use this skill when the user asks "does this follow our documented guidelines?", "check compliance", "verify against our KB standards", "audit against KB", or during a code review when checking compliance of any ServiceNow scripts, tables, flows, or other elements.
Draft customer/end-user-facing incident updates and KB-linked replies in the user's target language. ALWAYS use this skill whenever the user asks to "draft a response to this incident", "write an update for the customer/requester", "reply to this ticket in [language]", or "close this incident with a customer-facing note", even if they do not explicitly ask for multilingual support or KB integration.