content

Plugin content from marketplace rumblejack-skills in RumbleJack56/skills. Commands read from the repo's manifest — 11 days ago.

Skills (22)

• content-principles

  The psychology behind short-form content that holds attention. Use it whenever you plan, write, review or edit a short-form video script (Reels, TikTok, Shorts), a hook, or a social post. It teaches how a viewer's mind works, never a template to fill in, so apply the principles silently instead of t

• client-state-setup

  Sets up client state in an Expo React Native app with Zustand. It decides where each piece of state lives, then makes small stores for cross-route drafts, shared UI state and persisted preferences. Use for Zustand, stores, global or UI state, multi-step forms, values passed back between screens, per

• engineering-lifecycle

  Four-phase workflow for substantial engineering work: Explore, Design, Execute, Verify. Spends reasoning on ambiguity and trade-offs, freezes the approved plan as an execution contract, runs the work in dependency-ordered batches, and proves correctness with automated checks instead of code inspecti

• ota-playbook

  Sets up and runs releases for an Expo React Native app: EAS Update, runtime version, channels, rollouts, rollbacks and a server-enforced minimum app version (HTTP 426). Use for OTA updates, expo-updates, build-or-update decisions, hotfixes, forced updates, release planning, or breaking backend chang

• senior-dev

  Lazy senior developer discipline for any code change: solve the whole problem with the least new code. Maps every place a change must reach (callers, tests, fixtures, config, exports) and what it could break, then takes the first option that fully works: skip it, reuse the codebase, the standard lib

• server-api-setup

  Sets up server state in an Expo React Native app with Supabase, Zod and TanStack Query: feature modules (schema, api, queries, mutations), query keys, stale times, invalidation, Realtime and the auth session. Use for any data fetching, Supabase query or mutation, React Query, cache invalidation or s

• design-taste-frontend

  tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict n

• backlog

  Manage tasks that were planned for today but not done, and the overall backlog of the second brain, with no guilt. Use when the user asks about the backlog, what keeps slipping, a task has slipped three times, or says /backlog, or when daily-review reports a task at slips 3. Shows at most 8 lines an

• brain-notes

  Conventions of the user's second brain (an Obsidian vault that is also a Claude Code directory): the FLAP note tags, the folder layout, the project file format, the task line format and the rules for reading and writing notes through the brain engine. Use when working inside a brain folder or throug

• brain-setup

  Set up the user's second brain: one folder that is an Obsidian vault, a Claude Code directory and a private git repo, with the inbox, projects, daily, routines and knowledge-base layout, short slash commands, hooks and a project link. Use when the user wants to set up, start, repair or move their se

• capture

  Save anything the user wants to remember or do into the second brain's inbox without sorting, planning or answering it. Use automatically when a message states something to remember or do instead of asking a question or giving a command: 'need to...', 'remind me to...', 'don't forget...', 'idea:', '

• daily-review

  Run the second brain's day rhythm: the morning review (routines, due reminders, inbox count, today's plan), the evening wrap (flush live tasks, record wins, roll unfinished work back with no guilt) and the weekly review. Use when the user says good morning, morning, check-in, wrap up, end of day, we

• overwhelm

  Help the user when they are overwhelmed and cannot start: dump everything, pick three, shrink the first to a five-minute step, start a timer. Use when the user says they are overwhelmed, it is too much, they cannot start, they are stuck or frozen, they send a huge unstructured list, or /overwhelm. A

• plan

  Choose what the user does next or today from their second-brain task graph, matched to energy and time. Use when the user asks what to do next, what to work on, to plan their day, what is due, what is blocked, or says /next, /today or /all. Read-only: it picks and explains, it does not do the task.

• playbook

  Create, find and run the user's playbooks, methods and guides: repeatable processes they learnt or wrote down in the second brain. Use when the user asks how they do something, wants to turn what they just did into a repeatable process, wants a checklist from a playbook, or says /playbook. Playbooks

• project-sync

  Keep a second-brain project and its code repo in step: write the objectives, status and handoff files, change a project's state, link a repo, and wrap up a finished project. Use when the user starts, pauses, resumes or finishes a project, asks for a status or handoff note, says what a project is for

• refine

  Turn the user's fleeting notes into knowledge: literature notes on sources, atomic notes in the user's words, and knowledge-base notes about people, things, systems and playbooks. Everything it writes is a draft with a source link until the user confirms with one word. Use when the user says refine,

• reminders

  Set, list, snooze and clear reminders in the second brain, and turn on the optional phone notification. Use when the user says remind me, don't let me forget, what reminders do I have, snooze that reminder, or /remind, /due. A reminder is a dated line in the vault, so it survives everything and neve

• route

  Sort the second brain's inbox: move fleeting notes into the right project as tasks, snooze them, or propose a new project when 5 or more related items appear. Use when the user says route, triage, sort my inbox, process my notes, or /route, when the morning review reaches the inbox, or when a captur

• routines

  Create and edit the recurring routines of the second brain: daily template items, weekday habits, weekly and monthly chores. Use when the user wants something to happen every day, every week or every month, wants to add or change a daily checklist item, move a routine, or asks what their routines ar

• task-graph

  Add, break down and fix tasks in a second-brain project so the planner can use them. Use when the user wants to add a task to a project, break something big into tasks, set dependencies, due dates, energy or effort, mark something finished by name, or fix lint errors in tasks.md. Also use for /done

• setup-vps

  Sets up a fresh or existing VPS/Linux server over SSH as root. It creates users (with or without sudo), SSH keys and passwords, a `deploy` service user and group, shared group directories (/srv, /shared) with setgid and default ACLs, a firewall (SSH/80/443), fail2ban, rootless Podman, and optionally