LSRabbit6

Cursor Genesis — Development skill for Claude Code

Development community

Human–Agent Development Collaboration Mechanisms Leaf: reusable Rules / Skills / Validators / Packs for any coding harness (Claude Code, Codex, Cursor).

How to install Cursor Genesis

This entry records only its repository, not the path inside it, so there is no exact command to give. Open LSRabbit6/cursor-genesis and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Cursor Genesis does

Human–Agent Development Collaboration Mechanisms Leaf: reusable Rules / Skills / Validators / Packs for any coding harness (Claude Code, Codex, Cursor). Tool-independent; Cursor is the founding sample. First pack for outside users: delivery-data-app.

Alternatives in Development

Gemini Project Context For SaneBar — PRIMARY INSTRUCTION: This project uses a shared configuration with Claude 216 ★
Drift — Read the Genesis build phases document 90 ★
V1 Next — Bootstrap the next v1.0 (#150) item — red tests first, then sample + CI contract, then implementation 67 ★

README

cursor-genesis

**The Human–Agent Development Collaboration Mechanisms Leaf**

*"Stop writing code. Start engineering how your AI writes code."*

What is this?

`cursor-genesis` (CG) is the **Human–Agent Development Collaboration Mechanisms Leaf**: it studies and publishes human operation entry points, context assembly, Rule / Skill / Workflow selection, agent/model/tool invocation, deterministic guards, human gates, and capability composition, injection, distribution, and refinement.

CG is tool-independent. Cursor remains:

a founding sample whose history and design rationale are preserved;
a reference implementation from which Rules, multi-model entry points, explicit commands, Agent modes, and project-context mechanisms are generalized;
a non-core platform with no long-term compatibility promise and no role as CG's runtime dependency.

In short: **Cursor keeps its textbook role, not a constitutional role.**

Current stable assets are primarily Rules, Skills, Commands, Agent/Capability definitions, Patterns, Atoms + Packs, knowledge guides, and backflow mechanisms. `create-skill-workflow`, `create-subagent-workflow`, `create-command-workflow`, and `create-rule-workflow` now provide persisted gates/retries and machine Validators. Rule Contracts register into the project `AGENTS.md` author source; Cursor activation frontmatter remains an adapter concern. `audit-agent-assets` provides read-only, evidence-based review with Agent judgment, while `harvest-session` provides tool-neutral session-outcome triage; neither is represented as a machine Validator. Agent and Command Contracts stay tool-neutral while concrete model IDs, slash-command formats, and invocation syntax stay in host adapters. Additional Workflows, a generalized Validator framework, Hooks, and versioned runtime contracts remain planned.

CG mechanisms may be consumed during project initialization, but CG does not own concrete project-directory creation, personal workspace