rye-pattern-library

Create reusable Rye data modeling pattern contracts with JSON Schema definitions.

2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/BLTGV/project-rye --skill rye-pattern-library
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rye-pattern-library
Source: https://github.com/BLTGV/project-rye/tree/main/skills/rye-pattern-library
Command: npx skills add https://github.com/BLTGV/project-rye --skill rye-pattern-library

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill eliminates the need to reinvent Rye data modeling conventions for every domain or customer skill, enabling teams to create consistent, reusable pattern contracts for nodes, edges, assertions, events, artifacts, and associated JSON Schemas without modifying Rye core database tables.

Core Features & Use Cases

  • Pre-built Pattern Selection: Choose from a library of common Rye modeling patterns (such as source-backed entities, temporal relationships, and current state assertions) matched to specific use cases like tracking state changes or recording tabular data intake.
  • Contract Drafting Guidance: Use provided templates and schema authoring rules to draft formal pattern contracts and JSON Schema definitions that align with Rye's core data model constraints.
  • Use Case: For a team building a customer relationship management (CRM) skill for Rye, use this skill to define a standard pattern for tracking customer contact information changes, including assertion supersession rules and event contracts, to ensure consistency across all Rye implementations.

Quick Start

Use the rye-pattern-library skill to draft a reusable pattern contract for tracking employee role assignment changes in your Rye instance, including edge, assertion, and event definitions.

Frequently Asked Questions about rye-pattern-library

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define reusable Rye data modeling patterns for nodes and edges without modifying core database tables?

Rye pattern contracts provide standard modeling conventions for nodes, edges, and events without modifying core database tables. They use JSON Schema definitions and assertion rules to ensure domain-agnostic consistency across customer skills.

How do I draft a JSON Schema contract for tracking state changes and event participant roles in Rye?

Draft a JSON Schema contract for Rye state changes by applying assertion supersession logic and defining event participant roles. Use provided templates to structure edge and assertion definitions for consistent temporal relationship tracking.

What is the best way to prevent customer-specific vocabulary from leaking into generic Rye skill definitions?

The best way to prevent vocabulary leakage is using portable, convention-based Rye pattern definitions. By defining domain-agnostic assertion key rules and artifact deduplication strategies, generic skills remain separate from customer-specific terms.

Can I use assertion supersession logic and artifact deduplication strategies in a CRM skill built on Rye?

Yes, you can apply assertion supersession logic and artifact deduplication strategies in a Rye CRM skill. The pattern library provides standard contracts for tracking contact information changes while maintaining data model security.

When do I need to define assertion key rules and temporal relationships for Rye data modeling?

You need to define assertion key rules and temporal relationships when tracking state changes or recording tabular data intake in Rye. These conventions ensure consistent current state assertions and source-backed entity modeling across implementations.