Strict Format Rules | markus | ClaudePluginHub

Skill

Strict Format Rules

Extract noteworthy items from the current conversation into memory files. Use when a cron notification prompts periodic reflection, or when a decision, preference, or important context is observed.

Install

$

npx claudepluginhub swen128/markus --plugin markus

Tool Access

This skill uses the workspace's default tool permissions.

Preview

These rules are non-negotiable. Violating any of them is a bug.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.1k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

smart-explore

Performs token-optimized structural code search using tree-sitter AST parsing to discover symbols, outline files, and unfold code without reading full files.

65.8k

Stats

Stars0

Forks0

Last CommitMar 20, 2026

Actions

View Source View Plugin View on GitHub View README

Strict Format Rules

These rules are non-negotiable. Violating any of them is a bug.

Date-named files only. The only .md files allowed in memory/ are YYYY-MM-DD.md. NEVER create topic-based files like memory/feedback_tooling.md or memory/user_role.md.
No YAML frontmatter. NEVER start a memory file with ---.
No link format in MEMORY.md. NEVER write - [file.md](memory/file.md) -- description. Use plain - <observation> lines.

Daily Log Format (`memory/YYYY-MM-DD.md`)

Each entry uses an ## HH:MM time header followed by bullet observations:

## 14:30

- User prefers Bun over Node for the test runner
- Team decided on tabs over spaces

Long-term Memory Format (`MEMORY.md`)

Append significant items under a ## YYYY-MM-DD date header in the workspace root (not inside memory/):

## 2026-03-20

- User prefers Bun over Node for the test runner

Steps

Read today's memory/YYYY-MM-DD.md to avoid duplicates.
Review the current conversation context.
Identify new decisions, preferences, observations, or context worth persisting.
Append new items to memory/YYYY-MM-DD.md (create the file and memory/ directory if needed) using the daily log format above.
If any item warrants long-term retention, also append to MEMORY.md using the long-term memory format above.
If nothing noteworthy happened, do nothing.

Be selective — persist only genuinely useful information, not routine operations. One line per item.