When you're tasked with giving a client's owner a dashboard on their own site, the owner-console skill in the Local Business OS is your go-to tool. This skill sets up an /admin interface for a client's Next.js app, delivering a dashboard that includes stats, tasks, settings, and quick actions. It's not about rebuilding our existing rails; it's about consuming them effectively.
Every screen in the owner console adheres to the OWNER-ADMIN-PRESENTATION-STANDARD.md. This means using visual cues like a glowing orb for the next job and a ring that never starts at zero. Each card on the dashboard comes with a verb + thing heading, a one-line subhead, actionable buttons or tap-chips, and a mic for voice commands. The goal is clarity and actionability — no walls of text.
For setup tasks, cards are generated from scripts/onboarding-gates.json. These are verified with npm run verify:owner-gates. It's crucial to check the mobile responsiveness with the owner-console-look --mobile command before finalizing the design.
For new client sites, the authentication path is through teneo-auth-client. You initiate this with npx tsx scripts/onboard-client.ts --client <name> --stage auth, which handles owner identity and role grants. This ensures compatibility with the cockpit data model, dashboard routes, and UI patterns.
There's a legacy auth pattern using CLIENTS_SUPABASE for older sites, but it's not recommended for new clients unless specifically requested. The legacy pattern remains for maintaining Glacier-era sites.
The owner-console skill is designed to integrate with existing data sources rather than duplicating them. Stats are pulled from the AnalyticsOS endpoint GET /api/brands/:brandId/local-roi, allowing the console to render data without recomputing metrics. For RED-tier approvals, the console links to the existing HES/N4 approval console, avoiding unnecessary rebuilds.
Customer accounts and checkout processes are entirely separate, managed by features.account and the store module. The owner-console focuses strictly on owner-specific tasks and data.
Before implementing the owner-console, ensure the client app is already built via the appropriate client onboarding processes. This ensures the dashboard integrates seamlessly with the existing infrastructure.
By following these guidelines and utilizing the owner-console skill, you provide a functional and efficient admin dashboard tailored to client site owners without redundant development efforts.
Get weekly insights on AI architecture, pattern recognition, and building platforms without permission.
Resetting the overnight build system can be a daunting task, but it’s necessary to ensure everything is functioning as intended. I recently faced this during...
Read itWhen it comes to proving a boundary from the other side, the "seam-check" method offers a practical approach. This concept stems from the observation that...
Read itThe conversation-bench feature is an intriguing part of our autonomous business system, designed to facilitate meaningful dialogues based on voice recordings...
Read itHave thoughts on this post? I'd love to hear them! Join the conversation on X where we can discuss AI architecture, pattern recognition, and building platforms.
Discuss on XOr reach out directly at @TravisEric_