napkin

Maintain a curated per-repo Markdown runbook at .claude/napkin.md.

3|3|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/diegocamara89/ai-skills-hub --skill napkin-diegocamara89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: napkin
Source: https://github.com/diegocamara89/ai-skills-hub/tree/main/all-skills/napkin
Command: npx skills add https://github.com/diegocamara89/ai-skills-hub --skill napkin-diegocamara89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The napkin provides a per-repo memory and continuously curated runbook to accelerate session work, reducing repeated guidance and enabling fast, repeatable actions.

Core Features & Use Cases

  • Maintains a per-repo Markdown runbook at .claude/napkin.md for fast reference.
  • Curates and prioritizes content on every read, enforcing category caps and Do instead guidance.
  • Enables cross-session learning so patterns improve agent behavior over time.

Quick Start

In your first session, open and curate the .claude/napkin.md at the start of work to refresh guidance and enforce the top-priority rules.

Frequently Asked Questions about napkin

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

FAQPage Schema
How do I maintain consistent agent behavior across multiple coding sessions in a repository?

A per-repo runbook provides persistent memory and session guidance by maintaining a curated Markdown file, ensuring consistent agent behavior across recurring tasks without repeating instructions.

What is a per-repo runbook for automated session guidance?

A per-repo runbook is a continuously curated Markdown file stored within the repository that captures prioritized rules and patterns to guide agent behavior and accelerate session work.

How do I set up a persistent runbook to accelerate recurring software development tasks?

Start by creating and curating a YAML-frontmatted Markdown file at the designated path within your repository, adding mandatory metadata and prioritized rules to enforce top-priority guidance on every read.

Can I use a per-repo runbook to enforce category caps and specific guidance rules during development sessions?

Yes, the runbook curates and prioritizes content on every read, enforcing category caps and translating rules into actionable guidance to maintain structured and efficient session behavior.

Does a per-repo runbook support cross-session learning for software development patterns?

Yes, it enables cross-session learning by continuously curating patterns into the persistent memory file, which improves agent behavior and automates repeatable actions over time.

Why does my agent need repeated guidance for the same repository tasks across different sessions?

Without a persistent per-repo memory, agents lose context between sessions, requiring repeated guidance and slowing down work; a curated runbook solves this by providing fast, repeatable reference.