preferences

Capture and manage user preferences in `.claude/skill-context/` files.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/joesys/joesys-skills --skill preferences-joesys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preferences
Source: https://github.com/joesys/joesys-skills/tree/main/skills/preferences
Command: npx skills add https://github.com/joesys/joesys-skills --skill preferences-joesys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and manage user preferences that shape how every skill in the collection behaves.

Core Features & Use Cases

  • Interactive setup via /preferences to capture shared preferences (concise explanations, desired detail level, and project context) that apply across all skills.
  • Show/reset per-skill preferences using .claude/skill-context/ files, and store shared settings for reuse across sessions.
  • Automatically invoked by other skills on first contact when no preferences exist, enabling a smooth, guided setup experience.

Quick Start

Run /preferences to start the interactive setup and capture your default preferences.

Frequently Asked Questions about preferences

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

FAQPage Schema
How do I set up user preferences to personalize my AI workflow?

To set up user preferences, run the interactive `/preferences` command which triggers a core interview to capture your desired detail level, concise explanations, and project context for personalizing your AI workflow.

How does context management work for per-project and per-user settings?

Context management works by persisting your captured preferences into the `.claude/skill-context/` directory, storing shared settings for reuse across sessions and separate configuration files for per-project and per-user contexts.

Can I reset or view specific skill configurations after the initial setup?

You can view or reset specific skill configurations by running the `/preferences` command, which allows you to tailor settings for individual skills or clear previously stored per-skill preferences.

Do I need to manually configure preferences for every new skill I use?

You do not need to manually configure preferences for every new skill, as other skills automatically invoke the preferences setup on first contact when no existing configuration is detected in the context directory.

What is the best way to ensure consistent behavior across all my skills?

The best way to ensure consistent behavior across all skills is to establish shared preferences during the initial interactive interview, which applies your desired detail level and project context globally across the collection.