agentsclimarketplace
Sign in

Reflex init

Skill alumkal/claude-reflex/skills/reflex-init

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.From its SKILL.md

Install
npx -y skills add alumkal/claude-reflex --skill reflex-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, as published. Nobody here has run it

Seed reflex rules for this project

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.

Steps

  1. Read ${CLAUDE_PLUGIN_ROOT}/reflex-format.md. Everything you propose must conform to that schema.
  2. Read .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.
  3. Explore the project deeply before proposing anything. Launch an Explore subagent with thoroughness "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.
  4. Propose at most 5 candidate rules. Prefer rules that save the agent from a realistic, repeated mistake in this project over generic best-practice rules. A mix of gentle proceed reminders and stricter pause / reject guardrails usually serves better than five of the same kind.
  5. Use 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.
  6. Merge the selected rules into .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.

Why this shape

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.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.