devtools

Build products for developers: devtool interface design, CLI/panel UX, agent experience, devtool onboarding, landing pages/copy/PMF, and OSS strategy. Use for developer-facing product design or GTM. Building the UI itself → frontend-design; client pricing → client-work. Read one named reference. Triggers: command palette, CLI UX, agent experience, devtool landing page, README, maintainer burnout.

Jump to install

Repository: KevinGutowski/Skills
Last source activity: July 10, 2026 at 01:01
Detected SKILL.md language: English
Stars: 1
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/KevinGutowski/Skills --skill devtools

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

10 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

design-craft

Raise design quality and interface feel through craft methodology (noticing, range vs depth, facets, live tuning), execution values (shadows, spacing, radii, alignment, motion, type), and Linear-style quality rituals/triage. Use to critique or polish UI, build taste, decide wider vs deeper, or make quality practice repeatable. Strategy → design-principles; shaping/bets → shape-up. Triggers: feels off, polished, quality ritual, dogfood, unship.

2026-08-13

design-systems

Build, govern, and scale a design system — tokens, theming/multi-brand, governance, adoption as a measured product, DS-as-AI-context, icon systems. Use for creating or auditing a design system or icon set, token taxonomies, adoption planning, or wiring a DS into AI codegen. Apple platform → apple-design; brand marks → logo-design; org AI rollout → working-with-ai. Triggers: design system, design tokens, theming, Code Connect, icon set, icon font.

2026-08-13

frontend-design

Build distinctive, production-grade web UI — components, pages, apps — with a bold committed aesthetic, avoiding generic AI slop. Use when generating or building frontend interfaces. Craft rules/motion values → web-design (web-animation-design); restrained polish → design-craft; repairing AI-generated UI → working-with-ai (ai-ui-direction); generative visuals → creative-coding. Triggers: landing page, hero, component, distinctive UI.

2026-08-13

View all from this repository

Developer Tools

Read exactly one reference file below; each carries the full distillation for its area (sources and extras live in a same-named subdirectory next to it).

Devtool interface design — workbenches not funnels: the five UI zones, control-flow rule, panel layout, CLI progress/output and clean-log rules, command palettes, devtool onboarding to the a-ha moment, agent experience (AX): references/devtool-interface-design.md (AX and dev-data-viz depth: references/devtool-interface-design/data-viz-and-agents.md)

Developer go-to-market — earning adoption and revenue for a commercial devtool: landing-page anatomy and hero/CTA choices, the five conversion killers, devtool copywriting, the PMF Compass (TTFV/retention/NRR), free-to-paid: references/developer-tool-gtm.md

Open source strategy — making an OSS project adopted, sustainable, profitable: Sitnik's popularity formula, progressive-JPEG README, the promotion loop, maintainer burnout survival, monetization/open core: references/oss-strategy.md

Sources and gaps — provenance map and parked candidate standards: references/sources.md, references/coverage-gaps.md

GTM ↔ OSS split: marketing a commercial devtool (landing pages, conversion, PMF) → developer-tool-gtm; promoting an open-source project (README, stars, promotion loop, monetizing OSS) → oss-strategy. The two reference each other directly — "open source users are users, too" is the bridge; follow the link inside whichever you start in when the question straddles both.

Boundary splits to respect:

Building the UI itself → frontend-design — this skill decides what a devtool's UI should be; generating the components/pages lives there.

Pricing client/creative work → client-work (pricing-creative-work) — product/devtool pricing signals (PMF, free-to-paid) live here; pricing and negotiating client engagements live there.

Developer Tools

Read exactly one reference file below; each carries the full distillation for its area (sources and extras live in a same-named subdirectory next to it).

Sources and gaps — provenance map and parked candidate standards: references/sources.md, references/coverage-gaps.md

Boundary splits to respect:

Building the UI itself → frontend-design — this skill decides what a devtool's UI should be; generating the components/pages lives there.

Pricing client/creative work → client-work (pricing-creative-work) — product/devtool pricing signals (PMF, free-to-paid) live here; pricing and negotiating client engagements live there.

devtools

Source facts

Install options

Review the source files

More from this repository

More from this repository

Developer Tools

Developer Tools