yieldomega-guardrails

Guides editors to apply Yieldomega repository guardrails for compliant code and docs.

1|Updated Mar 25, 2026

Search Tags:#repository #coding-standards #guardrails #review-guidelines #agent-workflow #AGPL-3.0

Ready to run

npx skills add https://github.com/PlasticDigits/yieldomega --skill yieldomega-guardrails

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: yieldomega-guardrails
Source: https://github.com/PlasticDigits/yieldomega/tree/main/.cursor/skills/yieldomega-guardrails
Command: npx skills add https://github.com/PlasticDigits/yieldomega --skill yieldomega-guardrails

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guardrails skill ensures consistent application of Yieldomega repository standards when editing contracts, indexer, frontend, or docs, preventing license drift, aligning with phase guidance, and preserving on-chain logic integrity.

Core Features & Use Cases

Guides editors to consult phase documentation (docs/agent-phases.md) before making changes.
Enforces AGPL-3.0 licensing expectations and preserves header integrity across edits.
Aligns testing and validation with docs/testing/strategy.md to maintain repository quality.
Provides reference to TimeCurve and related docs (e.g., docs/frontend/timecurve-views.md) to keep UX and state alignment consistent during edits.

Quick Start

Start by reading docs/agent-phases.md and the matching phase guide, then follow AGPL-3.0 licensing guidance and timecurve guardrails before editing any code or docs.

Frequently Asked Questions about yieldomega-guardrails

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

FAQPage Schema

How do I enforce coding standards for AI agent edits in a repository?▼

Repository guardrails for agent edits prevent license drift by enforcing AGPL-3.0 header integrity and aligning code changes with phase guidance and testing strategies. This maintains on-chain logic integrity across contracts, indexer, frontend, and docs.

How do I maintain AGPL-3.0 license headers when自动化 editing code?▼

Maintain AGPL-3.0 license compliance during automated edits by applying repository guardrails that enforce header preservation. This prevents license drift and ensures all contributions remain compliant across contracts and frontend code.

What is the process for aligning agent workflow edits with repository phase guidance?▼

Aligning agent workflow edits with phase guidance requires reading docs/agent-phases.md and the matching phase guide before making changes. This ensures edits to contracts, indexer, or frontend maintain state alignment and repository quality.

Does this repository guardrails skill work with frontend TimeCurve views?▼

Yes, the guardrails skill works with frontend TimeCurve views by providing reference to docs/frontend/timecurve-views.md. This keeps UX and state alignment consistent during edits to the indexer or frontend components.

How do I validate testing strategy compliance for repository edits?▼

Validate testing strategy compliance by aligning all changes with docs/testing/strategy.md. This ensures repository quality is maintained and that code edits load correctly into agent workflows without breaking on-chain logic.