docs(readme): document project-bootstrap usage

Both README.md and README.ru.md gain a new "Using skills in projects"
/ "Использование в проектах" subsection right after the install
quick-start. Briefly describes what `project-bootstrap` lays down
(git, .gitignore, README, .wiki/, .tasks/, CLAUDE.md, manifest,
superpowers-plugin check) and the init/upgrade dual mode.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

README.md

@@ -41,6 +41,25 @@ The install target can be overridden with `CLAUDE_SKILLS_DIR=/path bash scripts/
 
 > `install.sh` works on Windows under git-bash. A native `install.ps1` is on the task board but not yet implemented.
 
+### Using skills in projects
+
+Once the skills are installed, the easiest way to wire them into a new
+(or existing) project is the [`project-bootstrap`](skills/project-bootstrap/)
+skill. Tell the agent **"bootstrap"** or **"set everything up"** from the
+project's folder and it will, in one pass:
+
+- initialize `git` (if missing) and write a sane `.gitignore`
+- create a starter `README.md`
+- lay out `.wiki/` per the [Karpathy LLM Wiki pattern](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) (delegated to [`setup-wiki`](skills/setup-wiki/))
+- lay out `.tasks/` with the canonical task board (delegated to [`setup-tasks`](skills/setup-tasks/))
+- write `CLAUDE.md` with skill triggers (`use superpowers`, `use project wiki`, `use task management system`, `we're on Windows`)
+- record the skill versions used in `.wiki/concepts/bootstrap-manifest.md` so cross-project layout drift stays debuggable
+- check whether the official `superpowers@claude-plugins-official` plugin is installed and, if not, print the install command — the `use superpowers` trigger is a no-op without it
+
+Two modes, picked automatically: **init** for an empty folder, **upgrade**
+for an existing project (the skill only fills the gaps and never overwrites
+without explicit confirmation).
+
 ### Edit a skill
 
 ```bash