Best Practices

A few habits that make working with Starcat smoother. Each one comes with an example you can adapt.

​

Scope Before You Build

For anything beyond a quick question, start in Plan or Chat mode so you and Starcat agree on the approach before any changes happen. Review the plan, adjust it, then switch to Agent to carry it out.

“We want a customer feedback widget on both the storefront and the help center. Plan how you’d add it before changing anything.”

Starcat researches both apps, lays out a numbered plan, and waits. You correct anything that looks off, then let it execute.

​

Keep Your Knowledge Store Current

Starcat checks your knowledge store before it answers, so the more your policies, brand guidelines, and decisions live there, the more consistent it gets. Save things as you settle them instead of re-explaining them in every chat.

“Save this for the team: refunds over $500 need manager approval. Add it to our refund policy.”

Later, any conversation can rely on that rule without you repeating it.

​

Let Starcat Coordinate, Not Micromanage

When you enable developer agents, describe changes at the level of features and behavior. Let each project’s Developer Agent decide how to implement them in code.

“Add a loyalty program to the POS app: customers earn one point per dollar and can redeem points at checkout.”

Skip the implementation details like table names, file structure, or which component to touch. Spelling those out ties the Developer Agent’s hands and usually leads to worse results.

​

Design First When Looks Matter

For visual work, use Design mode to settle on a direction with HTML mockups before any project starts building. Comparing options on screen is faster than describing them in words.

“In Design mode, mock up three layouts for our analytics dashboard so I can pick one.”

Once you’ve chosen, switch to Agent or dispatch a Developer Agent to build the real thing.

​

Share Work Your Team Should See

Set a chat to Shared with org when the conversation is something others should be able to follow or pick up later, like an investigation or a plan the team will act on.

A chat where Starcat traced last week’s revenue dip and proposed next steps is worth sharing, so the whole team sees the findings instead of just you.

​

Match the Tier to the Task

Pick the agent tier to fit the work. Drop to Lite or Core for quick lookups, and stay on Plus or move to Pro for heavier reasoning and multi-project work.

Lite: “What’s our return policy?” Pro: “Roll out a new checkout flow across our storefront, admin, and email apps.”

​

Common Mistakes

• “Starcat seems confused about what I’m looking at.” In an app’s sidebar, turn on the Include current page content toggle (the eye icon in the chat input) so Starcat reads the page you’re viewing instead of guessing. See Sharing what you’re looking at.
• “Starcat is doing things it shouldn’t.” Work the task out in Plan or Chat mode first, in as much detail as you need, and only switch to Agent once the plan is right. Agent mode acts right away, so the clearer the plan going in, the fewer surprises.
• “Starcat can’t reach one of my apps.” It can only operate apps that have Allow agent access turned on for the environment you’re using. Enable it in that app’s Settings → Cross-App tab.
• “Starcat won’t create an app or hand work to a project.” Those actions stay off until you turn on developer agents for the chat, which is available in Agent mode.

​

Related