chore(quantic): creation of new managing quantic components skill#7596
chore(quantic): creation of new managing quantic components skill#7596mmitiche wants to merge 9 commits into
Conversation
|
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
Important Testing in progress…🟢 UI Tests: 366 tests unchanged |
|
Tip All tests passed and all changes approved!🟢 UI Tests: 366 tests unchanged |
@coveo/atomic
@coveo/atomic-hosted-page
@coveo/atomic-legacy
@coveo/atomic-react
@coveo/auth
@coveo/bueno
@coveo/create-atomic
@coveo/create-atomic-component
@coveo/create-atomic-component-project
@coveo/create-atomic-result-component
@coveo/create-atomic-rollup-plugin
@coveo/headless
@coveo/headless-react
@coveo/shopify
commit: |
There was a problem hiding this comment.
Pull request overview
Adds a new agent skill managing-quantic-components under .agents/skills/ documenting conventions, lifecycle, UI patterns, accessibility, docs, and testing rules for Quantic LWC components, and whitelists the spelling of onquantic in cspell.
Changes:
- New
SKILL.mdwith quick reference, conventions table, ordering rules, Definition of Done, and progressive-disclosure links to three reference files. - Three reference docs covering headless integration/lifecycle, UI/label/event patterns, and docs/accessibility/testing.
.cspell.jsonupdated to allowonquantic(used in LWC event-listener attribute examples).
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| .agents/skills/managing-quantic-components/SKILL.md | Top-level skill entry with conventions, ordering, DoD, and references. |
| .agents/skills/managing-quantic-components/references/headless-and-lifecycle.md | Scaffolding, headless integration, error handling, Bueno, store registration. |
| .agents/skills/managing-quantic-components/references/ui-patterns.md | Labels (i18n/pluralization), template directives, CSS, events, multi-template. |
| .agents/skills/managing-quantic-components/references/docs-accessibility-testing.md | JSDoc requirements, AriaLiveRegion accessibility, testing strategy. |
| .cspell.json | Whitelists onquantic token used in event-listener attribute examples. |
|
|
||
| ### Documentation Requirements | ||
|
|
||
| Quantic reference docs are generated from component JSDoc. Every component class and `@api` property must be documented. See the full rules, valid categories, and code templates in **Section 8** of `references/quantic-component-workflow.md`. |
| For the testing strategy rationale, see [packages/quantic/decisions/0001-testing-strategy.md](../../../decisions/0001-testing-strategy.md). | ||
|
|
||
| - **Jest unit tests** — Isolated component behavior, rendering, lifecycle, and headless interactions with mocks. When writing tests, examine an existing test file for a similar component and follow its mock scaffolding, selector patterns, and assertion style. | ||
| - **Playwright E2E tests** — Real user workflows, analytics, API interactions, and Salesforce integration. See [packages/quantic/docs/adding-tests.md](../../../docs/adding-tests.md) for the full walkthrough. |
erocheleau
left a comment
There was a problem hiding this comment.
lgtm, just a bit weird the cspell.json file?
| * @fires quantic__eventname | ||
| * @slot slot-name - Description of the slot. | ||
| * @example | ||
| * <c-quantic-component-name engine-id={engineId} with-toggle></c-quantic-component-name> |
There was a problem hiding this comment.
Do you know if we need to specify that the names are always using kebab-case etc?
| .generated-answer__card-header { } | ||
| ``` | ||
|
|
||
| ### Custom properties (SLDS design tokens) |
There was a problem hiding this comment.
I would perhaps add that we should always include a fallback whenever we're using a SLDS design token, because they're not always available everywhere?
|
|
||
| ## Multi-Template Components | ||
|
|
||
| Components with multiple visual states override `render()`: |
There was a problem hiding this comment.
Not sure about the "multiple visual states" ?
But if an agent understands it then it's okay I guess
| ### Testing Strategy | ||
|
|
||
| Follow the package split: | ||
|
|
||
| - Jest unit tests verify isolated component behavior, rendering, lifecycle, and Headless interactions with mocks | ||
| - Playwright E2E tests verify real user workflows, analytics, API interactions, accessibility flows, and Salesforce integration behavior | ||
|
|
||
| Do not duplicate upstream Headless coverage unless the Quantic component adds behavior on top. |
There was a problem hiding this comment.
I think this is duplicated under the ui-patterns.md file?
| "στόμα", | ||
| "onquantic" |
There was a problem hiding this comment.
The spell check pre-commit hook was telling me onquantic was a typo preventing my commit, so I added it to this list of recognized words.
| Before marking any task as complete, verify every applicable item and output this table: | ||
|
|
||
|
|
||
| | Check | Status | |
There was a problem hiding this comment.
should we add a check in the list for accessibility related stuff?
SimonMilord
left a comment
There was a problem hiding this comment.
Looks good and exhaustive. Just wondering any use in having the AI use the sf cli commands for example to create a initial boilerplate component or do we want to leave it to the LLM to manage that on its own?
SFINT-6773
Summary
This PR adds the managing-quantic-components agent skill following the Agent Skills format
The skill is structured with progressive disclosure, a compact
SKILL.mdfor quick reference, and three focused reference files loaded only when needed:SKILL.md(~160 lines): Non-negotiable conventions table, canonical file ordering, directory layout, Definition of Done checklist, and working workflowheadless-and-lifecycle.md: Scaffolding, headless engine integration, error handling, Bueno validation, store registration, shared utilitiesui-patterns.md: Label management (including i18n, pluralization, translations), template directives, CSS/SLDS patterns, event dispatch/listening, multi-template renderingdocs-accessibility-testing.md: JSDoc documentation requirements, AriaLiveRegion accessibility, testing strategyWhat's next
This is the first iteration, we'll refine the skill as we observe how agents use it in practice. One planned improvement is extracting a dedicated testing skill (Jest unit tests + Playwright E2E) to keep this skill focused on component authoring and avoid overcrowding it.