Interactive onboarding guide for Claude Code fundamentals using a structured two-phase learning protocol.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionday1-onboardingExecute the skills CLI command in your project's root directory to begin installation:
Fetches day1-onboarding from ai-native-camp/camp-2 and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate day1-onboarding. Access via /day1-onboarding in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
14
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
14
stars
이 스킬이 호출되면 아래 STOP PROTOCOL을 반드시 따른다.
이 프로토콜은 이 스킬의 최우선 규칙이다. 아래 규칙을 위반하면 수업이 망가진다.
┌─ 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 시작 시, 해당 reference 파일 상단의 > 공식 문서: URL을 반드시 그대로 출력한다.
📖 공식 문서: [URL]
Phase A의 마지막에는 반드시 아래 형태의 문구를 출력하고 Stop한다:
---
👆 위 내용을 직접 실행해보세요.
실행이 끝나면 "완료" 또는 "다음"이라고 입력해주세요.
이 문구 이후에 어떤 도구 호출(AskUserQuestion 포함)이나 추가 텍스트도 출력하지 않는다.
| 블록 | 파일 |
|---|---|
| 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섹션으로 구성된다.
curl로 파일에 저장한 뒤 Read 툴로 꼼꼼히 읽고 정확한 정보로 다시 답한다 (WebFetch는 요약/손실 위험이 있으므로 사용하지 않는다)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부터 진행한다.
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
day1-onboarding has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in day1-onboarding — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
day1-onboarding has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added day1-onboarding from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
day1-onboarding reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: day1-onboarding is focused, and the summary matches what you get after install.
day1-onboarding fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
day1-onboarding fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: day1-onboarding is focused, and the summary matches what you get after install.
day1-onboarding is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 66