CoachDiscoverMapCompareSavedAI LearningAI WeeklyAbout
← All guides
Guide 01 · Foundations

SharePoint libraries don't have to be boring

One reusable skill, many style files. The brains live in one place; the look comes from anywhere you want.

Walk away with
One skill, many styles
Walk away with
Style files are just descriptions
Walk away with
Row formatter is the engine

The default SharePoint view is hard to read

The out-of-the-box library view shows rows of metadata. It is familiar but dense — important information sits buried in a column you have to scroll to find. The video opens with nine wildly different visual treatments of the same list to make this point: nothing about SharePoint forces the view to look like a spreadsheet.

SharePoint can render lists and libraries any way you want. The standard look is a default, not a limit.

The interactivity is preserved. Even when a library looks like a Bento grid or a blueprint, the underlying data is still the same SharePoint list. Click-throughs, sorting, and metadata edits all work as expected.

"Styling a library means rebuilding it as a custom web part." It does not. The data layer stays the same — only the presentation changes.

The List Styling skill — one reusable brain

The List Styling skill is the must-install piece. It contains the "brains" of how SharePoint applies a visual treatment to a library. You install it once and then point it at any individual style influence — Bento, Blueprint, your own design — and it applies that style.

List Styling is the framework. The individual style files are the inputs. Reuse the framework; vary the inputs.

This is the same composition pattern AI Skills use throughout SharePoint: a skill is a reusable building block, and you compose your own outputs by feeding it different references. You do not have to know SharePoint's internals — you just have to describe the look you want.

"I need to install a separate skill for every style." You don't. One List Styling skill plus N style files is the model — the skill stays put.

A style file is a description, not a template

Each style file (Bento, Blueprint, whatever you make) is mostly a description of intent — colors, mood, ASCII art sketches, and a row-formatter JSON block. The List Styling skill reads those descriptions and translates them into actual SharePoint formatting.

Generating a new style is direct: drop a reference image into your library, point the skill at one of your existing style files as a model, give it a few words ("technical engineering drawings, everything is blue"), and let it produce a new style file you can apply anywhere.

Inspiration goes in (image + words). A style file comes out (description + row formatter JSON). Then any library can wear it.
"The style file is a CSS theme I edit by hand." It is closer to a design brief plus a JSON config. Most of it is high-level description that the skill interprets.

The row formatter is the hidden engine

Buried in every style file is a chunk of row formatter JSON — SharePoint's built-in mechanism for customizing how each row renders. It is incredibly powerful, but few people know it well. The point of List Styling is that you do not have to.

SharePoint can already do beautiful. The skill just hides the JSON behind a description an AI can write.

This is why the styles look so different from each other while running on the same platform. Row formatter JSON can pivot a row into a tile, a card, a bar, or a Bento cell. The skill writes the JSON; you describe the vibe.

"This is some new rendering engine SharePoint added." No — row formatter has existed for years. The new thing is letting AI author it.
Flashcards — Foundations
01 · Foundations
List Styling Skill
tap to reveal →
The reusable AI skill that holds the rendering logic. Install once, then feed it any style file to apply a different look to any SharePoint library.
← tap to flip back
01 · Foundations
Style File
tap to reveal →
A description of a visual style — color palette, mood, ASCII sketch, and row-formatter JSON. The List Styling skill reads it to render a library.
← tap to flip back
01 · Foundations
Row Formatter
tap to reveal →
SharePoint's built-in JSON syntax for customizing how each row in a list renders. The hidden engine that makes alternative library looks possible.
← tap to flip back
01 · Foundations
AI Skill
tap to reveal →
A reusable AI building block in SharePoint. Composed by feeding it inputs — much like a function. The same skill produces different outputs from different inputs.
← tap to flip back
01 · Foundations
Bento Style
tap to reveal →
One of the demo style files — renders a library as a Bento-grid card layout. Used as a reference for generating new styles by example.
← tap to flip back
Guide 01 · Foundations · Beautiful SharePoint Libraries All flashcards →