gidila91

billing-ai-assisted-work

How to track and bill time honestly when AI agents do part of the work — the concurrency rule for parallel timers, what happens to the hour when you are waiting rather than typing, and the failure modes that silently over-bill or lose hours. Use when designing or auditing time tracking for an agency, freelancer or studio that runs AI coding agents; when a client asks what they are actually paying for; when reconciling logged hours against a calendar or an invoice; or when building the timer, hours-bank or invoicing part of a practice-management app.

hebrew-copy

עברית תקינה — the Hebrew writing standard for Gideon's work. Use whenever writing, reviewing or generating Hebrew text: UI copy, microcopy, marketing pages, emails, error messages, legal pages, AI generation prompts that output Hebrew, and replies to Gideon himself. Also use when reviewing Hebrew produced by an AI builder (Lovable, Base44, v0) or by a language model, since machine-generated Hebrew fails these rules predictably. Covers כתיב מלא per the Academy, gender and number agreement, the number-gender inversion, address form, סמיכות, punctuation, mixed-script direction, and a translationese blacklist.

lovable-accessibility

Legal + engineering playbook for making Lovable.dev apps accessible under Israeli law (ת"י 5568 / תקנה 35) and the EU European Accessibility Act (EN 301 549), including Hebrew/RTL correctness, the shadcn-Radix defect list, a self-built accessibility toolbar spec, and the הצהרת נגישות page. Trigger whenever the user mentions נגישות, accessibility, WCAG, תקן 5568, תקנה 35, EAA, EN 301 549, הצהרת נגישות, accessibility statement, סרגל/תוסף נגישות, accessibility widget/overlay, screen reader, keyboard navigation, color contrast, or RTL correctness in a Lovable project.

lovable-credits

Spending Lovable credits deliberately instead of burning them — which actions cost and which are free, how to prepare a request so the agent gets it right the first time, when to read the code yourself instead of asking, and the habits that turn a credit balance into weeks instead of days. Use before sending anything to Lovable's AI agent, when a credit balance is dropping faster than the work justifies, when deciding whether a fix is worth an agent round-trip, or when planning work across a client's workspace and your own.

lovable-rigor

Disciplined workflow for directing Lovable's AI agent on any project (via the Lovable + Supabase MCP connectors) — investigate before fixing, independently re-verify every claimed fix, catch the preview/production publish gap, and test safely against real-shaped data. Use whenever sending instructions to a Lovable project's AI agent or reviewing its work.

lovable-security-posture

Security posture and tooling playbook for any Lovable project — threat-modeling framing, when to escalate beyond AI-only security work, how to use Lovable's built-in scanner/Security Memory/Aikido pentest efficiently, and the RLS-vs-backend defense-in-depth model post-TanStack. Distinct from lovable-rigor (which covers HOW to direct Lovable's agent on a fix); this covers WHAT security posture to hold and WHEN to reach for which tool. Use when starting security work on a new Lovable project, deciding whether a finding needs deeper attention, or advising a non-technical founder on security tradeoffs.

lovable-seo-aeo

Specialized rules, prompt engineering templates, and technical standards for executing SEO (Search Engine Optimization) and AEO (Answer Engine Optimization) inside Lovable.dev applications (TanStack Start, SSR, Supabase). Trigger this skill whenever the user mentions SEO, AEO, answer engine optimization, schema markup, metadata, robots.txt, llms.txt, dynamic sitemaps, or Google/AI search optimization in Lovable.

lovable-stripe-billing

Building real payments into a Lovable app with Stripe — embedded checkout, hour packages and credit banks, subscriptions and retainers, per-customer discount codes, VAT and tax IDs, guest checkout, and the webhook plus reconciliation pattern that stops paid money from vanishing. Use when adding or auditing payments, checkout, coupons, subscriptions or invoicing in a Lovable or TanStack Start app backed by Supabase, or when a payment succeeded but the customer did not get what they paid for.

lovable-vibe-code-audit

Checklist and workflow for spotting the visual/copy/structural tells that a Lovable-built site still looks "vibe-coded" — generic, unpolished, and obviously AI-generated — rather than like custom-built client work. Use before showing a Lovable project to a client, before a real launch/publish, or whenever asked to review a site for polish/professionalism.