factory-setuplisted
Install: claude install-skill yybd/app-factory
# Setting up the factory in a repo
A track is enabled **per repo**, in that repo's own `.claude/settings.json`. That is
deliberate: App Store skills have no business loading in a website, and a plugin
installed at user scope loads in every directory on the machine.
The cost of that choice is a failure with no symptom — a repo where nothing was
enabled looks exactly like a repo where the skills decided they were not relevant.
Both are silence. This skill exists to break it.
## Prerequisites
- **Tools:** none beyond Claude Code and Python 3 (stdlib).
- **Credentials:** none.
- **Hub (`$APP_HUB`):** not used.
- **Other tracks:** none — this one is about which of them load.
The marketplace has to be known to this machine once:
```bash
claude plugin marketplace add <path-or-github-repo>
```
## Workflow
**1. Look at what is already on.**
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/enable.py --check
```
It prints which tracks this repo has, and — when it has none — what the repo looks
like and which tracks would follow.
**2. Enable them.** The proposal comes from files the project has whether or not
anyone described it: an `.xcodeproj`, a `build.gradle`, a `capacitor.config.ts`.
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/enable.py --yes # take the proposal
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/enable.py --tracks a,b # choose instead
```
The tool ships inside this plugin, so that path exists on any machine that installed
the marketplace — including one th