Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

architecting-projects

Organizes the current folder into a structured Obsidian project vault with standard folders, a home note, and a visual dashboard. Use when the user asks to "setup a project," "organize this folder," or "create an Obsidian structure."

Executar no Manus

Estrelas0

Forks0

Atualizado28 de fevereiro de 2026 às 06:29

Fonte

piriya33

piriya33/astrodian

Abrir repositório GitHub Ver repositórios do creator

Comando de instalação

Download

Executar no Manus

Útil paraSOC

Secretárias e assistentes administrativos (exceto jurídico, médico e executivo)Escritório e Suporte Administrativo43-6014L4

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	architecting-projects
description	Organizes the current folder into a structured Obsidian project vault with standard folders, a home note, and a visual dashboard. Use when the user asks to "setup a project," "organize this folder," or "create an Obsidian structure."

Architecting Projects

This skill transforms any folder into a fully featured Obsidian project space. It is designed to work directly on the file system.

Triggering Contexts

When the user wants to start a new complex project (e.g., "Plan a course," "Write a book").
When the user wants to organize an existing chaotic folder.
When the user explicitly asks for "Obsidian setup" or "Project structure."

Workflow Checklist

detailed requirements gathered (project name, goal)
folder structure created (00_Meta, 10_Research, 20_Development, 30_Output, 99_Archive)
resource files copied (Project_Home.md, Dashboard.canvas)
initial notes created or moved

Instructions

1. Structure Scaffolding

When asking to "architect" or "setup" a project, ALWAYS enforce this folder, numbering system for easy sorting:

[ProjectRoot]/
  ├── 00_Meta/          # Templates, system files, project config
  ├── 10_Research/      # Inputs: sources, raw notes, literature
  ├── 20_Development/   # Throughputs: drafts, outlines, thinking
  ├── 30_Output/        # Outputs: final deliverables, polished content
  └── 99_Archive/       # Deprecated or finished items

Action: Use run_command to create these directories if they don't exist.

2. The "Project Home" (MOC)

Every project needs a single entry point.

Read the template from .agent/skills/architecting-projects/resources/template-moc.md.
Replace {{date}} with the current date.
Replace {{project_name}} with the folder name or user-provided name.
Replace {{folder_path}} with the relative path of the project root (for Dataview queries).
Write this file to 00_Meta/Project_Home.md.

3. The Visual Dashboard (Canvas)

Obsidian Canvas is powerful for high-level thinking.

Read the template from .agent/skills/architecting-projects/resources/project-dashboard.canvas.
Write this file to the root of the project as Dashboard.canvas.
- Note: Creating it at the root makes it the first thing seen when opening the folder in some views.

4. Handling Existing Files

If the folder is NOT empty:

Ask the user if they want to move existing files into the new structure (likely into 10_Research or 20_Development).
Do NOT delete any user files.

Artifact Integration

task.md: Update the task list to reflect the "Project Setup" phase.
walkthrough.md: After setting up, create a walkthrough showing the new structure and links to the generated files.

Files & Resources

resources/template-moc.md: Template for the Home note.
resources/project-dashboard.canvas: Template for the Canvas dashboard.

Mais deste repositório

mesmo repositório

brainstorming-ideas

piriya33/astrodian

Explores user intent, requirements, and design before implementation. Use before creating features, building components, or modifying behavior.

2026-02-280

executing-plans

piriya33/astrodian

Guides the agent through the systematic execution of an implementation plan. Use when the user asks to "start working" on a plan or "execute the plan".

2026-02-280

frontend-design

piriya33/astrodian

Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. Use when building or styling web UIs, components, pages, dashboards, or frontend applications.

2026-02-280

ui-ux-pro-max

piriya33/astrodian

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

2026-02-280

name	architecting-projects
description	Organizes the current folder into a structured Obsidian project vault with standard folders, a home note, and a visual dashboard. Use when the user asks to "setup a project," "organize this folder," or "create an Obsidian structure."

Architecting Projects

This skill transforms any folder into a fully featured Obsidian project space. It is designed to work directly on the file system.

Triggering Contexts

When the user wants to start a new complex project (e.g., "Plan a course," "Write a book").
When the user wants to organize an existing chaotic folder.
When the user explicitly asks for "Obsidian setup" or "Project structure."

Workflow Checklist

detailed requirements gathered (project name, goal)
folder structure created (00_Meta, 10_Research, 20_Development, 30_Output, 99_Archive)
resource files copied (Project_Home.md, Dashboard.canvas)
initial notes created or moved

Instructions

1. Structure Scaffolding

When asking to "architect" or "setup" a project, ALWAYS enforce this folder, numbering system for easy sorting:

[ProjectRoot]/
  ├── 00_Meta/          # Templates, system files, project config
  ├── 10_Research/      # Inputs: sources, raw notes, literature
  ├── 20_Development/   # Throughputs: drafts, outlines, thinking
  ├── 30_Output/        # Outputs: final deliverables, polished content
  └── 99_Archive/       # Deprecated or finished items

Action: Use run_command to create these directories if they don't exist.

2. The "Project Home" (MOC)

Every project needs a single entry point.

Read the template from .agent/skills/architecting-projects/resources/template-moc.md.
Replace {{date}} with the current date.
Replace {{project_name}} with the folder name or user-provided name.
Replace {{folder_path}} with the relative path of the project root (for Dataview queries).
Write this file to 00_Meta/Project_Home.md.

3. The Visual Dashboard (Canvas)

Obsidian Canvas is powerful for high-level thinking.

Read the template from .agent/skills/architecting-projects/resources/project-dashboard.canvas.
Write this file to the root of the project as Dashboard.canvas.
- Note: Creating it at the root makes it the first thing seen when opening the folder in some views.

4. Handling Existing Files

If the folder is NOT empty:

Ask the user if they want to move existing files into the new structure (likely into 10_Research or 20_Development).
Do NOT delete any user files.

Artifact Integration

task.md: Update the task list to reflect the "Project Setup" phase.
walkthrough.md: After setting up, create a walkthrough showing the new structure and links to the generated files.

Files & Resources

resources/template-moc.md: Template for the Home note.
resources/project-dashboard.canvas: Template for the Canvas dashboard.