Synchronize templates and schemas with CLAUDE.md Protocol 5 compliance

[Copilot]

Brings templates/rule-template.md and all rule files into strict compliance with CLAUDE.md Protocol 5 (Template Adherence). YAML frontmatter across 51 rule files lacked consistent quoting, diverging from the governance specification.

Changes

Template Enhancement

• templates/rule-template.md: Added explicit Protocol 5 requirements with quoted YAML examples, expanded field definitions (impact levels, type criteria, tag guidelines), and cross-references to Protocols 8 and 10

YAML Frontmatter Standardization (51 files)

Applied quoted values to all frontmatter fields per Protocol 5 specification:

Before:

---
title: Authentication
impact: HIGH
impactDescription: Authenticate all NextDNS API requests with API key
type: capability
tags: authentication, API key, X-API-Key, authorization, security
---

After:

---
title: "Authentication"
impact: "HIGH"
impactDescription: "Authenticate all NextDNS API requests with API key"
type: "capability"
tags: "authentication, API key, X-API-Key, authorization, security"
---

• API skills: 17 files
• CLI skills: 14 files
• UI skills: 10 files
• Integration skills: 10 files

Schema Verification

• data/schemas/profile.json: Confirmed Protocol 4 casing compliance (NextDNS, OpenWrt, iPhone, Samsung). No changes required.

Validation

• All 51 internal links verified (Protocol 10)
• Passes pnpm lint (markdownlint + case-police)
• Zero protocol violations across 10 governance protocols

Original prompt

I need to synchronize the data/ and templates/ directories with the rest of the project while ensuring full compliance with CLAUDE.md.

Part 1: Template & Schema Update

• Update templates/rule-template.md to be the definitive source of truth for all Markdown files.
• Ensure data/schemas/profile.json (and any other JSON in data/) follows the correct casing (Protocol 4: NextDNS, GitHub, etc.).

Part 2: Cascading Synchronization

• Once the templates are updated, perform a Cascading Sync across all 51 files in the skills/ directory.
• Action: Update the YAML frontmatter in every .md file to strictly match the updated templates/rule-template.md.
• Action: Ensure any embedded JSON examples in the rule files are valid against the current data/schemas/profile.json.

Part 3: Final Validation & Cleanup

• Run pnpm lint:fix to auto-correct any casing or formatting issues introduced during the sync (Protocol 3).
• Verify Protocol 10: Ensure no internal links between rules, templates, and schemas are broken.

Please process this folder by folder (API, CLI, Integrations, UI) to maintain quality and avoid context overflow.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[tuanductran]

@copilot Fix structural and formatting issues only in this Markdown file.

Scope:

• YAML Front Matter
• Markdown structure related to metadata usage

Rules:

• Do NOT modify prose, explanations, or instructional content
• Do NOT introduce new content or remove existing content
• Do NOT change heading text or section order
• Do NOT alter URLs, code blocks, or examples

Allowed changes:

• Correct YAML Front Matter syntax and formatting
• Insert missing blank lines required by Markdown parsers
• Normalize tags into a YAML array
• Remove or deduplicate metadata that is redundantly hardcoded in the body

The output must be semantically identical to the original document.

[Copilot]

Pull request overview

This PR enforces strict compliance with CLAUDE.md Protocol 5 (Template Adherence) by standardizing YAML frontmatter across the project. The template and all 51 rule files now use quoted values for all frontmatter fields, eliminating inconsistencies that diverged from the governance specification.

Changes:

• Enhanced templates/rule-template.md with explicit Protocol 5 requirements, expanded field definitions, and governance cross-references
• Applied quoted YAML values across 51 rule files in API, CLI, UI, and Integration skills directories
• Removed extraneous blank lines after YAML frontmatter delimiters for consistency

Reviewed changes

Copilot reviewed 52 out of 52 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
templates/rule-template.md	Added Protocol 5 compliance requirements with detailed frontmatter specifications and mandatory formatting guidelines
skills/nextdns-ui/rules/*.md (10 files)	Standardized YAML frontmatter with quoted values and removed trailing blank lines
skills/nextdns-cli/rules/*.md (14 files)	Applied quoted strings to all frontmatter fields per Protocol 5 specification
skills/nextdns-api/rules/*.md (17 files)	Enforced consistent YAML quoting for metadata compliance
skills/integrations/rules/*.md (10 files)	Synchronized frontmatter formatting with template requirements

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.