Include instructions to find an application

[JamesY-Appian]

What this changes

Added a new section in applications.md:

• Encourage using the alternative object dependents workflow to find an application for a given object

Failure mode addressed

When tasked with renaming an Appian expression rule to match naming conventions, Claude:

1. Retrieved the rule object successfully
2. Attempted to find its parent application by calling listApplications() with search queries
3. Made multiple API calls searching for applications by name (e.g., searching for "Sandbox", "Test")
4. Failed to locate the application and asked the user: "Which application does this object belong to?"
5. The user then provided the answer: "It's in James Young's Sandbox"

This resulted in unnecessary user friction, multiple failed API calls, and a delay in completing the task.

Why

Claude was missing a critical piece of Appian knowledge: the direct discovery pattern for finding an application UUID from an existing design object.

The applications.md file focused entirely on the creation workflow (building applications from scratch) but omitted the complementary discovery workflow (finding application context for existing objects).

Claude had access to getObjectDependents() as a tool but didn't know it was the intended method for this use case, so it attempted inefficient alternatives (searching and asking the user).

How this fixes it

The modifications teach Claude the more efficient discovery pattern using getObjectDependents()