agentleFS
Sign inStart free
Codagent-AICodagent-AI/agent-skills/skills/design/SKILL.md

design

Skill31 starsChanged 6 months agoMITView on GitHub

Creates design artifacts through collaborative brainstorming of approaches, architecture, and trade-offs. Use when the user says "design this", "create a design", "brainstorm approaches", or "write a design doc".

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 176 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not implement, scaffold, or invoke an implementation skill before the user approves the design.

    line 14
  2. Distinctive:

    Read every specification, including deferred-to-design markers, and inspect the relevant code, interfaces, tests, and repository …

    line 18
  3. Very specific:

    Use codagent:ask-questions for consequential architectural choices that repository context cannot safely resolve.

    line 20
  4. Very specific:

    After approval, write design.md and apply any specification changes revealed by the design, including completing deferred scenarios, only …

    line 31
  5. Distinctive:

    If design work exposes a product or scope decision rather than a technical implication, discuss it with the user instead of silently …

    line 36
  6. Distinctive:

    Do not invoke another lifecycle skill after writing.

    line 40

“Common” is measured: kept by at least 6 in 10 of the 176 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

Turn approved specifications into an implementation-ready technical design. Requirements are already settled; focus on architecture, component boundaries, interfaces, data flow, failure handling, migration, testing, and meaningful trade-offs.

Do not implement, scaffold, or invoke an implementation skill before the user approves the design.

Process

  1. Read every specification, including deferred-to-design markers, and inspect the relevant code, interfaces, tests, and repository conventions.
  2. Use codagent:ask-questions for consequential architectural choices that repository context cannot safely resolve. Evaluate options first, recommend a path, and decide low-risk implementation details yourself.
  3. Compare plausible approaches when a real trade-off exists. Do not manufacture alternatives for an obvious, patterned solution.
  4. Present a design scaled to the change's complexity. Cover the important components, interactions, decisions, risks, verification strategy, and any resulting specification implications; use diagrams when they clarify the design. When the change produces something people look at, also cover its visual design: the visual style, the quality it must reach, and how that will be checked, not only legibility limits such as minimum text size or overlap. Ask the user about visual style choices the proposal and specifications leave open.
  5. After approval, write design.md and apply any specification changes revealed by the design, including completing deferred scenarios, only when those implications were presented with the approved design. Return to the user for a newly discovered behavioral or scope decision. Keep normative behavioral changes in specs and technical rationale in the design.

If design work exposes a product or scope decision rather than a technical implication, discuss it with the user instead of silently inventing behavior. The written artifacts must be self-contained for an implementing agent with no conversation history.

Do not invoke another lifecycle skill after writing.

Artifact template

Omit sections that do not apply.

## Context

<!-- Relevant current state and constraints. -->

## Goals / Non-Goals

**Goals:**
<!-- Outcomes this design enables. -->

**Non-Goals:**
<!-- Explicit exclusions. -->

## Approach

<!-- Components, interfaces, interactions, data flow, and failure behavior. -->

## Visual Design

<!-- For something people look at: visual style, quality bar, and how they are checked. -->

## Decisions

<!-- Consequential choices and rationale. -->

## Risks / Trade-offs

<!-- Material risks, mitigations, and alternatives considered. -->

## Migration Plan

<!-- Rollout and rollback when applicable. -->

## Open Questions

<!-- Only unresolved decisions that remain. -->

Download now (ZIP)

  • Other versions198 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 198

    1. nextlevelbuilder/ui-ux-pro-max-skill★ 144ksame name
    2. Yeachan-Heo/oh-my-codex★ 34ksame name
    3. tokio-rs/toasty★ 3.3ksame name
    4. PaulWoitaschek/Voice★ 3.2ksame name
    5. joye61/pic-smaller★ 2.9ksame name
    6. oxsecurity/megalinter★ 2.6ksame name
    7. Infisical/agent-vault★ 2.5ksame name
    8. static-web-server/static-web-server★ 2.4ksame name
    9. SethGammon/Citadel★ 927same name
    10. Ohh-889/skyroc-admin★ 795same name

    188 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects 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 37 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 38 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 42 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 41 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 47 projects that use this

  • In this repository30 other files it gives its agents.

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