agentleFS
meshery-extensionsmeshery-extensions/kanvas-site/.agents/skills/kanvas-animations/CLAUDE.md

kanvas-site / kanvas-animations

CLAUDE.md42 starsChanged 4 months agoApache-2.0View on GitHub

We split this CLAUDE.md into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep edits scoped, minimal, and aligned with this plugin's existing architecture.

    line 5
  2. Very specific:

    Do not delete or rename .claude-plugin/plugin.json.

    line 22
  3. Distinctive:

    Do not introduce secrets, credentials, or tenant-specific IDs in tracked files.

    line 23
  4. Distinctive:

    Do not modify unrelated plugins from this plugin workflow unless explicitly requested.

    line 24
  5. Very specific:

    If code/scripts changed in this plugin, run targeted tests for plugins/kanvas-animations.

    line 29
  6. Distinctive:

    If requirements conflict with plugin guardrails, pause implementation and document the conflict.

    line 38
  7. Distinctive:

    If validation fails and root cause is unclear, escalate with failing command output and touched files.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

React Animation Studio Plugin Guide

Purpose

  • Operational guide for working safely in plugins/kanvas-animations.
  • Keep edits scoped, minimal, and aligned with this plugin's existing architecture.

Supported Commands

  • animate-3d (see commands/animate-3d.md)
  • animate-audit (see commands/animate-audit.md)
  • animate-background (see commands/animate-background.md)
  • animate-component (see commands/animate-component.md)
  • animate-effects (see commands/animate-effects.md)
  • animate-export (see commands/animate-export.md)
  • animate-preset (see commands/animate-preset.md)
  • animate-scroll (see commands/animate-scroll.md)
  • animate-sequence (see commands/animate-sequence.md)
  • animate-text (see commands/animate-text.md)
  • animate-transition (see commands/animate-transition.md)
  • animate (see commands/animate.md)

Prohibited Actions

  • Do not delete or rename .claude-plugin/plugin.json.
  • Do not introduce secrets, credentials, or tenant-specific IDs in tracked files.
  • Do not modify unrelated plugins from this plugin workflow unless explicitly requested.

Required Validation Checks

  • Run npm run check:plugin-context.
  • Run npm run check:plugin-schema.
  • If code/scripts changed in this plugin, run targeted tests for plugins/kanvas-animations.

Context Budget

Load in this order and stop when you have enough context:

  1. CONTEXT_SUMMARY.md
  2. commands/index (or list files in commands/)
  3. README.md and only the specific docs needed for the current task

Escalation Path

  • If requirements conflict with plugin guardrails, pause implementation and document the conflict.
  • If validation fails and root cause is unclear, escalate with failing command output and touched files.
  • For production-impacting changes, request maintainer review before release/publish steps.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.