DKeken
Publisher identity comes from harvested source metadata and still needs manual verification: https://github.com/DKeken
Repositories
Published skills
Generate up to 25 diverse ad creative hypotheses — an angle × format matrix with headlines, visual prompts, and a testing rationale for each.
Converges on one visual direction by proposing 3-6 named, structurally distinct directions with rationale and reusable prompt stubs, plus one reference image each.
Builds 2-4 named visual territories with palette, texture, typography, and 4-6 generated tiles each so a team can align and sign off on a direction before production spend.
Turns a concrete offer (price, bundle, guarantee, deadline) into 3-5 hero promo visuals that make the value legible within two seconds, never inventing prices or terms.
Takes a chosen visual to production-ready state via diagnose-then-fix passes: inpaint artifacts, balance composition, color-grade, sharpen text, and conform to final size.
Maps business positioning (category, differentiator, audience, foil) onto a defensible visual language spec where every color, type, and imagery rule traces to a strategic reason.
Orchestrator that reads a broad creative goal and routes to the right creative-* sub-skill, sequencing direction, then assets, then polish for a coherent campaign set.
Generates believable product-in-use lifestyle scenes from concrete usage moments (who/where/when/doing-what) with natural light, keeping the product the clear hero.
Produces a consistent multi-angle ecommerce shot set of one product (hero, front, side, macro, packaging) with identity, lighting, and surface locked across every shot.
Audits an existing UI (URL, screenshot, or code) against usability, hierarchy, accessibility, and conversion heuristics, returning a severity-ranked issue list with fixes.
Clarifies the brief before design work by interrogating goal, user, JTBD, constraints, success, and scope, then writing a context.md the other design skills consume.
Generates 2-4 structurally distinct UI directions for a screen or flow, each with layout logic, component choices, and explicit optimizes/sacrifices mapped to the success criteria.
Reproduces a reference mockup as a runnable frontend, extracting its design system then screenshot-comparing the build and iterating until the gap is minor and explained.
Wires static screens into a clickable runnable prototype with routing, interaction states, and stubbed data, then verifies the whole happy path plus an error state in a browser.
Conformance-checks a built prototype against its mockup, context, and success criteria, flagging visual, behavioral, and a11y drift with expected-vs-actual and a verdict.
Gathers outside UX signal via convention scans, 3-5 competitor reviews, and pain mining from forums, synthesizing pains/patterns/gaps into a cited research.md for ideation.
Prepares a QA'd prototype to run cleanly and returns a working link plus run instructions and a review note, choosing local serve, tunnel, or deploy only with explicit consent.
Rebuilds a live site as a clean editable local frontend by extracting design tokens into url-dna.md, then reconstructing in your stack and screenshot-comparing it.
Orchestrator for the design-* set that frames the brief, explores options, builds the chosen direction, gates with QA, and ships, routing each request to a sub-skill.