Ia Nav Adr

Name: Ia Nav Adr
Author: nomadoor

ASecurity

Use when changing information architecture, section placement, navigation YAML, slugs, URLs, page identity, /ops rules, ADRs, or contribution rules.

20 stars

0 votes

0 copies

0 views

Added 9/29/2026

testing

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add nomadoor/Comfy-with-ComfyUI --skill ia-nav-adr --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ia Nav Adr?

Add the live security badge to your README — it updates automatically with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nomadoor-ia-nav-adr/badge)](https://www.skillsdirectory.com/skills/nomadoor-ia-nav-adr)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

Files

SKILL.md

---
name: ia-nav-adr
description: Use when changing information architecture, section placement, navigation YAML, slugs, URLs, page identity, /ops rules, ADRs, or contribution rules.
---

# IA, Nav, And ADR

## Read First

- `/ops/ia.md`
- `/ops/requirements.md`
- Relevant existing ADRs under `/ops/adr/`
- `src/_data/nav.ja.yml` and matching locale nav files when localization is in scope.

## Rules

- `/ops` is the source of truth.
- Slugs, `navId`, and public URLs are stable IDs.
- Renames need owner approval, nav updates, redirect consideration, and ADR coverage.
- Do not add EN/ZH nav entries unless matching localized pages are part of the requested task.
- Parent grouping changes and sidebar order changes are IA changes.

## Workflow

1. Update `/ops` or add an ADR before implementation.
2. Update nav YAML only for the requested locales.
3. Add or move content files only after IA is documented.
4. Validate nav and content integrity.

## Checks

- `npm run check:content`
- `npm run build`
- `npm run test:playwright` for sidebar, search, language switch, previous/next, or notes changes.

## Naming

An **asset prefix** is always singular, because it modifies the rest of the name and English uses the singular in attributive position — `loop_simple.png`, never `loops_simple.png`.

A **slug or navId** follows the subject instead: singular for a page about one mechanism (`queue`, `list`, `batch-video`, `loop`), plural for a page enumerating many items (`data-types`, `text-ops`, `wildcards`). Check the siblings before choosing.

A **display title or nav label** is not attributive either, and may be plural where that is the natural English even when the slug is singular — `loop` and `Loops`.

An ADR records the decision as it shipped. If the scope changes while the work is in progress — localization was requested halfway, placement moved — update the ADR before the PR, or it documents a plan nobody followed.

## Pipeline

Part of the article pipeline in [article-authoring](../article-authoring/SKILL.md), alongside [workflow-json](../workflow-json/SKILL.md).

Nav and slug changes do not reach a running dev server — restart it, see [preview-site](../preview-site/SKILL.md).

Attribution

nomadoor

View source See grades on GitHub More from nomadoor →

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

--- name: ia-nav-adr description: Use when changing information architecture, section placement, navigation YAML, slugs, URLs, page identity, /ops rules, ADRs, or contribution rules. --- # IA, Nav, And ADR ## Read First - `/ops/ia.md` - `/ops/requirements.md` - Relevant existing ADRs under `/ops/adr/` - `src/_data/nav.ja.yml` and matching locale nav files when localization is in scope. ## Rules - `/ops` is the source of truth. - Slugs, `navId`, and public URLs are stable IDs. - Renames need owner approval, nav updates, redirect consideration, and ADR coverage. - Do not add EN/ZH nav entries unless matching localized pages are part of the requested task. - Parent grouping changes and sidebar order changes are IA changes. ## Workflow 1. Update `/ops` or add an ADR before implementation. 2. Update nav YAML only for the requested locales. 3. Add or move content files only after IA is documented. 4. Validate nav and content integrity. ## Checks - `npm run check:content` - `npm run build` - `npm run test:playwright` for sidebar, search, language switch, previous/next, or notes changes. ## Naming An **asset prefix** is always singular, because it modifies the rest of the name and English uses the singular in attributive position — `loop_simple.png`, never `loops_simple.png`. A **slug or navId** follows the subject instead: singular for a page about one mechanism (`queue`, `list`, `batch-video`, `loop`), plural for a page enumerating many items (`data-types`, `text-ops`, `wildcards`). Check the siblings before choosing. A **display title or nav label** is not attributive either, and may be plural where that is the natural English even when the slug is singular — `loop` and `Loops`. An ADR records the decision as it shipped. If the scope changes while the work is in progress — localization was requested halfway, placement moved — update the ADR before the PR, or it documents a plan nobody followed. ## Pipeline Part of the article pipeline in [article-authoring](../article-authoring/SKILL.md), alongside [workflow-json](../workflow-json/SKILL.md). Nav and slug changes do not reach a running dev server — restart it, see [preview-site](../preview-site/SKILL.md).