chore: scaffold Astro project and configure agent skills

Initial commit: Astro minimal template (Node >= 22.12), agent docs (AGENTS.md/CLAUDE.md/QWEN.md), and docs/agents setup for the Gitea issue tracker via the tea CLI, triage labels, and domain docs.
2026-09-10 10:21:00 +02:00
commit 880e032ba1
17 changed files with 335 additions and 0 deletions
@@ -0,0 +1,51 @@
+# Domain Docs
+
+How the engineering skills should consume this repo's domain documentation when exploring the codebase.
+
+## Before exploring, read these
+
+- **`CONTEXT.md`** at the repo root, or
+- **`CONTEXT-MAP.md`** at the repo root if it exists: it points at one `CONTEXT.md` per context. Read each one relevant to the topic.
+- **`docs/adr/`**: read ADRs that touch the area you're about to work in. In multi-context repos, also check `src/<context>/docs/adr/` for context-scoped decisions.
+
+If any of these files don't exist, **proceed silently**. Don't flag their absence; don't suggest creating them upfront. The `/domain-modeling` skill (reached via `/grill-with-docs` and `/improve-codebase-architecture`) creates them lazily when terms or decisions actually get resolved.
+
+## File structure
+
+Single-context repo (most repos):
+
+```
+/
+├── CONTEXT.md
+├── docs/adr/
+│   ├── 0001-event-sourced-orders.md
+│   └── 0002-postgres-for-write-model.md
+└── src/
+```
+
+Multi-context repo (presence of `CONTEXT-MAP.md` at the root):
+
+```
+/
+├── CONTEXT-MAP.md
+├── docs/adr/                          ← system-wide decisions
+└── src/
+    ├── ordering/
+    │   ├── CONTEXT.md
+    │   └── docs/adr/                  ← context-specific decisions
+    └── billing/
+        ├── CONTEXT.md
+        └── docs/adr/
+```
+
+## Use the glossary's vocabulary
+
+When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in `CONTEXT.md`. Don't drift to synonyms the glossary explicitly avoids.
+
+If the concept you need isn't in the glossary yet, that's a signal: either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for `/domain-modeling`).
+
+## Flag ADR conflicts
+
+If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:
+
+> _Contradicts ADR-0007 (event-sourced orders), but worth reopening because…_
@@ -0,0 +1,56 @@
+# Issue tracker: Gitea
+
+Issues and specs for this repo live in the Gitea repository at
+`https://git.arthurerlich.de/haylan/php-node-renderer-playground`. Use the `tea` CLI
+(the official Gitea CLI, v0.15.1) for all operations.
+
+`tea` infers the repository from the local git remote (`origin` → this repo), so
+commands are run from the repo root without `-r`. Use `-o json` for machine-readable
+output (e.g. `tea issues ls -o json`). If a command can't find a login, run
+`tea login` first.
+
+## Conventions
+
+- **Create an issue**: `tea issues create -t "..." -d "..."` (add `-L "label, label"` for labels)
+- **Read an issue**: `tea issues <n> --comments -o json`
+- **List issues**: `tea issues ls -o json` (filters: `--state open|closed|all`, `--labels "..."`, `--keyword "..."`)
+- **List issue comments**: `tea comments list <n>`
+- **List labels**: `tea labels ls`
+- **Comment on an issue**: `tea comments add <n> "..."`
+- **Add / remove labels**: `tea issues edit <n> -L "label"` / `tea issues edit <n> --remove-labels "label"`
+- **Assign a dev**: `tea issues edit <n> -a <username>`
+- **Close**: `tea issues close <n>`
+- **Reopen**: `tea issues reopen <n>`
+
+Gitea shares one number space across issues and pull requests, so a bare `#42`
+may be either: resolve with `tea pulls view <n>` (or `tea issues -K pulls <n>`) and
+fall back to `tea issues <n>`.
+
+## Pull requests as a triage surface
+
+**PRs as a request surface: no.** _(Set to `yes` if this repo treats external PRs
+as feature requests; `/triage` reads this flag.)_
+
+When set to `yes`, PRs run through the same labels and states as issues, using the
+`tea pulls` equivalents (`tea pulls ls`, `tea pulls view <n>`).
+
+## When a skill says "publish to the issue tracker"
+
+Create a Gitea issue in `haylan/php-node-renderer-playground` (`tea issues create`).
+
+## When a skill says "fetch the relevant ticket"
+
+Run `tea issues <n> --comments` for the referenced number.
+
+## Wayfinding operations
+
+Used by `/wayfinder`. The **map** is a single issue with **child** issues as tickets.
+Gitea has no native sub-issues or issue-dependencies API, so links are recorded in
+issue bodies.
+
+- **Map**: a single issue labelled `wayfinder:map`, holding the Notes / Decisions-so-far / Fog body. Create with `tea issues create -t "..." -d "..." -L "wayfinder:map"`.
+- **Child ticket**: an issue linked to the map via a task list in the map body, with `Part of #<map>` at the top of the child body. Labels: `wayfinder:<type>` (`research`/`prototype`/`grilling`/`task`). Once claimed, the ticket is assigned to the driving dev.
+- **Blocking**: a `Blocked by: #<n>, #<n>` line near the top of the child body. A ticket is unblocked when every blocker is closed.
+- **Frontier**: scan the map's open children (task list / `Part of`), drop any with an open blocker (per the `Blocked by` line) or an assignee; first in map order wins.
+- **Claim**: assign the issue to the driving dev, the session's first write (`tea issues edit <n> -a <username>`).
+- **Resolve**: comment the answer (`tea comments add <n> "..."`), close the issue (`tea issues close <n>`), then append a context pointer (gist + link) to the map's Decisions-so-far.
@@ -0,0 +1,15 @@
+# Triage Labels
+
+The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
+
+| Label in mattpocock/skills | Label in our tracker | Meaning                                  |
+| -------------------------- | -------------------- | ---------------------------------------- |
+| `needs-triage`             | `needs-triage`       | Maintainer needs to evaluate this issue  |
+| `needs-info`               | `needs-info`         | Waiting on reporter for more information |
+| `ready-for-agent`          | `ready-for-agent`    | Fully specified, ready for an AFK agent  |
+| `ready-for-human`          | `ready-for-human`    | Requires human implementation            |
+| `wontfix`                  | `wontfix`            | Will not be actioned                     |
+
+When a skill mentions a role (e.g. "apply the AFK-ready triage label"), use the corresponding label string from this table.
+
+Edit the right-hand column to match whatever vocabulary you actually use.