swarm-error-handling-agent

Map Zod, Postgres, HTTP, and custom errors to Swedish messages.

209|46|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/erp-mafia/gnubok --skill swarm-error-handling-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm-error-handling-agent
Source: https://github.com/erp-mafia/gnubok/tree/main/.claude/skills/swarm-error-handling-agent
Command: npx skills add https://github.com/erp-mafia/gnubok --skill swarm-error-handling-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You are a read-only audit agent focused on error handling and user-facing messages in Swedish. Your job is to ensure every user-facing error is clear, actionable, and localized, preventing English or technical jargon from leaking through.

Core Features & Use Cases

  • Maps every error surfaced by the UI to Swedish messages via the centralized error-to-Swedish-message mapper, ensuring consistency across Zod, Postgres, HTTP, and custom app errors.
  • Audits API routes, server modules, and client components to detect missing translations, unhandled errors, and generic messages like “Something went wrong,” and suggests concrete Swedish replacements.
  • Supports real-world scenarios such as validation failures, authorization errors, timeouts, and unexpected server faults by steering them through the Swedish error mapper.

Quick Start

Scan the project to verify that all user-facing errors are translated into Swedish through the error mapper.

Frequently Asked Questions about swarm-error-handling-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure user-facing error messages are translated to Swedish in a full-stack app?

Swedish localization for error messages requires routing Zod, Postgres, HTTP, and custom application errors through a centralized error-to-Swedish mapper to prevent English jargon and stack traces from surfacing in the UI.

What is the best way to audit a codebase for unlocalized error handling?

Auditing for unlocalized error handling involves scanning server modules and client components to detect generic messages like 'Something went wrong' and unhandled exceptions, then replacing them with concrete, actionable Swedish feedback.

How do I prevent stack traces from leaking to the client UI during server faults?

Preventing stack trace leaks involves steering unexpected server faults and timeouts through a localized error mapper that intercepts technical exceptions and outputs clear Swedish responses instead of raw system errors.

Can I use a Swedish error mapper to handle Zod validation failures and Postgres database errors?

Yes, a centralized Swedish error mapper can intercept and translate Zod validation failures and Postgres database errors, ensuring consistent localized feedback across form validation and server-side data processing layers.

What are the limitations of using a read-only audit agent for error message localization?

A read-only audit agent for error message localization identifies missing translations and suggests concrete Swedish replacements, but it requires manual implementation to apply the fixes across the API routes and client components.