Praxis Landing Public Docs Contracts
Use this skill when public Praxis documentation or landing copy must explain the platform contract across backend metadata, governed config/AI authoring, Angular runtime, quickstart proof, and HTTP examples.
The landing is a publication layer. It explains, routes, and proves canonical contracts; it does not redefine them.
Source Audit
Inspect the landing/public docs owner before editing:
praxis-ui-landing-page/AGENTS.md
praxis-ui-landing-page/package.json
praxis-ui-landing-page/docs/landing-editorial-axis.md
praxis-ui-landing-page/docs/enterprise-positioning-plan-2026-04.md
praxis-ui-landing-page/docs/landing-editorial-rollout-plan-2026-05.md
praxis-ui-landing-page/src/app/app.routes.ts
praxis-ui-landing-page/src/app/data/site.data.ts
praxis-ui-landing-page/src/app/data/guides/landing-docs.registry.ts
praxis-ui-landing-page/src/app/data/guides/component-docs.registry.ts
- published guide markdown under
praxis-ui-landing-page/src/app/data/guides/**
praxis-ui-landing-page/public/llms.txt, llms-full.txt, llm-index.json, and sitemap.xml when LLM/search/public routing changes
Then inspect the canonical owner for every claim:
praxis-metadata-starter for resource + surfaces + actions + capabilities, /schemas/filtered, x-ui, HATEOAS, option sources, schema hashes, and semantic grounding.
praxis-config-starter for /api/praxis/config/**, ui_user_config, AI registry/config, agentic authoring, domain decisions, headers, and ETag.
praxis-ui-angular for @praxisui/* runtime contracts, component docs, manifests, AI registry projections, examples, recipes, playground behavior, and public API.
praxis-api-quickstart for reference-host proof by real HTTP.
praxisui-http-examples for executable examples, corpus manifests, safe-first LLM surfaces, and smoke evidence.
Canonical Boundary
Public docs should describe Praxis as a platform of AI-authored semantic decisions:
backend metadata grounding -> governed config/AI authoring -> Angular materialization -> quickstart/HTTP proof -> public docs projection
Do not turn landing copy, guide frontmatter, route registries, LLM text files, screenshots, playground labels, or examples into primary business semantics. If a public page needs a fact that the canonical owner cannot prove, classify it as a gap in the owner, not as copy freedom.
No Keyword Routing
Do not decide which platform pillar, resource, guide, route, capability, or AI flow a page describes by keywords, slugs, regexes, aliases, or fuzzy title matching as the primary mechanism. Use canonical owner, registry metadata, route declarations, manifests, published guide frontmatter, executable examples, HTTP proof, and semantic contracts. Text matching may only find candidate files after the canonical scope is known.
Aderence Inventory
Before adding or changing a public narrative, guide, route, registry entry, LLM page, example, or diagram, classify the need:
ja-suportado-so-ux: the canonical owner already exposes the meaning and only the page presentation must improve.
ja-suportado-mal-nomeado-ou-mal-materializado: the owner has the semantics but the public docs or runtime materialization misnames, hides, or weakly frames it.
suportado-parcialmente: some evidence exists, but claims must be narrowed or split between confirmed capability and roadmap.
lacuna-real-de-contrato: the public behavior cannot be stated truthfully because the canonical owner lacks data, contract, endpoint, manifest, tool, event, or proof.
Only lacuna-real-de-contrato justifies a new canonical contract. In that case name the missing UX/behavior, canonical owner, affected consumers, derived artifacts, and minimum validation before changing public docs.
Decision Rules
- Start from
praxis-ui-landing-page/AGENTS.md and the relevant canonical owner; never start by inventing landing-local semantics.
- Publish
praxis-metadata-starter as semantic grounding and structural schema source, not as a JSON generator.
- Publish
praxis-config-starter as governed authoring, simulation, approval, publication, persistence, and materialization boundary, not just preference storage.
- Publish
praxis-ui-angular as cockpit/runtime for materialized decisions, not as primary business-rule source.
- Use
praxis-api-quickstart and praxisui-http-examples as operational proof surfaces, not contract owners.
- Distinguish shipped, proven, public, beta, and roadmap claims. Do not upgrade aspirational direction into current capability.
- When public docs disagree with code, backend contracts, or HTTP proof, fix the canonical owner or document drift; do not normalize the landing as truth.
- If a new public route or guide is created, update registries, sitemap, LLM surfaces, related docs, and validation scope together.
- When validating a reference consumer after a runtime package update, use fixtures from the current canonical contract.
EnterpriseRuntimeContextService.ready() completing with a non-null response does not mean the selection is authorized: require state === 'ready' and effectiveContext before dependent persistence/provider reads. Prove selection-required, selection-invalid and missing effective context remain blocked; do not fabricate browser identity headers to make an obsolete fixture pass.
- If no derived artifact changes, record the negative evidence: no route, guide, sitemap, LLM surface, registry, example, playground, public API, or canonical contract claim changed.
Impact Map
For non-trivial landing/docs changes, map before editing:
- canonical subproject affected
- impacted consumers such as Angular docs, quickstart docs, HTTP corpus, LLM surfaces, examples, playgrounds, or public site visitors
- public docs and generated docs potentially affected
- examples, playgrounds, recipes, or screenshots potentially affected
- minimum validation
- breaking-change or public-claim risk
Validation
Use the narrowest landing gate that matches the changed surface:
- published guide or route:
npm run validate:published-guides and npm run validate:sitemap
- sitemap drift:
npm run sitemap:sync, then npm run validate:sitemap
- component docs publication:
npm run docs:validate and, when needed, npm run docs:coverage
- vendor/generated docs:
npm run validate:vendor-docs. For isolated checkouts, set PRAXIS_UI_ANGULAR_ROOT to the exact canonical Angular checkout for vendor-docs:sync, validate:vendor-docs and docs:validate; do not invent filesystem bridges. Keep unrelated preexisting vendor drift separate from the scoped synchronization and never report the full freshness gate as passed when it still lists other stale artifacts.
- dynamic page examples:
npm run validate:dynamic-page-examples
- table manifests/examples in
site.data.ts: npm run validate:table-manifests
- quickstart domain catalog projection:
npm run validate:quickstart-domain-catalog
- broad publication surface:
npm run check:integration. In isolated worktrees, the LLM workspace audit accepts PRAXIS_WORKSPACE_ROOT, PRAXIS_UI_ANGULAR_ROOT and PRAXIS_HTTP_EXAMPLES_ROOT; bind them to the real owner workspace and reviewed Angular/HTTP checkouts. Its report records resolved roots and missing sources must still fail. validate:llm-publication:ci validates publication only, not workspace evidence.
For browser proof against the public quickstart, use the official landing origins from AGENTS.md, especially 127.0.0.1:4301/localhost:4301. Do not invent ports.
Companion Skills
Use praxis-landing-dynamic-page-studio when a public contract is taught or proven through the Dynamic Page Studio journey.
Use praxis-landing-registries-sitemap-playgrounds for guide registries, sitemap, LLM files, playgrounds, examples, and validation tooling.
Use praxis-angular-docs-playgrounds for Angular component docs, manifests, examples, AI recipes, and playground behavior.
Use praxis-metadata-schema-contracts, praxis-metadata-discovery-capabilities, and praxis-metadata-domain-option-sources for metadata claims.
Use praxis-config-runtime-persistence, praxis-config-ai-registry-manifests, praxis-config-agentic-authoring-streaming, and praxis-config-domain-decisions for config/AI/governance claims.
Use praxis-api-quickstart-cockpit-http-validation for reference-host proof.
Use praxis-http-examples-corpus-manifest, praxis-http-examples-contract-surfaces, and praxis-http-examples-llm-smoke for executable HTTP examples and LLM surfaces.
Output Expectations
Report:
- canonical owner consulted
- adherence classification
- public docs/routes/registries/LLM surfaces changed or reviewed
- validation commands run
- derived artifacts updated or intentionally left unchanged, with reason
- unresolved drift between public docs and canonical owner
1---2name: praxis-landing-public-docs-contracts3description: "Use when Codex must update or audit praxis-ui-landing-page public docs as the official projection of Praxis canonical contracts: platform narrative, landing pages, published guides, metadata starter, config starter, Angular runtime, quickstart evidence, HTTP examples, LLM docs, generated docs, and derived artifact decisions."4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-landing-public-docs-contracts6---78# Praxis Landing Public Docs Contracts910Use this skill when public Praxis documentation or landing copy must explain the platform contract across backend metadata, governed config/AI authoring, Angular runtime, quickstart proof, and HTTP examples.1112The landing is a publication layer. It explains, routes, and proves canonical contracts; it does not redefine them.1314## Source Audit1516Inspect the landing/public docs owner before editing:1718- `praxis-ui-landing-page/AGENTS.md`19- `praxis-ui-landing-page/package.json`20- `praxis-ui-landing-page/docs/landing-editorial-axis.md`21- `praxis-ui-landing-page/docs/enterprise-positioning-plan-2026-04.md`22- `praxis-ui-landing-page/docs/landing-editorial-rollout-plan-2026-05.md`23- `praxis-ui-landing-page/src/app/app.routes.ts`24- `praxis-ui-landing-page/src/app/data/site.data.ts`25- `praxis-ui-landing-page/src/app/data/guides/landing-docs.registry.ts`26- `praxis-ui-landing-page/src/app/data/guides/component-docs.registry.ts`27- published guide markdown under `praxis-ui-landing-page/src/app/data/guides/**`28- `praxis-ui-landing-page/public/llms.txt`, `llms-full.txt`, `llm-index.json`, and `sitemap.xml` when LLM/search/public routing changes2930Then inspect the canonical owner for every claim:3132- `praxis-metadata-starter` for `resource + surfaces + actions + capabilities`, `/schemas/filtered`, `x-ui`, HATEOAS, option sources, schema hashes, and semantic grounding.33- `praxis-config-starter` for `/api/praxis/config/**`, `ui_user_config`, AI registry/config, agentic authoring, domain decisions, headers, and ETag.34- `praxis-ui-angular` for `@praxisui/*` runtime contracts, component docs, manifests, AI registry projections, examples, recipes, playground behavior, and public API.35- `praxis-api-quickstart` for reference-host proof by real HTTP.36- `praxisui-http-examples` for executable examples, corpus manifests, safe-first LLM surfaces, and smoke evidence.3738## Canonical Boundary3940Public docs should describe Praxis as a platform of AI-authored semantic decisions:4142`backend metadata grounding -> governed config/AI authoring -> Angular materialization -> quickstart/HTTP proof -> public docs projection`4344Do not turn landing copy, guide frontmatter, route registries, LLM text files, screenshots, playground labels, or examples into primary business semantics. If a public page needs a fact that the canonical owner cannot prove, classify it as a gap in the owner, not as copy freedom.4546## No Keyword Routing4748Do not decide which platform pillar, resource, guide, route, capability, or AI flow a page describes by keywords, slugs, regexes, aliases, or fuzzy title matching as the primary mechanism. Use canonical owner, registry metadata, route declarations, manifests, published guide frontmatter, executable examples, HTTP proof, and semantic contracts. Text matching may only find candidate files after the canonical scope is known.4950## Aderence Inventory5152Before adding or changing a public narrative, guide, route, registry entry, LLM page, example, or diagram, classify the need:5354- `ja-suportado-so-ux`: the canonical owner already exposes the meaning and only the page presentation must improve.55- `ja-suportado-mal-nomeado-ou-mal-materializado`: the owner has the semantics but the public docs or runtime materialization misnames, hides, or weakly frames it.56- `suportado-parcialmente`: some evidence exists, but claims must be narrowed or split between confirmed capability and roadmap.57- `lacuna-real-de-contrato`: the public behavior cannot be stated truthfully because the canonical owner lacks data, contract, endpoint, manifest, tool, event, or proof.5859Only `lacuna-real-de-contrato` justifies a new canonical contract. In that case name the missing UX/behavior, canonical owner, affected consumers, derived artifacts, and minimum validation before changing public docs.6061## Decision Rules6263- Start from `praxis-ui-landing-page/AGENTS.md` and the relevant canonical owner; never start by inventing landing-local semantics.64- Publish `praxis-metadata-starter` as semantic grounding and structural schema source, not as a JSON generator.65- Publish `praxis-config-starter` as governed authoring, simulation, approval, publication, persistence, and materialization boundary, not just preference storage.66- Publish `praxis-ui-angular` as cockpit/runtime for materialized decisions, not as primary business-rule source.67- Use `praxis-api-quickstart` and `praxisui-http-examples` as operational proof surfaces, not contract owners.68- Distinguish shipped, proven, public, beta, and roadmap claims. Do not upgrade aspirational direction into current capability.69- When public docs disagree with code, backend contracts, or HTTP proof, fix the canonical owner or document drift; do not normalize the landing as truth.70- If a new public route or guide is created, update registries, sitemap, LLM surfaces, related docs, and validation scope together.71- When validating a reference consumer after a runtime package update, use fixtures from the current canonical contract. `EnterpriseRuntimeContextService.ready()` completing with a non-null response does not mean the selection is authorized: require `state === 'ready'` and `effectiveContext` before dependent persistence/provider reads. Prove selection-required, selection-invalid and missing effective context remain blocked; do not fabricate browser identity headers to make an obsolete fixture pass.72- If no derived artifact changes, record the negative evidence: no route, guide, sitemap, LLM surface, registry, example, playground, public API, or canonical contract claim changed.7374## Impact Map7576For non-trivial landing/docs changes, map before editing:7778- canonical subproject affected79- impacted consumers such as Angular docs, quickstart docs, HTTP corpus, LLM surfaces, examples, playgrounds, or public site visitors80- public docs and generated docs potentially affected81- examples, playgrounds, recipes, or screenshots potentially affected82- minimum validation83- breaking-change or public-claim risk8485## Validation8687Use the narrowest landing gate that matches the changed surface:8889- published guide or route: `npm run validate:published-guides` and `npm run validate:sitemap`90- sitemap drift: `npm run sitemap:sync`, then `npm run validate:sitemap`91- component docs publication: `npm run docs:validate` and, when needed, `npm run docs:coverage`92- vendor/generated docs: `npm run validate:vendor-docs`. For isolated checkouts, set `PRAXIS_UI_ANGULAR_ROOT` to the exact canonical Angular checkout for `vendor-docs:sync`, `validate:vendor-docs` and `docs:validate`; do not invent filesystem bridges. Keep unrelated preexisting vendor drift separate from the scoped synchronization and never report the full freshness gate as passed when it still lists other stale artifacts.93- dynamic page examples: `npm run validate:dynamic-page-examples`94- table manifests/examples in `site.data.ts`: `npm run validate:table-manifests`95- quickstart domain catalog projection: `npm run validate:quickstart-domain-catalog`96- broad publication surface: `npm run check:integration`. In isolated worktrees, the LLM workspace audit accepts `PRAXIS_WORKSPACE_ROOT`, `PRAXIS_UI_ANGULAR_ROOT` and `PRAXIS_HTTP_EXAMPLES_ROOT`; bind them to the real owner workspace and reviewed Angular/HTTP checkouts. Its report records resolved roots and missing sources must still fail. `validate:llm-publication:ci` validates publication only, not workspace evidence.9798For browser proof against the public quickstart, use the official landing origins from `AGENTS.md`, especially `127.0.0.1:4301`/`localhost:4301`. Do not invent ports.99100## Companion Skills101102- Use `praxis-landing-dynamic-page-studio` when a public contract is taught or proven through the Dynamic Page Studio journey.103104- Use `praxis-landing-registries-sitemap-playgrounds` for guide registries, sitemap, LLM files, playgrounds, examples, and validation tooling.105- Use `praxis-angular-docs-playgrounds` for Angular component docs, manifests, examples, AI recipes, and playground behavior.106- Use `praxis-metadata-schema-contracts`, `praxis-metadata-discovery-capabilities`, and `praxis-metadata-domain-option-sources` for metadata claims.107- Use `praxis-config-runtime-persistence`, `praxis-config-ai-registry-manifests`, `praxis-config-agentic-authoring-streaming`, and `praxis-config-domain-decisions` for config/AI/governance claims.108- Use `praxis-api-quickstart-cockpit-http-validation` for reference-host proof.109- Use `praxis-http-examples-corpus-manifest`, `praxis-http-examples-contract-surfaces`, and `praxis-http-examples-llm-smoke` for executable HTTP examples and LLM surfaces.110111## Output Expectations112113Report:114115- canonical owner consulted116- adherence classification117- public docs/routes/registries/LLM surfaces changed or reviewed118- validation commands run119- derived artifacts updated or intentionally left unchanged, with reason120- unresolved drift between public docs and canonical owner