원클릭으로 Manus에서 모든 스킬 실행

memory-project-init

스타17

포크11

업데이트2026년 6월 15일 18:59

Initialise or refresh Memory Layer in a project directory after Memory Layer is already installed; use for repo-local setup with .mem, .agents/memory-layer.toml, and repo-local memory skills, previewing writes before applying them

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

3vilM33pl3

3vilM33pl3/memory

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Memory Project Init Skill

Use this skill when:

the user asks to initialise, configure, bootstrap, or set up Memory Layer for a project
Memory Layer is already installed on the machine
the target work is repo-local .mem/ and .agents/ setup

Do not use this skill for:

installing Memory Layer packages, PostgreSQL, pgvector, or system services
creating or reinitialising git history
broad Memory Layer behavior questions
completed-work remembering after setup is done

Workflow

Identify the target project directory; if the user did not specify one, use the current working directory.
Run memory health and memory doctor to check the shared backend and current repo state.
Inspect existing .mem/, .agents/memory-layer.toml, and .agents/skills/ if present.
Preserve existing local customisations; do not delete or overwrite them without an explicit user request.
Run memory wizard --dry-run in the target project and review the planned repo-local writes.
If the preview is safe, run memory wizard in the target project.
Run memory doctor again.
Report the project slug, files created or preserved, backend health, and next commands.

Optional Evidence Setup

Only run these if the user explicitly wants initial evidence imported:

memory commits sync --project <project-slug> --dry-run
memory scan --project <project-slug> --dry-run

Ask before running the non-dry-run versions. Use commits sync for commit history evidence and scan for LLM-assisted initial memory candidates.

Safety Rules

Preview write-capable setup commands first with --dry-run.
Do not run package managers or service installers from this skill.
Do not create, delete, or reinitialise git repositories.
If .mem/config.toml, .mem/project.toml, .agents/memory-layer.toml, or any skill directory exists, treat it as user/project state.

Runtime Requirement

The repo-local Memory Layer skill bundle uses the shared Go helper under .agents/skills/memory-layer/scripts/. go must be available on PATH for those helper commands to run after setup.

이 저장소의 다른 Skills

같은 저장소

memory-layer

3vilM33pl3/memory

Umbrella entrypoint for Memory Layer workflows; use for broad memory-related turns, shared invariants, and docs/admin work, while focused query/resume, plan-execution, and remember skills handle the narrow workflows

2026-06-2717

memory-direct-task-start

3vilM33pl3/memory

Record a task memory before starting direct no-plan implementation work when the user asks to implement, fix, change, add, update, release, install, or otherwise mutate the repository without first approving a plan

2026-06-1517

memory-github-init

3vilM33pl3/memory

Guide first-time GitHub repository initialization for a Memory Layer project; use when setting up or auditing GitHub remotes, repository metadata, Actions workflows, secrets, variables, branch protection, required checks, or Memory Layer repo onboarding, with discovery and dry-run review before write-capable changes

2026-06-1517

memory-plan-execution

3vilM33pl3/memory

Save the approved plan and checkpoint when execution starts, and verify all plan checkbox items are complete before claiming the task is finished

2026-06-1517

memory-query-resume

3vilM33pl3/memory

Query curated project memory before answering repo-specific questions, and use resume to get back into flow after interruptions

2026-06-1517

memory-remember

3vilM33pl3/memory

Remember meaningful completed work by capturing task context and curating it into durable project memory with provenance

2026-06-1517

name	memory-project-init
version	0.9.5
description	Initialise or refresh Memory Layer in a project directory after Memory Layer is already installed; use for repo-local setup with .mem, .agents/memory-layer.toml, and repo-local memory skills, previewing writes before applying them

Memory Project Init Skill

Use this skill when:

the user asks to initialise, configure, bootstrap, or set up Memory Layer for a project
Memory Layer is already installed on the machine
the target work is repo-local .mem/ and .agents/ setup

Do not use this skill for:

installing Memory Layer packages, PostgreSQL, pgvector, or system services
creating or reinitialising git history
broad Memory Layer behavior questions
completed-work remembering after setup is done

Workflow

Identify the target project directory; if the user did not specify one, use the current working directory.
Run memory health and memory doctor to check the shared backend and current repo state.
Inspect existing .mem/, .agents/memory-layer.toml, and .agents/skills/ if present.
Preserve existing local customisations; do not delete or overwrite them without an explicit user request.
Run memory wizard --dry-run in the target project and review the planned repo-local writes.
If the preview is safe, run memory wizard in the target project.
Run memory doctor again.
Report the project slug, files created or preserved, backend health, and next commands.

Optional Evidence Setup

Only run these if the user explicitly wants initial evidence imported:

memory commits sync --project <project-slug> --dry-run
memory scan --project <project-slug> --dry-run

Ask before running the non-dry-run versions. Use commits sync for commit history evidence and scan for LLM-assisted initial memory candidates.

Safety Rules

Preview write-capable setup commands first with --dry-run.
Do not run package managers or service installers from this skill.
Do not create, delete, or reinitialise git repositories.
If .mem/config.toml, .mem/project.toml, .agents/memory-layer.toml, or any skill directory exists, treat it as user/project state.

Runtime Requirement

The repo-local Memory Layer skill bundle uses the shared Go helper under .agents/skills/memory-layer/scripts/. go must be available on PATH for those helper commands to run after setup.