◆ Salesforce

Add Visualforce page to custom object

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskAdd the new Visualforce page 'ClientDetails' to the 'Account' custom object, making sure it's…+
Add the new Visualforce page 'ClientDetails' to the 'Account' custom object, making sure it's accessible to all sales profiles and appears as a related list on the standard Account layout before Friday's demo.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I add this Visualforce page to the custom object, check if there are any existing custom…+
Before I add this Visualforce page to the custom object, check if there are any existing custom pages that serve a similar purpose or if this new page could break any current automations tied to 'Account' records. I need to avoid conflicts for the sales team.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new 'ClientDetails' Visualforce page I just added to the Account object isn't visible to…+
The new Visualforce page isn't showing up for the sales team, but it works for me.
The new 'ClientDetails' Visualforce page I just added to the Account object isn't visible to the sales team, but it renders fine when I test it. I'm afraid I missed a critical permission or profile setting, and the regional sales manager needs to see it working by end of day. What did I likely miss, and what's the fastest way to diagnose and fix it so they can see it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time after deploying Visualforce pages because they're not visible to the right…+
Repeatedly struggle with Visualforce page visibility and access after deployment.
I keep losing time after deploying Visualforce pages because they're not visible to the right users, forcing me to backtrack on permissions. What habit should I change in my deployment process to ensure I cover all visibility and access settings upfront, avoiding these delays and frustration for the sales team?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Salesforce's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.