workspace-sync

Reconcile the ~/Projects workspace against WORKSPACE.md and GitHub — clone missing repos into their domains, report drift, add/move projects with map-and-territory discipline. Use when asked to "sync the workspace", "clone my repos", "add a repo to the workspace", or "check workspace status".

Ir para a instalação

Repositório: mazze93/claude-code-skills
Última atividade na origem: 15 de julho de 2026 às 09:06
Idioma detectado do SKILL.md: inglês
Estrelas: 1
Forks: 0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/mazze93/claude-code-skills --skill workspace-sync

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

component-factory

Convert a hand-maintained design system into generated output driven by one token file, with a build-failing guard that makes palette/type drift structurally impossible. Use when a design system has stale values scattered across pages, duplicated @font-face or CDN font imports, or a "source of truth" that nothing actually imports — and when delegating mechanical design migration to a cheaper agent needs a deterministic gate rather than trust.

2026-08-01

engram

Memory-as-first-class system for Claude sessions across a multi-domain workspace (~15+ active projects). USE THIS SKILL for: (1) setting up ENGRAM on a new device ("set up ENGRAM", "install memory system", "set up my context", "set up memory"); (2) capturing thoughts in-session ("remember X", "add to memory", "note that", "log that", "capture this"); (3) surfacing project context ("what's my context", "surface my memory", "what am I working on", "restore context", "what do I know about X"); (4) inbox consolidation ("consolidate my memory", "process my inbox", "clean up memory"); (5) creating per-repo CLAUDE.md stubs. Trigger when any workspace project is mentioned and context appears missing. Trigger on new-device setup and memory restoration. Workspace source of truth: ~/Code/WORKSPACE.md

2026-07-30

transcript-handoff

Produce a structured markdown session export for a long-form creative, intellectual, or research project (essays, theses, multi-session design work, personal-history-driven writing) so a future session — by this user or a future Claude instance — can pick up with full continuity. Use this whenever the user asks to "export this conversation," "give me a transcript," "systematize the handoff," "save this session," wants a "markdown export" of a working conversation, or references continuing a project across sessions. Also trigger proactively near the end of a long, substantive working session on a recurring creative/research project, even if the user hasn't asked yet — mention it as an option. Do not use this for ordinary code projects with their own repo/README conventions, or for one-off factual Q&A with no project continuity.

2026-07-30

Ver todas deste repositório

name	workspace-sync
description	Reconcile the ~/Projects workspace against WORKSPACE.md and GitHub — clone missing repos into their domains, report drift, add/move projects with map-and-territory discipline. Use when asked to "sync the workspace", "clone my repos", "add a repo to the workspace", or "check workspace status".

/workspace-sync

The workspace root ~/Projects (alias ~/Code) is a thin container repo (mazze93/projects-workspace); every project is a sibling clone under a domain dir. WORKSPACE.md is the map and the intent — if disk and map disagree, reconcile toward the map.

Commands (all via `~/Projects/scripts/ws`)

scripts/ws list      # registry vs disk (✓/✗)
scripts/ws status    # dirty/ahead/behind across every clone
scripts/ws sync      # ff-pull every clean clone (dirty ones skipped, never touched)
scripts/ws missing   # clone absent registry entries into their domain paths
scripts/ws open <q>  # fuzzy-open a project in Zed

Adding a new project (the contract, rule 3)

Decide its domain: blog/ apps/ tools/ cognitive/ creative/ secure-pride/ skills/ templates/ meta/ archive/. Doesn't fit? STOP and ask — never invent a top-level dir.
In the SAME commit to the container: add its row to the WORKSPACE.md registry AND its "path|repo" line to the REGISTRY array in scripts/ws.
scripts/ws missing to clone it. Commit message: map: add <name> to <domain>/.

Moving / retiring a project

Same-commit rule applies: mv the dir, update both registry locations, commit. Retired repos go to archive/, not deleted.

Full resync on a fresh machine

gh auth login
gh repo clone mazze93/projects-workspace ~/Projects
cd ~/Projects && bash scripts/install-hooks.sh && bash scripts/ws missing
ln -sfn ~/Projects ~/Code

Guardrails

Never git add a project into the container — the allowlist .gitignore and pre-commit hook will fight you; they are right.
secure-pride/* stays in private repos; never log identifiers unmasked.
New GitHub repos that are empty (0 KB) are listed under "Not cloned" in WORKSPACE.md rather than cloned.

workspace-sync

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

/workspace-sync

Commands (all via ~/Projects/scripts/ws)

Adding a new project (the contract, rule 3)

Moving / retiring a project

Full resync on a fresh machine

Guardrails

/workspace-sync

Commands (all via ~/Projects/scripts/ws)

Adding a new project (the contract, rule 3)

Moving / retiring a project

Full resync on a fresh machine

Guardrails

Commands (all via `~/Projects/scripts/ws`)

Commands (all via `~/Projects/scripts/ws`)