From ws-clamp
Knowledge about Claude Code's project data model, storage locations, and path encoding
npx claudepluginhub wsagency/ws-claude-marketplace --plugin ws-clampThis skill uses the workspace's default tool permissions.
This skill provides knowledge about how Claude Code stores project data, session history, and settings.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
This skill provides knowledge about how Claude Code stores project data, session history, and settings.
Claude Code maintains project data in three interconnected locations:
| Location | Purpose | Format |
|---|---|---|
| Project directory | Your code + .claude/ settings | Directory with config files |
~/.claude/projects/[encoded-path]/ | Session history per project | JSONL session files |
~/.claude/history.jsonl | Global project index | Line-delimited JSON |
When you work with Claude Code in a project, it creates and maintains data across these locations. Moving a project with mv breaks the references because the encoded path changes.
Claude encodes project paths by replacing / with - for the folder name in ~/.claude/projects/. For example:
/Users/john/projects/my-app → ~/.claude/projects/-Users-john-projects-my-app/The clamp utility handles all three locations atomically when moving projects, with rollback on failure.
references/data-stores.md for detailed data store documentationreferences/encoded-paths.md for path encoding detailsexamples/common-workflows.md for usage patterns