Praxis Table Rule Effects Runtime
The praxis-table-rule-* skill family is the canonical Codex skill surface for @praxisui/table-rule-builder and projects/praxis-table-rule-builder; do not create parallel praxis-table-rule-builder-* guidance unless this family cannot express a proven contract gap.
Use this skill for the canonical conditional visual effect editor in @praxisui/table-rule-builder. Treat it as the table-facing visual effects authoring surface, not as a generic CSS editor or business rules engine.
Source Audit
Before editing code or guidance, inspect:
projects/praxis-table-rule-builder/AGENTS.md
projects/praxis-table-rule-builder/README.md
projects/praxis-table-rule-builder/src/public-api.ts
projects/praxis-table-rule-builder/src/lib/effects/README.md
projects/praxis-table-rule-builder/src/lib/effects/rule-effects-panel.component.ts
projects/praxis-table-rule-builder/src/lib/effects/models/rule-effects.model.ts
projects/praxis-table-rule-builder/src/lib/effects/services/effect-registry.service.ts
projects/praxis-table-rule-builder/src/lib/effects/apply-effects.util.ts
projects/praxis-table-rule-builder/src/lib/praxis-table-rule-builder.metadata.ts
- focused effect panel, apply-effects, metadata, i18n, and docs manifest specs
Canonical Boundary
@praxisui/table-rule-builder owns:
RuleEffectsPanelComponent
RuleEffectDefinition
RuleScope
- effect editor categories:
estilo, layout, icone, fundo, animacao, and tooltip
EffectRegistryService plugin ordering and category availability
- default effect presets
- conversion to class/style through
toCellClassAndStyle(...)
- panel i18n namespace and host
labels overrides
@praxisui/table owns table config placement, columns, datasource, rowConditionalRenderers, columns[].conditionalRenderers, and renderer precedence. @praxisui/visual-builder owns general JSON Logic visual rule authoring. Do not move table visual effect semantics into table CSS hacks, host-local classes, or a parallel visual-builder DSL.
Runtime Rules
- Use
RuleEffectsPanelComponent for authoring one aggregate RuleEffectDefinition.
- Persist table embedded rules as
effects: RuleEffectDefinition[] when the table rule surface expects the canonical array.
- Accept singular legacy
effects: RuleEffectDefinition only as import compatibility and normalize to the canonical array on apply.
- Use
scope: cell | row | column | table to describe where the effect applies. Do not infer scope from labels or CSS selectors.
- Use
EffectRegistryService.register(...) for new editor categories; do not bypass the registry with hardcoded host panels.
- Keep preview classes out of persisted payloads. For persisted table mapping, use
toCellClassAndStyle(effect, { includeAnimationPreview: false }).
- Treat
cssClass and inlineStyle as advanced escape hatches that still need safety review.
- Keep panel chrome text in the package i18n catalog. Use
labels only for host-specific overrides and never persist labels as rule semantics.
- Treat
labels, i18n text, hover/reduced-motion preview state, and computed preview classes/styles as authoring presentation context only. The only persisted effect payload emitted by the panel is the normalized RuleEffectDefinition; do not infer domain meaning, rule scope, preset identity, authorization, or business status from translated copy, host label overrides, preview-only animation behavior, cssClass, or inlineStyle.
Inventory Before New Contract
Classify requested changes before adding fields:
ja-suportado-so-ux: the effect, preview, labels, tabs, or preset exists but is not surfaced clearly.
ja-suportado-mal-nomeado-ou-mal-materializado: consumers use CSS classes, singular effects, or local aliases where RuleEffectDefinition or the registry already carries the semantics.
suportado-parcialmente: table placement, visual-builder condition editing, docs, or AI registry projection needs completion around an existing effect model.
lacuna-real-de-contrato: no current effect model, registry category, preset, conversion util, metadata, or table delegation path can represent the visual decision.
Only real contract gaps justify public API changes. Name the canonical owner, affected consumers, docs/examples, AI manifest impact, and minimum validation before editing.
Validation
Use the smallest reliable proof:
rule-effects-panel.component.spec.ts
apply-effects.util.spec.ts
praxis-table-rule-builder.metadata specs when component discovery changes
- i18n catalog checks when labels or panel chrome change
ng build praxis-table-rule-builder when public API or package exports change
- table focused validation when effects materialize in row or column renderers
Report exactly what remained unvalidated, especially visual preview, persisted payload, and table runtime integration.
Companion Skills
- Use
praxis-table-rule-animation-presets for semantic animations, aliases, reduced-motion, and fail-closed animation resolution.
- Use
praxis-table-rule-table-integration when effects are embedded into @praxisui/table rules, renderers, config editors, or Settings Panel.
- Use
praxis-table-rule-ai-validation for AI authoring manifest operations, validators, examples, and registry ingestion.
- Use
praxis-visual-builder-rules as the umbrella for general Visual Builder work, and use praxis-visual-builder-jsonlogic-roundtrip for JSON Logic condition editing or round-trip outside table visual effect payloads.
1---2name: praxis-table-rule-effects-runtime3description: Use when Codex must implement, audit, document, or consume `@praxisui/table-rule-builder` or the praxis-table-rule-builder package visual effect runtime surfaces, including `RuleEffectsPanelComponent`, `RuleEffectDefinition`, `RuleScope`, effect editor tabs, `EffectRegistryService`, `DEFAULT_EFFECT_PRESETS`, `toCellClassAndStyle`, preview classes, labels/i18n overrides, component metadata, public API, docs, examples, or conditional table visual effects.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-table-rule-effects-runtime6---78# Praxis Table Rule Effects Runtime910The `praxis-table-rule-*` skill family is the canonical Codex skill surface for `@praxisui/table-rule-builder` and `projects/praxis-table-rule-builder`; do not create parallel `praxis-table-rule-builder-*` guidance unless this family cannot express a proven contract gap.1112Use this skill for the canonical conditional visual effect editor in `@praxisui/table-rule-builder`. Treat it as the table-facing visual effects authoring surface, not as a generic CSS editor or business rules engine.1314## Source Audit1516Before editing code or guidance, inspect:1718- `projects/praxis-table-rule-builder/AGENTS.md`19- `projects/praxis-table-rule-builder/README.md`20- `projects/praxis-table-rule-builder/src/public-api.ts`21- `projects/praxis-table-rule-builder/src/lib/effects/README.md`22- `projects/praxis-table-rule-builder/src/lib/effects/rule-effects-panel.component.ts`23- `projects/praxis-table-rule-builder/src/lib/effects/models/rule-effects.model.ts`24- `projects/praxis-table-rule-builder/src/lib/effects/services/effect-registry.service.ts`25- `projects/praxis-table-rule-builder/src/lib/effects/apply-effects.util.ts`26- `projects/praxis-table-rule-builder/src/lib/praxis-table-rule-builder.metadata.ts`27- focused effect panel, apply-effects, metadata, i18n, and docs manifest specs2829## Canonical Boundary3031`@praxisui/table-rule-builder` owns:3233- `RuleEffectsPanelComponent`34- `RuleEffectDefinition`35- `RuleScope`36- effect editor categories: `estilo`, `layout`, `icone`, `fundo`, `animacao`, and `tooltip`37- `EffectRegistryService` plugin ordering and category availability38- default effect presets39- conversion to class/style through `toCellClassAndStyle(...)`40- panel i18n namespace and host `labels` overrides4142`@praxisui/table` owns table config placement, columns, datasource, `rowConditionalRenderers`, `columns[].conditionalRenderers`, and renderer precedence. `@praxisui/visual-builder` owns general JSON Logic visual rule authoring. Do not move table visual effect semantics into table CSS hacks, host-local classes, or a parallel visual-builder DSL.4344## Runtime Rules4546- Use `RuleEffectsPanelComponent` for authoring one aggregate `RuleEffectDefinition`.47- Persist table embedded rules as `effects: RuleEffectDefinition[]` when the table rule surface expects the canonical array.48- Accept singular legacy `effects: RuleEffectDefinition` only as import compatibility and normalize to the canonical array on apply.49- Use `scope: cell | row | column | table` to describe where the effect applies. Do not infer scope from labels or CSS selectors.50- Use `EffectRegistryService.register(...)` for new editor categories; do not bypass the registry with hardcoded host panels.51- Keep preview classes out of persisted payloads. For persisted table mapping, use `toCellClassAndStyle(effect, { includeAnimationPreview: false })`.52- Treat `cssClass` and `inlineStyle` as advanced escape hatches that still need safety review.53- Keep panel chrome text in the package i18n catalog. Use `labels` only for host-specific overrides and never persist labels as rule semantics.54- Treat `labels`, i18n text, hover/reduced-motion preview state, and computed preview classes/styles as authoring presentation context only. The only persisted effect payload emitted by the panel is the normalized `RuleEffectDefinition`; do not infer domain meaning, rule scope, preset identity, authorization, or business status from translated copy, host label overrides, preview-only animation behavior, `cssClass`, or `inlineStyle`.5556## Inventory Before New Contract5758Classify requested changes before adding fields:5960- `ja-suportado-so-ux`: the effect, preview, labels, tabs, or preset exists but is not surfaced clearly.61- `ja-suportado-mal-nomeado-ou-mal-materializado`: consumers use CSS classes, singular effects, or local aliases where `RuleEffectDefinition` or the registry already carries the semantics.62- `suportado-parcialmente`: table placement, visual-builder condition editing, docs, or AI registry projection needs completion around an existing effect model.63- `lacuna-real-de-contrato`: no current effect model, registry category, preset, conversion util, metadata, or table delegation path can represent the visual decision.6465Only real contract gaps justify public API changes. Name the canonical owner, affected consumers, docs/examples, AI manifest impact, and minimum validation before editing.6667## Validation6869Use the smallest reliable proof:7071- `rule-effects-panel.component.spec.ts`72- `apply-effects.util.spec.ts`73- `praxis-table-rule-builder.metadata` specs when component discovery changes74- i18n catalog checks when labels or panel chrome change75- `ng build praxis-table-rule-builder` when public API or package exports change76- table focused validation when effects materialize in row or column renderers7778Report exactly what remained unvalidated, especially visual preview, persisted payload, and table runtime integration.7980## Companion Skills8182- Use `praxis-table-rule-animation-presets` for semantic animations, aliases, reduced-motion, and fail-closed animation resolution.83- Use `praxis-table-rule-table-integration` when effects are embedded into `@praxisui/table` rules, renderers, config editors, or Settings Panel.84- Use `praxis-table-rule-ai-validation` for AI authoring manifest operations, validators, examples, and registry ingestion.85- Use `praxis-visual-builder-rules` as the umbrella for general Visual Builder work, and use `praxis-visual-builder-jsonlogic-roundtrip` for JSON Logic condition editing or round-trip outside table visual effect payloads.