Praxis Landing Registries Sitemap Playgrounds
Use this skill for the operational publication layer of praxis-ui-landing-page: registries, guides, routes, sitemap, LLM files, examples, playgrounds, generated docs, and validation tooling.
This skill handles how public docs are wired and validated. Use praxis-landing-public-docs-contracts for what the docs are allowed to claim.
Source Audit
Inspect the landing publication surface before editing:
praxis-ui-landing-page/AGENTS.md
praxis-ui-landing-page/package.json
src/app/app.routes.ts
src/app/data/site.data.ts
src/app/data/guides/landing-docs.registry.ts
src/app/data/guides/component-docs.registry.ts
src/app/data/guides/**/*.md
src/app/pages/*guide*, *examples*, *playground*, and *detail*
src/app/playground/**
public/examples/**
public/sitemap.xml
public/llms.txt, public/llms-full.txt, and public/llm-index.json
tools/sync-sitemap.mjs
tools/validate-published-guides.mjs
tools/sync-dynamic-page-examples-catalog.mjs
tools/sync-vendor-docs.mjs
tools/validate-table-manifests.mjs
tools/validate-quickstart-domain-catalog.mjs
tools/docs/validate-docs.mjs
tools/docs/report-component-docs-coverage.mjs
- relevant E2E files under
e2e/** when behavior or browser rendering changes
Canonical Boundary
Registries, sitemap, LLM files, examples, and playground routes are derived publication artifacts. They should project:
- backend contracts from
praxis-metadata-starter
- config and AI authoring contracts from
praxis-config-starter
- runtime/component contracts from
praxis-ui-angular
- reference proof from
praxis-api-quickstart
- executable HTTP proof from
praxisui-http-examples
Do not add landing-local catalog fields, fake capabilities, static HTTP facts, or prompt shortcuts when the canonical source already has or lacks the semantics. If an example needs data that does not exist, fix the owner or narrow the example.
No Keyword Routing
Do not decide guide publication, sitemap inclusion, LLM exposure, playground scenario, or example category by title keywords, route slugs, regexes, aliases, or fuzzy text as the primary rule. Use route declarations, registry metadata, frontmatter, manifests, generated catalog scripts, canonical contracts, and validation output. Text search is only for locating candidate files after the owner and surface are known.
Aderence Inventory
Before changing registries, routes, sitemap, LLM files, examples, playgrounds, or generated docs, classify:
ja-suportado-so-ux
ja-suportado-mal-nomeado-ou-mal-materializado
suportado-parcialmente
lacuna-real-de-contrato
Only real gaps in the owning contract justify new canonical fields or route semantics. Most registry or sitemap changes are ja-suportado-so-ux or ja-suportado-mal-nomeado-ou-mal-materializado: the platform already knows the fact, but the public site is not publishing it well.
Decision Rules
- Treat
package.json scripts as the source of operational commands.
- Keep generated or synchronized artifacts generated. Do not hand-edit sitemap/vendor/generated docs when a sync script owns them.
- Treat the sitemap as the projection of the union returned by
getPraxisDocItems and getPraxisDocItemSurfaces, including generated and manual items. Preserve each item's canonical path and its indexable/enabled state; do not derive the sitemap from a manual JSON list alone.
- A public Angular catalog must reuse the installed release's package manifests and component registries. Do not infer exports, import paths, or runtime component availability from a registry entry, and preserve explicit
contextOnly and contractOnly entries as semantic contexts and runtime contracts, distinct from catalogued component surfaces. Carry each package manifest status into compact LLM projections as well as full catalogs.
- Preserve guide
slug, related_docs, publication status, internal markdown links, and route validity.
- When adding a published guide, wire registry, route visibility, sitemap, related docs, LLM files, and validation together.
- Flow-oriented published guides should use fenced Mermaid diagrams when they explain runtime, integration, request/response, sequence, state, or runbook flows. Treat
validate:published-guides Mermaid warnings in the changed/publication scope as editorial drift to resolve or explicitly justify from the landing rendering policy; do not let recurring warnings become background noise.
- When changing examples in
site.data.ts, review table/list/crud/dynamic-page manifests and run the matching manifest gate.
- When changing playground behavior, validate the focused adapter/spec/E2E path and capture browser evidence if visual/product quality changed.
- Public playgrounds must not auto-call protected config, AI, or domain evidence endpoints unless the endpoint has repeatable public proof, allowed origin/header coverage, and a console-clean fallback. Prefer curated fixtures or prompt examples for public-first UX when the canonical endpoint is protected or has no published release for the scope.
- When public docs mirror quickstart or HTTP examples, verify the referenced evidence still exists; do not cite stale smoke output.
- Exclude
dist/, artifacts/, output/, tmp/, .angular/, and node_modules/ from source audits unless debugging generated output.
Initial HTML For Technical Documentation
For discoverability work, audit the public GET response before editing: HTTP 200
and a valid route do not prove that a crawler receives documentation. Inspect
initial body text, headings and code with JavaScript disabled. Reuse the existing
crawler publication pipeline and the adopted release's canonical public sources;
do not hand-maintain a parallel inventory or silently copy newer private source.
Render complete approved documentation with tables, code and working fragment
links. Preserve readable prose when sanitizing raw HTML, reject active content
and unsafe protocols, and resolve source-relative links only through known public
routes. Account for the application base URL when rendering fragment links.
A manifest may reference an internal curation plan: that is not visitor copy.
For an interactive examples page, project its existing visitor-facing catalog and
code; clearly distinguish readable examples from previews requiring JavaScript.
Validate content completeness in the generated and hosted HTML, not merely a
crawler marker, then prove no-JavaScript reading and normal Angular bootstrap.
Use the official build/deploy pipeline so the verified HTML is included in the
published artifact. Record uncovered routes and separate local evidence from
hosted publication and search-engine indexing.
Validation Matrix
Choose the smallest sufficient gate:
- guide registry/frontmatter/route:
npm run validate:published-guides
- sitemap:
npm run validate:sitemap
- expected sitemap regeneration:
npm run sitemap:sync then npm run validate:sitemap
- docs markdown/component docs:
npm run docs:validate
- docs coverage report:
npm run docs:coverage
- vendor docs projection:
npm run validate:vendor-docs
- dynamic-page examples:
npm run validate:dynamic-page-examples
- table manifests/examples:
npm run validate:table-manifests
- quickstart domain catalog projection:
npm run validate:quickstart-domain-catalog
- broad publication/integration change:
npm run check:integration
- decision playground:
npm run e2e:decision-playground or npm run audit:decision-playground:visual when behavior/visual proof changed
- live quickstart:
npm run e2e:live-quickstart only when the public host integration itself is in scope
If the landing node_modules was installed in a platform-specific environment, run Node/Angular commands in the owner environment. Inspect package binaries before mixing WSL/Linux/Windows installs when applicable.
Companion Skills
Use praxis-landing-dynamic-page-studio for Studio execution policy, safe operational JSON, guided recipes, and hosted workstation proof.
Use praxis-landing-public-docs-contracts before changing platform-level claims.
Use praxis-angular-docs-playgrounds for component docs manifests, Angular examples, AI recipes, and generated registry projections.
Use praxis-api-quickstart-cockpit-http-validation when the page cites quickstart/cockpit evidence.
Use praxis-http-examples-llm-smoke when llms.txt, llms-full.txt, llm-index.json, or safe-first HTTP lanes mirror executable examples.
Use metadata/config skills when a registry or guide exposes backend contract semantics.
Output Expectations
Report:
- publication surfaces touched
- canonical evidence checked
- generated artifacts synced or deliberately not changed
- validation commands run
- any route, sitemap, LLM, guide, or playground drift left open
1---2name: praxis-landing-registries-sitemap-playgrounds3description: Use when Codex must update or audit praxis-ui-landing-page registries, published guide frontmatter, sitemap, llms.txt/llms-full.txt/llm-index.json, dynamic examples, live playgrounds, decision playground, table manifests, vendor docs sync, generated docs, and local validation for public Praxis docs.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-landing-registries-sitemap-playgrounds6---78# Praxis Landing Registries Sitemap Playgrounds910Use this skill for the operational publication layer of `praxis-ui-landing-page`: registries, guides, routes, sitemap, LLM files, examples, playgrounds, generated docs, and validation tooling.1112This skill handles how public docs are wired and validated. Use `praxis-landing-public-docs-contracts` for what the docs are allowed to claim.1314## Source Audit1516Inspect the landing publication surface before editing:1718- `praxis-ui-landing-page/AGENTS.md`19- `praxis-ui-landing-page/package.json`20- `src/app/app.routes.ts`21- `src/app/data/site.data.ts`22- `src/app/data/guides/landing-docs.registry.ts`23- `src/app/data/guides/component-docs.registry.ts`24- `src/app/data/guides/**/*.md`25- `src/app/pages/*guide*`, `*examples*`, `*playground*`, and `*detail*`26- `src/app/playground/**`27- `public/examples/**`28- `public/sitemap.xml`29- `public/llms.txt`, `public/llms-full.txt`, and `public/llm-index.json`30- `tools/sync-sitemap.mjs`31- `tools/validate-published-guides.mjs`32- `tools/sync-dynamic-page-examples-catalog.mjs`33- `tools/sync-vendor-docs.mjs`34- `tools/validate-table-manifests.mjs`35- `tools/validate-quickstart-domain-catalog.mjs`36- `tools/docs/validate-docs.mjs`37- `tools/docs/report-component-docs-coverage.mjs`38- relevant E2E files under `e2e/**` when behavior or browser rendering changes3940## Canonical Boundary4142Registries, sitemap, LLM files, examples, and playground routes are derived publication artifacts. They should project:4344- backend contracts from `praxis-metadata-starter`45- config and AI authoring contracts from `praxis-config-starter`46- runtime/component contracts from `praxis-ui-angular`47- reference proof from `praxis-api-quickstart`48- executable HTTP proof from `praxisui-http-examples`4950Do not add landing-local catalog fields, fake capabilities, static HTTP facts, or prompt shortcuts when the canonical source already has or lacks the semantics. If an example needs data that does not exist, fix the owner or narrow the example.5152## No Keyword Routing5354Do not decide guide publication, sitemap inclusion, LLM exposure, playground scenario, or example category by title keywords, route slugs, regexes, aliases, or fuzzy text as the primary rule. Use route declarations, registry metadata, frontmatter, manifests, generated catalog scripts, canonical contracts, and validation output. Text search is only for locating candidate files after the owner and surface are known.5556## Aderence Inventory5758Before changing registries, routes, sitemap, LLM files, examples, playgrounds, or generated docs, classify:5960- `ja-suportado-so-ux`61- `ja-suportado-mal-nomeado-ou-mal-materializado`62- `suportado-parcialmente`63- `lacuna-real-de-contrato`6465Only real gaps in the owning contract justify new canonical fields or route semantics. Most registry or sitemap changes are `ja-suportado-so-ux` or `ja-suportado-mal-nomeado-ou-mal-materializado`: the platform already knows the fact, but the public site is not publishing it well.6667## Decision Rules6869- Treat `package.json` scripts as the source of operational commands.70- Keep generated or synchronized artifacts generated. Do not hand-edit sitemap/vendor/generated docs when a sync script owns them.71- Treat the sitemap as the projection of the union returned by `getPraxisDocItems` and `getPraxisDocItemSurfaces`, including generated and manual items. Preserve each item's canonical `path` and its `indexable`/`enabled` state; do not derive the sitemap from a manual JSON list alone.72- A public Angular catalog must reuse the installed release's package manifests and component registries. Do not infer exports, import paths, or runtime component availability from a registry entry, and preserve explicit `contextOnly` and `contractOnly` entries as semantic contexts and runtime contracts, distinct from catalogued component surfaces. Carry each package manifest status into compact LLM projections as well as full catalogs.73- Preserve guide `slug`, `related_docs`, publication status, internal markdown links, and route validity.74- When adding a published guide, wire registry, route visibility, sitemap, related docs, LLM files, and validation together.75- Flow-oriented published guides should use fenced Mermaid diagrams when they explain runtime, integration, request/response, sequence, state, or runbook flows. Treat `validate:published-guides` Mermaid warnings in the changed/publication scope as editorial drift to resolve or explicitly justify from the landing rendering policy; do not let recurring warnings become background noise.76- When changing examples in `site.data.ts`, review table/list/crud/dynamic-page manifests and run the matching manifest gate.77- When changing playground behavior, validate the focused adapter/spec/E2E path and capture browser evidence if visual/product quality changed.78- Public playgrounds must not auto-call protected config, AI, or domain evidence endpoints unless the endpoint has repeatable public proof, allowed origin/header coverage, and a console-clean fallback. Prefer curated fixtures or prompt examples for public-first UX when the canonical endpoint is protected or has no published release for the scope.79- When public docs mirror quickstart or HTTP examples, verify the referenced evidence still exists; do not cite stale smoke output.80- Exclude `dist/`, `artifacts/`, `output/`, `tmp/`, `.angular/`, and `node_modules/` from source audits unless debugging generated output.8182## Initial HTML For Technical Documentation8384For discoverability work, audit the public GET response before editing: HTTP 20085and a valid route do not prove that a crawler receives documentation. Inspect86initial body text, headings and code with JavaScript disabled. Reuse the existing87crawler publication pipeline and the adopted release's canonical public sources;88do not hand-maintain a parallel inventory or silently copy newer private source.8990Render complete approved documentation with tables, code and working fragment91links. Preserve readable prose when sanitizing raw HTML, reject active content92and unsafe protocols, and resolve source-relative links only through known public93routes. Account for the application base URL when rendering fragment links.94A manifest may reference an internal curation plan: that is not visitor copy.95For an interactive examples page, project its existing visitor-facing catalog and96code; clearly distinguish readable examples from previews requiring JavaScript.9798Validate content completeness in the generated and hosted HTML, not merely a99crawler marker, then prove no-JavaScript reading and normal Angular bootstrap.100Use the official build/deploy pipeline so the verified HTML is included in the101published artifact. Record uncovered routes and separate local evidence from102hosted publication and search-engine indexing.103104## Validation Matrix105106Choose the smallest sufficient gate:107108- guide registry/frontmatter/route: `npm run validate:published-guides`109- sitemap: `npm run validate:sitemap`110- expected sitemap regeneration: `npm run sitemap:sync` then `npm run validate:sitemap`111- docs markdown/component docs: `npm run docs:validate`112- docs coverage report: `npm run docs:coverage`113- vendor docs projection: `npm run validate:vendor-docs`114- dynamic-page examples: `npm run validate:dynamic-page-examples`115- table manifests/examples: `npm run validate:table-manifests`116- quickstart domain catalog projection: `npm run validate:quickstart-domain-catalog`117- broad publication/integration change: `npm run check:integration`118- decision playground: `npm run e2e:decision-playground` or `npm run audit:decision-playground:visual` when behavior/visual proof changed119- live quickstart: `npm run e2e:live-quickstart` only when the public host integration itself is in scope120121If the landing `node_modules` was installed in a platform-specific environment, run Node/Angular commands in the owner environment. Inspect package binaries before mixing WSL/Linux/Windows installs when applicable.122123## Companion Skills124125- Use `praxis-landing-dynamic-page-studio` for Studio execution policy, safe operational JSON, guided recipes, and hosted workstation proof.126127- Use `praxis-landing-public-docs-contracts` before changing platform-level claims.128- Use `praxis-angular-docs-playgrounds` for component docs manifests, Angular examples, AI recipes, and generated registry projections.129- Use `praxis-api-quickstart-cockpit-http-validation` when the page cites quickstart/cockpit evidence.130- Use `praxis-http-examples-llm-smoke` when `llms.txt`, `llms-full.txt`, `llm-index.json`, or safe-first HTTP lanes mirror executable examples.131- Use metadata/config skills when a registry or guide exposes backend contract semantics.132133## Output Expectations134135Report:136137- publication surfaces touched138- canonical evidence checked139- generated artifacts synced or deliberately not changed140- validation commands run141- any route, sitemap, LLM, guide, or playground drift left open