sc

# sc — the main SI-Coder entry point `sc` is the canonical SI-Coder skill identity. Invocation syntax is chosen by the host product, not by the `.skill` package itself. Examples: - ChatGPT Web: `@sc Create a booking app for my salon with customer and admin access, then put it on my domain.` or ask naturally and let ChatGPT select `sc` automatically. - Claude Code: `/sc Create a booking app for my salon with customer and admin access, then put it on my domain.` - Frontend quality on slash-capable hosts: `/sc-fe --workbench improve the desktop shell` or `/sc-fe --apple refine settings`. ## Language Write the skill instructions and documentation in English, but **reply in the user's language** unless the user asks for another language. ## Intent routing Do not ask the user to choose a SI-Coder sub-skill. - New or vague product idea → follow the `sc-build` skill. - Existing app that needs frontend/UI/UX improvement or any substantial frontend work → follow `sc-fe`. - Focused visual interface request → `sc-ui` through `sc-fe` unless the user explicitly invokes `sc-ui`. - Focused usability/accessibility/interaction request → `sc-ux` through `sc-fe` unless explicitly invoked. - Focused frontend developer-experience request → `sc-dx` through `sc-fe` unless explicitly invoked. - Focused Agent Experience/tool ergonomics request → `sc-ax` through `sc-fe` unless explicitly invoked. - Existing app that needs to go live, change hosting, or attach a domain → follow the `sc-all` skil...