Skip to content

Commit 3a3f169

Browse files
authored
Merge branch 'main' into feat/add-llms
2 parents 19dbfc4 + 003171c commit 3a3f169

3 files changed

Lines changed: 55 additions & 0 deletions

File tree

component-library/.cursorrules

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
AGENTS.md

component-library/AGENTS.md

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
You are an expert in TypeScript, Vite, Vue.js, Tailwind, and PrimeVue wrappers, with strong focus on maintainability, API consistency, and performance.
2+
3+
## Scope And Priority
4+
5+
- These instructions apply to work in component-library, especially src and docs.
6+
- If instructions conflict, use this order:
7+
8+
1. System or developer instructions
9+
2. This AGENTS.md file
10+
3. Task-level preferences
11+
12+
## Project Context
13+
14+
- This library wraps PrimeVue components.
15+
- PrimeVue docs: https://primevue.org/
16+
- PrimeVue source: https://github.com/primefaces/primevue
17+
18+
## Implementation Rules
19+
20+
- Write concise, maintainable, technically accurate TypeScript.
21+
- Prefer modularization and iteration to keep code DRY.
22+
- Keep code readable and easy to review.
23+
- Follow existing patterns and naming in the codebase.
24+
- If a requirement is ambiguous, ask one concise clarifying question before implementing.
25+
- Use Vue Composition API with script setup.
26+
- Place the script section above the template section.
27+
28+
## Vue Template Conventions
29+
30+
- In templates, use auto-unwrapped refs and props.
31+
32+
## Component Placement
33+
34+
- Put fully custom components in src/components/custom.
35+
- Put wrappers around PrimeVue components in src/components/wrapped.
36+
- Wrapper components should reuse and extend PrimeVue types where possible.
37+
- Wrapper components should keep the PrimeVue API as close as possible so PrimeVue docs remain useful to consumers.
38+
39+
## Storybook And Styling
40+
41+
- Put Storybook preview-only styles in .storybook.
42+
- Use Tailwind for component styling.
43+
- Build responsive UIs with a mobile-first approach.
44+
45+
## Validation Before Finalizing
46+
47+
- When code is changed, run pnpm lint and address issues related to the change.
48+
- When relevant tests exist for touched code, run the smallest relevant test set and address issues related to the change.
49+
50+
## Response Style
51+
52+
- Keep responses concise and practical.
53+
- Explain what changed, why, and which files were affected.

component-library/CLAUDE.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
AGENTS.md

0 commit comments

Comments
 (0)