---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/application-development
Release :
- australia
ft:locale :
- en-US
ft:publication_title :
- Australia Build or modify applications
ft:clusterId :
- cadev
bundleId :
- cadev
workflow :
- Development, Data, and Analytics
---
# General guidelines
# General guidelines for Build Agent {#ariaid-title1}
Release version: Australia
Updated July 24, 2026
 3 minutes to read
Summarize
 Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
## Summary of General guidelines for Build Agent
These guidelines help ServiceNow customers optimize the use of Build Agent in their development workflows.
Build Agent assists with application development by interpreting detailed instructions, managing metadata, and automating coding tasks.
Following these best practices ensures efficient collaboration, accurate outputs, and maintainable applications within the ServiceNow platform.
Show full answer Show less
## Development guidelines
* **Plan before coding:** Define application requirements across data and UI layers using tools like Workflow Studio or Figma.
* **Collaborate on scope:** Work with Build Agent to clarify tables, metadata types, and project boundaries.
* **Provide clear, contextual instructions:** Use Markdown files in your project directory to give Build Agent detailed, structured guidance.
* **Use precise ServiceNow terminology:** Reference exact table names, fields, roles, and artifact types to improve accuracy and reduce iterations.
* **Test frequently:** Add sample data, use the Automated Test Framework (ATF), and validate changes early and often.
* **Utilize version control:** Employ Git to track changes and maintain a clean workspace.
* **Provide visual aids:** Share screenshots to help Build Agent troubleshoot UI issues.
* **Extend functionality:** Incorporate third-party Node Package Manager (NPM) libraries, such as React JS, for advanced interfaces.
* **Maintain thorough documentation:** Use Build Agent to generate knowledge base articles and enforce coding standards.
* **Iterate and prototype:** Experiment freely, then refine prompts for reproducible builds.
## Prompting guidelines
* **Use Autonomous Engineer for complex projects:** It conducts interviews, generates and parallelizes work plans, and requires plan approval before building.
* **Request prompt suggestions:** Ask Build Agent to help craft ideal prompts or highlight pitfalls for specific metadata types.
* **Be comprehensive:** Combine all relevant elements such as tables, fields, roles, and automations in one detailed prompt to improve results.
* **Leverage planning and interviews:** Allow Build Agent to ask clarifying questions to better understand requirements and reduce guesswork.
* **Prefer specific ServiceNow terminology:** Naming exact entities (e.g., sysuser) reduces building cycles and enhances precision.
* **Write prompts offline:** Compose and refine prompts in a text editor before submitting to Build Agent to improve clarity and outcomes.
* **Develop incrementally:** Build and test features separately in consecutive sessions for better control and quality.
* **Use Markdown grounding files:** Include files like `GUIDE.md` or `BUILDAGENTRULES.md` in your project to enforce organizational standards during sessions (available in ServiceNow IDE only).
## Advanced configuration
* **Custom skills and rules:** Define instance-, application-, or user-level instructions to ensure consistent Build Agent behavior without needing project files. This supports enforcing naming conventions, required fields, and on-demand guidance.
* **ESLint integration:** Configure ESLint on the ServiceNow AI Platform for preferred coding styles (e.g., snake case). Build Agent can manage and enforce these configurations automatically.
Use these guidelines to get the most out of Build Agent in your development workflow.
## Development guidelines {#build-agent-general-guidelines__gg-overview}
To maximize Build Agent effectiveness, use the following practices:
* Design before coding: Think through and document the requirements for your application across the data and UI layers, for example using Workflow Studio or Figma.
* Start with a clear plan: Collaborate with Build Agent to define scope, required tables, and metadata types.
* Instruct with context: Write instructions for what you want to achieve with your application using Markdown in your file system. You can then ask Build Agent to use the file as context for its work.
* Use specific terminology: Treat Build Agent as your development partner. Provide specific, clear instructions using ServiceNow platform terminology such as table names, field names, roles, and artifact types.
* Test early and often: Add sample records, test on the instance, and run ATF tests throughout development.
* Use version control: Use Git for tracking changes and maintaining a clean workspace structure.
* Provide visual context: Give screenshots to Build Agent to troubleshoot UI issues and request changes.
* Extend with third-party libraries: Integrate third-party Node Package Manager (NPM) libraries, such as React JS, for enhanced interfaces.
* Maintain documentation: Keep clear rules and documentation in project folders; use Build Agent to create knowledge base articles.
* Iterate and experiment: Prototype freely, then ask Build Agent for an ideal prompt to recreate the result once your vision is complete.
{#build-agent-general-guidelines__ul_bhg_21f_yhc}
## Prompting guidelines {#build-agent-general-guidelines__section_old_trc_2jc}
Use the following guidelines to get better results from Build Agent.
Use Autonomous Engineer for large implementations
: For complex apps or ServiceNow product implementations, use Autonomous Engineer. Autonomous Engineer interviews you, generates a plan with work items, and builds all work items in parallel in the background. Review and approve the plan before Build Agent starts building. For more information, see [Autonomous Engineer in Build Agent](https://www.servicenow.com/docs/zb6G6vaJadtISGWATD~UoQ "Autonomous Engineer is an agentic worker that augments product development capacity across the SDLC. It intakes requirements, applies platform best practices through agent packs, and generates an implementation plan before building work items in parallel through Build Agent.").
Ask Build Agent to prompt for you
: Ask Build Agent to suggest an ideal prompt for your goal or coach you on common pitfalls for a given metadata type. To learn more, see this Community article on [The fastest way to learn Build Agent prompting? Ask Build Agent](https://www.servicenow.com/community/now-assist-for-creator-articles/the-fastest-way-to-learn-build-agent-prompting-ask-build-agent/ta-p/3533544).
Be comprehensive
: One detailed prompt can provide better results than several vague ones. Include tables, fields, roles, and automation in a single prompt.
Use the planning tool
: For complex apps, ask Build Agent to create a plan first. Review and approve before it starts building.
Let Build Agent interview you
: For broad ideas, let Build Agent ask clarifying questions before planning. In Autonomous Engineer, this interview is built into the workflow. In standard chat, you can prompt Build Agent to ask questions before it starts building. Both approaches produce better results than trying to anticipate every detail yourself.
Use specific ServiceNow terminology
: Say reference to sys_user instead of add a field for who ordered. Naming the table, field, scope, role, or artifact reduces interview cycles and produces more accurate output on
the first attempt. Conversational prompts work well for early exploration, while precision works better as the build progresses.
Draft offline
: Write prompts in a text editor, refine them, then paste into the chat, which saves prompts and can help to produce better results.
Develop incrementally
: Develop each page or feature in separate chats. Implement and test, then start a new conversation for the next feature.
Use markdown
: Place a markdown file (for example, named GUIDE_\*.md or BUILD_AGENT_RULES.md) in your project directory. Build Agent reads these grounding files and follows your conventions throughout the session.
Note:
Markdown for Build Agent is currently available only in the ServiceNow IDE. Teams that get the most value from Build Agent markdown files document their organizational standards in these files, including the following:
* Naming conventions: table names, field names, business rule naming patterns, and scope prefixes
* Technical standards: coding practices, preferred patterns, and anti-patterns to avoid
* Development cadence: processes, update set management, and code review requirements
* Last-resort actions that require explicit approval: creating new tables, changing ACLs or roles, modifying system properties, and altering base system business rules
{#build-agent-general-guidelines__ul_guides_content}
Use custom skills and rules
: Define instance-level, application-level, and user-level instructions that Build Agent follows in every session. Use rules to enforce consistent behavior automatically, such as naming conventions or required fields. Use skills to provide on-demand guidance for specific tasks.
Unlike markdown grounding files, custom skills and rules require no project files and apply across all sessions at the configured scope. For more information, see [Configure custom skills and rules](https://www.servicenow.com/docs/LtRpDHZkp~kmMTLlM624KQ "Create and manage custom skills and rules, or instructions to control how Build Agent behaves during a session. Rules are preloaded into every session automatically. Skills are available on demand when you or the agent invokes them by name.").
Use ESLint
: Use ESLint on the ServiceNow AI Platform to define your preferred coding style, and ask Build Agent to manage and enforce the ESLint configuration, for example using snake case for variables.
{#build-agent-general-guidelines__dl_prompting_guidelines}