Autocomplete

Autocomplete is derived from configured semantic domains rather than learned from runtime source usage:

PikaCSS no longer has a global autocomplete configuration or runtime appendAutocomplete() pool. Each semantic subsystem owns the Typegen information it can describe correctly.

Generated authoring state is always published as <stateDir>/pika.gen.ts. Run pikacss prepare before standalone editor/typecheck/ESLint workflows and include that declaration in your TypeScript project.

Selector and shortcut concrete members

Static selector and shortcut names are deterministic concrete members by definition. Dynamic selector and shortcut definitions use two complementary fields:

inputType: raw TypeScript describing the full accepted dynamic input family.
autocomplete: deterministic concrete values that receive named completion members.

For both static members and accepted dynamic autocomplete members, Core attempts to generate a resolved PikaCSS Preview for Typegen/IDE hover documentation. Authored description text is additive and appears before the preview. A preview-only resolution failure is diagnosed without removing the concrete Typegen member.

selectors: {
  definitions: [
    {
      pattern: /^state-(.+)$/,
      inputType: '`state-${string}`',
      resolve: match => `$[data-state="${match[1]}"]`,
      autocomplete: ['state-open', 'state-closed'],
    },
  ],
}

Concrete members come from project/plugin configuration or deterministic catalogs. Their previews follow the runtime selector/style-item transform order while remaining provisional: preview hooks use isolated plugin state, do not commit atomic style IDs, and do not teach runtime resolver caches. If plugin state cannot be isolated safely, preview generation degrades for that member and reports a diagnostic without removing the member or its authored description. PikaCSS does not learn Typegen members from transformed application usages.

Variable suggestions

Variables use leaf-local suggest metadata:

variables: {
  definitions: {
    '--brand-color': {
      value: '#3b82f6',
      suggest: {
        asProperty: true,
        asValueOf: ['color', 'backgroundColor'],
      },
    },
  },
}

Plugin Typegen

Plugins contribute authoring declarations through the owner-bound engine.typegen capability during configureEngine, or preferably lower semantic definitions into an existing Core subsystem in configureRawConfig so that subsystem owns Typegen and runtime behavior together.

There is no supported manual PikaAugment.Autocomplete, DefineAutocomplete, or runtime .add() compatibility path.

Suggestions are not arbitrary runtime validation

Generated types describe configured semantic members and supported static authoring. They do not make PikaCSS a runtime validator and they do not authorize runtime-dynamic pika() arguments. Compiler/ESLint static-usage rules remain authoritative for source legality.

Examples

autocomplete.example.ts

import { defineEngineConfig } from '@pikacss/core'

export const autocompleteConfig = defineEngineConfig({
	selectors: {
		definitions: [
			{
				pattern: /^state-(.+)$/,
				inputType: '`state-${string}`',
				resolve: match => `$[data-state=\"${match[1]}\"]`,
				autocomplete: ['state-open', 'state-closed'],
			},
		],
	},
	variables: {
		definitions: {
			'--brand-color': {
				value: '#3b82f6',
				suggest: { asValueOf: 'color' },
			},
		},
	},
})

Autocomplete ​

Selector and shortcut concrete members ​

Variable suggestions ​

Plugin Typegen ​

Suggestions are not arbitrary runtime validation ​

Examples ​