house-conventionslisted

Use before writing any code, spec, or store asset on a Mobify Studio app — loads the relevant House Knowledge Base pack(s) so output matches the studio's established conventions instead of generic defaults. Every IC invokes this first; execs invoke it when their document names a platform, version, library, or store surface.
vmobifystudio/app-dev-team · ★ 4 · AI & Automation · score 74

Install: claude install-skill vmobifystudio/app-dev-team

# House conventions The plugin ships a House Knowledge Base under `knowledge/` mined from our internal shipped apps. This skill is how an agent loads the right pack before working, so what it produces looks like the studio's other apps — same architecture, same monetization patterns, same store hygiene. ## When to use Invoke this **before** the first edit/spec on any ticket, sprint, or asset. It costs one read and prevents a whole class of "this doesn't match how we build" rework. ## Procedure 1. Identify what you're about to do and load the matching pack(s). The packs live at **`${CLAUDE_PLUGIN_ROOT}/knowledge/<pack>.md`**. If `CLAUDE_PLUGIN_ROOT` is not set in your environment, glob for `**/knowledge/stack-defaults.md` inside the plugin install and read the packs from that directory. If you genuinely cannot locate the packs, **STOP and report a blocker** — do not silently proceed on generic defaults; that is exactly the failure this skill exists to prevent. | You are about to… | Read | |---|---| | Pick stack / versions / libraries | `stack-defaults.md` | | Write or review iOS code | `ios-conventions.md` (+ `stack-defaults.md`) | | Write or review Android code | `android-conventions.md` (+ `stack-defaults.md`) | | Add ads, IAP, or a paywall | `monetization.md` | | Add analytics / events / KPIs | `analytics.md` | | Prepare store assets / submission | `aso.md` | | Set up git, CI, signing, releases | `git-workflow.md` | | Write