Quickstart

---
context: fork
name: quickstart
description: "Interactive first-run quickstart guide with project type detection and command suggestions for new user onboarding. Use when user says quickstart, getting started, first run, new project, onboarding, welcome, or setup, or needs help navigating available commands for the first time."
lang: [en]
platforms: [claude-code]
level: 1
triggers:
  - "quickstart"
  - "getting started"
  - "first run"
  - "new project"
  - "onboarding"
  - "welcome"
  - "setup"
agents:
  - "orchestrator"
argument-hint: "[project-type] e.g., node, python, rust, go"
tokens: "~1K"
category: "onboarding"
source_hash: 66cdaeca
whenNotToUse: "Returning users with an established project context; do not re-run the quickstart guide when the user has already completed onboarding and is working on an existing task."
---

# Interactive Quickstart Guide

Use `$ARGUMENTS` to specify the project type for targeted quickstart guidance.

> **Plain-language onboarding (P3-7/8)**: On first run, call `detectSkillLevel()` from `lib/core/user-profile.js`. If it returns `novice` (default), offer to enable plain-language mode by setting `ux.plainLanguage.enabled = true` and `ux.skillLevel = "auto"` in `artibot.config.json`. Every subsequent status message will then be passed through `toPlainLanguage()` (see `lib/core/plain-language.js`) so beginners see friendly Korean/English phrasing while experts keep the terse developer output. The detection auto-promotes to `pro` once ~10 slash-commands or jargon-dense prompts accumulate — no explicit toggle needed for most users.

## When This Skill Applies
- First time a user interacts with Artibot in a new project
- User explicitly asks for help getting started
- New project onboarding and setup guidance needed
- User is unfamiliar with available commands

## Core Guidance

### 1. Project Detection
Scan the current working directory for configuration files to determine the project type:
- `package.json` -> Node.js (suggest: load, analyze, implement)
- `pyproject.toml` -> Python (suggest: load, analyze, test)
- `Cargo.toml` -> Rust (suggest: load, analyze, build)
- `go.mod` -> Go (suggest: load, analyze, test)
- `pom.xml` / `build.gradle` -> Java (suggest: load, analyze, build)

### 2. Command Suggestions
Suggest the 3 most relevant commands based on detected project type. Always include `/sc load` as the first recommendation.

### 3. Welcome Message
Display a clear, formatted welcome message with:
- Detected project type
- Three recommended commands
- Quick tips for navigation

## Quick Reference

| Project | Config File | Top Commands |
|---------|-------------|-------------|
| Node.js | package.json | load, analyze, implement |
| Python | pyproject.toml | load, analyze, test |
| Rust | Cargo.toml | load, analyze, build |
| Go | go.mod | load, analyze, test |
| Java | pom.xml | load, analyze, build |

## Rationalizations

The following table captures common excuses agents make to skip the rigor of this skill, paired with factual rebuttals.

| Excuse | Rebuttal |
|--------|----------|
| "I will figure it out from the docs" | docs scatter across files; quickstart is the sequenced path to first success |
| "quickstart is for beginners only" | quickstart is the regression test for onboarding — experts use it to validate setup too |
| "our tool is too complex for quickstart" | if you cannot write a quickstart, new users cannot start — that is a product bug |
| "I will skip the detection step" | project detection is what makes quickstart personalized — skipping it gives generic advice |
| "screenshots will go stale" | so will your UX; update screenshots as a sign the quickstart is maintained |