| name | component-field |
| description | Use when the user asks to generate, create, or scaffold a Field — accessible form field wrapper with label, hint, and error message association via aria-describedby. |
| disable-model-invocation | true |
| hint | Invoke explicitly via `/kit-add field`, `/kit-create` (then ask for a field), or call the `component-field` skill by name. Describe the label, hint text, error message, required flag, and which child input control (input/checkbox/select) the field wraps. |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion |
SKILL: component-field
Generate an fpkit-style accessible Field component directly into a developer's project.
Workflow
- Read the source doc. Prefer the neutral
field.component.md in this skill directory (the spec-driven source of truth). Read its ## Target: react adapter (Generation Contract on its generation: line, ## Props Interface, ## TSX Template), its ## Styles section, plus ## Accessibility and ## Examples. If field.component.md is absent, fall back to reference.md (canonical templates, Generation Contract, Props Interface, CSS Variables, Accessibility, Usage Examples). Both yield byte-identical output (golden-guarded).
- Init check — run
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/detect_target.py <cwd>. If foundation (ui.tsx) is missing, run Step A of ${CLAUDE_PLUGIN_ROOT}/skills/kit-core/SKILL.md to initialize it before generating this component.
- Dependencies — Field has no upstream dependencies (it is a leaf component). Skip dep resolution.
- Generate — apply the Generation Contract to produce:
<targetDir>/field.tsx from the ## TSX Template (under ## Target: react in field.component.md, or top-level in reference.md)<targetDir>/field.module.scss from the ## Styles section (field.component.md) or the ## SCSS Template section (reference.md)
Substitute {{IMPORT_SOURCE:...}}, {{NAME}}, {{FIELDS}} placeholders if present.
- Verify — run
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/verify_integration.py <projectRoot> and print the summary to the developer.
Reference
Templates and documentation live in field.component.md (the neutral spec-driven source) alongside this SKILL.md, with reference.md kept as the byte-identical fallback. The shared generation contract, accessibility patterns, SCSS conventions, and CSS variable strategy are documented in ${CLAUDE_PLUGIN_ROOT}/skills/kit-core/references/.
