agentleFS
Sign inStart free
PeanutGTPeanutGT/NutsSkills/skills/design/SKILL.md

design

Skill3 starsChanged 20 days agoApache-2.0View on GitHub

Use when adding a new module, service, API, or data model, choosing between architectural approaches, or when code is hard to test or change. Covers module boundaries, interfaces, domain naming, and recording decisions.

197 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use banner-design, ui-styling and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • seikaikyoSkill

    banner-design

    Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with optional generated or supplied visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage.

    Also in 38 projects that use this

  • MicrosoftSkill

    ui-styling

    Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components.

    Also in 39 projects that use this

  • seikaikyoSkill

    brand

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

    Also in 43 projects that use this

  • mayankjain1815-commitsSkill

    infra-audit

    Reads docker-compose, env files, ORM configs, and connection strings to map current infrastructure. Flags missing layers (cache, queue, analytics) based on observed access patterns. Outputs a structured infrastructure manifest.

    Also in 3 projects that use this

  • JetBrainsSkill

    slides

    Create and edit presentation slide decks (`.pptx`) with PptxGenJS and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding charts/diagrams/visuals, or diagnosing layout issues such as overflow, overlaps, and font substitution.

    Also in 42 projects that use this

  • AnthropicSkill

    design-system

    Audit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system.

    Also in 49 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Core rule: Follow the existing pattern unless you can name the concrete problem it fails to solve.

    line 14
  2. Distinctive:

    Design for testability: If it needs heavy mocking to test, the boundaries are wrong.

    line 23
  3. Distinctive:

    YAGNI: No extension points, plugins, or config for needs that do not exist yet.

    line 24
  4. Distinctive:

    Look at how similar things are done in this codebase.

    line 28
  5. Distinctive:

    If a new approach is warranted, sketch two or three options briefly: interface, data flow, trade-offs.

    line 29
  6. Distinctive:

    Write the public interface (types, function signatures) before the implementation.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 174 edited versions of this file we could read. “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

Design modules and interfaces

Core rule: Follow the existing pattern unless you can name the concrete problem it fails to solve.

Most tasks need no new architecture. Check the codebase first.

Principles

  • Deep modules. A small, simple interface hiding a lot of behavior. Avoid shallow modules whose interface is as complex as their implementation.
  • Information hiding. Each module owns one decision that is likely to change (a storage format, a vendor, an algorithm) and hides it.
  • Dependencies point inward. Business logic does not import frameworks, databases, or HTTP. Adapters depend on the core, not the reverse.
  • Domain language. Name types and functions with the words the users and docs use. If the code says Item but the business says Shipment, fix the name.
  • Design for testability. If it needs heavy mocking to test, the boundaries are wrong. Pass dependencies in.
  • YAGNI. No extension points, plugins, or config for needs that do not exist yet.

Process

  1. Describe the problem and the forces (what changes often, what must stay stable, scale, team).
  2. Look at how similar things are done in this codebase. Prefer that.
  3. If a new approach is warranted, sketch two or three options briefly: interface, data flow, trade-offs.
  4. Recommend one. Pick the simplest that meets the forces. If the decision is hard to undo or crosses module boundaries, run fresh-eyes on it before committing.
  5. Write the public interface (types, function signatures) before the implementation.
  6. Record significant decisions as an ADR (template below), default docs/adr/NNNN-title.md.

API checklist

  • Names describe intent, not implementation
  • Inputs validated at the boundary; errors are explicit and typed
  • Hard to misuse: no boolean flag soup, no order-dependent calls
  • Backward compatibility / versioning considered for public APIs
  • Idempotency for anything retried over the network

ADR template

# NNNN. <Decision title>
Status: proposed | accepted | superseded by NNNN
## Context
## Decision
## Options considered
## Consequences (good and bad)

Rationalizations to reject

ExcuseAnswer
"We might need this flexibility later"Add it later, when you know its shape.
"Let's use the pattern from <famous system>"Your forces are not theirs. Name the problem it solves here.

Related: tdd, simplify, spec, fresh-eyes.

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