ck

Persists per-project session context and auto-loads project briefings via Node.js scripts.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill ck-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/ck
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill ck-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? AI coding sessions lose all context when they end, forcing you to re-explain your project's goal, stack, decisions, and progress every time. This Skill maintains a persistent per-project memory so each new session starts with a compact briefing of where you left off. ## Core Features & Use Cases - Project Registration & Auto-Detection: The /ck:init command scans package.json, go.mod, Cargo.toml, pyproject.toml, CLAUDE.md, and README.md to auto-detect your project's name, stack, goal, and repo. - Session Save & Resume: /ck:save records a structured session summary (left-off point, next steps, decisions, blockers, git activity) into context.json, and /ck:resume renders a full bordered briefing box to pick up exactly where you stopped. - SessionStart Hook: A hook injects a ~100-token compact summary on every session start, detecting unsaved sessions, new git commits, and goal mismatches against CLAUDE.md. - Use Case: You work across three repositories during the week. Run /ck:list to see a portfolio table of all projects with staleness indicators, then /ck:resume 2 to get a full briefing on the second project including its last decisions and next steps. ## Quick Start Ask the assistant to run /ck:init to register the current project, then use /ck:save at the end of each work session and /ck:resume when you return.

Frequently Asked Questions about ck

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

FAQPage Schema
How do I save and restore project context between Claude Code sessions?▼

Run /ck:init once to register the project, then /ck:save at the end of each session to record a summary, next steps, and decisions. Use /ck:resume in a later session to display a full briefing of where you left off.

How do I auto-load project context on session start?▼

Register the session-start.mjs hook in ~/.claude/settings.json under the SessionStart hooks section. The hook injects a compact five-line summary per session and warns about unsaved sessions, new git commits, or goal mismatches with CLAUDE.md.

Does ck work with non-JavaScript projects like Go, Rust, or Python?▼

Yes. The init script detects stack and project name from go.mod, Cargo.toml, and pyproject.toml in addition to package.json. It also reads CLAUDE.md and README.md for goals, constraints, and descriptions regardless of language.

What happens if my projects.json file becomes malformed?▼

The scripts treat unreadable JSON as an empty registry rather than crashing. Per the Skill rules, the assistant should inform you of the malformed file and offer to reset projects.json to an empty object.

Can I migrate old v1 context data to the v2 format?▼

Yes. Run /ck:migrate with the --dry-run flag first to preview changes, then without it to convert v1 CONTEXT.md and meta.json files into v2 context.json. Originals are backed up as meta.json.v1-backup and nothing is deleted.