AIBiz Claude Code Starter plugin
A ready .claude folder in Polish: skills, agents and rules that lead a project from idea to a React and Supabase app.
- 94 ★ on the repository
- Last commit
Broad access
Why this level
- The autopilot writes code, creates branches and pull requests and runs checks in a real browser
- Agents need `gh` login and access to project secrets for scenarios and E2E
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/aibiz-claude-code-starterDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The autopilot writes code, creates branches and pull requests and runs checks in a real browser
- Agents need `gh` login and access to project secrets for scenarios and E2E
This is third-party code. Review the repository files before installing.
What it does
Claude Code Starter is copied into a project as a `.claude/` folder and sets a working process: `/dev-brainstorm` clarifies requirements question by question, `/dev-prep` lists what a human must provide, `/dev-plan` builds a technical plan by phases, a `feature/<name>` branch and a task in `docs/active/`. Then `dev-autopilot-wf` runs the phases one after another: implementation, review, fixing, followed by `/dev-pr` and `/dev-smoke`. Each phase is checked by up to seven independent reviewer agents: security, performance, code quality, correctness, spec compliance, tests and E2E in a real browser. Serious findings go through a skeptic agent. The phase order, quality gates and fix limits are set by deterministic JS workflows, and lessons land in `docs/solutions/`. The set is tuned for React 19, TypeScript, Supabase, Vite and Tailwind v4.
Who it is for. Polish-speaking developers and teams building React and Supabase apps who want a structured process with review in Claude Code.
Good fit when
- A new feature starts with a vague idea and a requirements document comes first.
- You want implementation split into phases where independent reviewers check each one.
- Found errors should become rules for future sessions.
- A list of manual checks is needed after autopilot: `/dev-smoke` walks it in a new session.
Not a fit when
- The project uses another stack: the core works but the technical skills must be replaced.
- You need a one-line edit: the multi-stage process with agents will be too heavy.
- You do not read Polish: instructions and prompts are written in Polish.
Example request
/dev-brainstorm: I want to add an order system to the app, ask questions one at a time.Limitations
Text and instructions are in Polish and the set targets React 19, TypeScript, Supabase, Vite and Tailwind v4. On another stack the pipeline, review and knowledge base work, while technical skills must be replaced. Git, Node 22 or newer and an authenticated `gh` are required. Project plugins such as `dev-browser` and `figma` are installed separately with `claude plugin install`, Claude Code does not install them itself. No license is declared in the repository. Up to seven reviewers per phase spend many tokens.
How to disable. Delete the `.claude/` folder from the project or revert the commit that added it and remove plugins with `claude plugin uninstall`.
FAQ
What are the process stages?
`/dev-brainstorm`, `/dev-prep`, `/dev-plan`, then the `dev-autopilot-wf` autopilot, `/dev-pr` and `/dev-smoke`. The first two steps are optional.
Who reviews the code?
Up to seven reviewers per phase: security, performance, quality, correctness, spec, tests and E2E. A skeptic agent challenges serious findings.
What decides phase order?
Phases, quality gates and fix limits live in deterministic JS workflows, so code sets the order.
How does the set remember experience?
Solved problems go to `docs/solutions/` and agents working on the same files get rules from them.
Where do the ideas come from?
From the `compound-engineering-plugin` by EveryInc and `mattpocock/skills`, adapted to Polish and this stack.
Discussion
No questions or reviews yet.
Related
PluginsClaude Code plugins with development recipes: agree on the outcome, design, implement with checks and run an independent review
A Claude Code template: wireframe, prototype and an HTML spec before the code, then a build with the native plan and goal modes
A Claude Code working configuration: a planner with per-milestone review, sub-agents and skills for analysis, refactoring and docs sync
A Claude Code environment installer: CLAUDE.md, rules, skills, agents, hooks and two-layer project memory in one script
A handbook and starter set for Claude Code: guides, CLAUDE.md templates, starter kits, hooks and the commit-helper plugin.
Claude Code plugin with 17 skills: task sizing, design review, TDD, fresh-context subagents and a PR after three human decisions.
README in short
The README describes the flow from brainstorm to merge, agent roles, installation by copying `.claude/` and the environment requirements.