New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vibe Production Mindset

by ash1794 in ash1794/vibe-engineering

Checks production-bound code for observability, error handling at system boundaries, input validation, graceful degradation, and resource management, scaled to the project's real stakes.

MITAuto-check passedDevOps & Cloud

Install Vibe Production Mindset

skills CLI
$ npx skills add ash1794/vibe-engineering --skill vibe-production-mindset -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ash1794/vibe-engineering vibe-production-mindset --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-production-mindset .claude/skills/vibe-production-mindset && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vibe-production-mindset
GitHub stars
163
Token cost
~1.1k tokens
SKILL.md length
525 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Checks production-bound code for observability, error handling at system boundaries, input validation, graceful degradation, and resource management, scaled to the project's real stakes.

  • Works in 6 steps: Observability → Error Handling at System Boundaries → Input Validation → …
  • Tasks that involve Error handling
  • SKILL.md covers When to Use This Skill, When NOT to Use This Skill, Calibrate First and The Checklist, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vibe Production Mindset is an agent skill from ash1794/vibe-engineering. Checks production-bound code for observability, error handling at system boundaries, input validation, graceful degradation, and resource management, scaled to the project's real stakes. Use before declaring a production feature done.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Error handling and Observability. The repository describes itself as: 33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development. Born from… The licence is MIT.

When your agent uses it

  • Tasks that involve Error handling
  • Tasks that involve Observability

Example prompts

  • “Use the vibe-production-mindset skill to check production-bound code for observability, error handling at system boundaries, input validation…”
  • “/vibe-production-mindset”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Observability
  2. Error Handling at System Boundaries
  3. Input Validation
  4. Graceful Degradation (only where dependencies justify it)
  5. Resource Management
  6. Performance Budgets (when performance is a requirement)

What it can do on your machine

Read from SKILL.md and the folder at commit 8f1d71b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vibe Production Mindset loads about 1.1k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 525 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ash1794/vibe-engineering at commit 8f1d71b, republished under its MIT licence (© ash1794). 525 words, ~1,055 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-production-mindset/SKILL.md (or your agent's skills folder).
name
vibe-production-mindset
description
Checks production-bound code for observability, error handling at system boundaries, input validation, graceful degradation, and resource management, scaled to the project's real stakes. Use before declaring a production feature done.
user-invocable
true

vibe-production-mindset

The gap between "works on my machine" and "works in production" is where incidents live. The goal is to avoid under-engineering the critical paths, not to add every hardening pattern to every feature. Pair it with vibe-scope-guard.

When to Use This Skill

  • Implementing API endpoints, data processing, or user-facing features that will run in production
  • Before declaring a production feature "done"
  • When the user cares about production quality

When NOT to Use This Skill

  • Prototypes or spikes explicitly marked as throwaway
  • Internal scripts that run once
  • Test code (different quality criteria)
  • When the user says "just get it working"

Calibrate First

Before running the checklist, establish the stakes and the conventions:

  • What already exists? Use the project's existing logger, metrics, retry, and validation libraries. Don't introduce a second one.
  • What's the real scale and blast radius? An internal admin tool and a public payments API need different answers.
  • Only flag an item if it applies at this project's scale. A missing circuit breaker is not a gap in a service with one dependency and ten users.

The Checklist

1. Observability
  • Logs at key decision points use the project's structured logger
  • Request/correlation IDs are propagated, if the project already uses them
  • Metrics for key operations, if the project has a metrics pipeline
2. Error Handling at System Boundaries
  • External calls (HTTP, DB, queues) have timeouts
  • Retries with backoff where the operation is idempotent
  • Specific handling for expected failures (not found, permission denied, conflict)
  • Errors carry enough context to debug, and no secrets
3. Input Validation
  • External input is validated before processing
  • Size limits on strings, arrays, and uploads
  • Parameterized queries and output encoding (injection, XSS)
  • Authentication before authorization, and authorization on every access path
4. Graceful Degradation (only where dependencies justify it)
  • Defined behavior when a dependency is down
  • Graceful shutdown (drain in-flight work)
  • Health check, if the deploy target uses one
Show full SKILL.md (213 more words)Show less
5. Resource Management
  • Connections, files, and handles are closed or returned to the pool
  • Goroutines, threads, and tasks have bounded lifetimes
  • No unbounded in-memory growth (caches, queues, buffers)
6. Performance Budgets (when performance is a requirement)
  • Budgets are targets from the spec (published thresholds, competitor medians), not today's measurement plus a margin
  • Named profiles: a constrained one for CI (slow link, throttled CPU) and a typical target device
  • Per-route or per-endpoint budgets: payload sizes (JS, CSS, HTML, fonts, total) and timings (e.g., LCP, CLS, TBT, p95 latency)
  • Overrides carry a written reason; raising a default requires a spec change
  • Enforced in CI; a failing budget is fixed in code, never raised to pass
  • Performance changes report "no budgets loosened", and call out mechanical key renames so they aren't mistaken for loosening

Steps

  1. Calibrate (above)
  2. Read the implementation
  3. Run the checklist, skipping items that don't apply
  4. Flag gaps with file:line and a specific fix that uses existing project conventions

Output Format

Production Readiness: [Feature Name]

Stakes: [e.g., public API, ~10k req/min] · Overall: READY / NEEDS_WORK / NOT_READY

CategoryStatusGaps
Observability✓/◐/✗/n/a[count]
Error Handling✓/◐/✗/n/a[count]
Input Validation✓/◐/✗/n/a[count]
Graceful Degradation✓/◐/✗/n/a[count]
Resource Management✓/◐/✗/n/a[count]
Performance Budgets✓/◐/✗/n/a[count]
Critical Gaps
  1. [gap with file:line and the fix]

© ash1794, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/vibe-engineering/skills/vibe-production-mindset of ash1794/vibe-engineering.

Open the folder on GitHubat commit 8f1d71b

Compare with similar skills

Vibe Production Mindset next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vibe Production Mindset compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vibe Production Mindset this skillash1794/vibe-engineering163—~1.1kAutomated safety check: PassMIT
Logging Observabilitygetsentry/toolkit920—~2.6kAutomated safety check: PassCustom licence
Crash Instrumentationnexus-labs-automation/mobile-observability116—~744Automated safety check: PassMIT
Golang Error Handlingunxed/f42433 repos~1.8kAutomated safety check: PassMIT
Error HandlerEliasOulkadi/shokunin114—~3.6kAutomated safety check: NotesMIT
Release Itwondelai/skills2.4k—~4kAutomated safety check: PassMIT

Similar skills

  • Logging Observability

    getsentry/toolkit

    Official

    Review code for correct logging and error handling patterns.

    920 GitHub stars~2.6k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Crash Instrumentation

    nexus-labs-automation/mobile-observability

    Set up crash instrumentation with actionable context. An agent skill from nexus-labs-automation/mobile-observability.

    116 GitHub stars~744 tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Golang Error Handling

    unxed/f4

    Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog…

    243 GitHub starsUsed in 3 repos~1.8k tokens
    DevOps & CloudAuto-check passed

  • Error Handler

    EliasOulkadi/shokunin

    Design error handling, structured logging, and observability with OpenTelemetry (traces, metrics, logs), error classification, recovery patterns (retry with jitter, circuit breaker, bulkhead…

    114 GitHub stars~3.6k tokensUpdated 5 days ago
    DevOps & CloudAuto-check: notes

  • Release It

    wondelai/skills

    Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic.

    2.4k GitHub stars~4k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Rust Error Observability

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, debugging, or reviewing Rust service error handling and observability, especially when separating domain errors from HTTP responses, adding…

    1.3k GitHub stars~969 tokensUpdated today
    DevOps & CloudAuto-check passed

More from ash1794/vibe-engineering

All 33 skills in this repo

  • Vibe Concurrent Test Safety

    ash1794/vibe-engineering

    Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.

    163 GitHub stars~665 tokensUpdated 3 days ago
    Auto-check passed

  • Vibe Fuzz Parser Inputs

    ash1794/vibe-engineering

    Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).

    163 GitHub stars~722 tokensUpdated 3 days ago
    Auto-check passed

  • Vibe Golden File Testing

    ash1794/vibe-engineering

    Implements snapshot/golden file tests with temporal normalization so tests don't break daily.

    163 GitHub stars~669 tokensUpdated 3 days ago
    Auto-check passed

  • Vibe Parallel Task Decomposition

    ash1794/vibe-engineering

    Analyzes large tasks for independent subtasks that can be safely parallelized.

    163 GitHub stars~717 tokensUpdated 3 days ago
    Auto-check passed

  • Vibe Slop Filter

    ash1794/vibe-engineering

    Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).

    163 GitHub stars~2.3k tokensUpdated 3 days ago
    Auto-check passed

  • Vibe Spec Sync

    ash1794/vibe-engineering

    Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.

    163 GitHub stars~2.2k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Vibe Production Mindset

What does Vibe Production Mindset do?

Checks production-bound code for observability, error handling at system boundaries, input validation, graceful degradation, and resource management, scaled to the project's real stakes. Vibe Production Mindset is an agent skill from ash1794/vibe-engineering. Checks production-bound code for observability, error handling at system boundaries, input validation, graceful degradation, and resource management, scaled to the project's real stakes.

When should I use Vibe Production Mindset?

Vibe Production Mindset fits situations like: tasks that involve Error handling; tasks that involve Observability.

How do I install Vibe Production Mindset in Claude Code?

Run `npx skills add ash1794/vibe-engineering --skill vibe-production-mindset -a claude-code`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-production-mindset in ash1794/vibe-engineering) into .claude/skills/vibe-production-mindset in your project. Claude Code loads it when a task matches its description.

How do I install Vibe Production Mindset in Codex?

Run `npx skills add ash1794/vibe-engineering --skill vibe-production-mindset -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-production-mindset in ash1794/vibe-engineering) into .agents/skills/vibe-production-mindset in your project. Codex loads it when a task matches its description.

Can I use Vibe Production Mindset in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ash1794/vibe-engineering --skill vibe-production-mindset -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-production-mindset, .gemini/skills/vibe-production-mindset, .github/skills/vibe-production-mindset and .opencode/skills/vibe-production-mindset in your project.

What does Vibe Production Mindset need to run?

SKILL.md names no scripts, command-line tools or credentials: Vibe Production Mindset is instructions for the agent only.

Does Vibe Production Mindset access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vibe Production Mindset safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vibe Production Mindset use?

Vibe Production Mindset is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vibe Production Mindset use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vibe Production Mindset?

Skills that share tags, products or a category with Vibe Production Mindset: Logging Observability (getsentry/toolkit, 920 stars), Crash Instrumentation (nexus-labs-automation/mobile-observability, 116 stars), Golang Error Handling (unxed/f4, 243 stars) and Error Handler (EliasOulkadi/shokunin, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Production Mindset?

ash1794 (a GitHub user) maintains it in ash1794/vibe-engineering, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.

Source: ash1794/vibe-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.