{
  "markdown": "# claudify\n\nBootstrap `.claude/` structure for any existing repo.\n\nRun `/claudify:init` from the root of any repo and get a clean, well-structured `.claude/` folder — generated from your actual codebase, not generic templates. Follows official [Claude Code memory best practices](https://code.claude.com/docs/en/memory).\n\n## Install\n\nAdd the phucbm marketplace (once, ever):\n```shell\n/plugin marketplace add phucbm/skills\n```\n\nInstall plugin:\n```shell\n/plugin install claudify@phucbm\n```\n\nUpdate all phucbm plugins:\n```shell\n/plugin marketplace update phucbm\n```\n\n## Usage\n\nBootstrap `.claude/` for a repo:\n```shell\n/claudify:init\n```\n\nRefresh CLAUDE.md to match the current codebase:\n```shell\n/claudify:update\n```\n\n`/claudify:update` delegates to `claude-md-management@claude-plugins-official`. If that plugin is not installed, it will tell you how to install it.\n\n## What gets generated\n\n| File | Description |\n|---|---|\n| `.claude/CLAUDE.md` | Entry point with `@import` directives, exact commands, and codebase-specific rules (≤ 80 lines) |\n| `.claude/docs/architecture.md` | Stack, structure, data flow, and key files (≤ 150 lines) |\n| `.claude/docs/agents.md` | AI/LLM layer details — only generated if your repo uses AI (≤ 150 lines) |\n\nIf `.claude/` already exists with content, claudify shows you exactly what will change and asks for confirmation before writing anything.\n\n## Auto-hook\n\n`/claudify:init` writes a `PostToolUse` hook to `.claude/settings.json` that fires whenever Claude edits a `.md` file and reminds you to run `/claudify:update`.\n",
  "bytes": 1558,
  "sha": "8208b6397489fb2e76ab14046265a5755f3b9569a8847061212a33d345024a8c",
  "repo_slug": "phucbm/claudify",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_phucbm_claudify_claudify_1d571b6d/readme"
}