OpeItcLoc03/skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(skills): delete setup-tasks/setup-wiki — мета в сервисе (#983)

Browse Source 
Нечего настраивать (решение 14/15). Свип ссылок: project-bootstrap v2.1.0
(Steps 3/4 → mappa, манифест без setup-строк), project-discipline (Rule 1),
setup-projects-meta README, using-tasks/using-wiki README.
This commit is contained in:
vitya
2026-08-24 16:45:59 +03:00
parent c5ebde174d
commit afca818a05
5 changed files with 39 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
skills/project-bootstrap/README.md
View File

@@ -24,16 +24,11 @@ clearly intends to turn into a workspace.
## Prerequisites
`project-bootstrap` does not lay out `.wiki/` or `.tasks/` by itself — it
delegates to two companion skills, which must be installed on the machine
running it:
- [`setup-wiki`](../setup-wiki/) — creates the canonical `.wiki/` layout.
- [`setup-tasks`](../setup-tasks/) — creates the canonical `.tasks/` layout.
If either is missing, `project-bootstrap` stops with a clear error rather
than falling back to ad-hoc creation. This keeps layout drift between
projects bootstrapped at different times debuggable.
Мета в сервисе (решения 14/15): вики и таски проекта живут в **mappa**
(`using-wiki` / `using-tasks` v2 — mappa-тулы), файловый `.wiki/` / `.tasks/`
не создаётся. `setup-wiki` / `setup-tasks` умерли (нечего настраивать);
для проектов вне mappa файловый layout создаётся ad-hoc по канону
Karpathy / `.tasks/` (см. using-wiki/using-tasks, legacy-раздел).
## What it creates
@@ -42,8 +37,8 @@ projects bootstrapped at different times debuggable.
| `.git/` | `git init` | Skipped if repo already initialized. |
| `.gitignore` | `assets/.gitignore.template` | Skipped if file exists. |
| `README.md` | minimal stub | Skipped if file exists. |
| `.wiki/` | delegated to `setup-wiki` | Karpathy LLM Wiki layout — `CLAUDE.md`, `index.md`, `log.md`, `overview.md`, `raw/`, `entities/`, `concepts/`, `packages/`, `sources/`. |
| `.tasks/` | delegated to `setup-tasks` | Canonical board — `STATUS.md` plus per-task `<task-slug>.md` files. |
| вики | mappa (`using-wiki`) | сущности `type=wiki` в сервисе; файловый layout — только вне mappa (легаси). |
| таски | mappa (`using-tasks`) | сущности `type=task` в сервисе; файловый `.tasks/` — только вне mappa (легаси). |
| `AGENTS.md` | `assets/AGENTS.md.template` | **Canon** — skill triggers (`use project wiki`, `use task management system`, etc.). On non-Windows hosts, swap the `we're on Windows` line for `we're on Linux` / `we're on macOS`. On upgrade, the template is treated as a canonical set and merged idempotently — only missing trigger lines are appended after user confirm. Re-runs are no-ops. |
| `CLAUDE.md` | generated pointer | `Canon is AGENTS.md. Read AGENTS.md.` — legacy pointer for tooling that looks for the old name. |
| `.wiki/concepts/bootstrap-manifest.md` | generated | Records which skill versions initialized the project, so cross-project layout drift is debuggable. |
@@ -55,11 +50,11 @@ projects bootstrapped at different times debuggable.
found, what will be created, what will be skipped.
2. **Confirm.** One question, one confirmation. Nothing is written before the
user agrees.
3. **Steps 1–5.** Create or skip each piece in order — git, README, `.wiki/`,
`.tasks/`, `AGENTS.md` + `CLAUDE.md` pointer. Steps 3 and 4 delegate to the setup-skills.
3. **Steps 1–5.** Create or skip each piece in order — git, README, вики/таски
(mappa, см. using-wiki/using-tasks), `AGENTS.md` + `CLAUDE.md` pointer.
4. **Step 5.5.** Write `bootstrap-manifest.md` recording the versions of
`project-bootstrap`, `setup-wiki`, `setup-tasks`, `project-discipline`,
`setup-interns`, and `using-interns` used.
`project-bootstrap`, `project-discipline`, `setup-interns`, and
`using-interns` used.
5. **Step 5.6.** Skill dependencies check. Walk the canonical trigger list
in `AGENTS.md`, look each up in an embedded `trigger → fulfiller` map,
detect what's missing on this host (`~/.claude/skills/<name>/SKILL.md`
@@ -105,10 +100,8 @@ target with `CLAUDE_SKILLS_DIR=/path bash scripts/install.sh …`.
## See also
- [`setup-wiki`](../setup-wiki/) — companion, owns `.wiki/` layout.
- [`setup-tasks`](../setup-tasks/) — companion, owns `.tasks/` layout.
- [`using-wiki`](../using-wiki/) — runtime policy for working with `.wiki/`.
- [`using-tasks`](../using-tasks/) — runtime policy for working with `.tasks/`.
- [`using-wiki`](../using-wiki/) — runtime policy for the mappa wiki (v2).
- [`using-tasks`](../using-tasks/) — runtime policy for the mappa task board (v2).
- [`project-discipline`](../project-discipline/) — cross-project rules
activated by the `follow project discipline` trigger.
- [`setup-interns`](../setup-interns/), [`using-interns`](../using-interns/) —

30
skills/project-bootstrap/SKILL.md
View File

@@ -1,7 +1,7 @@
---
name: project-bootstrap
author: ours
version: 2.0.1
version: 2.1.0
description: >
Initializes or upgrades a project in the current folder: git, .gitignore, README.md,
.wiki/ using Karpathy's method, .tasks/ for task tracking, AGENTS.md (canon) with
@@ -178,13 +178,14 @@ If it exists — leave it untouched.
---
## Step 3 — .wiki/
## Step 3 — вики (mappa, решение 14/15)
**Delegate to the `setup-wiki` skill.** It handles greenfield creation, canon migration, and the no-op case (already canon) uniformly, with its own confirmation gate. Don't recreate the layout inline here — that's how drift happens.
If `setup-wiki` is not installed on this machine, **stop** and tell the user: project-bootstrap requires `setup-wiki` (and `setup-tasks`) installed. Don't fall back to ad-hoc creation.
**Reference (for context only — `setup-wiki` is the source of truth):** the canonical layout per Karpathy (gist: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) and `using-wiki`:
**Канал — mappa:** вики проекта = сущности `type=wiki` в сервисе (решения 14/15:
мета в сервисе). Ничего файлового создавать не нужно; операции — `using-wiki`
v2 (mappa wiki-тулы). Файловый `.wiki/` — только для проектов вне mappa
(легаси): layout по Karpathy (gist: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f).
`setup-wiki` умер (нечего настраивать) — при необходимости создания страниц
используй `wiki.create` под лизом (см. using-wiki).
```
.wiki/
@@ -311,13 +312,14 @@ each get a `.gitkeep` so git tracks them.
---
## Step 4 — .tasks/
## Step 4 — таски (mappa, решение 14/15)
**Delegate to the `setup-tasks` skill.** It handles greenfield creation, migration from flat STATUS.md, and the no-op case uniformly, with its own confirmation gate. Don't recreate the layout inline.
If `setup-tasks` is not installed, **stop** and tell the user — same rule as Step 3.
**Reference (for context only — `setup-tasks` is the source of truth):** the canonical layout is `.tasks/STATUS.md` (the board, with emoji status 🔴/🟡/⚪/🟢/🔵) plus `.tasks/<task-slug>.md` per active or paused task. The full pattern is documented in this repo at `.wiki/raw/setup-task-status-wiki.md`.
**Канал — mappa:** борд проекта = сущности `type=task` в сервисе (решения
14/15: мета в сервисе). Ничего файлового создавать не нужно; операции —
`using-tasks` v2 (mappa task-тулы). Файловый `.tasks/` — только для проектов
вне mappa (легаси: `STATUS.md` + per-task файлы). `setup-tasks` умер
(нечего настраивать) — таски создаются через `task_create` под лизом
(см. using-tasks/task-format).
---
@@ -474,8 +476,6 @@ Skills used to initialize this project's `.wiki/` and `.tasks/` layout, with the
| Skill | Version | Role |
|---|---|---|
| `project-bootstrap` | <version> | orchestrator |
| `setup-wiki` | <version> | wiki canonical layout |
| `setup-tasks` | <version> | tasks canonical layout |
| `project-discipline` | <version> | cross-project policy |
| `setup-interns` | <version> | interns MCP server install (one-time, per machine) |
| `using-interns` | <version> | interns runtime policy + per-session permission grant |