Skip to content

Latest commit

 

History

History
47 lines (40 loc) · 3.08 KB

File metadata and controls

47 lines (40 loc) · 3.08 KB

CLAUDE.md

See @README.md for project overview. Use fully qualified names for plugin components (e.g., claude-ecosystem:plugin-component-auditor).

Rules

  • MCP First: Verify with MCP servers (perplexity, microsoft-learn, context7, ref, firecrawl) before answering technical questions or writing code
  • Microsoft Tech: Query microsoft-learn, then validate with perplexity (docs can be stale)
  • Correctness Over Speed: Verify, comply, ask permission - never cut corners
  • Minimal Changes: Do exactly what's asked, no "improvements" or refactoring
  • Ask Before: Modifying config files, architectural decisions, rule changes, adding dependencies
  • Fix Code, Not Rules: Never modify .editorconfig, .eslintrc, etc. to bypass violations
  • No Suppressions Without Proof: MCP verify APIs before adding #pragma, // eslint-disable, etc.
  • Windows Edit Bug: If Edit fails, use sed -i or Write tool - never retry Edit, never PowerShell
  • No PowerShell: Never use Set-Content, -replace, or .ps1 for file edits (data loss risk)
  • Git Bash Paths: Use MSYS_NO_PATHCONV=1 prefix for scripts
  • Load Skills First: Before auditing/modifying components, load the relevant development skill
  • Use docs-management Skill: For Claude Code documentation, never read index.yaml directly
  • MCP Research Isolation: Delegate multi-step MCP research to agents (mcp-research, general-purpose)
  • Plugin Dev Mode: Set env vars for local code when modifying plugin scripts
  • Python 3.13: Required for spaCy operations
  • No Destructive Git: Never git reset --hard, git clean -fd, git checkout . without explicit permission
  • Trust But Verify: Validate claims with MCP before implementing fixes
  • UTF-8/ASCII: Use UTF-8 encoding, straight quotes only (no smart quotes)
  • UTC Timestamps: Store in UTC (ISO-8601), convert to local for display only
  • Execution First: When asked to implement changes, execute directly. Do NOT write plan files or enter plan mode unless explicitly asked. Bias toward action over planning
  • Conventional Commits: Use Conventional Commits format for all git commits. GPG-sign when configured. Invoke melodic-software:git-commit skill for the commit workflow
  • Autonomous Commit Rules: ONLY commit when changes have been reviewed, vetted, validated, researched, etc. Default to NOT auto commit unless explicitly prompted to do so.
  • Verify Before Running: Always read script source files before executing them. Verify correct arguments, flags, and expected behavior. Never assume --skip-existing is appropriate for rescrapes

Commands

pytest -v                              # Python tests
npx markdownlint-cli2 "**/*.md"        # Markdown linting
/claude-ecosystem:audit-skills         # Validate skills and commands
/claude-ecosystem:audit-agents         # Validate agents

Plugin Structure

plugins/<name>/.claude-plugin/plugin.json  # Manifest
plugins/<name>/skills/<skill>/SKILL.md     # Skills (noun-phrase names)
plugins/<name>/agents/                     # Subagents
plugins/<name>/hooks/                      # Hooks