Customer command system

AI Commands Dictionary

Use short commands like /goal, /review, /deploy, and @Neuralito to tell Opcelerate Neural what you want done, which lane should handle it, what proof you need, and where human approval is required.

How commands work

Write the outcome, then set the boundary.

Good commands are not magic words. They are compact business instructions. The best ones say what should happen, where the evidence lives, what quality bar matters, and what must not happen without approval.

Command formula
@roleWho should think first: shop guide, news desk, security, training, scout, or human.
/commandThe job mode: goal, review, build, research, deploy, scan, train, or fix.
objectiveThe business result you want, written in plain English.
sourceLink, screenshot, page, product, document, customer note, or context.
boundaryBudget, deadline, approval rule, citation requirement, or no-go area.
Use /goal when the work has a finish line.Example: create, test, deploy, and verify a page.
Use @ when the request has a clear owner.@Quetzal for news, @Jaguar for security, @Monarch for training, @Neuralito for shop help.
Use approval words for risky actions.Publishing, sending, checkout changes, deleting, data exports, and client-facing promises need explicit confirmation.
Slash command dictionary

Every customer command in one place.

Filter by mode or search by outcome. Each card includes the best model lane, what the command does, and a prompt you can copy.

28 commands
/goalPlanner lane

Lock the objective and finish line.

Use this when the work needs persistence: a page, article, audit, shop repair, campaign, deployment, or full workflow.

/goal create a customer-ready AI Commands Dictionary page, add it to navigation, test mobile, and deploy.
/planReasoning lane

Map the safest sequence before execution.

Good for large changes, migrations, product decisions, or anything where order matters.

/plan compare three ways to add Shopify checkout without breaking the public shop experience.
/startAction lane

Begin from the current context.

Use after the scope is clear and you want work to move, not another round of discussion.

/start use the latest approved brief and begin the homepage contrast cleanup.
/continueContinuation lane

Resume the last verified path.

Best when work was interrupted and you want the next safe step, not a restart.

/continue from the last deployment check and finish the remaining mobile QA.
/stopControl lane

Pause execution cleanly.

Use this when you need to review, redirect, or prevent further changes until you approve.

/stop do not deploy or edit more files until I review the live page.
/statusEvidence lane

Get the current state with proof.

Asks for what changed, what passed, what failed, what is live, and what remains.

/status tell me what is deployed, what was verified, and what still needs attention.
/reviewReview lane

Inspect for problems before customers see it.

Use for code, pages, product copy, Shopify products, AI responses, forms, and flows.

/review this shop page with customer eyes: trust, clarity, checkout friction, mobile layout, and copy.
/auditAudit lane

Run a deeper evidence-backed check.

Use when you need screenshots, accessibility checks, source proof, SEO checks, or a ranked issue list.

/audit the mobile homepage for contrast, readable text, menu behavior, page speed, and conversion blockers.
/fixCoding lane

Make a targeted correction.

Best for a specific bug, broken link, bad contrast, layout overlap, mobile issue, or wrong copy.

/fix the phone menu overlay so it never covers the chat input or action buttons.
/buildBuilder lane

Create a new page, tool, or workflow.

Use for public pages, landing pages, quote flows, dashboards, training surfaces, or internal tools.

/build a public Edmonton AI agency page with local proof, service cards, citations, and a booking CTA.
/researchResearch lane

Gather source-backed context.

Use when claims may be current, technical, financial, legal, competitive, or source-sensitive.

/research current AI model releases this week and only use official vendor sources where possible.
/newsQuetzal lane

Turn a real-world update into a briefing.

Use for AGI Times headlines, source notes, local Opcelerate takes, and customer education articles.

/news create an AGI Times article from this source with headline, cool image direction, citations, and the Opcelerate take.
/imageMultimodal lane

Create or improve visuals.

Use for article images, link previews, mascot assets, product cards, hero artwork, and ad-style thumbnails.

/image create a bright article image about private AI hardware on a desk, realistic, warm, clickable, not dark.
/copyCopy lane

Improve words that sell or explain.

Use for headlines, service descriptions, product pages, SEO snippets, emails, and customer-facing summaries.

/copy make this service card clearer for business owners who do not want to prompt and just want the work done.
/deployPublish lane

Publish and verify live state.

Use when a page or fix is ready to go public. It should include build, deploy, and live URL verification.

/deploy after tests pass and verify the live URL returns 200 on desktop and phone.
/scanOpportunity lane

Find practical first AI wins.

Use for company profiles, workflows, websites, grants, tenders, automation ideas, and quick-win matching.

/scan this company and return 5 realistic AI opportunities, each with effort, value, and first step.
/quoteSales lane

Turn a need into a scoped offer.

Use to translate a vague request into deliverables, timeline, assumptions, price path, and approval points.

/quote a 2-week AI receptionist pilot for a local clinic with setup, training, and handoff included.
/trainMonarch lane

Create learning people can use.

Use for staff lessons, AI policy training, role-based classes, onboarding, workshops, and practice exercises.

@Monarch /train create a 60-minute class for sales staff using AI safely with customer notes.
/docDocument lane

Produce a polished document.

Use for reports, proposals, playbooks, handoff notes, SOPs, training guides, or one-page briefs.

/doc create a client-ready AI Opportunity Scan report with findings, recommendations, and next steps.
/shopNeuralito lane

Choose the right service card.

Use when the customer wants to buy a quick win, compare packages, or understand what happens after checkout.

@Neuralito /shop I need website help, SEO, and a chatbot. Which card should I start with?
/handoffOperations lane

Make the next step unambiguous.

Use after builds, audits, repairs, and research so the next person knows status, files, decisions, and risks.

/handoff summarize what changed, what is live, what needs client approval, and the next 3 actions.
/citeSource lane

Add citations and source notes.

Use when an article, page, claim, report, or recommendation needs links people can check.

/cite this article with official sources, clearly separate facts from Opcelerate recommendations.
/protectJaguar lane

Set privacy and approval boundaries.

Use before sharing customer data, publishing, payment edits, integrations, exports, or public claims.

@Jaguar /protect this automation: identify private data, approvals, rollback plan, and logging needs.
/compareDecision lane

Compare options before buying or building.

Use for model choices, software vendors, service paths, hardware, pricing tiers, and build-vs-buy questions.

/compare ChatGPT, Claude, Gemini, Grok, and local models for private customer-support workflows.
/localPrivate model lane

Use the private or on-device path.

Use when sensitive workflows should avoid unnecessary cloud exposure or need local inference planning.

/local design a private AI setup for internal documents, no customer data sent to public tools.
/agentAgent lane

Design a bounded AI agent workflow.

Use for multi-step work where the AI needs tools, memory, checks, logs, and human review points.

/agent design a lead intake agent that qualifies, drafts a reply, logs CRM notes, and waits for approval.
/sopOperations lane

Turn a workflow into a repeatable process.

Use when a business task should be documented, trained, delegated, or automated in stages.

/sop create a weekly AI content publishing process with source checks, image review, and deploy verification.
/verifyQA lane

Check the result with evidence.

Use after any change where “done” requires screenshots, live URLs, build logs, or customer-flow checks.

/verify the new page on mobile and desktop: live 200, no horizontal scroll, readable contrast, links work.
/bookHuman lane

Move from AI guidance to a human call.

Use when the next step needs pricing, commitments, timeline, client context, or final approval.

/book prepare a short agenda for a strategy call about CRM automation and AI receptionist setup.
Model lanes

We route the work by risk, speed, and proof.

Customers do not need to memorize model names. The command decides which lane is safest for the job.

Fast model

Quick drafts and triage.

Best for summaries, first-pass copy, small answers, simple product guidance, and low-risk brainstorming.

/status/copy/shop
Reasoning model

Decisions, plans, and tradeoffs.

Best when the answer needs multiple constraints, business judgment, step ordering, or risk comparison.

/goal/plan/compare
Coding agent

Files, tests, and deploys.

Best for website changes, code repair, data cleanup, local verification, build checks, and live deployment.

/build/fix/deploy
Multimodal model

Screenshots, images, and documents.

Best for reading screenshots, improving visuals, checking layout, creating article imagery, and document review.

/image/audit/doc
Private model

Sensitive work with tighter boundaries.

Best when data exposure, local hardware, private documents, or customer confidentiality is the main concern.

/local/protect/agent
Human review

Money, legal, security, and promises.

Best when a decision creates a public claim, charge, customer message, irreversible edit, or formal commitment.

/book/quote/verify
@ mention routing

Use @ when the work needs a role.

The companion family gives customers a memorable way to route the request without knowing the internal stack.

Neuralito mascot badge
@NeuralitoShop guide

Service cards, checkout questions, quick wins, website help, and customer routing.

Quetzal badge
@QuetzalNews desk

AGI Times articles, source-backed briefings, headlines, citations, and current-event takes.

Jaguar badge
@JaguarSecurity

Privacy, approvals, data boundaries, rollback plans, compliance, and enterprise controls.

Monarch badge
@MonarchTraining

Staff learning, transformation, SOPs, role-based lessons, adoption plans, and workshops.

Neural Scout signal badge
@NeuralScoutOpportunities

Tenders, grants, local market signals, prospect lists, and realistic win paths.

Service shop button
@ShopService menu

Packages, product fit, payment path, delivery expectations, and which card to buy first.

Opcelerate Neural logo
@AndresHuman approval

Escalate for pricing, final commitments, calls, client-sensitive decisions, and scope judgment.

Opcelerate public page preview
@PageWebsite review

Point to a page, screenshot, product, form, or URL and ask for customer-eye feedback.

Customer workflow

One strong request beats ten vague prompts.

Use this sequence when you want Opcelerate Neural to take a messy idea and turn it into a finished result.

1. Name the role@Neuralito, @Quetzal, @Jaguar, @Monarch, @Shop, or @Andres.
2. Pick the command/goal, /review, /build, /scan, /quote, /deploy, or /protect.
3. Attach contextSend a URL, screenshot, product, source, document, or customer note.
4. Set the barSay mobile-first, cite sources, customer-ready, no dark visuals, or under budget.
5. Require proofAsk for live URL, screenshot, test result, source list, or checkout verification.
Approval rules

Commands speed up work. They do not remove judgment.

The safest AI systems are explicit about what can move automatically and what needs a human checkpoint.

Always ask before these actions.

  • Charging money, changing checkout, or modifying payment settings.
  • Sending emails, SMS, DMs, outreach, or customer-facing promises.
  • Deleting data, overwriting active work, changing DNS, or touching credentials.
  • Publishing legal, medical, financial, security, or high-stakes claims.

Ask for this proof when it matters.

  • Live URL and HTTP status after deployment.
  • Mobile and desktop screenshots for important pages.
  • Source links for news, technical claims, and citations.
  • Known remaining risks, test gaps, and next recommended move.
Ready starter

Copy this when you do not know where to begin.

Use this as the default customer prompt for Opcelerate Neural. It gives enough structure to start without forcing you to become a prompt engineer.

@Neuralito /scan my business and find the first useful AI win. Keep it practical, explain the value, note the risk, show the first step, and tell me whether I should buy a Quick Win, book a call, or wait.