research
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
소스 정보
- 저장소
- NVIDIA/multi-storage-client
- 최근 소스 활동
- 2026년 9월 9일 18:30
- 감지된 SKILL.md 언어
- 영어
- 스타
- 87
- 포크
- 28
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- research
- description
- Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
- invocable
- auto
# Research
Research the problem space before designing or implementing a feature to avoid reinventing the wheel and catch issues early.
## When to Use
- Starting a new feature or significant enhancement.
- Working with unfamiliar APIs, cloud SDKs, or library internals.
- User explicitly asks to research or investigate an approach.
## Workflow
### 1. Clarify scope
Confirm with the user:
- What problem are we solving?
- Which language layers are involved (Python, Rust)?
- Any known constraints or preferences?
### 2. Research comparable solutions
Search for:
- How other multi-cloud storage libraries solve the same problem.
- Best practices for the relevant cloud SDKs (AWS S3, GCS, Azure, OCI).
- Known pitfalls or breaking changes in upstream dependencies.
- PyO3/maturin patterns (if Rust bindings are involved).
### 3. Check upstream
Look for:
- Recent releases of relevant dependencies.
- Open issues or PRs related to the feature area.
- Deprecation notices.
### 4. Produce a summary
Output using this format:
```markdown
## Research Summary: <topic>
### Approaches Found
- <approach 1>: <trade-offs>
- <approach 2>: <trade-offs>
### Recommendation
- <recommended approach with rationale>
### Risks / Blockers
- <anything that could derail implementation>
### References
- <links to docs, issues, examples>
```
GitHub에서 보기