agentic-component-authoring
Implement, change, or plan changes to components and primitives in packages/agentic/components, including every new component. Covers public APIs, slots, state, token styling, rendering, tests, and stories. Not for contract-only work, read-only reviews, v0/v1 maintenance, or the Storybook app toolchain.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.4k
- Forks
- 179
01 前言 Front Matter
- name
- agentic-component-authoring
- license
- MIT
- description
- Implement, change, or plan changes to components and primitives in packages/agentic/components, including every new component. Covers public APIs, slots, state, token styling, rendering, tests, and stories. Not for contract-only work, read-only reviews, v0/v1 maintenance, or the Storybook app toolchain.
03 SKILL.md 正文
Agentic component authoring
Build components in packages/agentic/components as React Native adaptations of the Fluent UI v9 component pattern.
New components always use this workflow; v0 and v1 are maintenance-only. This skill routes the work. Load only the
references the current change needs.
Choose the component kind
- Higher-order components live in
src/components. Read the package instructions and the higher-order component reference. The component'sSPEC.mdandspec/companions are its contract. - Primitives live in
src/primitives. Read the package instructions and the primitive reference. A primitive's colocatedCONTRACT.mdis its contract; primitives have no upstream-backedSPEC.md. - Changes spanning components, repeated helpers, or dependency boundaries also use the optimization skill. Do not audit the whole package for a small edit.
- Read-only reviews use review-component. Storybook application, native project, bundling, or CocoaPods work uses the Storybook skill.
- Native views, codegen, or registration also use the native component skill as an overlay.
Load focused references
| Work | Reference |
|---|---|
| Source interpretation, provenance, contract drafting, or divergences | Contract authoring |
| Public props, slots, state types, native prop exposure, or exports | Types and slots |
| Defaults, derived state, interaction hooks, accessibility, or slots | State and accessibility |
| Focus, focus visuals, keyboard activation, or native focus refs | Common focus authoring, then Windows/Win32 or macOS |
| Tokens, theme caching, state precedence, or slot style application | Styles and tokens and design tokens and styling |
| Pure slot rendering, component assembly, or display names | Rendering and assembly |
| Runtime tests, type tests, snapshots, Storybook stories, or validation | Tests and stories |
| Native React Native Windows Fabric components, codegen, registration, or UIA | Windows Fabric native components |
A new higher-order component normally needs the types, state, styles, rendering, and tests references, plus focus guidance when it is focusable. Load the Windows Fabric reference only for native Windows views. A focused fix loads only the affected reference and its immediate neighbors.
Workflow
For a plan-only request, follow steps 1 to 4 without editing, then return the planned contract revision, the references used, the implementation order, and the validation plan.
- Read the package instructions and the component's contract:
SPEC.md,spec/source.json, and every React Native companion it references for a higher-order component, orCONTRACT.mdfor a primitive. - Higher-order components: use an existing reviewed contract directly when its source evidence and requested behavior are unchanged. If the contract is absent, stale, still a draft, or accompanied by new source evidence, run the contract authoring workflow and complete its pre-code review gate first (R-AGENTIC-001 in the package instructions).
- Inspect the closest canonical implementation:
packages/agentic/components/src/components/buttonfor a styled higher-order component, orpackages/agentic/components/src/primitives/iconfor a direct primitive. - Establish the public contract before implementation: variants, slots, native props, accessibility, interaction states, and platform behavior.
- Implement in dependency order: types and slots, state and accessibility, styles and slot props, pure rendering, component assembly, and explicit exports.
- Preserve the contract. Record a genuine token or platform gap rather than substituting an unrelated value or web-only behavior.
- Add focused tests and stories that exercise the public API and the resolved native output.
- Reconcile and ratify the local contract against the realized public types, tests, stories, and platform evidence. Upstream changes require explicit re-review and never overwrite the local contract.
- Iterate with focused validation (R-VALID-004):
yarn test <component>from the package,yarn buildafter type changes, andyarn test --findRelatedTests <files>after editing shared code. Before handover, run the package format, lint, build, and whole test suite, the Storybook bundle for story changes, and the root build when public types, manifests, or project references change. Then runyarn clean-lage-cacheandyarn lage buildcionce as final acceptance (R-VALID-003) and report results truthfully (R-VALID-002).
Do not divide one component implementation into separate sub-agent or sub-skill phases. Its types, state, styling, and rendering form one contract and should remain in one implementation context.
04 同仓库更多 Skills
review-component
Review component code or changes of any generation (v0, v1, agentic, primitive, or native-backed) without editing files. Classifies each changed surface, applies the matching checklists and native overlay, and reports evidence-backed findings with validation status.
maintain-v0-v1-component
Fix or maintain existing v0 (foundation-compose) or v1 (framework compose/compressible) components, including their platform variants. Classifies the generation first and loads only its recipe. Not for new components, agentic components, read-only reviews, or native-only changes.
maintain-desktop-testing
Change, review, or plan source changes to desktop-driver, desktop-test, storybook-desktop, or storybook-desktop-runtime, including native helpers. Applies package invariants, documentation, native and consumer validation, and changesets.
implement-native-component
Implement or change native components, TurboModules, native services, codegen specs, or native-backed platform wrappers (Swift, Objective-C, C++/WinRT, podspecs, Windows projects). Also supplies the native overlay checklist for v0, v1, and agentic work. Not for Storybook toolchain failures.
fix-security-issues
Audit and remediate dependency security advisories while respecting package age policy, removing unused vulnerable capabilities, deduplicating Yarn resolutions, and validating affected tooling.
desktop-testing
Configure, run, or troubleshoot native desktop tests using desktop-test, desktop-driver, and storybook-desktop, including app targets and suites, helpers, permissions, WDIO suites, Storybook story tests and smoke runs, reports, and CI. Not for package source changes or the Storybook app build toolchain.