Document manual adaptation path for non-native harnesses like Grok

[affaan-m]

Source discussion

• How to use everything-claude-code with Grok (xAI)? Best practices for agents & skills? #1077

Problem

Users are trying to adapt ECC to non-native harnesses like Grok/xAI by manually copying agents, skills, and rules into prompts or custom instructions. We do not yet have a canonical manual-adaptation guide for harnesses that do not support the native ECC folder layouts.

Proposed outcome

Document and/or package a fallback workflow for non-native harnesses that covers:

• how to pick the minimal agent/skill/rule set for a task
• how to compress ECC context into a manual master prompt without dragging the whole repo in
• how to reproduce the value of commands and hooks when the target harness has no native support
• what the limits are compared with first-class targets like Claude, Cursor, Codex, Opencode, and CodeBuddy

Definition of done

• there is a documented ECC-native adaptation path for manual / non-native harnesses
• the answer is reusable for Grok and similar tools instead of living in one-off discussion replies

[affaan-m]

Shipped on main in 0aad18a.

Added a canonical ECC-native Manual Adaptation Guide for Grok and similar non-native harnesses.

The final version keeps the useful manual-adaptation workflow from the discussion, but makes ECC-native manual packing the default path and treats external packers like repomix as optional helpers rather than the core workflow.