# Init Project Light

> Use when you need to bootstrap a lightweight project with minimal structure.

- **Type:** Skill
- **Install:** `agentstack add skill-flonat-claude-research-init-project-light`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [flonat](https://agentstack.voostack.com/s/flonat)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [flonat](https://github.com/flonat)
- **Source:** https://github.com/flonat/claude-research/tree/main/skills/init-project-light

## Install

```sh
agentstack add skill-flonat-claude-research-init-project-light
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Init Project Light

> Lightweight project bootstrapper for small projects that don't need the full `/init-project-research` scaffold.

## When to Use

- Small document collections (proposals, applications, meeting notes)
- One-off or short-lived projects
- Projects without a code pipeline or Overleaf link
- When the user says "set up something light", "quick init", "organise this folder"
- Any project that doesn't warrant `/init-project-research`

## When NOT to Use — Escalate to `/init-project-research`

- Research papers targeting a journal or conference
- Projects with code, data, or computational pipelines
- Anything that needs Overleaf, git, or a vault atlas entry

---

## Phase 1: Scan

Read everything already in the directory before asking questions.

1. List all files and folders (excluding `.claude/`, `.DS_Store`)
2. Read text files (`.md`, `.tex`, `.bib`, `.txt`) to understand content — respect file size (skip files > 500 lines, note them)
3. Build a mental model: what is this project, what's the main output, who's involved?

**Goal:** Minimise interview questions by inferring answers from existing files.

---

## Phase 2: Interview (2-3 questions max)

Use `AskUserQuestion`. Only ask what you couldn't infer from Phase 1.

Pick from these (skip any you can already answer):

1. **What is this project?** — one sentence (e.g., "PhD research proposal for [University]")
2. **What's the main output?** — document, application, collection of notes, etc.
3. **Anyone else involved?** — names and roles if relevant

If Phase 1 gave you enough, confirm your understanding instead of asking:
> "From the files, this looks like [X]. The main output is [Y]. Correct?"

---

## Phase 3: Create CLAUDE.md

Follow the `lean-claude-md` rule. Include only:

1. **Project overview** — 2-3 sentences from interview/scan
2. **People** — if collaborators/supervisors exist
3. **Directory structure** — compact tree of what exists
4. **Conventions** — only if detectable (e.g., LaTeX compilation, bibliography style)
5. **Key context** — anything a future session needs to know immediately

**Do NOT include:**
- Detailed literature notes or reference lists
- Action items or timelines (those go to vault)
- Anything that duplicates global rules

---

## Phase 4: Organise (suggest, don't force)

Based on what's in the directory, **suggest** lightweight organisation. Present options and wait for approval.

### Standard suggestions

| Folder | When to suggest |
|--------|----------------|
| `to-sort/` | Multiple unsorted documents exist |
| `docs/` | Reference materials, guidelines, or background reading present |
| `archive/` | Old versions or abandoned drafts detected |

### Rules

- Never create more than 2-3 folders — this is a light project
- Never move files without explicit approval
- If the existing structure already makes sense, say so and skip this phase
- If there's a `.claude/settings.local.json`, leave it. If not, create one with standard permissions.

### Standard permissions (`.claude/settings.local.json`)

```json
{
  "permissions": {
    "allow": [
      "Bash(latexmk *)",
      "Bash(ls:*)",
      "Bash(mkdir:*)",
      "Bash(tree:*)",
      "Edit",
      "Glob",
      "Grep",
      "Read",
      "Write"
    ],
    "deny": []
  }
}
```

Only create if missing. Never overwrite existing permissions.

---

## Phase 5: Confirmation

Short report:

```
Set up lightweight project: 

Created:
  - CLAUDE.md
  - [any folders created]
  - [.claude/settings.local.json if created]

Skipped (use /init-project-research if needed later):
  - Git, Overleaf, vault atlas, code scaffold
```

---

## Cross-References

| Skill | Relationship |
|-------|-------------|
| `/init-project-research` | Escalate to this for full research projects |
| `/update-project-doc` | Run later to refresh CLAUDE.md if the project grows |

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [flonat](https://github.com/flonat)
- **Source:** [flonat/claude-research](https://github.com/flonat/claude-research)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-flonat-claude-research-init-project-light
- Seller: https://agentstack.voostack.com/s/flonat
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.