Praxis Rich Content Authoring Settings
For composing cards, indicators, timelines and navigation in a page, read
browser-content-composition.md.
It applies across analytical, registration and detail screens.
Use this skill for the canonical rich-content editor and Settings Panel surface. The editor must preserve the same document envelope consumed by the renderer.
Source Audit
Before editing code or guidance, inspect:
projects/praxis-rich-content/README.md
projects/praxis-rich-content/src/lib/praxis-rich-content-config-editor.ts
projects/praxis-rich-content/src/lib/praxis-rich-content-config-editor.spec.ts
projects/praxis-rich-content/src/lib/rich-content-authoring.ts
projects/praxis-rich-content/src/lib/rich-content-authoring.spec.ts
projects/praxis-rich-content/src/lib/rich-content-document-validator.ts
projects/praxis-rich-content/src/lib/i18n/**
projects/praxis-rich-content/src/lib/praxis-rich-content.metadata.ts
Read projects/praxis-rich-content/AGENTS.md before editing rich-content authoring. Use praxis-angular-agents-governance if the local AGENTS file is missing, stale, or contradicts this skill.
Canonical Editor Contract
The editor opens and saves the widget input envelope:
{
inputs: {
document: { kind: 'praxis.rich-content', version: '1.0.0', nodes: [] },
layout: 'block',
rootClassName: 'employee-summary'
}
}
Do not create editor-only document shapes or host wrappers that the renderer cannot consume.
Authoring Rules
- Preserve guided editing, preview, and advanced JSON as synchronized views of one canonical document.
- Use
EDITABLE_TOP_LEVEL_NODE_TYPES, presenter node types, and default node factories from rich-content-authoring.ts.
- Validate before apply/save with
validateRichContentDocument.
- Keep document-level context, aliases, bindings,
visibleWhen, disabledWhen, loadWhen, classWhen, and styleWhen available through structured controls or focused JSON.
- Keep labels and validation messages in
providePraxisRichContentI18n() catalogs.
- Use presets for repeatable structures instead of copying bulky local JSON into consumers.
- Keep Settings Panel apply/save/reset/reopen behavior aligned with runtime rendering.
- When another editor embeds Rich Content, delegate through the canonical document/input contract and keep guided editing, preview, advanced JSON, validation, and unapplied-draft state connected to the host apply/save lifecycle. Do not fork a reduced host-local card or callout editor.
- Preserve semantic callout/card tone, icon, title, message, context-path bindings, action references, and safe advanced properties. Validate
rootClassName and the full document even when content enters through advanced JSON.
- Treat action nodes as references only. The owning host must resolve them against its governed action catalog and enforce capability, record authorization, confirmation, and dispatch; a rendered button never grants authority.
- Prefer semantic tones and platform tokens. Arbitrary styles or gradients remain advanced input and require the canonical safety validator plus rendered contrast evidence across supported themes.
- Selecting Custom/manual for an icon or badge preserves its existing preset or manually authored
node.style. Continue manual edits through the existing style controls without clearing styles or persisting a new mode/preset id. Use the explicit visual-style reset when the intent is to remove overrides; selecting another named preset still applies that preset. Prove preset→Custom→Save, manual edit→Custom→Save, and explicit Reset for both icon and badge in the focused editor spec.
Invalid payload and advanced-JSON drafts belong to the edited object, not its
mutable array index. Preserve that ownership through reorder, sibling removal and
parse/clone round trips; removing or replacing an owner discards only its own draft.
Do not clear a surviving sibling's error or document-context draft to restore
validity. Keep identity bookkeeping internal, without persisted node IDs. Test nested
card/content/compose actions, swaps, type replacement, valid-node cloning and
repair of a temporarily invalid structured document. Apply/Save stays blocked until
all surviving errors are repaired; verify the accepted envelope through reopen.
Validation
Use the smallest reliable proof:
praxis-rich-content-config-editor.spec.ts
rich-content-authoring.spec.ts
rich-content-document-validator.spec.ts
- Settings Panel round-trip validation when hosted editor behavior changes
- i18n audit when authoring text changes
- docs/playground validation when public authoring examples change
Companion Skills
- Use
praxis-rich-content-runtime for renderer and document semantics.
- Use
praxis-rich-content-ai-security-validation when authoring touches manifest operations, sanitization, safe URLs/styles, or AI-generated documents.
- Use
praxis-authoring-editors and praxis-settings-roundtrip-authoring for shared Settings Panel protocol and round-trip behavior.
1---2name: praxis-rich-content-authoring-settings3description: Use when Codex must implement, audit, document, or author `@praxisui/rich-content` visual authoring, including `PraxisRichContentConfigEditor`, Settings Panel round-trip, guided block editing, preview, advanced JSON, preset insertion, rich content i18n, validation badges, widget config editor metadata, apply/save/reset/reopen behavior, docs, examples, or public authoring API for `RichContentDocument`.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-rich-content-authoring-settings6---78# Praxis Rich Content Authoring Settings910For composing cards, indicators, timelines and navigation in a page, read11[browser-content-composition.md](references/browser-content-composition.md).12It applies across analytical, registration and detail screens.1314Use this skill for the canonical rich-content editor and Settings Panel surface. The editor must preserve the same document envelope consumed by the renderer.1516## Source Audit1718Before editing code or guidance, inspect:1920- `projects/praxis-rich-content/README.md`21- `projects/praxis-rich-content/src/lib/praxis-rich-content-config-editor.ts`22- `projects/praxis-rich-content/src/lib/praxis-rich-content-config-editor.spec.ts`23- `projects/praxis-rich-content/src/lib/rich-content-authoring.ts`24- `projects/praxis-rich-content/src/lib/rich-content-authoring.spec.ts`25- `projects/praxis-rich-content/src/lib/rich-content-document-validator.ts`26- `projects/praxis-rich-content/src/lib/i18n/**`27- `projects/praxis-rich-content/src/lib/praxis-rich-content.metadata.ts`2829Read `projects/praxis-rich-content/AGENTS.md` before editing rich-content authoring. Use `praxis-angular-agents-governance` if the local AGENTS file is missing, stale, or contradicts this skill.3031## Canonical Editor Contract3233The editor opens and saves the widget input envelope:3435```ts36{37 inputs: {38 document: { kind: 'praxis.rich-content', version: '1.0.0', nodes: [] },39 layout: 'block',40 rootClassName: 'employee-summary'41 }42}43```4445Do not create editor-only document shapes or host wrappers that the renderer cannot consume.4647## Authoring Rules4849- Preserve guided editing, preview, and advanced JSON as synchronized views of one canonical document.50- Use `EDITABLE_TOP_LEVEL_NODE_TYPES`, presenter node types, and default node factories from `rich-content-authoring.ts`.51- Validate before apply/save with `validateRichContentDocument`.52- Keep document-level context, aliases, bindings, `visibleWhen`, `disabledWhen`, `loadWhen`, `classWhen`, and `styleWhen` available through structured controls or focused JSON.53- Keep labels and validation messages in `providePraxisRichContentI18n()` catalogs.54- Use presets for repeatable structures instead of copying bulky local JSON into consumers.55- Keep Settings Panel apply/save/reset/reopen behavior aligned with runtime rendering.56- When another editor embeds Rich Content, delegate through the canonical document/input contract and keep guided editing, preview, advanced JSON, validation, and unapplied-draft state connected to the host apply/save lifecycle. Do not fork a reduced host-local card or callout editor.57- Preserve semantic callout/card tone, icon, title, message, context-path bindings, action references, and safe advanced properties. Validate `rootClassName` and the full document even when content enters through advanced JSON.58- Treat action nodes as references only. The owning host must resolve them against its governed action catalog and enforce capability, record authorization, confirmation, and dispatch; a rendered button never grants authority.59- Prefer semantic tones and platform tokens. Arbitrary styles or gradients remain advanced input and require the canonical safety validator plus rendered contrast evidence across supported themes.60- Selecting **Custom/manual** for an icon or badge preserves its existing preset or manually authored `node.style`. Continue manual edits through the existing style controls without clearing styles or persisting a new mode/preset id. Use the explicit visual-style reset when the intent is to remove overrides; selecting another named preset still applies that preset. Prove preset→Custom→Save, manual edit→Custom→Save, and explicit Reset for both icon and badge in the focused editor spec.6162Invalid payload and advanced-JSON drafts belong to the edited object, not its63mutable array index. Preserve that ownership through reorder, sibling removal and64parse/clone round trips; removing or replacing an owner discards only its own draft.65Do not clear a surviving sibling's error or document-context draft to restore66validity. Keep identity bookkeeping internal, without persisted node IDs. Test nested67card/content/compose actions, swaps, type replacement, valid-node cloning and68repair of a temporarily invalid structured document. Apply/Save stays blocked until69all surviving errors are repaired; verify the accepted envelope through reopen.7071## Validation7273Use the smallest reliable proof:7475- `praxis-rich-content-config-editor.spec.ts`76- `rich-content-authoring.spec.ts`77- `rich-content-document-validator.spec.ts`78- Settings Panel round-trip validation when hosted editor behavior changes79- i18n audit when authoring text changes80- docs/playground validation when public authoring examples change8182## Companion Skills8384- Use `praxis-rich-content-runtime` for renderer and document semantics.85- Use `praxis-rich-content-ai-security-validation` when authoring touches manifest operations, sanitization, safe URLs/styles, or AI-generated documents.86- Use `praxis-authoring-editors` and `praxis-settings-roundtrip-authoring` for shared Settings Panel protocol and round-trip behavior.