creatyss-doc-routing

Route documentation sources and arbitrate priorities before proposing Creatyss changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Deadpool042/Creatyss --skill creatyss-doc-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creatyss-doc-routing
Source: https://github.com/Deadpool042/Creatyss/tree/main/.agents/skills/creatyss-doc-routing
Command: npx skills add https://github.com/Deadpool042/Creatyss --skill creatyss-doc-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ce skill établit un protocole pour identifier, lire et arbitrer les sources du dépôt Creatyss avant toute proposition de code, structure ou décision technique.

Core Features & Use Cases

  • Routage documentaire obligatoire: détermine quelles sources consulter avant une proposition et évite les décisions sans fondement documentaire.
  • Arbitrage des sources: priorise les sources pertinentes entre docs/architecture, docs/domains et Prisma selon les règles du dépôt.
  • Validation avant sortie: assure que les instructions IA minimisent les ambiguïtés et respectent les conventions du projet.

Quick Start

Identifie la nature de la demande, localise les sources pertinentes et arbitre-les avant toute proposition.

Frequently Asked Questions about creatyss-doc-routing

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

FAQPage Schema
How do I determine which architecture docs to read before proposing code changes?

Source arbitration prioritizes relevant architecture docs, domain docs, and Prisma schemas before proposing changes to Creatyss. It enforces a deterministic, source-driven workflow so every technical decision has documented foundations and avoids baseless proposals.

What is documentation routing and when do I need it for repository governance?

Documentation routing is a protocol that identifies and arbitrates relevant repository sources before any technical proposal. You need it for repository governance to enforce reading sources like AGENTS.md, ensuring decisions respect project conventions and minimize AI ambiguities.

How to enforce documentation reading sources before generating AI responses?

You enforce reading sources by applying a deterministic workflow that arbitrates between architecture docs, domain docs, and Prisma before answering. This validation requires frontmatter presence in SKILL.md and ensures AI instructions respect repository conventions before proposing solutions.

Does source arbitration work with Prisma schemas and AGENTS.md files?

Yes, source arbitration explicitly works with Prisma schemas, AGENTS.md, architecture docs, and domain docs. It applies repository-specific arbitration rules to prioritize these sources, ensuring technical proposals align with existing documentation and governance standards before answering.

What are the limitations of automated documentation routing for source validation?

Automated documentation routing is limited to the Creatyss repository context and its specific source types like docs, Prisma, and AGENTS.md. It cannot validate external sources and requires strict frontmatter presence in SKILL.md to function deterministically.