@wandb/vibes
BCursor Rules for Vibes Project
Install
agr install @wandb/vibes --target cursorWrites 1 file into .cursor/rules/, pinned to git-8203e014.
- .cursorrules
Document
Cursor Rules for Vibes Project
Project Context
This is a demonstration repository showing AI coding assistant capabilities using dev containers. The project includes:
- Claude Code CLI (@anthropic-ai/claude-code)
- Gemini CLI (@google/gemini-cli)
- OpenAI Codex (@openai/codex)
- Marp for slide generation
Coding Standards
General
- Use TypeScript when possible
- Prefer functional programming patterns
- Write clear, self-documenting code
- Include proper error handling
File Structure
- Keep related files in logical directories
- Use descriptive filenames
- Create README files for complex directories
Documentation
- Document all public APIs
- Include usage examples
- Keep documentation up to date with code changes
- Use JSDoc for TypeScript/JavaScript functions
Dependencies
- Prefer well-maintained packages
- Keep dependencies minimal and focused
- Use exact versions in package.json for reproducibility
AI Assistant Guidelines
Prompting Best Practices
- Provide clear context about the project structure
- Specify which CLI tool you're using (Claude, Gemini, or Codex)
- Reference the appropriate prompting guide (CLAUDE.md, GEMINI.md, AGENTS.md)
Code Generation
- Generate code that follows the project's existing patterns
- Include appropriate TypeScript types
- Add error handling and edge case considerations
- Provide explanations for complex logic
Testing
- Include tests for new functionality
- Follow existing test patterns in the project
- Test edge cases and error conditions
Dev Container Specifics
- Use the configured environment variables
- Leverage the pre-installed tools and CLIs
- Follow the setup instructions in README.md
Commands
pnpm slides- Generate presentation slides using Marpclaude- Start Claude Code CLIgemini- Start Gemini CLIcodex- Start OpenAI Codex CLI
Notes
- This project focuses on demonstration and education
- Prioritize clarity and learning over optimization
- Include examples that showcase AI assistant capabilities
- Keep the codebase accessible to developers of all skill levels
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- warnFreshnessstale (>1y)
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-8203e01479cf2026-08-06