📄 CodeRabbit inference engine (AGENTS.md)

**/*.{ts,tsx}: Use TypeScript and React for implementation
Use early returns to improve readability
Props and variable names use camelCase
Props naming: initialization as default + PropName (e.g., defaultValue)
Props naming: forceRender for forced render
Props naming: child force render as force + SubComponentName + Render
Props naming: child render as SubComponentName + Render
Props naming: dataSource for data source
Props naming: use open instead of visible for open state
Props naming: display-related as show + PropName
Props naming: capability as PropName + able
Props naming: disabled for disabled state
Props naming: extra for extra content
Props naming: icon for icon
Props naming: trigger for trigger elements
Props naming: className for CSS class
Event naming: on + EventName
Event naming: child component events on + SubComponentName + EventName
Event naming: before + EventName for pre events
Event naming: after + EventName for post events
Event naming: on + EventName + Complete for completion
Component token naming: variant(optional) + semantic parts + css property + size/disabled(optional)
Provide accurate TypeScript types for all components and functions
Avoid any; prefer precise types
Use interfaces instead of type aliases for object shapes
Export all public interface types
No TypeScript errors or warnings in compilation
Component props must be defined with interface named ComponentNameProps
Define component state interfaces like ComponentNameState where applicable
All callback types must declare parameter and return types explicitly
Use generics appropriately for flexibility
Use intersection types (&) to combine types when needed
Use literal union types for finite option sets
Avoid enum; prefer union types with as const
Prefer type inference; use assertions only when necessary

Files:

• components/list/style/index.ts

📄 CodeRabbit inference engine (AGENTS.md)

components/**/style/**/*.ts: Use @ant-design/cssinjs for styling
Keep each component’s styles under its style/ directory and mirror component structure
Name style generator functions as gen[ComponentName]Style
Prefer class selectors over tag selectors to increase specificity
Use Ant Design token system; avoid hardcoded colors, sizes, spacing
Component styles should be based on global and component-level tokens; propagate token changes downward
Component-level token naming: Component + property (e.g., buttonPrimaryColor)

Files:

• components/list/style/index.ts

📄 CodeRabbit inference engine (AGENTS.md)

components/**/style/**/*.{ts,tsx}: Support responsive layouts, dark mode, and RTL; prefer CSS logical properties (e.g., margin-inline-start)
Use CSS transitions for simple animations; use rc-motion for complex ones; respect prefers-reduced-motion; keep duration/easing consistent
Accessibility styling: visible focus states, adequate contrast, avoid color-only cues, support 200% zoom, avoid flicker

Files:

• components/list/style/index.ts