quest-system

finpack-claude

A lean .claude/ setup for daily development. Five reviewer agents, nine workflow skills, six modular rules, and a few safety hooks. No bloat, no model assignments, no opinions you can't override. NOTE: This plagiarised work is hugely copied from https://github.com/poshan0126/dotclaude.git. Big clap and please go check it out for the original work.

Get started

Two paths to the same place: a customized .claude/ in your project. Most people should pick the marketplace path. It's faster, there's nothing to clean up afterward, and you don't have to think about where files go.

Option 1 (recommended): install via the marketplace

Add the marketplace once on your machine, then install the all-in-one setup plugin:

/plugin marketplace add findexu/finpack-claude
/plugin install setup-finpack@finpack-claude

Open your project in Claude Code and run:

/setup-finpack

That's the whole flow. The setup-finpack plugin bundles the complete finpack-claude template (settings, rules, hooks, all agents and skills, CLAUDE.md). When you run the slash command it asks you to confirm, copies the bundled template into your project's .claude/ and CLAUDE.md at the project root, then scans your codebase to detect language, framework, package manager, test runner, linter, and architecture, and tunes every config file to match. Every change is confirmed before it's applied.

After it finishes, restart Claude Code so the new agents, skills, rules, and hooks load.

If you only want one or two pieces instead of the full kit, install them individually:

/plugin install code-reviewer@finpack-claude
/plugin install pr-review@finpack-claude
/plugin install ship@finpack-claude

Full plugin list: code-reviewer, security-reviewer, performance-reviewer, doc-reviewer, frontend-designer, setup-finpack, debug-fix, ship, pr-review, tdd, explain, refactor, test-writer, context-budget, quest-system, quest-system-tutorial, install-quest-system.

Option 2: clone the repo

Pick this if you'd rather own the files in your dotfiles repo or skip the plugin layer entirely.

git clone https://github.com/findexu/finpack-claude.git /tmp/finpack-claude

cd your-project
mkdir -p .claude

cp /tmp/finpack-claude/settings.json .claude/
cp -r /tmp/finpack-claude/{rules,skills,agents,hooks} .claude/
cp /tmp/finpack-claude/CLAUDE.md ./
cp /tmp/finpack-claude/CLAUDE.local.md.example ./

chmod +x .claude/hooks/*.sh
rm -rf /tmp/finpack-claude

echo "CLAUDE.local.md" >> .gitignore

Reload Claude Code, then run /setup-finpack. It's the same skill as Option 1, just operating on files you copied yourself instead of files the plugin bundled. It also strips out anything you might have dragged in by accident: the .claude-plugin/, plugins/, and scripts/ folders if you did a bulk cp -r, plus the README files in each subfolder.

Troubleshooting

Problem	Fix
Skills or agents not showing up	Restart Claude Code. Everything loads at session start.
Hooks not running	Run chmod +x .claude/hooks/*.sh and verify jq is installed.
"jq not found" blocking everything	Install jq: brew install jq (macOS) or apt install jq (Linux).
format-on-save not formatting	Make sure the formatter binary is installed and its config file exists in the project root.
Permission denied on allowed commands	Check the glob in settings.json. Bash(npm run test *) matches arguments after test.
/setup-finpack asks to confirm settings.json edits	Expected. protect-files.sh prompts when editing settings.json. Hook scripts stay hard-blocked.

Make it yours

/setup-finpack gets you most of the way. To take it the rest of the way:

• rules/code-quality.md. Naming conventions to match your team's style. Comment guidelines, code marker format, import order.
• rules/frontend.md. Pick your design principle. Highlight the component framework your project actually uses.
• rules/security.md. Add paths specific to your project's sensitive areas, beyond the defaults.
• CLAUDE.md. Architectural decisions, domain knowledge, workflow quirks unique to your project.
• CLAUDE.local.md. Personal preferences (gitignored). Rename the .example file to start.
• hooks/format-on-save.sh. If detection missed your formatter, uncomment the right section manually.

The defaults are foundations. Your edits on top are what make Claude effective for your project.

Skills (slash commands)

Skills are invoked with /name in your Claude Code session. All except /test-writer are manual only.