Skip to content
cccskills
FreePublished on GitHub

vibeguard

Lightweight anti-hallucination workflow for task kickoff, review prioritization, and regression retrospectives. Use when the user asks for guardrails, task contracts, risk scoring, or review templates.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (4)

  • SKILL.md2.8 KB
  • references/review-template.md1.1 KB
  • references/scoring-matrix.md1.9 KB
  • references/task-contract.yaml1.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

VibeGuard

Lightweight VibeGuard for everyday use inside Spellbook.

This skill helps with three moments where AI-assisted work usually drifts:

  • before implementation starts
  • while review findings are being prioritized
  • after regressions or avoidable mistakes happen

What This Skill Includes

  • A task contract checklist for scoping work before coding
  • A scoring matrix for prioritizing findings with evidence
  • A weekly review template for regression and guardrail retrospectives

Hard Boundaries

This skill is intentionally lightweight.

It does:

  • guide task kickoff
  • structure review output
  • make risk tradeoffs explicit

It does not:

  • install hooks
  • run guard scripts automatically
  • patch global Claude or Codex configuration
  • claim that full VibeGuard enforcement is active

If the user asks for automated interception, repo-level rules, or environment setup, escalate to the full VibeGuard repository and tooling.

When To Use It

Trigger this skill when the user asks for:

  • anti-hallucination guardrails
  • task startup checks
  • review scoring or triage
  • regression prevention
  • retrospective templates
  • "vibeguard" by name

Workflow

1. Start With The Task Contract

Open references/task-contract.yaml and confirm:

  • goal
  • source of truth
  • acceptance criteria
  • scope

Do not move into implementation until these are concrete.

2. Score Findings Before Acting

Open references/scoring-matrix.md and score each finding on:

  • impact
  • effort
  • risk
  • confidence

Use the score to separate urgent fixes from weak guesses.

3. Pick The Right Delivery Mode

  • 1-2 files: implement directly once the contract is clear
  • 3-5 files: write a short spec or step plan first
  • 6+ files: produce a full design/spec and staged execution plan

4. Review The Failure, Not Just The Symptom

If something regressed, identify which defense failed:

  • scope control
  • source-of-truth validation
  • verification depth
  • review prioritization
  • missing guardrail

Then capture the follow-up in references/review-template.md.

Expected Outputs

Depending on the request, produce one of these:

  • a filled task contract
  • a scored findings table with priorities
  • a short regression review or weekly retrospective

Reference Files

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Audit and organize AI coding-agent instructions, including AGENTS.md, CLAUDE.md, skills, and agent definitions. Use when the user asks to diagnose conflicting instructions, excessive approval pauses, broad skill triggers, duplicate guidance, or broken instruction references, or to clean up that instruction set. Ordinary code review, Markdown editing, or application debugging alone does not trigger this workflow. Inspection stays read-only; apply changes when authorized.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 23, 2026

Generate or update repository-specific AGENTS.md instruction files from real repo evidence. Use when asked to create, design, scaffold, split, or improve root or scoped AGENTS.md files for Codex/Claude/agent workflows, especially when a repo needs directory-specific rules, validation commands, generated-file boundaries, or a short agent onboarding router.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 23, 2026

REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 23, 2026

Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 23, 2026

End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 23, 2026

Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before coding.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 23, 2026

See all skills by majiayu000

Report a problem with this skill