Service pages
500 with Incident Code
A 500 page in the "we are already on it" spirit: a hazard tape of CSS stripes, an incident code for support in a dashed frame, a refresh button and a link to the service status.
React + Tailwind, shadcn-compatible: press “Copy for AI” and your Cursor or Claude Code agent installs it with the shadcn CLI.
What you can change
- title and description — the heading and the explanation in your own words
- incident — the real incident code from your monitoring
- statusHref and statusLabel — the address and label of the status page
Built from
The install command brings these components too. The block only passes them props: their palette and behaviour stay their own.
A link for your AI agent: preview, code and instructions.
Preview
Use it with AI
- 1. Copy the link.
- 2. Write to your agent in your own words and drop the link into the sentence.
- 3. The agent opens the link and installs the component from the registry.
put this on the home page as the hero:
https://vibeui.club/c/errorpage-002?lang=en&theme=dark
Not sure where to paste it? Step-by-step guide
Show the full instructions
What the link says, spelled out. Use it when your agent cannot open links — paste this text instead.
Loading…
How to use
<Errorpage002
incident="INC-0906-2417"
statusHref="/status"
/>A sample call. The agent installs the component itself from the registry via the “Copy for AI” link.
Settings
- Heading
title· default: It broke on our side- Incident code
incident· default: INC-0906-2417- Accent
accent· default: theme colour- Background
background· default: theme colour
More in Service pages
FAQ
- How do I add 500 with Incident Code with Cursor or Claude Code?
- Press “Copy for AI” on this page and paste it into your agent's chat. The instruction contains the shadcn CLI install command, the dependencies and what to keep, so the agent installs this exact component instead of recreating a lookalike.
- What does 500 with Incident Code depend on?
- No npm packages beyond React and Tailwind CSS. It also installs catalog components: button-016, heading-001.
- What can I change in 500 with Incident Code?
- Adapt: title and description — the heading and the explanation in your own words; incident — the real incident code from your monitoring; statusHref and statusLabel — the address and label of the status page. Keep as installed: the button-016, heading-001 imports from @/components/vibeui/ — do not inline their code into the block or swap in your own; the parts receive props only; the local --vibeui-errorpage-002-* palette — do not swap it for your theme tokens (bg-card, border-border and the like); the incident code in plain sight: with it a support request is resolved in minutes, without it — in a back-and-forth of "what were you doing".
- Is 500 with Incident Code free?
- Yes. The preview is open without an account; with a free account you can copy up to 20 components a month.
For developers
npx shadcn@latest add https://vibeui.club/r/pro/errorpage-002.jsonThis command needs a signed link: sign in and open “Component source” below — it issues a working link valid for 30 minutes. All install options
Technical notes
A composite block: imports button-016, heading-001 from @/components/vibeui/ — the install command brings them along with the block. The block owns the layout and its own text, passes the parts props only and leaves their --vibeui-<name>-* palettes alone. The block is self-contained: one file, no npm dependencies, its palette in local --vibeui-errorpage-002-* variables. A server component with no JS: the refresh button is a link with an empty href that points at the current address, and after a 500 a repeated request usually goes through. The hazard tape is drawn with repeating-linear-gradient — no images. The incident code is marked up as a dl and carries user-select:all: one tap selects it whole for pasting into a ticket.
Tags
- 500
- error
- incident
- status
- server
- composite
Component source
The same file your agent installs. Here in case you would rather copy it by hand.
Loading…