agentleFS
Sign inStart free
davidvkimballdavidvkimball/obsidian-dev-skills/obsidian-theme-dev/SKILL.md

obsidian-theme-dev

Skill51 starsChanged 10 months agoMITView on GitHub

CSS/SCSS development patterns for Obsidian themes. Load when working with theme.css, SCSS variables, or CSS selectors.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Obsidian CSS Variables: Always prefer Obsidian's built-in CSS variables over hardcoded values

    line 25
  2. Distinctive:

    Consistent Naming: Use a consistent naming convention (BEM, prefixed classes, or other - see conventions file)

    line 26
  3. Distinctive:

    Mobile-First: Consider mobile layouts and responsive design

    line 27
  4. Distinctive:

    Dark/Light Mode Support: Test themes in both light and dark modes

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Obsidian Theme Development Skill

This skill provides patterns and rules for developing Obsidian themes, focusing on CSS/SCSS development, styling conventions, and theme-specific coding practices.

Purpose

To ensure consistent theme development, proper CSS organization, and adherence to Obsidian's theming patterns and CSS variable usage.

Scope

This skill covers:

  • Writing or modifying CSS/SCSS for theme.css
  • Working with Obsidian's CSS variables and theming system
  • Implementing responsive design or dark/light mode support
  • Debugging CSS layout or styling issues
  • CSS/SCSS coding conventions for Obsidian themes

Core Rules

  • Use Obsidian CSS Variables: Always prefer Obsidian's built-in CSS variables over hardcoded values
  • Consistent Naming: Use a consistent naming convention (BEM, prefixed classes, or other - see conventions file)
  • Mobile-First: Consider mobile layouts and responsive design
  • Dark/Light Mode Support: Test themes in both light and dark modes
  • Performance: Minimize CSS complexity and avoid expensive selectors

Bundled Resources

  • references/theme-best-practices.md: Essential CSS patterns and Obsidian variable usage
  • references/theme-coding-conventions.md: CSS/SCSS style guidelines and naming conventions

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.

Check your setup, free