obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states,
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 3475
- Лиценз
- MIT
- Последна проверка на записа
- 22.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add Ar9av/obsidian-wikiСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
Obsidian Layout Adjustment
This skill is for changing how Obsidian looks with CSS files while working with the user's visual language.
Obsidian is always the same kind of environment: app frame, tab headers, side docks, view headers, pane shells, note surface, properties, file explorer, backlinks, graph, rendered markdown, and status bar. The vault, theme, snippets, plugins, and desired taste direction change, but the canvas stays Obsidian.
The core behavior is translation:
the user names a visible Obsidian object. Translate that phrase into the stable Obsidian layer/backend object, edit the active snippets safely, screenshot the result, and keep iterating without losing good states.
This is not a general CSS workflow and not a fixed-theme generator.
Normal Output Mode
This skill should make live styling work faster, not turn every small request into a report.
In normal use:
- Say the mapping only when it prevents ambiguity.
- Keep the mapping short: one sentence is usually enough.
- Then act: inspect active snippets, checkpoint, patch, format, reload, screenshot.
- Report the result concisely with changed files, checkpoint, and screenshot status.
Good normal update:
"I’m treating 'tabs above the note' as workspace tab headers, not the arrows/book/dots view header. I’ll checkpoint active snippets, patch that selector family only, and screenshot the tab strip."
Do not write a long workflow report unless:
- the user asks for a plan, audit, review, or explanation.
- You are running evals or building this skill.
- You are refactoring without visual changes.
- The request is ambiguous enough that acting first would be risky.
The value is in preventing bad CSS loops while still moving quickly.
Use The Reference
Read references/workflow-reference.md when:
- the user names a visible Obsidian object in natural language.
- The requested target could be more than one Obsidian layer.
- A screenshot shows "nothing changed," "still wrapped," "not lifted," uneven edges, washed-out surfaces, or unreadable icons.
- You are refactoring active snippets without changing the accepted look.
- You need the Obsidian surface map, change-type map, or failure-pattern list.
The reference is Obsidian-specific. Use it before treating the UI as an unknown web page.