Max prompt

Skill kennykankush/skillpack/plugins/workbench/skills/max-prompt

My daily-driver Claude Code and Codex loadout

Install

npx -y skills add kennykankush/skillpack --skill max-prompt

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Turn vague feedback, screenshots, taste, frustration, or half-formed product intuition into an implementation-ready prompt for a coding agent. Use for UI/UX bugs, frontend polish, animation behavior, component architecture, and "it feels wrong but I don't know how to say it" moments.

SKILL.md

1.5 KB, 252 tokens by cl100k_base, as published. Nobody here has run it

Max Prompt

Purpose

Use this skill when the user wants help turning vague feedback, screenshots, taste, frustration, or half-formed product intuition into a strong prompt for a coding agent.

This skill is especially useful for:

UI/UX bugs
frontend implementation
React/TypeScript components
CSS layout and visual polish
animation behavior
GSAP / Framer Motion issues
interaction design
gesture/snap behavior
component architecture
state/lifecycle bugs
“it feels wrong but I don’t know how to say it” moments

The goal is to translate the user’s instinct into an implementation-ready prompt.

Do not simply restate the user’s words.

Convert their feeling into:

the underlying mechanism
the likely root cause
the correct architecture or ownership
the intended visual/interaction model
explicit constraints
state priority rules
lifecycle rules
animation cleanup rules
concrete implementation direction
expected verification behavior

Core Philosophy

The job is not to “write a better prompt.”

The job is to convert taste into engineering language.

The formula:

Feeling → Mechanism → Ownership → Constraints → Implementation → Expected Result

Gives 0 of the 12 instructions most design frontend skills give in 252 tokens

Counted across 1,170 of the 1,878 authors here whose files we hold, read 2026-08-06

use css variables for color consistencyin 73 of 1170, across 24 files
match implementation complexity to the aesthetic visionin 70 of 1170, across 20 files
commit to one bold aesthetic direction before codingin 70 of 1170, across 25 files
add atmospheric background effects and texturesin 58 of 1170, across 10 files
use unexpected spatial compositions and layoutsin 55 of 1170, across 7 files
implement real working codein 55 of 1170, across 7 files
vary themes and aesthetics across different designsin 48 of 1170, across 7 files
launch chromium in headless modein 47 of 1170, across 4 files
close the browser when donein 47 of 1170, across 4 files
run provided scripts with help flag firstin 47 of 1170, across 4 files
use descriptive selectors for elementsin 47 of 1170, across 4 files
wait for network idle statein 46 of 1170, across 3 files

Said here and by no other author read

Convert user taste into engineering language
Translate feeling into underlying mechanism
Identify the likely root cause
Define correct architecture or ownership
Specify explicit constraints
Provide concrete implementation direction

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.