Bullframe Docs Page logo

Bullframe Docs Page

Community
marcop135
bullframe-docs-page

Build a documentation, article or reference page with Bullframe CSS. Use for docs, guides, changelogs, help center articles, blog posts, or any prose-first page.

Overview

Publishermarcop135
Repositorybullframe.css
Skill namebullframe-docs-page
Stars
47
Forks
3
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by marcop135 on GitHub. Read the source before you install it.

Installation

Install the Bullframe Docs Page AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/marcop135/bullframe.css/tree/main/src/skills/bullframe-docs-page
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/marcop135/bullframe.css.git /tmp/bullframe.css
mkdir -p .claude/skills
cp -r /tmp/bullframe.css/src/skills/bullframe-docs-page .claude/skills/bullframe-docs-page
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bullframe Docs Page in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bullframe Docs Page on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bullframe Docs Page is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Documentation page

Prose is where the classless builds win. Semantic HTML with no class attributes at all renders as a finished document: headings, lists, tables, quotes, code blocks and figures are styled by element.

When to use

Documentation, a guide, a changelog, a help center article, a blog post, an API page, or any page that is mostly text.

Inputs to gather

Title, section outline, whether a table of contents or breadcrumb is needed, code sample languages, and the theme. Default to the classless light build and say so.

Rules

  1. Default to bullframe-classless.css. Write zero class attributes. Escalate to the class-based build only when the page needs a real multi-column layout, and state why.
  2. .bf-* classes do not exist in a classless build. Writing them there produces unstyled markup.
  3. One <h1>, then <h2> sections in order. Give every heading that is a link target an id.
  4. The body is <article> inside <main>. A table of contents is a <nav> with an aria-label and an ordered list.
  5. Code samples are <pre><code>. Inline code is <code>. Do not add a highlighter unless the task asks for one.
  6. Tables carry a <caption> and <th scope="col"> headers.
  7. Use <blockquote>, <figure> with <figcaption>, <dl>, <abbr> and <time> where they fit. All of them are styled.
  8. A skip link needs .bf-skip-link, which only exists on class-based builds. On a classless page, a <main> landmark plus ordered headings is the accessible structure.

Recipe

  1. Confirm the page is prose. If it needs a sidebar with independent scroll, it is a layout page, not this.
  2. Emit the classless scaffold from bullframe-core.
  3. Breadcrumb <nav> in <header> if the page sits inside a hierarchy.
  4. <article> with the <h1>, a lead paragraph, then the sections.
  5. Table of contents as a <nav aria-label="On this page"> with anchors matching the heading ids.
  6. Close with a <footer> carrying the review date or edit link.

Example

examples/docs-page.html is a complete classless page: breadcrumb, table of contents, code block, captioned table and a quote. It contains no class attribute.

Expected output

An HTML file whose class attribute count is zero on the classless path, and which reads correctly with stylesheets disabled.

Failure modes

  • Reaching for .bf-container or .bf-lead on a classless build, where neither exists.
  • Wrapping every paragraph in a <div>.
  • Restating framework typography in a <style> block.
  • Heading levels chosen for size rather than structure; use .bf-h1 … .bf-h6 on a class-based build when the visual level must differ from the semantic one.
  • A table of contents built from <div>s instead of a <nav> and a list.
  • Anchors that do not match any heading id.

Do not

  • Do not add a JavaScript table of contents generator for a static page.
  • Do not mix a classless build with utility classes; add the utilities sheet if you need them, or move to the class-based build.
  • Do not put a skip link on a classless page; the class is not in that stylesheet.

Canonical docs

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Bullframe Docs Page AI skill do?

Build a documentation, article or reference page with Bullframe CSS. Use for docs, guides, changelogs, help center articles, blog posts, or any prose-first page.

Why use Bullframe Docs Page on TypingMind?

Because you install it once and use it with any model. Bullframe Docs Page is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bullframe Docs Page in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/marcop135/bullframe.css/tree/main/src/skills/bullframe-docs-page. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Bullframe Docs Page?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bullframe Docs Page?

As many as you like. As long as a model supports skills, you can use Bullframe Docs Page with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bullframe Docs Page AI skill free?

Yes. It is published on GitHub by marcop135 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇