Stats
Actions
Tags
From reflex
Use this whenever the user runs /reflex:reflex-init or asks to set up, seed, bootstrap, or extend reflex rules for the current project. Proposes a handful of candidate rules for .reflex/reflex.json based on what the project appears to care about, then lets the user pick which to keep.
How this skill is triggered — by the user, by Claude, or both
Slash command
/reflex:reflex-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The goal is a `.reflex/reflex.json` whose rules actually help the next agent working in this repo — not a generic checklist. Quality of the patterns and messages *is* the product.
The goal is a .reflex/reflex.json whose rules actually help the next agent working in this repo — not a generic checklist. Quality of the patterns and messages is the product.
${CLAUDE_PLUGIN_ROOT}/reflex-format.md. Everything you propose must conform to that schema..reflex/reflex.json if it exists. Don't propose duplicates of rules already present; you may suggest refinements if an existing rule looks clearly broken."medium" to survey the codebase: agent-instruction docs (CLAUDE.md, AGENTS.md, README.md, subdirectory CLAUDE.md files), directory structure, sensitive paths, scripts, and any signals about how the team wants agents to behave. If the user passed $ARGUMENTS, include it in the agent prompt as a strong steer. Wait for the agent to return before continuing.proceed reminders and stricter pause / reject guardrails usually serves better than five of the same kind.AskUserQuestion (multi-select) to let the user pick which rules to add. Include these non-rule options:
"Propose different candidates" — if chosen, re-run step 4 from a different angle (look somewhere else, lean on a different signal)."None — I'll write my own" — exit without changes..reflex/reflex.json. Create the file and .reflex/ directory if they don't exist. Preserve any pre-existing rules and keep "version": 0. Close with a one-line summary of what changed.Generic guardrails that don't match anything real are worse than no rule: they add noise every session. Steps 3 and 4 exist to keep proposals grounded in project-specific signal instead of recognizable directory names.
npx claudepluginhub alumkal/claude-reflex --plugin reflexGenerates project-specific CLAUDE.md rules by detecting stack from package.json, Cargo.toml, pyproject.toml, go.mod, git log, and user-selecting categories like response format, library preference, code review stance. Use for new projects, repo onboarding, or establishing conventions.
Guides creation of .claude/rules/ files for path-scoped project conventions using TDD workflow: RED (test gaps), GREEN (write rule), REFACTOR (optimize). Triggers on 'add rule', 'create convention', 'scope guideline'.
Adds a new rule, convention, or instruction to the project's agent configuration, analyzing placement in root CLAUDE.md, docs/agents/ files, or a new skill.