setup

Configure the personal assistant plugin by merging settings, initializing context, and generating imli-core rules.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/prince-khanna/claude-code-plugins --skill setup-prince-khanna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/prince-khanna/claude-code-plugins/tree/main/personal-assistant/skills/setup
Command: npx skills add https://github.com/prince-khanna/claude-code-plugins --skill setup-prince-khanna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the initial configuration and onboarding needed to turn Claude Code into a persistent, proactive personal assistant (Imli) so users do not have to manually edit settings, copy context files, or generate derived rules.

Core Features & Use Cases

  • Apply default settings safely: Merge the Imli outputStyle into ~/.claude/settings.json while preserving all other user settings and notifying the user of changes.
  • Initialize native context: Create ~/.claude/.context by copying a context template only when no existing context directory is present to avoid overwriting user data.
  • Generate imli-core rules: Run the sync-context script to produce ~/.claude/rules/imli-core.md containing identity, preferences, rules, and active projects for native rule loading.
  • Use case: A newly installed plugin needs to enable persistent context, session hooks, and onboarding so the assistant behaves proactively without per-message context overhead.

Quick Start

Run the personal-assistant setup to configure Imli, initialize native context, and generate imli-core rules.

Frequently Asked Questions about setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Claude Code settings to enable persistent context for a personal assistant?

To enable persistent context, you need to merge specific outputStyle fields into your ~/.claude/settings.json file and initialize a native context directory to store session data without overwriting existing configurations.

What is the best way to generate native rules for Claude Code from a context template?

Generating native rules requires running a sync-context script that processes your context template to produce a derived rules file, typically stored in ~/.claude/rules/, enabling native rule loading for proactive assistant behavior.

Does setting up a personal assistant in Claude Code overwrite my existing settings.json configurations?

No, the setup process safely merges new assistant output styles into ~/.claude/settings.json while preserving all your unrelated user settings, ensuring no existing data is lost during the onboarding configuration.

Can I initialize a context directory for Claude Code if I already have existing context files?

No, the context initialization process only copies a context template to create the ~/.claude/.context directory when no existing context directory is present, actively preventing the overwrite of your current user data.

Why does my personal assistant plugin require access to the ~/.claude directory during onboarding?

Access to the ~/.claude directory is required to merge settings.json fields, initialize native context templates, and generate derived rules that enable the persistent, proactive behavior needed for the assistant.

Do I need to manually edit settings to turn Claude Code into a proactive personal assistant?

No, you do not need to manually edit settings or copy context files; the setup process automates merging configurations, initializing context, and generating core rules to enable proactive behavior automatically.