agentsclimarketplace

Max prompt

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

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.From its SKILL.md

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.

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.