Build complete Dublyobase backends through remote HTTP MCP, admin REST APIs, and public project APIs. Use when an AI agent needs to connect to a live Dublyobase instance, create projects, design Postgres collections and fields, configure rules, seed records, create app users, upload files, configure SMTP/storage/CORS/auth settings, cron jobs, backups/restores, webhooks, quotas, orgs, invitations, SaaS or ecommerce schemas, schema import, and verify a PocketBase/Supabase-style backend.
Use when the user is building, scaffolding, or shipping an app that will be deployed to Dublyo (https://dublyo.com — a managed self-hosted PaaS). Triggers on phrases like "deploy to Dublyo", "deploy on Dublyo", "Dublyo-ready app", "host this on my Dublyo server", "scaffold a Dublyo project", "Dublyo Panel API", or when the user provides Dublyo Panel credentials and asks to manage a stack. Ensures the project follows Dublyo deployment conventions (containerized, env-driven, stateless, listens on $PORT, single web service, image published to ghcr.io, docker-compose ready) AND gives the AI exact API recipes for managing stacks on the user's Dublyo Panel when admin credentials are given.
Write the shortest correct code that does exactly what was asked - nothing more. Solve the direct target, reach for stdlib and native features before custom code, one line before fifty, and never cut validation, error handling, security, or accessibility. Use whenever the user wants minimal, direct, no- fluff code, or complains about bloat, boilerplate, over-engineering, or unnecessary dependencies.
Build, improve, or audit web apps using MDN Web Docs as the standards baseline. Use for frontend and web design/code tasks including new app or landing page creation, redesigns, refactors, code review, accessibility audits, responsive QA, performance checks, security reviews, forms, browser APIs, semantic HTML, CSS, JavaScript, and validation of existing web projects across any framework.
Evaluate, design, or improve SaaS moats: the structural barriers that protect profitability, retention, pricing power, distribution, and long-term defensibility. Use when the user asks whether a SaaS idea is defensible, profitable, hard to copy, has a real moat, can survive AI copycats, has switching costs, network effects, workflow lock-in, proprietary data, integrations, white-label/reseller defensibility, system-of-record potential, pricing power, NRR expansion, CAC payback, gross-margin risk, or needs a moat-focused product/business review.
Test websites and local web apps with the Playwright plugin in a fresh browser context, separate from the user's Chrome profile. Use for full website QA, mobile and desktop checks, route crawling, login-from-scratch testing, console and network error monitoring, screenshots, accessibility snapshots, forms/buttons/navigation checks, responsive layout review, and browser-visible error reports. Do not use the Chrome extension connector for this workflow.
Use when the user is working with a PocketBase backend they deployed on Dublyo (or plans to). Triggers on phrases like "I have PocketBase on Dublyo", "create a PocketBase collection", "PocketBase schema", "PocketBase API from my app", "set up auth in PocketBase", "PocketBase cron / webhook / scheduled job", "connect my Go/Node app to PocketBase". Covers (1) talking to a deployed PocketBase via its REST API to create/edit collections + fields + records, (2) the right architecture pattern when the user needs custom logic (cron, external API calls, queues) — do NOT teach them to write pb_hooks JS; instead guide them to deploy a separate Go/NestJS API container next to PocketBase, plus Redis for queues, (3) suggesting Dublyo open-source app templates from the 155-app catalog when the user's actual need is already solved by one (forum → Discourse, survey → HeyForm, wiki → BookStack, etc).
Full Spec Kit-inspired workflow for AI-assisted SaaS planning, implementation, review, and evolution. Use when the user wants to plan, spec, build, audit, or evolve a SaaS product, MVP, dashboard, CRUD app, workflow system, admin tool, PocketBase/Supabase-backed app, or Spec Kit artifact set. The skill enforces one A/B/C/D clarification question at a time, produces a detailed SaaS spec focused on product workflows before stack decisions, maps the result to constitution/spec/plan/tasks/checklists/analyze/converge artifacts, supports Spec Kit when installed or a manual equivalent when absent, and blocks coding until the user approves the spec.