One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill ck-llmh333
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/ck
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill ck-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ck keeps your project’s evolving notes, goals, decisions, and “where I left off” in persistent per-project memory so you don’t have to re-explain everything each time you start a Gemini session.

Core Features & Use Cases

  • Persistent context per project: Registers a project once and stores structured session history in context.json, regenerating CONTEXT.md for readable guidance.
  • Session lifecycle commands: Use /ck:resume for a full briefing and /ck:save to record your session outcomes (including decisions, next steps, and blockers) with optional goal syncing.
  • Session start auto-injection: A session-start hook automatically injects a compact first-message briefing for the registered project (and a mini portfolio view for unregistered directories).

Use Case: You’re implementing a feature across multiple days; ck captures your decisions, blockers, and next steps at each session, then re-loads a bordered briefing so you can immediately continue work without losing context.

Quick Start

Ask your AI to run /ck:init to register the current project, then continue by saving your first session state with /ck:save after you finish what you were working on.

Frequently Asked Questions about ck

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

FAQPage Schema
How do I keep project context across multiple Gemini sessions?

To keep project context across multiple Gemini sessions, you can use persistent storage to save session summaries, goals, and decisions, reloading them as a briefing when you start a new session.

What is the best way to track goals and next steps in Node.js across sessions?

Tracking goals and next steps in Node.js across sessions involves deterministic command execution via routes to save session outcomes, syncing goals, and recording blockers for continuous iterative work.

How do I automatically inject project context at the start of a session?

You can automatically inject project context at the start of a session by using a session-start hook to insert a compact briefing of your saved notes and 'where I left off' into the first message.

How do I highlight git activity and goal mismatches during software development?

Highlighting git activity and goal mismatches requires a system that stores persistent project context, analyzing your recorded goals against recent repository changes to identify inconsistencies during your workflow.

Does context management for iterative software work require manual re-explanations?

Context management for iterative software work does not require manual re-explanations, as persistent per-project memory automatically saves and reloads your structured session history to eliminate repetitive setup.

Can I use deterministic Node.js commands to manage session memory?

You can use deterministic Node.js commands to manage session memory by executing specific routes to register projects, save outcomes, and resume work with full context briefings.