[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DM0SV6VBG96FSNWM3C1ZT2":3,"skill-same:01M7DM0SV6VBG96FSNWM3C1ZT2":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7DM0SV6VBG96FSNWM3C1ZT2","build-feature",null,"Implement an approved feature spec end to end on its own branch\u002Fworktree. Migration → backend endpoint + tests → mobile adapter + screen + analytics → gates → E2E flow → PR → review. Use after feature-discovery has produced an approved spec, or when asked to build a specced ticket.","foxinthehenhouse\u002Fapp-in-a-box","foxinthehenhouse","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F144333692?v=4","01M7DKXRK1CCGY9F45FYGWVD29","Kyle Fox","01M7DKXRKNG8A1ADJFXVH15RXT",0,"MIT","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fbuild-feature\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: build-feature\ndescription: Implement an approved feature spec end to end on its own branch\u002Fworktree. Migration → backend endpoint + tests → mobile adapter + screen + analytics → gates → E2E flow → PR → review. Use after feature-discovery has produced an approved spec, or when asked to build a specced ticket.\nargument-hint: \"\u003Cspec path or ticket id>\"\nallowed-tools: \"Bash(git:*), Bash(gh:*), Bash(scripts\u002Fdev-venv.sh:*), Bash(npm:*), Bash(npx:*), Bash(maestro:*), Bash(cd:*), Read, Glob, Grep, Edit, Write\"\n---\n\n# Build feature\n\nInput: an approved spec in `docs\u002Fproduct\u002Fspecs\u002F`. No spec means you run\n`feature-discovery` first.\n\n**Claude Code accelerators (optional, both cost more tokens):**\n- *Thorough mode:* the `build-feature` Workflow (`.claude\u002Fworkflows\u002Fbuild-feature.js`)\n  runs this same order as a script: plan, tests first, backend and mobile in parallel,\n  break-it self-review, draft PR, then the `pr-review` workflow. Use it only when the\n  owner asks for it.\n- *Several specced tickets at once:* spawn one background subagent per ticket with\n  `isolation: worktree`, so each builds in its own checkout, and review each PR as it\n  lands. In Codex, run tickets one after another (or in separate `codex --worktree`\n  sessions).\n\n## Order of work (each step verified before the next)\n\n0. **Re-screen the risk:** `python3 scripts\u002Frisk_gate.py rescreen --file \u003Cspec path>`.\n   A feature can carry the idea into a category it was never screened for (a map, a\n   chat, a kids mode, a health log). If it reports a new category, the tier may rise and\n   it opens that category's must-answer questions: stop and put them to the owner in one\n   structured round before any code, write each answer back to `design\u002Fbrief.json` →\n   `risk`, add the misuse case it asks for, and regenerate `docs\u002Fproduct\u002FRISK.md`. The\n   answers usually change the design (who consents, who sees what, how long it's kept),\n   and `ship` refuses while any stays open.\n1. **Branch:** `new-worktree` skill → `feat\u002F\u003Cticket>-\u003Cslug>`.\n2. **Tests first where it's cheap:** write the FR→TC tests from the spec's test plan\n   (backend pytest; pure mobile logic in jest). Watch them fail.\n3. **Migration** (if any): new timestamped file, additive, RLS, rollback in header.\n4. **Backend:** service (pure logic) → router (I\u002FO, `get_current_user`, scoped by\n   `user.id`) → `Wire` response model. `scripts\u002Fdev-venv.sh python -m pytest -q`.\n5. **Mobile:** `*Wire` type + adapter in `lib\u002Fapi.ts` → screen from `components\u002Fui`\n   primitives + theme tokens → analytics helpers (view event, success+failure) → honest\n   loading\u002Fempty\u002Ferror states → testIDs. `cd mobile && npm run gates`, which must pass\n   the accessibility checks too: `mobile\u002Fscripts\u002Fcheck-a11y.js` (a role and a label on every control,\n   images labelled or decorative, text that scales, motion through `lib\u002Fmotion.ts`) and\n   `mobile\u002F__tests__\u002Fa11y-screens.test.tsx` (every route at 100% and 200% text). Fix the\n   screen; an `\u002F\u002F a11y-ignore: \u003Cwhy>` is for a real exception the reviewer can judge.\n   Then `python3 scripts\u002Fa11y_labels.py` and commit `docs\u002Fproduct\u002FACCESSIBILITY.md` if\n   it changed (CI fails on a stale one). Build to\n   `docs\u002FDEFAULTS.md` unless the spec or the ledger overrides it: ask for a permission\n   only from the moment it's useful, after the payoff; a notification goes out at most\n   once a day, never in quiet hours (9pm to 8am local), and points at the core loop.\n6. **E2E:** give the new screen a root `\u003Cscreen>-screen` (or `-sheet`) testID and add\n   a flow under `mobile\u002F.maestro\u002F` for its happy path (`check-maestro-coverage` in the\n   gates fails without one). Write the flow even when `maestro` isn't installed here:\n   the YAML is the spec of the happy path. Run it through the Maestro MCP\n   (`list_devices` → `run`; `inspect_screen` when a selector misses) and say in the PR\n   whether it ran on a device, only passed `maestro check-syntax`, or is\n   written but unrun. Never report an E2E pass you didn't watch. See `docs\u002Fqa\u002FMAESTRO.md`.\n7. **Self-review:** re-read your diff as a hostile reviewer. What would break for a\n   user on last month's app build? What if the request comes from a different user?\n   What if the user taps twice on a slow network? For each important test, **break\n   the code on purpose** (drop the filter, pick the wrong row, skip a field) and\n   confirm the test goes red. A test whose fixture can't tell right from wrong\n   (e.g. \"latest by X\" where X and list order agree) proves nothing.\n8. **Context:** update `AGENTS.md` → \"Where things live\" (a new screen, router,\n   service or table gets its row; the harness lint fails CI otherwise), and any\n   rule or product line this feature made untrue. Future agents read this first.\n9. **PR:** draft PR, body = spec link + what changed + how it was verified (real\n   command output). Then run the `land` skill, which reviews (`pr-review`), fixes, waits on CI\n   and merges. After it merges, run `next`.\n\n## Never\n\n- Weaken or delete a test to get green.\n- Change a wire field in place (add alongside).\n- Claim done on code you didn't run.\n- Widen scope silently. File a ticket for anything you notice and keep going.\n- Build past a re-screen with open risk questions, or edit `design\u002Fbrief.json` → `risk`\n  to quiet the gate. The owner answers or accepts them.\n\n## Ask the owner\n\nFollow `.agents\u002Frules\u002Fproduct-judgement.md`: ask with a structured question (recommended option first), never decide these silently. In this skill that means: Anything the spec didn't settle that a user would notice: an extra state or screen, cutting an acceptance criterion, copy, a default value, a limitation you'd ship with. Stop and ask before building it, not in the PR afterwards. Pure implementation choices stay yours.\n","# Build feature\n\nInput: an approved spec in `docs\u002Fproduct\u002Fspecs\u002F`. No spec means you run\n`feature-discovery` first.\n\n**Claude Code accelerators (optional, both cost more tokens):**\n- *Thorough mode:* the `build-feature` Workflow (`.claude\u002Fworkflows\u002Fbuild-feature.js`)\n  runs this same order as a script: plan, tests first, backend and mobile in parallel,\n  break-it self-review, draft PR, then the `pr-review` workflow. Use it only when the\n  owner asks for it.\n- *Several specced tickets at once:* spawn one background subagent per ticket with\n  `isolation: worktree`, so each builds in its own checkout, and review each PR as it\n  lands. In Codex, run tickets one after another (or in separate `codex --worktree`\n  sessions).\n\n## Order of work (each step verified before the next)\n\n0. **Re-screen the risk:** `python3 scripts\u002Frisk_gate.py rescreen --file \u003Cspec path>`.\n   A feature can carry the idea into a category it was never screened for (a map, a\n   chat, a kids mode, a health log). If it reports a new category, the tier may rise and\n   it opens that category's must-answer questions: stop and put them to the owner in one\n   structured round before any code, write each answer back to `design\u002Fbrief.json` →\n   `risk`, add the misuse case it asks for, and regenerate `docs\u002Fproduct\u002FRISK.md`. The\n   answers usually change the design (who consents, who sees what, how long it's kept),\n   and `ship` refuses while any stays open.\n1. **Branch:** `new-worktree` skill → `feat\u002F\u003Cticket>-\u003Cslug>`.\n2. **Tests first where it's cheap:** write the FR→TC tests from the spec's test plan\n   (backend pytest; pure mobile logic in jest). Watch them fail.\n3. **Migration** (if any): new timestamped file, additive, RLS, rollback in header.\n4. **Backend:** service (pure logic) → router (I\u002FO, `get_current_user`, scoped by\n   `user.id`) → `Wire` response model. `scripts\u002Fdev-venv.sh python -m pytest -q`.\n5. **Mobile:** `*Wire` type + adapter in `lib\u002Fapi.ts` → screen from `components\u002Fui`\n   primitives + theme tokens → analytics helpers (view event, success+failure) → honest\n   loading\u002Fempty\u002Ferror states → testIDs. `cd mobile && npm run gates`, which must pass\n   the accessibility checks too: `mobile\u002Fscripts\u002Fcheck-a11y.js` (a role and a label on every control,\n   images labelled or decorative, text that scales, motion through `lib\u002Fmotion.ts`) and\n   `mobile\u002F__tests__\u002Fa11y-screens.test.tsx` (every route at 100% and 200% text). Fix the\n   screen; an `\u002F\u002F a11y-ignore: \u003Cwhy>` is for a real exception the reviewer can judge.\n   Then `python3 scripts\u002Fa11y_labels.py` and commit `docs\u002Fproduct\u002FACCESSIBILITY.md` if\n   it changed (CI fails on a stale one). Build to\n   `docs\u002FDEFAULTS.md` unless the spec or the ledger overrides it: ask for a permission\n   only from the moment it's useful, after the payoff; a notification goes out at most\n   once a day, never in quiet hours (9pm to 8am local), and points at the core loop.\n6. **E2E:** give the new screen a root `\u003Cscreen>-screen` (or `-sheet`) testID and add\n   a flow under `mobile\u002F.maestro\u002F` for its happy path (`check-maestro-coverage` in the\n   gates fails without one). Write the flow even when `maestro` isn't installed here:\n   the YAML is the spec of the happy path. Run it through the Maestro MCP\n   (`list_devices` → `run`; `inspect_screen` when a selector misses) and say in the PR\n   whether it ran on a device, only passed `maestro check-syntax`, or is\n   written but unrun. Never report an E2E pass you didn't watch. See `docs\u002Fqa\u002FMAESTRO.md`.\n7. **Self-review:** re-read your diff as a hostile reviewer. What would break for a\n   user on last month's app build? What if the request comes from a different user?\n   What if the user taps twice on a slow network? For each important test, **break\n   the code on purpose** (drop the filter, pick the wrong row, skip a field) and\n   confirm the test goes red. A test whose fixture can't tell right from wrong\n   (e.g. \"latest by X\" where X and list order agree) proves nothing.\n8. **Context:** update `AGENTS.md` → \"Where things live\" (a new screen, router,\n   service or table gets its row; the harness lint fails CI otherwise), and any\n   rule or product line this feature made untrue. Future agents read this first.\n9. **PR:** draft PR, body = spec link + what changed + how it was verified (real\n   command output). Then run the `land` skill, which reviews (`pr-review`), fixes, waits on CI\n   and merges. After it merges, run `next`.\n\n## Never\n\n- Weaken or delete a test to get green.\n- Change a wire field in place (add alongside).\n- Claim done on code you didn't run.\n- Widen scope silently. File a ticket for anything you notice and keep going.\n- Build past a re-screen with open risk questions, or edit `design\u002Fbrief.json` → `risk`\n  to quiet the gate. The owner answers or accepts them.\n\n## Ask the owner\n\nFollow `.agents\u002Frules\u002Fproduct-judgement.md`: ask with a structured question (recommended option first), never decide these silently. In this skill that means: Anything the spec didn't settle that a user would notice: an extra state or screen, cutting an acceptance criterion, copy, a default value, a limitation you'd ship with. Stop and ask before building it, not in the PR afterwards. Pure implementation choices stay yours.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Bash(git:*), Bash(gh:*), Bash(scripts\u002Fdev-venv.sh:*), Bash(npm:*), Bash(npx:*), Bash(maestro:*), Bash(cd:*), Read, Glob, Grep, Edit, Write","\u003Cspec path or ticket id>","main","82b5819f074e18b5d31db7a122e1f0ae5f5abbf7","plugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fbuild-feature","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse","Not a developer","2026-10-06 17:24:46",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add foxinthehenhouse\u002Fapp-in-a-box --skill build-feature",{"tool":39,"command":40},"bunx","bunx skills add foxinthehenhouse\u002Fapp-in-a-box --skill build-feature",{"tool":42,"command":43},"pnpm","pnpm dlx skills add foxinthehenhouse\u002Fapp-in-a-box --skill build-feature","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fbuild-feature\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7DM2EPAFBTFNV5EW5GHKD5Q","ship","Release checklist for getting a build to testers or the stores. Runs the risk gate first (refuses while a risk item is open) and walks the owner through the compliance checklist. Covers the version bump, EAS build and submit, OTA updates and when they're safe, changelog, store listing, privacy nutrition label \u002F data safety form, the Accessibility Nutrition Labels, and the account-deletion requirement. Guidance-level; it never handles signing secrets. Use when asked to ship, release, submit to TestFlight \u002F App Store \u002F Play, or push an OTA update.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7DM2AGRJ822B3C8NQCDK3JG","routines","Put the project's recurring rituals on a schedule, with the owner's consent. Weekly north-star report, monthly market watch, dependency triage, Supabase advisor sweep, reflect and harness-optimize. Uses Claude Code Routines (cloud cron) where they fit, and documents the Codex \u002F local cron equivalent. Use when asked to automate, schedule or \"keep the project moving on its own\", or after setup finishes.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Froutines\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DM27C3K1Y7FM0NZSBRSVEN","reflect","Consolidate what recent sessions learned into the project's long-term memory (.agents\u002Fmemory). Use at the end of a substantial session, after a correction from the user, after a painful debugging session, when the session-start healthcheck says reflect is overdue or a pending-reflection seed is waiting, or when MEMORY.md exceeds its budget.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Freflect\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7DM2146TCNYXVVS2QXF08GS","pr-review","Review a pull request on the owner's behalf and fix what's safe to fix. Runs the deterministic gates first, then correctness\u002Fsecurity, design-system, accessibility and analytics review passes, verifies each blocking finding, applies safe fixes, re-checks, and ends with a plain-English verdict. Use when a PR is opened, when asked to review a PR, a branch or a pasted diff, or before merging anything.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fpr-review\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DM1X6QP3QAT47ET852S0P8","north-star-report","Weekly product-analytics and reliability readout. Pulls the funnel of the brief's 5 north-star events from PostHog, finds the biggest drop-offs and errors, checks each SLO in docs\u002Fslo.yaml against its error budget, compares with last week, and proposes (then, with a yes, files) tickets that target them. Use weekly, when the session-start line says it's overdue, when the backlog is empty, or when asked \"how is the app doing?\".","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fnorth-star-report\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DM1QX8F3D95JSTEHC0P9QA","next","Decide the single next best thing to work on, with two alternates. Reads setup progress, work in progress, open PRs and failing CI, the backlog (GitHub Issues or Linear), overdue harness rituals, product decisions parked until now, and north-star analytics if PostHog is connected. Use when someone asks \"what next?\", \"what should I work on?\", at the start of a session, or after a PR merges.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fnext\u002FSKILL.md",[],[]]