rule-laravel-shared-foundation-docs-sync-model-decision

Enforce canonical ownership rules for Laravel foundation documentation and domain vocabulary.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/belluga/delphi-ai --skill rule-laravel-shared-foundation-docs-sync-model-decision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule-laravel-shared-foundation-docs-sync-model-decision
Source: https://github.com/belluga/delphi-ai/tree/main/.cline/skills/rule-laravel-shared-foundation-docs-sync-model-decision
Command: npx skills add https://github.com/belluga/delphi-ai --skill rule-laravel-shared-foundation-docs-sync-model-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This rule ensures governance over foundation documentation by aligning route, screen, repository, and domain changes with canonical ownership sources, preventing drift between contracts and implementation.

Core Features & Use Cases

  • Loads and enforces canonical ownership by applying foundation_documentation policies as the single source of truth.
  • Synchronizes foundation_documentation/modules, foundation_documentation/screens, and domain vocabulary across touched surfaces to reflect new flows and UI behaviors.
  • Requires explicit policy updates before introducing new subscope or making contract changes, and ensures roadmap and module entries are updated accordingly.

Quick Start

Apply this rule whenever you touch routes, screens, repositories, or domain models to enforce governance updates against foundation documentation.

Frequently Asked Questions about rule-laravel-shared-foundation-docs-sync-model-decision

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

FAQPage Schema
How do I prevent documentation drift when modifying Laravel routes and domain models?

To prevent documentation drift in Laravel, enforce canonical ownership rules that synchronize foundation documentation, domain vocabulary, and module docs whenever you touch routes, screens, or repositories. This alignment ensures implementation matches contract surfaces.

What is canonical ownership in Laravel foundation documentation?

Canonical ownership in Laravel uses foundation documentation policies as the single source of truth for contract surfaces. It governs route, screen, repository, and domain changes to maintain alignment between contracts and implementation.

When do I need to update foundation documentation in a Laravel project?

You need to update Laravel foundation documentation whenever you touch routes, screens, repositories, or domain models. Explicit policy updates are required before introducing new subscopes or making contract changes to maintain alignment.

How do I enforce governance updates for Laravel contract changes?

Enforce Laravel contract governance by applying canonical ownership rules that require explicit policy updates before making changes. Synchronize foundation documentation, roadmap entries, and module docs to reflect new flows and UI behaviors.

Does this approach require policy updates before adding new subscopes in Laravel?

Yes, introducing a new subscope or making contract changes in Laravel requires explicit policy updates beforehand. This ensures foundation documentation and module entries reflect the new domain vocabulary and maintain alignment.

What is the best way to align Laravel domain vocabulary with module docs?

The best way to align Laravel domain vocabulary is to apply canonical ownership rules that synchronize foundation documentation across touched surfaces. This updates roadmap and module entries to reflect new flows and UI behaviors accurately.