Beautiful Intelligent Notion Enhancement & Reformatting
An opinionated formatter for Notion pages. Like Prettier, but for Notion.
Why "BINER"? In climbing, a biner (short for carabiner) is the essential link that connects everything on the wall — rope to harness, protection to anchor, climber to safety. BINER does the same for your Notion pages: it's the link between raw content and polished, professional structure. Part of the Alpine toolkit alongside PACK, MYNAH, IBEX, and SHERPA.
BINER is a plugin for Claude that transforms plain Notion pages into professionally structured documents. It applies a consistent design system — colored section headers, structured layouts, tables, columns — so your pages look polished without manual formatting.
Four commands:
| Command | What it does |
|---|---|
| "Create notion page" | Builds a new page from scratch with the design system applied |
| "Beautify" + a Notion URL | Reformats an existing page — preserves all your content, just makes it look great |
| "Learn my Notion style" + page URLs | Extracts your design preferences from sample pages and saves them |
| "Forget my Notion style" | Removes a saved design profile |
- Claude — either Claude Code (terminal) or Cowork (desktop app)
- Notion connected — Claude needs access to your Notion workspace via the Notion MCP connector
Open Claude and prompt:
Install this plugin: https://github.com/Percona-Lab/BINER
Claude will clone the repo, install the plugin to ~/.claude/plugins/biner/, and clean up. Done.
Download biner-plugin.zip from the
latest release and
upload it in Cowork under Settings > Plugins > Upload. This also works for
org-level installation: a team admin can upload the ZIP to make BINER available
to all members on Team or Enterprise plans.
- Clone or download this repo
- Copy the contents into
~/.claude/plugins/biner/ - Restart Claude (or reload plugins)
mkdir -p ~/.claude/plugins/biner
git clone https://github.com/Percona-Lab/BINER.git /tmp/biner
cp -r /tmp/biner/.claude-plugin /tmp/biner/skills ~/.claude/plugins/biner/
rm -rf /tmp/binerIn Claude Code, run /plugins — you should see biner in the list. In Cowork, the plugin will appear automatically when you start a new session.
biner/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata (name, version, author)
├── skills/
│ └── notion-beautifier/
│ ├── SKILL.md # Formatting rules and design system
│ └── references/
│ ├── design-dimensions.md # What to extract during LEARN mode
│ └── profile-schema.md # Memory storage format for profiles
├── README.md
└── LICENSE
Just tell Claude what you want:
Create notion page: Your Notion Page
Beautify https://www.notion.so/your-workspace/Your-Page-abc123
BINER can learn your design preferences from existing Notion pages you love — similar to how MYNAH learns your writing voice.
Learn my Notion style from these pages: [URL1] [URL2] [URL3]
Optionally name the profile:
Learn my Notion style as "technical" from these pages: [URL1] [URL2] [URL3]
Once learned, all future Create and Beautify commands automatically apply your preferred patterns, colors, and formatting choices. Profiles are stored in your persistent memory (PACK or equivalent), not in the plugin itself. The default design system still applies if no profile exists.
BINER works out of the box using Claude's built-in memory, but installing PACK unlocks the full experience:
- Train once, use everywhere. Train your design profiles in Cowork or Claude Code, then use them in Claude Desktop, Cursor, Open WebUI, and any other MCP client connected to PACK. No plugin needed on the other end.
- Any Claude interface can use your profiles. PACK is an MCP server, so even a plain Claude Desktop chat can read your Notion design preferences and apply them when formatting pages. Without PACK, profiles are only available inside the platform where you trained them.
- Cross-project. Claude's built-in memory is scoped per project directory. PACK memory is global, so your design preferences are available no matter which repo you're working in.
- Version controlled. PACK backs memory to a private GitHub repo. Full git history of every profile change, and you can clone it anywhere.
- Shared context. Other Alpine toolkit tools (like MYNAH) can read the same memory, enabling a connected workflow across tools.
Without PACK, BINER stores profiles in Claude's built-in memory. This works for single-platform, single-project use, but profiles won't sync across platforms or be accessible to other tools.
BINER works with any type of Notion page:
- Vision / Strategy docs — Two-column pillars, synthesis sections, summary callouts
- Proposals — Colored section headers, phased plans, comparison tables
- Goals / Metrics — Priority headings, collapsible details, checkboxes
- Architecture / Technical docs — Code blocks in styled callouts, layer diagrams, reference tables
- Workspace plans — Principles lists, scope controls, paired columns
BINER applies a consistent color language:
| Color | Meaning |
|---|---|
| Red | Major section headers, critical warnings |
| Blue | Key objectives, commitments, highlighted statements |
| Green | Next steps, success metrics, positive outcomes |
| Yellow | Caution areas, table header rows, security/governance |
| Purple | Innovation sections, advanced features |
| Orange | Priority 1 items, phased labels |
| Gray | Reference tables, notes, supplementary context |
- Full width: The Notion API doesn't support setting pages to full width — toggle it manually after creation.
- Toggle + code: Notion's toggle blocks can't contain code blocks (the code gets stripped). BINER works around this with styled headings and callouts instead.
- Privacy: Pages are created as private by default. Tell Claude where to put the page if you want it somewhere specific.
MIT