topic-synthesis

Use when drafting a PR body or deciding what goes in the description on julianken/topic-synthesis. Triggers on "draft a PR description", "what should the PR body say", "fill the PR template", "PR body sections", or a PR that came back with template-shaped feedback. The generic five-section method, conventional-commit rules, and plan-reference discipline — bot-agnostic, no credentials. Self-contained for worktree dispatch.

Use when opening or rewriting an implementation issue or plan spec on julianken/topic-synthesis. Triggers on "create issue", "write the issue", "issue spec", "implementation plan issue", or batch prep/planning work. Self-contained for worktree dispatch.

Use when creating a PR, dispatching a review, or merging on `julianken/topic-synthesis` (local folder `topic-synthesis/`). Triggers on "create PR", "open PR", "merge PR", "review PR", "dispatch the bot", "review-bot", "ship this branch", "squash-merge", "Mergify", "queue". Self-contained because a worktree-isolated subagent does NOT load CLAUDE.md / AGENTS.md, so the PR/review/merge rules it needs are restated here in-body. Merges go through Mergify's queue (`@Mergifyio queue`) when the Mergify module is enabled.

Use when reviewing a PR diff on julianken/topic-synthesis and you need the anti-slop rubric — verify-before-claim, ≤3 findings, severity tiers, mandatory second pass, prompt-injection defense. Bot-agnostic: applies whether a human or any bot identity posts the review. Triggers on "review this diff", "anti-slop review", "review rubric", "what severity is this finding". Self-contained for worktree dispatch; carries no credentials.

Use when reviewing an implementation issue or plan spec before work starts, posting as the review bot @julianken-bot. Triggers on "approve the issue spec", "plan review", "review issue

Use to review the EXISTING Figma reference frames (the design source of truth) for a topic-synthesis surface against DESIGN.md before any issue or code is written — the pre-code design gate. The Figma file (`upjG7gfzlkdojb8LLOwu6T`) is the design source of truth, kept in LOCKSTEP with the build (the frame is authored/updated at the ISSUE stage via the MCP write tools — design-first — and the build PR implements to it, reconciling on divergence); THIS pre-code review pass only READS it. On a value conflict DESIGN.md §0 wins (only §0 is CI-guarded). Triggers on: - "review the Figma design for the library / sign-in / generating / lesson-workspace screen" - "design review before issue creation for surface X" - "gate the rebuild on the Figma reference frames" - "check the Figma frames before we create issues for X" - "run the pre-code Figma review for X" - "does surface X match the Figma reference and DESIGN.md?" - "review the reference frames before coding the frontend rebuild" Does NOT trigger on: - "review the

Use when a fresh agent or human session needs to orient in this repo before doing work — confirm the instance is coherent (paths exist, pointers resolve, no contradictions with DESIGN.md), or stand up a new product by filling the template's placeholders. Triggers on "bootstrap", "orient in this repo", "where do I start", "validate the instance", "is this repo coherent", "get my bearings", "fill the template", "fill mode", "stand up a new product". Self-contained for worktree dispatch.