Claude Code Setup

claude-code-setup

My personal Claude Code toolkit. Templates and skills I use day-to-day on Shopify themes, React/Nuxt sites, and AI tooling for freelance work. Open-sourced so others can adopt or fork.

What's inside

• [templates/](./templates/): drop-in CLAUDE.md files for specific stacks
• [skills/](./skills/): external Claude Code skills I rely on, with install instructions
• [hooks/](./hooks/): settings.json snippets for automation (coming)
• [snippets/](./snippets/): reusable instruction blocks (coming)

Templates

• [Shopify theme development](templates/shopify.md): OS 2.0 conventions, custom section workflow, schema rules.
• [Figma Dev Mode MCP integration](templates/figma-mcp.md): connecting Figma to Claude Code, node-id handling, asset extraction.

More on the way: Shopify Hydrogen (headless track), Nuxt + TypeScript + Tailwind, production AI agents with state machines, typed tools, and evaluations.

Skills

I curate external skills here rather than reimplement. See [skills/README.md](skills/README.md) for the full list and install instructions. The most-used one:

• avoid-ai-writing by Conor Bronsdon. Audits and rewrites text to remove AI writing patterns: em-dashes, flag vocabulary, structural regularity. Mandatory in my workflow before publishing any client-facing or public content.

Why this exists

I'm a freelance web developer based in Warsaw. Shopify, React, Nuxt are my main stacks, and I use Claude Code as my primary build tool. After a handful of projects, I noticed I was copy-pasting the same rules into every new CLAUDE.md: don't edit original theme files, configure everything from the customizer, reuse existing snippets first.

So I extracted them into templates I can drop into any new project.

The Shopify template captures rules I learned from real OS 2.0 work. The Figma MCP template covers connecting Figma Dev Mode to Claude Code, including the node-id parsing gotchas that almost everyone hits the first time.

Most Shopify devs only do Liquid. Most React devs avoid Liquid. Picking between them shouldn't depend on what the dev knows. The right architecture depends on the project: integration count, app dependency, multi-store needs, AI work. Templates here cover the Liquid track today; the headless Hydrogen track is next.

This is a personal toolkit, not a methodology. Adopt what's useful, ignore the rest.

How to use

For a new Shopify project:

cp templates/shopify.md /path/to/your/theme/CLAUDE.md

Edit project-specific paths and conventions to match your codebase.

For Figma MCP integration, copy the relevant rules from [templates/figma-mcp.md](templates/figma-mcp.md) into your existing CLAUDE.md, or paste them into ~/.claude/CLAUDE.md for global use across projects.

Philosophy

• Pick the architecture that fits the business, not the framework you know best.
• Reuse the project's existing patterns first.
• Configure from the customizer, not from code.
• Treat AI as the build tool, not the author of what's published.
• Production agents are systems, not prompts: typed tools, explicit state, layered memory.

Contributing

This is a personal setup. If you spot something useful to add or have feedback, open an issue first and let's talk. I'm not generally accepting PRs of new templates without discussion.

License

MIT

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: iromanovich
• Source: iromanovich/claude-code-setup
• License: MIT

Install and usage instructions live in the source repository linked above.