day1-onboarding▌
ai-native-camp/camp-2 · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Interactive onboarding guide for Claude Code fundamentals using a structured two-phase learning protocol.
- ›Guides learners through 5 blocks (Setup, Experience, Why, What, Basics) covering CLI, terminal, git, and Claude Code's core features
- ›Enforces strict two-phase progression: Phase A explains concepts and prompts hands-on execution, then stops; Phase B delivers quizzes and feedback after learner confirmation
- ›Includes 7 independent feature modules (Memory, Context, Streaming, Subagen
Day 1: Onboarding
이 스킬이 호출되면 아래 STOP PROTOCOL을 반드시 따른다.
STOP PROTOCOL — 절대 위반 금지
이 프로토콜은 이 스킬의 최우선 규칙이다. 아래 규칙을 위반하면 수업이 망가진다.
각 블록은 반드시 2턴에 걸쳐 진행한다
┌─ Phase A (첫 번째 턴) ──────────────────────────────┐
│ 1. references/에서 해당 블록 파일의 EXPLAIN 섹션을 읽는다 │
│ 2. 기능을 설명한다 │
│ 3. references/에서 해당 블록 파일의 EXECUTE 섹션을 읽는다 │
│ 4. "지금 직접 실행해보세요"라고 안내한다 │
│ 5. ⛔ 여기서 반드시 STOP. 턴을 종료한다. │
│ │
│ ❌ 절대 하지 않는 것: 퀴즈 출제, QUIZ 섹션 읽기 │
│ ❌ 절대 하지 않는 것: AskUserQuestion 호출 │
│ ❌ 절대 하지 않는 것: "실행해봤나요?" 질문 │
└──────────────────────────────────────────────────────────┘
⬇️ 사용자가 돌아와서 "했어", "완료", "다음" 등을 입력한다
┌─ Phase B (두 번째 턴) ──────────────────────────────┐
│ 1. references/에서 해당 블록 파일의 QUIZ 섹션을 읽는다 │
│ 2. AskUserQuestion으로 퀴즈를 출제한다 │
│ 3. 정답/오답 피드백을 준다 │
│ 4. 다음 블록으로 이동할지 AskUserQuestion으로 묻는다 │
│ 5. ⛔ 다음 블록을 시작하면 다시 Phase A부터. │
└──────────────────────────────────────────────────────────┘
핵심 금지 사항 (절대 위반 금지)
- Phase A에서 AskUserQuestion을 호출하지 않는다 — 설명 + 실행 안내 후 바로 Stop
- Phase A에서 퀴즈를 내지 않는다 — QUIZ 섹션은 Phase B에서만 읽는다
- Phase A에서 "실행해봤나요?"를 묻지 않는다 — 사용자가 먼저 말할 때까지 기다린다
- 한 턴에 EXPLAIN + QUIZ를 동시에 하지 않는다 — 반드시 2턴으로 나눈다
공식 문서 URL 출력 (절대 누락 금지)
모든 블록의 Phase A 시작 시, 해당 reference 파일 상단의 > 공식 문서: URL을 반드시 그대로 출력한다.
📖 공식 문서: [URL]
- reference 파일에 URL이 여러 개 있으면 전부 출력한다
- URL을 요약하거나 생략하지 않는다
- 참가자가 직접 클릭해서 공식 문서를 볼 수 있어야 한다
Phase A 종료 시 필수 문구
Phase A의 마지막에는 반드시 아래 형태의 문구를 출력하고 Stop한다:
---
👆 위 내용을 직접 실행해보세요.
실행이 끝나면 "완료" 또는 "다음"이라고 입력해주세요.
이 문구 이후에 어떤 도구 호출(AskUserQuestion 포함)이나 추가 텍스트도 출력하지 않는다.
블록 특수 규칙
- Block 0 (Setup): 퀴즈 없음. Phase A에서 설명+실행 안내 → Stop. Phase B에서 완료 확인만.
- Block 1 (Experience): Phase A에서 3가지 데모 안내 → Stop. Phase B에서 체험 소감 확인.
- Block 2 (Why): Phase A에서 Quiz 1 출제 → 피드백 → Stop. Phase B에서 Quiz 2 + 영상 안내.
- Block 3 (What): 7개 기능 각각이 독립 블록. 3-1부터 3-7까지 각각 Phase A → Phase B.
- Block 3-Break (쉬어가기): Phase A만 있고 Phase B 없음. 퀴즈 없음. 터미널 소개 + Status Line 설정 체험.
- Block 4 (Basics): Phase A에서 설명+실행 안내 → Stop. Phase B에서 퀴즈 3개 연속.
References 파일 맵
| 블록 | 파일 |
|---|---|
| Block 0 | references/block0-setup.md |
| Block 1 | references/block1-experience.md |
| Block 2 | references/block2-why.md |
| Block 3-1 ~ 3-4 | references/block3-1-memory.md ~ references/block3-4-subagent.md |
| Block 3-Break | references/block3-break.md (쉬어가기: 터미널 & Status Line) |
| Block 3-5 ~ 3-7 | references/block3-5-agent-teams.md ~ references/block3-7-plugin.md |
| Block 3 마무리 | references/block3-summary.md |
| Block 4 | references/block4-basics.md |
파일 경로는 이 SKILL.md 기준 상대경로다. 각 reference 파일은
## EXPLAIN,## EXECUTE,## QUIZ섹션으로 구성된다.
진행 규칙
- 한 번에 한 블록씩 진행한다
- "다음", "skip", 블록 번호/이름으로 이동한다
- Claude Code 관련 질문이 오면 claude-code-guide 에이전트(내장 도구)로 답변한다. 답변 후 사용자가 직접 따라할 수 있게 단계별로 안내하고, 질문할 때는 AskUserQuestion을 사용한다. 내장 에이전트 답변이 부정확하다고 판단되면, 공식 문서를
curl로 파일에 저장한 뒤 Read 툴로 꼼꼼히 읽고 정확한 정보로 다시 답한다 (WebFetch는 요약/손실 위험이 있으므로 사용하지 않는다) - Block 3-4(Subagent) 완료 후 → Block 3-Break(쉬어가기) → Block 3-5(Agent Teams)로 이어진다
- Block 3의 7개 기능이 모두 끝나면
references/block3-summary.md를 읽고 관계도를 보여준다
시작
스킬 시작 시 아래 테이블을 보여주고 AskUserQuestion으로 어디서 시작할지 물어본다.
| Block | 주제 | 내용 |
|---|---|---|
| 0 | Setup | 첫 실행 설정 + 에디터 |
| 1 | Experience | Working Backward 데모 3가지 |
| 2 | Why | 왜 CLI? 왜 터미널? (퀴즈 2개) |
| 3 | What | 7개 기능 소개 |
| 4 | Basics | CLI + git + GitHub (퀴즈 3개) |
AskUserQuestion({
"questions": [{
"question": "어디서부터 시작할까요?",
"header": "시작 블록",
"options": [
{"label": "Block 0: Setup", "description": "첫 실행 설정 + 에디터"},
{"label": "Block 1: Experience", "description": "Working Backward 데모 3가지"},
{"label": "Block 2: Why", "description": "왜 CLI? 왜 터미널?"},
{"label": "Block 3: What", "description": "7개 기능 소개"}
],
"multiSelect": false
}]
})
시작 블록 선택 후 → 해당 블록의 Phase A부터 진행한다.
How to use day1-onboarding on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add day1-onboarding
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches day1-onboarding from GitHub repository ai-native-camp/camp-2 and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate day1-onboarding. Access the skill through slash commands (e.g., /day1-onboarding) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★66 reviews- ★★★★★Ava Yang· Dec 28, 2024
day1-onboarding has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ganesh Mohane· Dec 24, 2024
Useful defaults in day1-onboarding — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Lucas White· Dec 20, 2024
day1-onboarding has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Lucas Jackson· Dec 12, 2024
We added day1-onboarding from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Meera White· Dec 12, 2024
day1-onboarding reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Naina Khanna· Dec 12, 2024
Solid pick for teams standardizing on skills: day1-onboarding is focused, and the summary matches what you get after install.
- ★★★★★Ava Chawla· Nov 19, 2024
day1-onboarding fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Sakura Choi· Nov 11, 2024
day1-onboarding fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ava Bhatia· Nov 3, 2024
Solid pick for teams standardizing on skills: day1-onboarding is focused, and the summary matches what you get after install.
- ★★★★★Naina Malhotra· Nov 3, 2024
day1-onboarding is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 66