Praxis Component Minimums
Use this skill when the task is about the minimum viable runtime setup of Praxis components.
Typical triggers:
- "qual o minimo para renderizar"
- "de onde vem os metadados"
- "é só preencher resourcePath?"
- "qual o menor host possível"
- "bootstrap mínimo"
- "quick connect"
- "schema-driven mínimo"
This skill is about runtime bootstrap and host wiring, not authoring/editor parity. If the task changes visual editors or authoring flows, also use praxis-authoring-editors. If the task changes dynamic-fields discovery/editorial chains, also use praxis-dynamic-fields-editorial.
If the task implements or reviews backend RESOURCE_ENTITY option sources, use
praxis-resource-entity-lookup-backend; this skill may explain why resourcePath alone is not
enough, but it does not define the backend contract.
For dynamic-fields runtime or control coverage, use praxis-fields-runtime-loader. For select-like
remote options, use praxis-fields-option-sources. For editor/tooling discovery, use
praxis-fields-editorial-discovery. For AI authoring or canvas coverage, use
praxis-fields-ai-canvas-validation.
For Settings Panel, authoring drawer, Global Config Editor, or apply/save/reset minimums, use the
specialized praxis-settings-* family instead of treating a drawer as a generic host shell.
Before changing this skill or answering a minimum-setup question, inspect the current source for the
target component and its host services. For Angular components this normally means component inputs,
metadata files, config editor metadata, service injections, local/remote mode tests, and the owning
@praxisui/core contracts. The purpose is to codify canonical Praxis runtime knowledge, not repeat
a remembered setup recipe.
Use praxis-core-runtime-contracts when the minimum depends on core tokens, providers, public API,
shared models, logging, or i18n. Use praxis-core-resource-runtime when the minimum depends on
GenericCrudService, schema discovery, resource discovery, capabilities, actions, surfaces,
option sources, or related-resource materialization. Use praxis-core-composition-runtime when the
minimum involves dynamic widget pages, composition links, widget events, or surface hosts.
Canonical Decision Rule
Always answer by separating the component into one of these modes:
- local-only runtime
- backend metadata-driven runtime
- authored/customizable runtime
Do not collapse these into a single "minimum".
Dynamic Form Minimum
For @praxisui/dynamic-form, there are two different minimums:
- Local-only minimum: import
PraxisDynamicFormand pass aFormConfigwith local layout andfieldMetadata. This renders without backend discovery and is appropriate for demos, transient host-only forms, or authoring previews. - Backend metadata-driven minimum: provide runtime endpoints the form can
resolve.
resourcePathcan connect the form to backend discovery, but for metadata-driven surfaces published by the backend, preferschemaUrl + submitUrl + submitMethodor the operation-specific inputs expected by the consuming CRUD/surface runtime. - Schema-driven layout minimum: when the backend schema owns fields,
labels, controls, groups, order, and width, do not add local
FormConfig.sectionsor placeholdersections: []just to make the form render. Use the runtime's generated layout orlayoutPolicypresets first. If the generated layout is not acceptable, classify the gap against metadata/runtime ownership instead of copying local sections into every host screen.
Local/transient field minimum:
- Host-owned fields that do not come from the backend schema belong in
FormConfig.fieldMetadata, not inpraxis-metadata-starterschemas. - Mark host-only fields with
source: 'local'ortransient: truewhen they must participate in the UI, validation, rules, visibility, andvalueChangebut must not be sent to the backend by default. - Use
submitPolicyonly when the default submit behavior must be overridden:includesends the field even when it is local/transient.omitalways removes it from submit payloads.includeWhenDirtysends it only when its control is dirty.
formSubmit.formDatais the backend payload after submit filtering;formSubmit.rawFormDatais the complete UI value bag.- Do not solve local/transient fields by adding backend DTO fields, ad hoc frontend aliases, or CRUD-specific payload filters. The canonical runtime owner is
@praxisui/dynamic-formwith the sharedFieldMetadatacontract in@praxisui/core.
Important guardrails:
resourcePathis not the only path.resourcePathis not the canonical answer for every form question.- If no
FormConfigis provided, the runtime can generate a default layout from backend metadata. - If the host uses runtime fetch/submit flows, confirm the host scope provides the effective API/CRUD service wiring.
- CRUD hosts consume the dynamic-form submit contract; they should not redefine local/transient field filtering.
Table Minimum
For @praxisui/table, answer differently depending on local vs remote mode:
- Local minimum: pass local
dataand/orconfig; no remote schema bootstrap is required. - Remote minimum:
resourcePathis the canonical lightweight entry point, as long as the host already provides the Praxis API/CRUD wiring needed by the table runtime.
Important guardrails:
resourcePathis enough for the remote bootstrap only when the host wiring is already present.- Without effective
resourcePath, the table does not enter the remote schema/data flow. - In remote mode, the table derives columns from
/schemas/filteredand data from the backend resource/filter contract. - Optional collection operations, including export, are not implied by remote bootstrap. Gate them through backend
capabilitiesand_links.
CRUD Minimum
For @praxisui/crud, do not describe the minimum as "table plus resourcePath". CRUD is a
composed runtime with table, form launcher, action resolution, capabilities, and optional
modal/drawer form contracts.
- Local/static minimum: pass
metadatawith local resource/data/table/form structure sufficient for the desired static display or hosted example. This does not prove backend action availability. - Remote resource minimum: pass
metadata.resource.pathand ensure the host provides the Praxis API/CRUD wiring. The runtime can use the resource path for table/schema/data flows, but create, view, edit, delete, and collection workflows must still be aligned with resource capabilities and HATEOAS links. - Explicit form-action minimum: when a modal/drawer action uses backend-published surfaces or a
non-generic operation, provide
metadata.actions[].form.schemaUrl,submitUrl, andsubmitMethodinstead of relying on a generic fallback frommetadata.resource.path. - Nested or contextual resource minimum: use
metadata.resource.schemaPathwhen schema discovery needs the canonical schema template whilemetadata.resource.pathtargets a concrete nested collection.
Host requirements:
- effective API endpoint/CRUD service configuration
- dynamic-form dependencies for opened forms
- table dependencies for the embedded collection surface
- resource capabilities resolvable before claiming action availability
Answer "is resourcePath enough?" for CRUD as: enough only to enter a basic remote resource flow when host wiring exists; not enough to prove action permissions, export, modal form endpoints, or nested schema binding.
Collection Operation Minimums
For collection operations reused by Table, List, or future collection components, separate render/data bootstrap from operation availability:
resourcePathcan be enough to enter remote data mode, but it is not proof that a resource supports export or another optional collection action.- Treat
capabilities.canonicalOperations.<operation>and matching HATEOAS links as the availability contract. - For collection export specifically, require
canonicalOperations.export === trueor_links.exportbefore telling a host to expose export UI. - Do not infer export support from a generic base route such as
POST /{resource}/export; the service must opt in.
For @praxisui/table, use praxis-table-runtime-data when the minimum involves local/remote data mode, renderers, selection, export, analytics, or runtime observations. Use praxis-table-filter-actions when the question involves filters, toolbar actions, row actions, bulk actions, global actions, or export availability. Use praxis-table-authoring-settings when the minimum includes customization or Settings Panel support.
For @praxisui/list, use praxis-list-runtime-data when the minimum involves local versus remote data precedence, dataSource.data, dataSource.resourcePath, query context, selection, item actions, templating, skin, export, grouping, or declared-only runtime boundaries. Use praxis-list-authoring-settings when customization or Settings Panel support is part of the minimum, and praxis-list-docs-evidence before promoting list examples or docs as canonical behavior.
Entity Lookup Minimum
For entityLookup, separate render bootstrap from governed backend semantics:
- Local/manual minimum: a host can pass metadata and options directly for a local field.
- Remote generic minimum:
resourcePathplus generic/options/filtercan feed select-like controls, but it is not a governed entity lookup contract. - Governed backend minimum: a business entity lookup should be published as
x-ui.optionSource.type = RESOURCE_ENTITYwith a named/option-sources/{sourceKey}/options/filterendpoint and matching/by-idsrehydration.
When a question asks whether resourcePath alone is enough, answer: enough only for lightweight
remote bootstrap when host wiring exists; not enough for a canonical governed entity lookup.
Required Workflow
- Identify the target component and whether the question is local-only, remote metadata-driven, or authoring/customizable.
- Identify the minimum runtime inputs required for that mode.
- Identify where metadata comes from in that mode.
- Identify what the host must already provide.
- Answer explicitly whether
resourcePathis sufficient, optional, or not the preferred canonical path. - If the question involves an optional collection action, identify the capability or link that proves availability.
- If the target is composed, such as CRUD, map the minimum of each embedded runtime instead of collapsing the answer to the outer component input.
For @praxisui/dynamic-form, use praxis-form-runtime-submit when the minimum involves schema metadata, runtime mode, submit payload, local/transient fields, or hooks/actions. Use praxis-form-layout-canvas when the minimum involves schema-driven layout, visual blocks, compact presentation, grouped command forms, or canvas. Use praxis-form-authoring-settings when customization or Settings Panel support is part of the minimum. (In external projects, read companion skills from ~/.gemini/praxis-skills/<skill-name>/SKILL.md or $CODEX_HOME/skills/<skill-name>/SKILL.md when not already listed in active <skills>.)
Required Output Shape
When answering, prefer this structure:
- minimum local path
- minimum remote/schema-driven path
- metadata source
- host requirements
- whether
resourcePathalone is enough
High-Risk Failure Modes
- answering with a single "minimum" when the component has distinct local and remote modes
- claiming
resourcePathis always the canonical answer fordynamic-form - claiming a component is metadata-driven without naming the metadata source
- omitting host requirements for API/CRUD wiring
- confusing runtime bootstrap with editor/authoring requirements
- assuming Table/List export is available because a base controller route exists
- treating generic
/options/filterorresourcePathas equivalent to a governedRESOURCE_ENTITYoption source - treating CRUD as a thin table wrapper and omitting
metadata.actions[].form, capabilities, row links, ormetadata.resource.schemaPathwhen those are the contracts that make the runtime safe
References
Load only what you need:
references/dynamic-form-minimums.mdreferences/table-minimums.mdreferences/metadata-sources.md