How do I install the Rules Repo Conventions skill?

Run npx skillmds add majiayu000/rules-repo-conventions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rules Repo Conventions safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rules Repo Conventions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rules Repo Conventions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rules Repo Conventions?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rules Repo Conventions by majiayu000

Name: Rules Repo Conventions
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Rules Repo Conventions

Apply Rules Repository conventions and forward-only workflow. Use when generating or editing docs, prompts, or code in projects that consume this repository or when this repository is the active workspace. Ensure Pact → Rules → Guides → Implementation links are created and updated, and prefer linking to submodule guides over duplicating content.

majiayu000 df9b33f 2 files · 3.2 KB Updated Sep 9, 2026 567 repo stars

File contents

Rules Repository Conventions

This Skill encodes the essential conventions for working with this repository (as a submodule or directly) so Claude can apply them automatically.

Instructions

Load and apply the repository root skills catalog: see skills.md.
Honor RULES.md anchors for behavior and technical commitments:
Close loops between artifacts:
- Pact → Rules → Guides → Implementation, and back-links from Implementation to its source guide and rule.
Link discipline:
- Use relative paths; do not place project-specific docs inside the Rules Repository submodule directory when used downstream.
Observability defaults:
- Prefer wiring to the Observability index and relevant guides: generative/platform/observability/README.md.
When adding new topic docs under generative/:
- Add the entry to the nearest topic index README and cross-link to related guides.
When updating structure/content:
- Apply the Forward-Only policy in one change: update or remove conflicting docs and links; no compatibility stubs.

Examples

When scaffolding a new host project README, include links to PACT.md, RULES.md, GUIDES.md, IMPLEMENTATION.md, and the Rules Repository submodule path.
When creating a new Observability guide, add it to generative/platform/observability/README.md and cross-link from related platform indexes.

Validation Checklist

Links resolve and remain relative
Loop closure present (forward/back links)
No project-specific files placed inside the submodule directory
Forward-only edits applied (no legacy anchors retained)

---name: rules-repo-conventionsdescription: Apply Rules Repository conventions and forward-only workflow. Use when generating or editing docs, prompts, or code in projects that consume this repository or when this repository is the active workspace. Ensure Pact → Rules → Guides → Implementation links are created and updated, and prefer linking to submodule guides over duplicating content.--- # Rules Repository Conventions This Skill encodes the essential conventions for working with this repository (as a submodule or directly) so Claude can apply them automatically. ## Instructions 1. Load and apply the repository root skills catalog: see [skills.md](../../../../skills.md). 2. Honor RULES.md anchors for behavior and technical commitments: - [./RULES.md#4-behavioral-agreements](../../../../RULES.md#4-behavioral-agreements) - [./RULES.md#5-technical-commitments](../../../../RULES.md#5-technical-commitments) - [./RULES.md#document-modularity-policy](../../../../RULES.md#document-modularity-policy) - [./RULES.md#6-forward-only-change-policy](../../../../RULES.md#6-forward-only-change-policy) 3. Close loops between artifacts: - Pact → Rules → Guides → Implementation, and back-links from Implementation to its source guide and rule. 4. Link discipline: - Use relative paths; do not place project-specific docs inside the Rules Repository submodule directory when used downstream. 5. Observability defaults: - Prefer wiring to the Observability index and relevant guides: [generative/platform/observability/README.md](../../../../generative/platform/observability/README.md). 6. When adding new topic docs under generative/: - Add the entry to the nearest topic index README and cross-link to related guides. 7. When updating structure/content: - Apply the Forward-Only policy in one change: update or remove conflicting docs and links; no compatibility stubs. ## Examples - When scaffolding a new host project README, include links to PACT.md, RULES.md, GUIDES.md, IMPLEMENTATION.md, and the Rules Repository submodule path. - When creating a new Observability guide, add it to [generative/platform/observability/README.md](../../../../generative/platform/observability/README.md) and cross-link from related platform indexes. ## Validation Checklist - Links resolve and remain relative - Loop closure present (forward/back links) - No project-specific files placed inside the submodule directory - Forward-only edits applied (no legacy anchors retained) ## See also - Repository skills catalog — [skills.md](../../../../skills.md) - Enterprise RULES — [RULES.md](../../../../RULES.md) - Platform Observability — [generative/platform/observability/README.md](../../../../generative/platform/observability/README.md)

Frequently asked questions