Anthony Bordonaro

How to Write a Toolkit Entry

CLAUDE.md
metacontributingdocumentation

This is the meta-entry — a template for writing new toolkit entries. Use it when adding prompts, skills, configs, patterns, or techniques to the collection.

Frontmatter schema

Every entry needs this YAML frontmatter:

---
title: "Entry Title"
date: "2026-02-22T10:00:00.000Z"
description: "One sentence. What it does and why you'd use it."
category: "prompt"  # prompt | skill | mcp-config | claude-md-pattern | technique
tags: ["tag1", "tag2"]
copyable: true  # true = copy buttons on code blocks, false = prose only
---

Category guide:

  • prompt — a structured prompt you paste into Claude (or any LLM)
  • skill — a Claude Code slash command or installable skill
  • mcp-config — an MCP server configuration for Claude Desktop
  • claude-md-pattern — a CLAUDE.md file pattern or template
  • technique — a workflow or approach, not a single copyable artifact

Content structure

Every entry should follow this pattern:

1. Opening paragraph (required)

One paragraph explaining what this is and why it matters. No fluff. Answer: "Why should I care?"

2. The artifact (required)

The actual prompt, command, config, or pattern in a fenced code block. This is what people came for — don't bury it.

3. How to use it (required)

Practical instructions. Where to put it, how to invoke it, what to expect.

4. When to use it (recommended)

Specific situations where this entry is the right tool. Helps readers self-select.

5. Why it works (optional)

Explanation of the design decisions. Why is the prompt structured this way? What makes this approach better than alternatives?

6. Tips (optional)

Practical advice from real usage. Follow-up prompts, common mistakes, pairing suggestions.

Quality checklist

Before publishing:

  • [ ] Title is specific — "Code Review Prompt" not "Useful Prompt"
  • [ ] Description is one sentence — fits in a card on the landing page
  • [ ] The artifact is real — tested in actual use, not hypothetical
  • [ ] Examples use concrete values — real file paths, real commands, not placeholders
  • [ ] No generic advice — if a tip applies to everything, it doesn't belong here
  • [ ] Cross-links where relevant — reference related entries with [title](/ai-toolkit/slug)
  • [ ] Tags are lowercase — match existing tags where possible
  • [ ] copyable is set correctly — true for prompts/configs/commands, false for pure prose techniques

File naming

Save as _ai-toolkit/your-entry-slug.md. The slug becomes the URL: /ai-toolkit/your-entry-slug.

Use lowercase with hyphens. Keep it short but descriptive: tdd-with-claude.md, not test-driven-development-workflow-for-use-with-claude-code.md.

Back to AI Toolkit