Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ar9av/obsidian-layout-adjustment
Workflow for working with Dan on changing how Obsidian looks using CSS snippets. Use this whenever Dan 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, or CSS snippets. Also use it when Dan says a visual CSS change did nothing, still looks wrapped, is not lifted, is unreadable, or needs to be refactored without changing the current appearance.
Passed 17 of 20 test cases with the skill, and 13 of 20 without it.
and 2 more in the full report
4 fixed15 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I modified a CSS selector in Obsidian and my CSS editor shows valid syntax without errors. Can I consider the task complete without launching/focusing Obsidian or taking a screenshot?
| Checked | Without skill | With skill |
|---|---|---|
| requires taking a screenshot of the affected Obsidian UI area as visual verification before declaring completion | Missed | Passed |
| treats visual screenshot capture as mandatory truth over CSS syntax validation | Missed | Passed |
The instructions your model reads when the skill loads.
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.
This skill should make live styling work faster, not turn every small request into a report.
In normal use:
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 value is in preventing bad CSS loops while still moving quickly.
Read references/workflow-reference.md when:
test cases passed, vs 13 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.