vercel-labs/agent-skills
Vercel's official collection of agent skills
https://skillcdn.ai/gh/vercel-labs/agent-skills내 AI에 이 주소를 연결하면 이 스킬들을 쓸 수 있어요. 연결 방법 보기
- 미확인
- 기본 브랜치
main - 커밋
1a2c79d - 라이선스
선언되지 않음 - 검색단어와 의미
저장소 둘러보기
스킬과 문서의 원문에서 단어와 의미로 찾습니다. 화면용 번역은 검색되지 않아요.
문서
- SectionsThis file defines all sections, their ordering, impact levels, and descriptions. The section ID (in parentheses) is the filename prefix used to group rules.skills/composition-patterns/rules/_sections.md
- Rule Title HereBrief explanation of the rule and why it matters.skills/composition-patterns/rules/_template.md
- Avoid Boolean Prop ProliferationDon't add boolean props like isThread, isEditing, isDMThread to customize component behavior. Each boolean doubles possible states and creates unmaintainable conditional logic. Use composition instea…skills/composition-patterns/rules/architecture-avoid-boolean-props.md
- Use Compound ComponentsStructure complex components as compound components with a shared context. Each subcomponent accesses shared state via context, not props. Consumers compose the pieces they need.skills/composition-patterns/rules/architecture-compound-components.md
- Prefer Composing Children Over Render PropsUse children for composition instead of renderX props. Children are more readable, compose naturally, and don't require understanding callback signatures.skills/composition-patterns/rules/patterns-children-over-render-props.md
- Create Explicit Component VariantsInstead of one component with many boolean props, create explicit variant components. Each variant composes the pieces it needs. The code documents itself.skills/composition-patterns/rules/patterns-explicit-variants.md
- React 19 API ChangesIn React 19, ref is now a regular prop (no forwardRef wrapper needed), and use() replaces useContext().skills/composition-patterns/rules/react19-no-forwardref.md
- Define Generic Context Interfaces for Dependency InjectionDefine a generic interface for your component context with three parts: state, actions, and meta. This interface is a contract that any provider can implement—enabling the same UI components to work…skills/composition-patterns/rules/state-context-interface.md
- Decouple State Management from UIThe provider component should be the only place that knows how state is managed. UI components consume the context interface—they don't know if state comes from useState, Zustand, or a server sync.skills/composition-patterns/rules/state-decouple-implementation.md
- Lift State into Provider ComponentsMove state management into dedicated provider components. This allows sibling components outside the main UI to access and modify state without prop drilling or awkward refs.skills/composition-patterns/rules/state-lift-state.md
제외됨 (2)
아래 매니페스트는 제공되지 않았습니다. 수정해서 푸시하면 다음 커밋부터 다시 색인됩니다.
skills/react-best-practices/AGENTS.mdlink_missing3 links name no file of the repository (./async-defer-await.md, ./async-cheap-condition-before-await.md, ./server-hoist-static-io.md)skills/react-view-transitions/AGENTS.mdlink_missing20 links name no file of the repository (css-recipes.md, css-recipes.md#persistent-element-isolation, css-recipes.md#backdrop-blur-workaround, ...)