Index of every page on this site: llms.txt
All skills
makenotion avatar

/set-up-my-project

@016c74f official
Run it yourself

Create a useful initial Notion project home with tasks, docs, and meeting notes, then work with the user to confirm the team and choose a Projects database. Use when starting or organizing a project in Notion; routine task edits, status reports, and implementing a technical spec are separate workflows.

  • 19 files
  • 1.1 MB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/makenotion/claude-code-notion-plugin/set-up-my-project

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referenceproject-home-layout.md

≈907 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Build a connected EPD project home

Create a project home that makes the next decision and the work behind it clear. Give the portfolio, project home, and detail records distinct jobs.

Organize the project inside the team system

Place the project in the agreed Projects database and reuse its shared Tasks, Docs, and Meetings collections. When placement is unresolved, follow the setup workflow: deliver the private initial project before asking where it belongs.

Build the portfolio as a compact project gallery. Show each project's outcome, status, lead, and target with a meaningful colored icon. Write a concise outcome summary for the card and retain the full outcome in the project. Use consistent card proportions and wrapped text. Keep shared collection navigation easy to find; keep individual projects' work surfaces inside their homes.

Compose the first screen

Set the EPD home to full width. Pin status, lead, and target near the title; group secondary properties in details. Show the full outcome once. Use a roughly 65/35 row for the current milestone or decision on the left and known collaborators with responsibilities on the right. Give the milestone a restrained accent and keep the team readable without repeating the metadata.

Place native Tasks, Docs & decisions, Meetings, and Overview tabs immediately below that context. Keep the first actionable task visible on the initial screen. Adjust the length of the introduction, spacing, and metadata grouping until the work and its context fit together. Keep expanded scope and working agreements in Overview rather than above the work.

Set Tasks to actionable work with title, status, owner, and due date; retain a completed view. Show Docs as compact cards or a list with document type and review state. Show the next prepared meeting agenda and reusable format clearly separated from meeting history. Give projects, tasks, docs, and meetings meaningful colored icons so their mentions and return links remain recognizable.

Connect useful detail

Filter every embedded view by the exact project relation, including meetings. Populate task completion criteria, substantive brief/design/decision documents, and a contextual agenda. Link tasks to the relevant specifications and return paths to the project. Preserve proposed dates and decisions as proposals. Prepare weekly reviews or standups to match the team's cadence; follow meeting setup to connect agendas, notes, and follow-ups.

Inspect the project and connected records

Enter through the portfolio. Read the project's status, outcome, next milestone, and team, then act on a task without scrolling through introductory prose. Switch among Tasks, Docs, and Meetings; open a real record in each and follow its links back. Verify that another project's records are excluded and that blocked, undated, and unassigned work remains discoverable.

Inspect the home and detail pages at normal desktop zoom with the sidebar visible, and at a narrow width. Check text wrapping, card proportions, aligned columns, visible properties, and the amount of work above the fold. Correct clipping, stranded headings, excessive empty space, and duplicate database titles. Preserve existing objects and verify the saved hierarchy after moving blocks.

Compare the rendered project home and connected records with the project design principles, not merely its schema. A polished home with missing docs, disconnected tasks, or empty meeting placeholders fails. Share the usable initial home before asking team, cadence, and placement questions; reuse known answers.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 016c74f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 2 weeks ago

README badge

README badge for makenotion/claude-code-notion-plugin/set-up-my-project