agent-development Cursor ruleA

agent-development from vibeeval/vibecosystem is a Cursor rule: instructions the Cursor agent follows in that repo.

mdr add vibeeval/vibecosystem/.cursor/rules/agent-development.mdc@git:20260330.cd5da78

Pins git:20260330.cd5da78 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 14 of 14 checks passed

Kind

Cursor rule

Repository

vibeeval/vibecosystem

Path

.cursor/rules/agent-development.mdc

Versions recorded

1

Latest version

git:20260330.cd5da78, committed Mar 30, 2026

Size

1,195 bytes

Repository stars

539

License

MIT

Rules for creating and editing vibecosystem agent definitions.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Agent Development Rules

## Agent File Format

Each agent is a Markdown file with YAML frontmatter:

```yaml
---
name: agent-name
description: One-line description of what the agent does
tools: [Read, Write, Edit, Bash, Grep, Glob]
---
```

Followed by the agent's system prompt in Markdown.

## Naming Conventions
- Filename: `kebab-case.md` (e.g., `code-reviewer.md`)
- Name field: same as filename without extension
- Description: starts with a verb (e.g., "Reviews code for...")

## Agent Categories
- Core Dev: frontend-dev, backend-dev, kraken, spark, devops
- Review & QA: code-reviewer, security-reviewer, verifier, qa-engineer
- Domain Experts: graphql-expert, kubernetes-expert, ddd-expert
- Architecture: architect, planner, clean-arch-expert
- Testing: tdd-guide, e2e-runner, arbiter, mocksmith
- Analysis: scout, sleuth, data-analyst, profiler

## Quality Rules
- Every agent must have a clear, specific purpose
- Avoid overlapping responsibilities between agents
- Keep system prompts focused and actionable
- Include specific output format expectations

Read the whole file at its exact version.

How to install

mdr add vibeeval/vibecosystem/.cursor/rules/agent-development.mdc@sha256:bf72891afd960efd

[![mdr](https://markdownregistry.com/badge/art_zjwnb3aydfkez7xq.svg)](https://markdownregistry.com/a/art_zjwnb3aydfkez7xq)

Versions

The registry has recorded 1 version of this file, committed on Mar 30, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_zjwnb3aydfkez7xq
GET https://markdownregistry.com/api/v1/resolve?ref=vibeeval/vibecosystem/.cursor/rules/agent-development.mdc
GET https://markdownregistry.com/api/v1/blob/bf72891afd960efdf740e0b6926a918eecf71ea83d81385928f7b1f02c69db9d

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: Cursor rules vs AGENTS.md · which agent file does what.

More from vibeeval/vibecosystem

Every file in vibeeval/vibecosystem

Other files named agent-development

Browse by kind, by grade A, or by owner.