floc

Plugin floc from marketplace floc in AidanInceer/Floc. Commands read from the repo's manifest — today.

Skills (25)

• add-mobile-dep

  Add or upgrade a package in the Floc Expo app (floc/apps/mobile) at the version the SDK pins, then rebuild what the change needs — Metro restart, prebuild, or native rebuild. Use when the user says /floc:add-mobile-dep, "install X in the app", "add a native module", "upgrade an Expo package", or whe

• analytics

  Collect fresh Floc numbers into the private metrics board (C:\dev\Floc\metrics), serve it on http://localhost:4200 and open it in the browser pane, then say what it shows. Counts and hashed ids only, no PII. Use when the user says /floc:analytics, "run analytics", "show me the metrics", "open the me

• audit

  Walk the whole running Floc website as a signed-in member and report what is wrong or missing — bugs, pages that say something untrue, two pages that disagree, broken house rules, and product gaps measured against the mission, the decision log and the backlog. Reports in chat and in docs/process/sit

• feedback

  Turn what the user noticed in the built product — "that's not what I meant", something off, something missing — into tickets in AidanInceer/Floc, each traced to why it drifted, and fix the mission page or decision log so it does not happen again. Use when the user says /floc:feedback, reviews a buil

• grill

  Grill the user in rounds of 2–4 questions about a Floc plan, idea or `grilling` ticket until every decision is settled, then write the decisions and acceptance criteria into the ticket and hand over to /floc:implement-feature. Use when the user says /floc:grill, "grill me", "stress-test this", or /f

• implement-feature

  Take a feature — from prior context, a prompt, or one or more tickets — and build it on Floc web and app test-first, checking parity, UI consistency and docs, then report a short summary. Use when the user says /floc:implement-feature, or after a grilling or prototyping session wants the agreed feat

• improve-codebase-architecture

  Find places in the Floc code where one idea is written in many files, or where a file does too many jobs, and write a plain-English report of what to change and why. Then grill the pick and hand it over to tickets or a build. Use when the user says /floc:improve-codebase-architecture, "architecture

• marketing

  Make and iterate on a Floc marketing post (Reel or stills) in the marketing studio — build variants, act on the timed notes Aidan leaves in the studio, refine the pick, then render it into the raw → reviewed → live pipeline. Use when the user says /floc:marketing, "new marketing post", "make variant

• pickup-ticket

  Show the top five startable tickets on the Priority stack in AidanInceer/Floc, let the user choose one, then start work on it. Use when the user asks what's next, or wants to pick up the next ticket.

• prioritise-tickets

  Order and tag every unprioritised open issue in AidanInceer/Floc, give each a phase, prefix each title with its feature category, and write the result to the phased Priority stack issue. Use when the user wants to prioritise the backlog, groom ticket order, or fix ticket labels and titles.

• prototype

  Build a throwaway prototype or mock-ups to answer a design question. Use when the user says /floc:prototype, asks for mock-ups, variants or options ("give me four mock-ups", "two more like C"), wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like —

• push

  Ship the current task worktree to develop — one commit through the pre-commit gate, a PR to develop that merges itself when CI is green, a ci-watch agent that reports red or merged, then docs, worktree close and a summary after the merge. Use when the user says /floc:push, "push this", "ship it", or

• release

  Release develop to main for AidanInceer/Floc — one version for the batch, a release PR that merges itself once the full checks and Sonar pass, a ci-watch agent that reports red or merged, then a finish step that confirms production serves it and closes the tickets. Use when the user says /floc:relea

• reset-dev-db

  Put the Floc dev database back to the exact same seeded state every time — empty local.db and the uploads folder, then load scenarios A and B with fixed ids — and sign the web and phone back in. Use when the user says /floc:reset-dev-db, "reset the db", "start fresh", "back to the seed state", or wa

• retro

  Review a Floc coding session and suggest changes to the agent's setup — checks, rules, pointers and tools — most severe first. Use when the user says /floc:retro, "retro", "retrospective", "why did the agent get that wrong", or wants the agent to do better next time.

• review-docs

  Act on the marks a person left in the local docs editor — delete red highlights, tighten yellow ones, resolve comments, and repair markup the editor broke. Use when the user says /floc:review-docs, "review the docs", or "go through my doc comments".

• rotate-secrets

  Rotate the Floc production credentials stored in Railway (BETTER_AUTH_SECRET, CRON_SECRET, TURSO_AUTH_TOKEN, GOOGLE_CLIENT_SECRET, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET) in one run with one redeploy. Use when the user says /floc:rotate-secrets, "rotate the secrets", "rotate keys", or after a prov

• run

  Bring up the whole Floc development loop — Pixel 9 emulator, floc-web dev server, Metro, and the mobile app — then confirm each piece is actually answering. Use when the user says /floc:run, "start everything", "launch the emulator", or wants to test a feature on the phone.

• scenario

  Drop Aidan straight into a Floc moment that is hard to reach from the dev account — a new sign-up, the first-trip walkthrough, an invite link, a guest who signs up, a dead link, the "keep these countries?" question after being removed. Resets a dev database, starts the web server and opens a link th

• schema-change

  Change the Floc database schema end to end — edit schema.ts, generate the migration, apply it to local.db, update the ERD, and keep the invariants. Use when the user says /floc:schema-change, "add a column", "new table", "change the schema", or any work that edits floc/apps/web/src/db/schema.ts.

• security-loop

  Score the Floc website's security with three blind reviewers (two Opus 5.5, one Sonnet 5.5), fix what they prove test-first, and review once more. Stops when all three score 9.0/10 or more, or after two rounds. Covers sign-in and sessions, trip access, data leaks, injection, files and mail, failure

• seed-dev-db

  Load the Floc dev scenarios (A and B) into local.db alongside whatever is already there, so the web and phone apps have trips, friends, packing claims, money and profiles to test with — and sign in as any seeded person. Use when the user says /floc:seed-dev-db, "seed the db", "load scenario A/B", "I

• sync-docs

  Find every Floc doc page that the current diff makes untrue, fix it with the smallest edit in the same slice, and run pnpm docs:check. Restrained by default — most changes need a line or two on an existing page, or nothing; never a new page without asking. Use when the user says /floc:sync-docs, "up

• tdd

  Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

• to-tickets

  Break a plan, spec, or conversation into tracer-bullet GitHub issues in AidanInceer/Floc, each labelled and declaring its blocking edges. Use when slicing a feature into tickets.

Subagents (3)

• ci-watch

  Watches one Floc PR's CI until it settles and reports back — merged, red (which check and why) or a conflict. It never edits code. /floc:push and /floc:release start it in the background for every PR they open; also started by hand for a red develop or main commit. The prompt names the PR number, or

• design-review

  Fresh-eyes visual review of a Floc UI change before it is called done. Reads the diff and the screenshots it is given (web at 1280 and 375, light and dark, the phone, and the chosen mockup if there is one), checks them against the design card and the visual language, and returns findings most severe

• security-reviewer

  One blind security review of the Floc website. Reports every finding it can prove and a score out of 10 to one decimal place, worked out from those findings. Reads the code and probes the local dev server it is given; edits nothing. Started three at a time by /floc:security-loop, or by hand.

Similar plugins