- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add Ar9av/obsidian-wiki --skill obsidian-layout-adjustment -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add Ar9av/obsidian-wiki --skill obsidian-layout-adjustment -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add Ar9av/obsidian-wiki --skill obsidian-layout-adjustment -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add Ar9av/obsidian-wiki --skill obsidian-layout-adjustment -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/Ar9av/obsidian-wiki/tree/HEAD/skills/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.
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:
The reference is Obsidian-specific. Use it before treating the UI as an unknown web page.
<vault>/.obsidian/appearance.json.enabledCssSnippets as the active styling source of truth..obsidian/snippet-archive/, never into .obsidian/snippets, so the snippet picker stays clean.The user will usually name what they see, not the selector:
Before editing, map the phrase:
user phrase -> visible object -> Obsidian layer -> likely selector/settings surface -> change type -> owning layer
Say the mapping back when it could be ambiguous:
"When you say the tabs above the note, I am treating that as the workspace tab headers, not the arrows/book/dots row inside the note pane."
This is the main mistake-prevention step. Most frustrating failures came from changing a plausible element that was not the object the user meant, or changing a child when the wrapper/header/stage owned the visible shape.
Use this compact map first, then verify exact selectors in the live vault:
The visible object and backend layer should be treated as stable across Obsidian work. Exact class names can vary by theme/plugin/app version, so verify in the live vault before patching.
The same object needs different work depending on the request:
box-shadow.If a target needs two change types, do two passes. For example, make side-dock icons readable first, then tune the selected-state color.
Start with:
appearance.jsonAvoid changing first:
Ask for explicit confirmation before:
.obsidian/snippets or Obsidian settingsCSS validity is not visual success. The screenshot is product truth.
For every meaningful visual pass:
If another window covers Obsidian, retake the screenshot. Verify the verifier: confirm Obsidian is actually frontmost before trusting a capture (AppleScript can check the frontmost process). If the issue is tiny, capture just that region — screencapture -R<x,y,w,h> out.png — around the edge, icon, tab, row, or pane.
If the screenshot disproves the fix, keep working, restore, or say it failed. Do not close as if formatting proved success.
the user's corrections are selector evidence:
If a direction fails twice, restore the last good checkpoint and change the ownership model.
Do not refactor during taste exploration.
When the user likes the look:
.obsidian/snippets.CSS size is usually less dangerous than cascade confusion and a messy active snippet picker.
When done, keep the closeout short. Report:
Avoid explaining the whole workflow after every small pass. The workflow should be visible in the actions: checkpoint, scoped edit, screenshot, and evidence-based next step.
>
---name: obsidian-layout-adjustmentdescription: >---# skills/obsidian-layout-adjustment/SKILL.mdFAQ
게시자에게서 skills/obsidian-layout-adjustment/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/Ar9av/obsidian-wiki에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.