Imprint

Your habits, imprinted on AI. Learns how you work from conversation, builds a portable profile, and applies judgment that adapts to you: when to act, when to check with you, when to follow the project's rules over your own defaults. Use this skill whenever the user starts a new session, opens a project, writes or reviews code, debugs, plans, or writes commits. If .dna.md does not exist yet, start the onboarding conversation before doing anything else. Active in almost every working session.

104 stars 6 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add ilang-ai/Imprint

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ilang-ai/Imprint --skill imprint
Manual install
git clone --depth 1 https://github.com/ilang-ai/Imprint.git /tmp/Imprint
mkdir -p ~/.claude/skills
cp -r /tmp/Imprint/skills/imprint ~/.claude/skills/imprint

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Imprint

One profile. Judgment that fits you. Gets sharper every session.

Imprint does two things. It **remembers how you work** (a portable profile that
travels across every AI tool), and it **judges how to act** on your behalf:
execute, confirm first, advise only, defer, or hold. The judgment adapts to your
profile, the project you are in, and how much is at stake. The judgment layer
follows the I-Lang v5.0 vector protocol (see "Judgment" below), but you never see
its internals — only the behavior.

## RULE 1: Never Expose Internal Concepts

NEVER use these words when talking to the user: "DNA", "gene", "behavioral pattern", "encode", "extract", "mutation", "decay", "confidence level", "tentative", "confirmed gene", "anti-pattern", "vector", "dimension", "sovereignty", "judgment mode", "M1", "M8", "compression ratio".

To the user, say things like:
- "Let me get to know how you work so we can collaborate better"
- "I saved a quick memo so I remember next time"
- "This one's a bigger call — want me to go ahead, or check with you first?"

When creating `.dna.md`, say something like: "Saving some notes so things go smoother next time." Then create the file without fanfare. Do not proactively show its contents or explain the format. If the user asks to see it, show it openly. It is their file.

## RULE 2: One Question at a Time

THIS IS NON-NEGOTIABLE.

During onboarding or at any other time, ask exactly ONE question per message. Wait for the answer before asking the next.
Read the full skill on GitHub

Details

Skill name
imprint
Path
skills/imprint/SKILL.md
License
MIT
Repo updated
22 September 2026

FAQ

What does the Imprint skill do?

Your habits, imprinted on AI. Learns how you work from conversation, builds a portable profile, and applies judgment that adapts to you: when to act, when to check with you, when to follow the project's rules over your own defaults. Use this skill whenever the user starts a new session, opens a project, writes or reviews code, debugs, plans, or writes commits. If .dna.md does not exist yet, start the onboarding conversation before doing anything else. Active in almost every working session.

How do I install the Imprint skill?

Claude Code plugin: /plugin marketplace add ilang-ai/Imprint. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Imprint popular?

It lives in ilang-ai/Imprint, which has 104 GitHub stars and 6 forks, and is included in 1 curated skill list.

Related skills

Mojo Syntax

213

modular/skills

Help to write Mojo code using current syntax and conventions. Always use this skill when writing any Mojo code, including when other Mojo-specific skills (e.g., mojo-gpu-fundamentals) also apply. Use when writing or reviewing Mojo code, translating projects to Mojo, or otherwise generating Mojo. Use this skill to overcome misconceptions with how Mojo is written.

Writing & Content22

Tech Article Reproducibility

423

mizchi/skills

Evaluate the reproducibility of technical articles. Dispatch a subagent to simulate a first-time reader reproducing the work locally and list missing information. Use as the final check on a draft before publication or to recheck a published article before responding to reader feedback.

Writing & Content

Simplified Technical English

206

thomast1906/github-copilot-agent-skills

Writes and rewrites technical text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation. Use when the user asks for STE, Simplified Technical English, controlled language, or plain technical writing, or asks to write, rewrite, simplify, clarify, review, or check technical documentation, procedures, manuals, instructions, warnings, error messages, or reports. Do NOT use for marketing copy, creative writing, or general prose simplification outside a technical context.

Writing & Content54

Natural Writing Ja

423

mizchi/skills

Japanese prose norm for writing explanatory text that does not read as machine-generated. Built on one diagnostic axis (does a sentence update the situation or the document?) plus register purity, sentence-beat and 体言止め/反問 rules calibrated against 937 sentences of human technical writing. Use when drafting or revising Japanese articles, docs, or long-form explanations, especially after an LLM produced the draft. For English use natural-writing-en; for scoring a draft use ai-index.

Writing & Content

Slm Compress

278

qualixar/superlocalmemory

Compress large text, tool output, or transcripts to reduce context-window usage while keeping the full 1M window intact — call slm_compress(content, mode, reversible, ttl_seconds) to shrink content; if the result is lossy a ccr_id is returned so you can call slm_retrieve(ccr_id) later to recover the exact original; always fail-open (ok:false → continue with the original).

Writing & ContentIn 1 list36

Natural Writing En

423

mizchi/skills

English prose norm for writing explanatory text that does not read as machine-generated. One diagnostic axis (does a sentence update the situation or the document?) plus measured thresholds for burstiness, hedging, enumeration and paragraph openings, with corrections to widely-cited signals that false-positive on human technical writing. Use when drafting or revising English articles, docs, READMEs or long-form explanations, especially after an LLM produced the draft. For Japanese use natural-writing-ja; for scoring a draft use ai-index.

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.