skills/barnhardt-enterprises-inc/checkpoint/SKILL.md
Save current progress to memory-keeper to prevent work loss.
npx skillsauth add aiskillstore/marketplace checkpointInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Automatically checkpoint current progress to memory-keeper to prevent catastrophic work loss when context is exhausted.
/checkpointCollect the following information:
context_save(key: "current-task", value: "<task description>", category: "progress", priority: "high")
context_save(key: "files-modified", value: "<comma-separated file list>", category: "progress")
context_save(key: "implementation-progress", value: "<percentage or phase>", category: "progress")
context_save(key: "next-action", value: "<exact next step>", category: "progress", priority: "high")
context_checkpoint(
name: "checkpoint-<timestamp>",
description: "Task: <task>, Progress: <progress>, Files: <count>, Next: <action>"
)
context_prepare_compaction()
| Activity | Checkpoint Frequency | |----------|---------------------| | File creation/modification | After every file | | Running tests | After each test run | | Research/exploration | Every 10 tool calls | | Debugging | After each hypothesis tested | | Multi-step implementation | After each step |
| Key | Description | Priority |
|-----|-------------|----------|
| current-task | What you're currently working on | high |
| files-modified | All files touched this session | normal |
| implementation-progress | How far along (%, phase) | normal |
| next-action | Exact next step to take | high |
| blockers | Current issues/blockers | high |
| todo-state | Serialized todo list | normal |
After checkpointing, confirm with:
Checkpoint saved:
- Task: <current task>
- Progress: <progress>
- Files modified: <count>
- Next action: <next step>
If context is lost, use /recover to restore state from checkpoints.
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.