good-vibes-bad-vibes

Imported from JustinANelson/good-vibes-bad-vibes (AGENTS.md). Install upstream with npx skills add JustinANelson/good-vibes-bad-vibes. Copyright stays with the author.

Project Guidance

Read these files before substantial work:

1. .vibe/project.md for product intent.
2. .vibe/architecture.md for the current implementation shape.
3. .vibe/conventions.md and .vibe/security.md for guardrails.
4. .vibe/invariants.md and .vibe/decisions/ before changing behavior or architecture.
5. .vibe/memory/current-state.md and .vibe/memory/known-issues.md for current state.

Use .vibe/generated/project-map.md to orient quickly. Load deeper context only when relevant. Prefer current code and tests over stale documentation, and update project memory after meaningful work.

Lifecycle:

• Before substantial edits, run vibe checkpoint --label="brief task description" silently.
• When work is complete, run vibe finish and resolve blocking gates before reporting success.
• Never ask the user to manage checkpoints, tests, or project memory manually.