agentleFS
RonenMarsRonenMars/threadbase-mobile/design/SKILL.md

threadbase-design

Skill4 starsChanged 2 days agoMITView on GitHub

Use this skill to generate well-branded interfaces and assets for Threadbase, either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Very specific:

    Read DESIGN.md at the repository root — the brand doc for 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 10
  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 12

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 DESIGN.md at the repository root — the brand doc for this skill — and explore the other available files. Copy it into this folder as README.md when exporting the skill standalone; it is kept at the root so there is only one copy to keep current.

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.

Key files:

  • ../DESIGN.md — voice, content fundamentals, visual foundations, iconography
  • figma-plugin/ — builds the Figma design-system file from this repo's code
  • colors_and_type.css — single source of truth for color/type CSS variables; import on every page
  • assets/threadbase-icon.svg, assets/threadbase-icon-chat.svg — brand marks
  • preview/ — small HTML cards illustrating colors, type, components
  • ui_kits/mobile/ — high-fidelity recreation of the Threadbase mobile app

Quick brand summary: dark IDE-grade canvas (#070b11), cyan-blue (#63b3ff) for "thread / data / past", amber (#f08a24) for "live / running / now". Inter + JetBrains Mono. No purple gradients, no emoji-as-UI, no bounce animations. Glow is the brand's expressive move.

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.