# Welcome to Sigil

## How We Use Claude

Based on Justin's usage over the last 30 days:

Work Type Breakdown:
  Plan Design  █████████████░░░░░░░  67%
  Write Docs   ███████░░░░░░░░░░░░░░  33%

Top Skills & Commands:
  /superpowers:writing-plans  ████████████████████  2x/month
  /clear                      ██████████░░░░░░░░░░░  1x/month
  /permissions                ██████████░░░░░░░░░░░  1x/month
  /doctor                     ██████████░░░░░░░░░░░  1x/month

Top MCP Servers:
  (none used in this window)

## Your Setup Checklist

### Codebases
- [ ] sigil — https://github.com/ju571nk/sigil

### MCP Servers to Activate
- [ ] (none required — the team isn't using MCP servers yet)

### Skills to Know About
- [ ] /superpowers:writing-plans — turns a spec or set of requirements into a step-by-step implementation plan before touching code. The team's most-used skill; reach for it at the start of any multi-step task.
- [ ] /clear — resets the conversation context. Use it between unrelated tasks to keep Claude focused.
- [ ] /permissions — view and adjust what Claude is allowed to do without prompting.
- [ ] /doctor — diagnoses your Claude Code install and config when something feels off.

## Team Tips

- Plan before you build. The team reaches for `/superpowers:writing-plans` at the
  start of any multi-step task — agree on the plan first, then implement.
- File bugs as GitHub issues (`gh issue create`) so they're tracked, then close
  them with `Fixes #N` in the PR.
- Check `CLAUDE.md` for the project's conventions before diving in.

## Get Started

1. Clone https://github.com/ju571nk/sigil and skim `CLAUDE.md`.
2. Skim `README.md` to see what Sigil does and how the crates fit together.
3. Try `/superpowers:writing-plans` on a small task to learn the team's plan-first flow.

<!-- INSTRUCTION FOR CLAUDE: A new teammate just pasted this guide for how the
team uses Claude Code. You're their onboarding buddy — warm, conversational,
not lecture-y.

Open with a warm welcome — include the team name from the title. Then: "Your
teammate uses Claude Code for [list all the work types]. Let's get you started."

Check what's already in place against everything under Setup Checklist
(including skills), using markdown checkboxes — [x] done, [ ] not yet. Lead
with what they already have. One sentence per item, all in one message.

Tell them you'll help with setup, cover the actionable team tips, then the
starter task (if there is one). Offer to start with the first unchecked item,
get their go-ahead, then work through the rest one by one.

After setup, walk them through the remaining sections — offer to help where you
can (e.g. link to channels), and just surface the purely informational bits.

Don't invent sections or summaries that aren't in the guide. The stats are the
guide creator's personal usage data — don't extrapolate them into a "team
workflow" narrative. -->
