agentleFS
Sign inStart free
Pesty-MarketingPesty-Marketing/agent-skills/pesty-design/SKILL.md

pesty-design

Skill0 starsChanged 26 days agoMITView on GitHub

Use this skill to generate well-branded interfaces and assets for Pesty Marketing (the #1 pest control marketing agency — SEO, PPC & web design), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping. This is the default Pesty design system for all new frontend work.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the readme.md file within this skill, and explore the other available files.

    line 7
  2. Distinctive:

    If creating visual artifacts (slides, mocks, throwaway prototypes, etc), copy assets out and create static HTML files for the user to view.

    line 8
  3. Distinctive:

    If the user invokes this skill without any other guidance, ask them what they want to build or design, ask some questions, and act as an …

    line 9
  4. Very specific:

    When building static artifacts, copy the assets and the relevant CSS into your output folder and link styles.css (or inline the tokens you …

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Read the readme.md file within this skill, and explore the other available files. If creating visual artifacts (slides, mocks, throwaway prototypes, etc), copy assets out and create static HTML files for the user to view. If working on production code, you can copy assets and read the rules here to become an expert in designing with this brand. If the user invokes this skill without any other guidance, ask them what they want to build or design, ask some questions, and act as an expert designer who outputs HTML artifacts or production code, depending on the need.

Quick reference

  • Brand: Pesty Marketing — pest control marketing agency. Voice is confident, aggressive, results-obsessed ("dominate your market," lead with real numbers). See readme.md → CONTENT FUNDAMENTALS.
  • Colors: Pesty Red #D90429 (primary/CTAs/accents, used sparingly), Deep Teal #002330 (dark surfaces/headings), white canvas. Full token set in tokens/colors.css.
  • Type: Epilogue (display, 700–800), Montserrat (body), JetBrains Mono (data). See tokens/typography.css. These are Pesty's actual brand fonts (loaded from Google Fonts).
  • Foundations: link styles.css to inherit every token. Cards 16px radius + soft cool shadow; buttons/badges/tags are pills; motion is quick with no bounce; primary buttons glow red on hover.
  • Icons: Lucide-based set in components/core/Icon.jsx (24px, 2px stroke). No emoji.
  • Assets: assets/brand/ — logo (light/dark) + mark/favicon.
  • Components: React primitives under components/ — Button, IconButton, Icon, Badge, Tag, Stat, Card, Avatar, Input, Textarea, Select, Checkbox. Each has a .prompt.md.
  • Dashboards / data-dense UI (internal tools, admin panels, analytics dashboards, client reports): the same light system tuned for density. Components — DataTable, KpiTile, KpiGrid, StatusPill, DeltaPill, Tabs, Chip, SectionHeader, DashboardShell (+ Sidebar, Topbar). Rules + density spec in readme.md → DASHBOARDS & DATA-DENSE INTERFACES; density tokens in tokens/dashboard.css. Copy the working example at ui_kits/dashboard/index.html.
  • UI kits: ui_kits/marketing-site/ — interactive recreation of pestymarketing.com; ui_kits/dashboard/ — self-contained dense-dashboard example. Copy patterns from either.
  • Templates: templates/ — ready-to-seed starting points.

When building static artifacts, copy the assets and the relevant CSS into your output folder and link styles.css (or inline the tokens you need).

Maintained by Pesty Marketing · Browse the full skill catalog.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free