Conversation
Installable plugin that helps developers consume lime-elements to build UIs. Bundles distilled design system knowledge and component guidance as self-contained reference docs, with four auto-triggering skills: - build: scaffold UIs with correct design system conventions - component-guide: look up components, props, and usage patterns - design-review: audit code against color, sizing, shadow, and interaction pattern rules - accessibility: WCAG 2.1 AA audit with lime-elements-specific checks References cover ~50 public components, the full color system, 4x sizing rhythm, shadow variables, declutter philosophy, and interaction patterns (switch vs checkbox, disabled vs readonly, action buttons). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add orchestration agent (ui-assistant) that coordinates component selection, build, design review, and accessibility audit phases. Add quick-start.md reference with verified standalone HTML loading patterns (local dev, unpkg CDN, npm dist), required setup (limel-config, z-index variables, dark mode), and a complete minimal working example. Update build skill to ask Stencil vs standalone HTML and reference quick-start.md for the correct loading boilerplate. Add prerequisites section to component-catalog.md. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Tip You can customize the tone of the review comments and chat replies.Configure the |
|
Documentation has been published to https://lundalogik.github.io/lime-elements/versions/PR-3965/ |
| ## Steps | ||
|
|
||
| 1. **Read the reference docs:** | ||
| - `${CLAUDE_PLUGIN_ROOT}/references/design-system.md` |
There was a problem hiding this comment.
I know this is a draft so I won't go through it with a fine-toothed comb, but while quickly eyeing over the diff, I got to wondering if we really need to duplicate these guideline files that are already markdown files? Could we get close enough to the same result by simply copying the existing guideline files into the plugin directory at build-time, do we don't have to keep two separate files in sync?
If we can't, an alternative might be to set up a build-check that checks if any of the relevant files have been changed, and if they have, calls an AI to evaluate if the two corresponding files are still equivalent, or if one needs updating… 🤔
There was a problem hiding this comment.
I like that idea, will look into both options.
2 participants
@coderabbitai summary
Review:
Browsers tested:
(Check any that applies, it's ok to leave boxes unchecked if testing something didn't seem relevant.)
Windows:
Linux:
macOS:
Mobile: