jacked

Plugin jacked from marketplace jacked-marketplace in jackneil/claude-jacked. Commands read from the repo's manifest — 5 days ago.

Skills (28)

• aesthetic-dogfood-audit

  Use to dogfood and evaluate the SHIT out of a running web app end-to-end — drive it in a browser as EACH real user persona through EVERY workflow (login → core jobs → the nitty-gritty), catching both how it WORKS and how it LOOKS. Finds misalignment, dark-mode dark-text / low contrast, a modal that

• animation-vocabulary

  Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without know

• apple-design

  Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking,

• chain-of-command

  Lock in the session model-dispatch policy - the main loop (Fable, or best available) does ALL strategy, planning, understanding, judging, and verification; every dispatched subagent that writes code or reviews from an established plan runs on Opus; pure locate/sweep hunts run on Haiku or Sonnet. Use

• checkpoint

  Save and resume working state checkpoints. Captures git state, decisions, research, session context, and remaining work so a new session can pick up exactly where you left off. Use when asked to "checkpoint", "save progress", "where was I", "resume", "what was I working on", or "pick up where I left

• claude-md-optimizer

  Use when CLAUDE.md feels bloated or too long, when starting a new project, or when optimizing documentation for token efficiency. Audits content quality, extracts reference material to sub-docs, and enforces a token budget.

• clone-website

  Reverse-engineer and clone one or more websites in one shot: extracts assets, CSS, and content section-by-section and proactively dispatches parallel builder agents in worktrees as it goes. Use this whenever the user wants to clone, replicate, rebuild, reverse-engineer, or copy a website they own or

• coverage-matrix

  Use to analyze product completeness, find gaps, decide what to build next for best-in-class coverage, audit feature depth across user types, or build a prioritized roadmap. Triggers on "what's missing", "gap analysis", "10/10", "best-in-class", "coverage audit", "feature completeness", "what should

• dcr

  Use after implementing a feature, fixing a bug, or completing any non-trivial code change. Risk-tiered multi-lens review - the SMALL/MEDIUM/LARGE tier sets reviewer count and agent budget (4/8/16), findings are validated before fixing, and the run stops after two waves by default.

• demo-video

  Use to produce a polished, narrated product DEMO / walkthrough / how-to video for documentation and education — teaching a feature or capability to end users, to embed in docs, a README, a release note, or onboarding. NOT for bug/regression evidence (that's /qa-video). Triggers include "make a demo

• deploy-to-railway

  Use when deploying a project to Railway from scratch — provisioning a Postgres database, one or more app services (a full-stack monolith OR separate frontend/backend), an S3-compatible bucket, sharing credentials + env vars between services, wiring GitHub auto-deploy on merge to main, and adding aut

• docs-sync

  Use when a branch has code changes that may have made documentation stale, after completing a feature, or before creating a PR. Diffs branch against base and maps changes to affected docs.

• emil-design-eng

  This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

• jack-it-up

  Use when starting any significant feature or non-trivial task that deserves a thorough development cycle. Triggers on "jack it up", "do this right", "full cycle", "build this properly", or when the user wants quality-first development over speed.

• launch-post

  Use when the user wants to announce, launch, promote, ship, or showcase a project, repo, feature, demo, or release on X (Twitter) — including deciding what to highlight, creating the media, and publishing the post + replies. LinkedIn support planned.

• lockdown

  Use when auditing or hardening a repository against software supply-chain attacks — including dependency lockfile integrity, CVE scanning, malware/typosquat detection, GitHub Actions SHA pinning, secrets scanning, provenance/signing, and SLSA/HIPAA control mapping. Triggers on phrases like "lock dow

• logo-forge

  Use when designing or upgrading a brand logo, favicon/app icon, or social link-preview cards (Open Graph / Twitter cards that unfurl in iMessage, Slack, X/Twitter) for a repo or product. Triggers on "design a logo", "make me a logo", "better logo / favicon", "brand mark", "app icon", "social card",

• memory-librarian

  Groom the jacked memory vault for a group. Dedupe notes, reconcile contradictions newest-wins-with-a-trail, review candidate auto-captures, archive stale hot entries, validate frontmatter, and re-sync the index. Use when the SessionStart brief nudges "memory drift is high", when asked to "groom the

• night-shift

  Use when the user wants a product continuously driven forward without them steering each step — an autonomous session (overnight or daytime) that discovers, builds, verifies, and lands improvements across every lens (user types, UX, security, compliance, reliability, DX, product strategy). Triggers

• qa-video

  Use when you want a playable video recording of a QA/test session plus a synced narrated journey — not just screenshots. For regression evidence, "it worked" proof, bug reproduction with motion, or a recorded walkthrough. Pass a URL as argument, or let it auto-detect the running app.

• qa

  Use when testing UI changes for visual correctness, interactions, console errors, and edge cases. Performs browser-based QA and returns a detailed issue list for planning fixes.

• recover

  Use when a Claude Code session in this folder crashed or was lost mid-work (computer died, terminal closed, Claude broke) and the user reopened Claude without a checkpoint and does not know the session ID — rebuild the last session for THIS folder from its on-disk transcript and continue. Any reques

• recursive-10-10-product-hardening

  Use to harden a product to verified 10/10. Derives each feature's expected behavior from the code into a behavior-spec workbook, dogfoods it, fixes defects at the source, and retests until every row is evidence-verified. Triggers on "harden to 10/10", "behavior spec from the code". Arg auto-merge la

• release

  Use when ready to cut a release. Detects how THIS repo actually ships (PyPI, npm, changesets, CalVer, Cargo, Go tag, or PR-to-main deploy), suggests the semver bump, gates on the repo's OWN build+test before anything irreversible, then publishes/deploys the way that repo really ships and verifies it

• review-animations

  Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.

• swarm-research

  Use when approaching non-trivial planning — architectural decisions, major features, system design, or any decision with multiple viable approaches.

• ux

  Use when UI changes span multiple components or pages, layout or navigation changed, a new user-facing feature was added, or comprehensive UX validation is needed. For single-component or bug-fix checks, use the qa skill instead.

• whats-next

  Use when the user wants help choosing or prioritizing what to work on next, or asks where to start. Weighs a coverage-matrix read plus plans, issues, commits, and lifecycle to decide the single highest-leverage initiative and forge a ready-to-run /goal brief.

Slash commands (20)

• /jacked:audit-rules

  Use after adding several rules to CLAUDE.md, or when rules feel contradictory or stale. Audits for duplicates, contradictions, and vague directives. Companion to /learn.

• /jacked:benchmark

  Use before and after performance-sensitive changes. Captures web performance metrics, compares against baselines, flags regressions.

• /jacked:bhag

  Use ONLY when you deliberately want an autonomous, full-product build-out — drive the ENTIRE coverage matrix cell by cell and, on a pre-production repo you explicitly authorize, open a PR and merge each verified improvement to main in a loop until the product is built out. Forges a long-running /goa

• /jacked:blindspot

  Use BEFORE building when a request is vague/underspecified or in unfamiliar territory — surfaces your unknown-unknowns, teaches you enough to prompt well, then asks the must-have questions. Triggers on vague build/feature requests, "I don't know X", a new codebase area or domain, "blindspot pass", "

• /jacked:browser-reset

  Use when browser MCP tools are failing, stuck, or unresponsive. Diagnoses connection issues, kills stale processes, and tests connectivity.

• /jacked:canary

  Use after a production deploy to monitor for regressions. Takes periodic screenshots, checks console errors, and compares performance against baselines.

• /jacked:cleanup

  Verify git hygiene and safely clean branches, stashes, stale worktrees, and untracked state in any repo. Report-first, confirm-each, never loses work.

• /jacked:cso

  Use after implementing security-sensitive changes — auth, RBAC, multi-tenancy, billing, credential handling. Systematic OWASP Top 10 + STRIDE threat model analysis.

• /jacked:dc

  Use after completing a plan, implementation, or any non-trivial code change. Auto-detects phase and risk tier, then reviews inline (small changes) or spawns tiered review threads with pre-mortem analysis.

• /jacked:goal-maker

  Forge a hardcore, overnight-sized /goal brief from the work already in front of you — this conversation, a spec, a plan, or an in-progress build. Use when you ALREADY know what to build and want it packaged for autonomous, fully-tested delivery (TDD + tests green, UI/UX + front-end-polish gates, evi

• /jacked:jacked-setup

  Use when setting up jacked in a new repo or after significant codebase changes. Analyzes the repo and generates faster, customized versions of jacked commands.

• /jacked:land-and-deploy

  Use after a PR is approved and CI passes. Merges, waits for deploy, runs canary checks, and offers revert on failure.

• /jacked:learn

  Use after corrections, mistakes, or when the user wants to codify a preference into a permanent CLAUDE.md rule.

• /jacked:pr

  Use when checking PR status, creating a PR, or managing the pull request workflow for the current branch. Conforms to the repo's own PR template, derives a Conventional-Commits title when the repo uses one, flags breaking changes, writes a release-note line, and can open a draft PR with post-create

• /jacked:redo

  Use when an approach has gone sideways and patching patches. Scraps the current approach and re-implements from scratch with full hindsight after structured reflection.

• /jacked:remember

  Route a durable fact the user asked to remember into the jacked memory vault as a typed, cross-repo note, falling back to native Claude Code memory when the vault is off.

• /jacked:retro

  Use periodically during long sessions or weekly. Analyzes git history for contributor metrics, test health, velocity trends, and team patterns.

• /jacked:retry

  Transient API/rate-limit error — check where you actually fell off, then resume only what's needed without changing the task

• /jacked:swarm

  Use when implementing a plan with multiple independent tasks that can be worked in parallel using Claude Code's experimental agent teams.

• /jacked:techdebt

  Use periodically during long sessions to scan for accumulating debt. Finds TODOs, oversized files, missing tests, linter issues, and dead code. Pass a path to focus on a specific area.

Subagents (10)

• code-simplicity-reviewer

  Use this agent when you need to review recently written code changes with a focus on simplicity, readability, and future-proofing. This agent excels at identifying overly complex implementations and suggesting cleaner, more maintainable alternatives that accomplish the same goals. Perfect for post-i

• defensive-error-handler

  Use this agent when you need to review code for error handling, add comprehensive error management, or audit existing code for potential failure points. This agent excels at identifying missing error handling, suggesting custom exception hierarchies, and implementing defensive programming patterns.

• double-check-reviewer

  Use this agent when you've completed a design document, planning session, or code implementation and want a fresh, critical review. This agent operates in two modes: (1) Design Review Mode - when the recent work involved creating specs, design docs, or planning for features/bugs/enhancements, it per

• git-pr-workflow-manager

  Use this agent when you need help managing git branches, commits, and pull requests to maintain clean, reviewable code submissions. This includes: creating new branches for features or bug fixes, determining when to split work into separate PRs, writing comprehensive PR descriptions and commit messa

• issue-pr-coordinator

  Use this agent when you need to manage GitHub issues and pull requests in a coordinated manner. This includes scanning open issues, analyzing and grouping related issues for efficient resolution, managing PR workflows, and ensuring proper issue tracking throughout the development cycle. The agent ex

• pr-workflow-checker

  Use this agent when you need to check your current PR status and manage pull request workflow. Analyzes current branch state, determines if a PR exists or needs to be created, examines commits and changes, searches for related issues, and handles PR creation/updates with proper issue linking. Perfec

• readme-maintainer

  Use when creating, updating, or syncing a README — and the companion AGENTS.md — so documentation matches the current codebase (entry points, env vars, install, usage, requirements, outputs). Trigger after significant code changes, new features, changed CLI/APIs/env, or when documentation drift is d

• test-coverage-engineer

  Use this agent when you need to analyze, create, update, or maintain comprehensive test coverage for your codebase. This includes writing unit tests, integration tests, end-to-end tests, property-based tests, and ensuring test quality aligns with VibeCoding standards. The agent should be invoked per

• test-coverage-improver

  Use this agent when you need to systematically improve test coverage in a codebase by adding both doctests and separate test files. This agent should be invoked after writing new code, during code review phases, or when explicitly asked to improve test coverage for existing code. Examples:\n\n<examp

• wiki-documentation-architect

  Use this agent when you need to create, update, or maintain comprehensive GitHub Wiki documentation for a project. This includes initial wiki setup with all essential pages, updating existing documentation to reflect code changes, creating project-specific documentation pages, and ensuring documenta

Similar plugins