error
v2.0.3Error skills — the unified error envelope + reason-code vocabulary (format) and the framework-agnostic client-side error-handling architecture (architecture).
By Roman Maslennikov1 GitHub starsUpdated 2 weeks ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Oct 6, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install error for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install error@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/aquivalabs/BladeForgeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/error/.
Plugin files
├── .claude-plugin/plugin.json├── skills/architecture/SKILL.md└── skills/format/SKILL.md
Included Skills2
Use when defining, adopting, or reviewing a client/UI app's WHOLE error-handling architecture — where every failure surfaces and how adherence is checked — across any framework (React, Vue, Angular, Svelte). Triggers on "design our app-wide error handling", "is our error handling consistent / does this codebase follow one pattern", "audit how errors are shown", "we map error codes to UX in a dozen places", "one place to decide retry vs redirect vs toast", or reviewing a diff for error-surfacing consistency. Foreground: the single code→UX policy table that classifies every error once. NOT for wrapping one component in a boundary or styling one error tile (that is your framework's component/primitive skill), and NOT for the wire envelope or reason-code vocabulary (that is error:format).
Use when adding or handling any error path on any layer — throwing from a service/route/controller, mapping an upstream failure, or reading an error on the client (backend or frontend). Do NOT use to design the whole app's error-handling architecture — the single code-to-UX policy table (error:architecture) — or to wrap one component in a boundary or style one error tile (your framework's component skill); this skill owns the wire envelope and the reason vocabulary.
Plugin manifests1
{
"name": "error",
"description": "Error skills — the unified error envelope + reason-code vocabulary (format) and the framework-agnostic client-side error-handling architecture (architecture).",
"version": "2.0.3",
"keywords": [
"error",
"error-handling",
"error-format",
"error-architecture",
"envelope",
"resilience"
],
"author": {
"name": "Roman Maslennikov",
"email": "[email protected]"
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[error on Agent Plugins Marketplace](https://pluginsmp.com/plugins/error)