Agent WranglersAgent Wranglers
Agent Wranglers is a team of senior engineers in Stockholm, Sweden. We review and fix apps built with AI, and we write the guides and playbooks we check them against.
AI-assisted development playbook
Rules for building software with AI coding agents. Set up the project, work in small steps, turn rules into checks and review every change before it ships.
Engineering playbook
Rules for building any software. Every rule is checked in code, every change is tested the same way, and every deploy can roll itself back.
Clean code and architecture playbook
Rules for code that people and AI agents can read, change and trust. Clean names, small functions, typed data, SOLID design and a numbered review.
Testing playbook
Rules for tests that catch bugs, run fast and never cry wolf. Strategy, unit, integration, browser, data, flaky tests and test quality.
Website optimization playbook
Rules for fast, findable, secure and accessible websites that AI agents can use too. Each has a level, how to do it and how to check it.
API design playbook
Rules for HTTP APIs that people and AI agents can learn fast and trust. Clear resources, honest errors, safe retries and contracts that never surprise.
Data and databases playbook
Rules for data you can trust. Constraints in the database, fast queries, safe transactions and migrations, tested backups and personal data handled with care.
Email playbook
Rules for email that arrives, reads well and stays safe. Authentication, deliverability, unsubscribe, rendering, privacy and security, each with a check.
Operations and observability playbook
Rules for running software people depend on. Service levels, logs, metrics, traces, alerts, incidents, capacity and recovery, each with a check.
Adversarial testing playbook
Instructions for an AI agent that attacks your own software with permission. It covers the common security holes, how to test each one and how to close it.
Payments and billing playbook
Rules for taking money in a web app or SaaS through a payment provider. Checkout, orders, webhooks, subscriptions, refunds, disputes, tax and invoices.
Infrastructure and environments playbook
Rules for the infrastructure a service runs on. Infrastructure as code, environments, access, secrets, networks, policy, servers and cost, each with a check.
AI features playbook
Rules for product features built on language models. Prompts, structured output, retrieval, evals, guardrails, cost, privacy and agents, each with a check.
Accounts and identity playbook
Rules for user accounts in web apps and SaaS. Sign-up, passkeys, recovery, sessions, roles, teams, staff access, deletion and business sign-on.
Compliance and governance playbook
Rules for meeting and proving the duties a software company has under privacy, AI, security and accessibility law, written as data and checks.
Web app interface playbook
Rules for the screens of web apps, such as dashboards and admin tools. States, forms, data, lists, feedback, permissions, errors and tests.
Notifications playbook
Rules for notifications people want. Channel choice, preferences, quiet hours, push, SMS and an in-app inbox, each with a check you can run.
Is Lovable secure?
Is your Lovable app safe? What Lovable takes care of, the common gaps in Lovable and Supabase apps, a quick self-check, and when to get an Expert to look.
Vibe coding security checklist
A plain-language security checklist for apps built with Lovable, Bolt, Replit or Cursor. It covers keys, database rules, logins, payments and data.
App not working? Start here
Your AI-built app works in the preview but breaks once live? Common causes behind Lovable, Bolt and Replit apps not working, and how to escape the fix loop.
Technical due diligence checklist for AI-built code
A technical due diligence checklist for investors buying AI-built products. It covers code ownership, security, hidden costs, the team and AI use.