mattrguerra.comHouston area
Matt Guerra
  1. 01AI & Automation
  2. 02Photography
  3. 03Design
  4. 04About
  5. 05Notes
  6. 06Contact
Back to the systems

mattrguerra/meridian-skillsmainPrivate on GitHub, published here in full

SETUP.md.tmpl

3.9 KB110 lines

skills/cowork-project-architect/templates/SETUP.md.tmpl

  1. ---
  2. type: setup
  3. scope: project-root
  4. tags:
  5. - setup
  6. - onboarding
  7. - obsidian
  8. - cowork
  9. created: [YYYY-MM-DD]
  10. updated: [YYYY-MM-DD]
  11. ---
  13. <!--
  14. SETUP.md: Step-by-step setup for both Obsidian and Cowork.
  16. Goal: get a new install of this project running in under 10 minutes.
  18. Order: open as Obsidian vault first, then connect to Cowork. Obsidian
  19. opening is faster and lets the user verify file structure before paying
  20. the Cowork setup cost.
  21. -->
  23. # [PROJECT NAME]: Setup
  25. Get this project running in Obsidian and Cowork in under 10 minutes.
  27. ## Prerequisites
  29. - Obsidian installed
  30. - Cowork installed and signed in
  31. - [Any required MCP / tool / account access, listed specifically]
  32. - [Any required local files or folder structure already in place]
  34. ## Steps
  36. ### 1. Open as Obsidian vault
  38. Obsidian → File → Open folder as vault → select this folder ([PROJECT-PATH]).
  40. On first open, Obsidian creates a `.obsidian/` config folder. Default settings work fine. If you want graph view to be useful, enable: Settings → Core plugins → Backlinks, Graph view, Outline.
  42. ### 2. Verify vault structure
  44. After opening, the file explorer should show:
  45. - Root reference files: [[CLAUDE]], [[MEMORY]], [[HEARTBEAT]], [[CHANGELOG]], [[DECISIONS]], [[MODEL_GUIDE]], [[SETUP]], [[SKILLS_REFERENCE]], [[README]], [[00-Index]]
  46. - Numbered folders: `01-Knowledge/`, `02-Working/`, `03-Outputs/`, plus `_attachments/` and `_templates/`
  48. If anything is missing, the project wasn't fully generated. Check [[CHANGELOG]] for the init entry and re-run generation if needed.
  50. ### 3. Create the Cowork project
  52. Cowork → New Project → point it at this folder ([PROJECT-PATH]).
  54. ### 4. Paste custom instructions into Cowork
  56. Open [[CLAUDE]]. Copy everything below the YAML frontmatter (everything from the first `#` heading down). Paste into Cowork's Project Settings → Custom Instructions.
  58. The "Reference index" section at the bottom of CLAUDE.md is intentional context for Claude, so keep it in the paste.
  60. ### 5. Set the default model in Cowork
  62. In Project Settings, set the default model to **[MODEL]**. See [[MODEL_GUIDE]] for which model handles which task.
  64. ### 6. Connect MCPs / tools
  66. This project uses:
  67. - [MCP / tool]: [scope. E.g., "Gmail, read access only"]
  68. - [MCP / tool]: [scope]
  70. Verify each is connected and authorized before starting.
  72. ### 7. Verify knowledge base
  74. Open [[01-Knowledge/KNOWLEDGE_INDEX]]. Confirm the listed files exist. Fill any `[TBD]` slots before running the validation task.
  76. ### 8. Verify scoped CLAUDE files (if any)
  78. Check [[CLAUDE]] under "Subdirectory reference files." If any `CLAUDE-[scope].md` files are listed, confirm they exist and match what the index claims.
  80. ### 9. Run the validation task
  82. First-run validation: [SPECIFIC TASK, e.g., "Ask Claude to summarize 01-Knowledge/sample-input.csv into the format defined in CLAUDE.md."]
  84. Expected output: [What success looks like.]
  86. If the validation task fails, the most common causes are: [2-3 likely issues, each with a one-line fix.]
  88. ### 10. Initialize HEARTBEAT
  90. Update [[HEARTBEAT]]:
  91. - Set `last-updated` (frontmatter and body) to today
  92. - Set `status` (frontmatter) to `idle`
  93. - Set "Current objective" to "Idle, awaiting next task"
  95. This is your starting state.
  97. ## Maintenance
  99. - After significant work, append a [[CHANGELOG]] entry.
  100. - When you change scope, instructions, model assignments, or vault structure, write a [[DECISIONS]] entry.
  101. - Review [[MEMORY]] monthly (or whenever it stops feeling accurate).
  102. - If you add a subdirectory `CLAUDE-[scope].md` file, log it in [[CLAUDE]] under "Subdirectory reference files."
  104. ## Useful Obsidian features for this vault
  106. - **Graph view**: visualize connections between files. Wikilinks make this work.
  107. - **Backlinks pane**: see what links to the file you're reading.
  108. - **Tag pane**: navigate by tag taxonomy. See [[MEMORY]] for active tags.
  109. - **Quick switcher** (Cmd/Ctrl + O): jump to any file by name.
  110. - **Templates plugin**: point it at `_templates/` to use the project's note templates.