[DO NOT MERGE] chore(skills): sync-inbox-to-cloud reference scaffold#2489
Draft
Twixes wants to merge 2 commits into
Draft
[DO NOT MERGE] chore(skills): sync-inbox-to-cloud reference scaffold#2489Twixes wants to merge 2 commits into
Twixes wants to merge 2 commits into
Conversation
…not merge) Adds a parent /sync-inbox-to-cloud skill plus five sub-skills that orchestrate porting features and UI polish from the desktop Inbox to PostHog Cloud: - /inspect-inbox-surfaces - /plan-inbox-sync - /implement-inbox-sync (with translation.md reference) - /finalize-inbox-sync - /reflect-on-inbox-sync Plus references/parallelization.md describing how to slice work across parallel sub-agents and the upcoming-direction mock screenshots used as supplementary context. Not for merge — this branch exists as a long-lived reference / checkout target while the cloud Inbox port is in flight. See PR description.
…ts view The desktop Agents view (`/code/agents`) mounts `ConfigureAgentsSection` from `features/inbox/components/`, so the sync should treat it as inbox parity. Add explicit scope, planning, and anti-checklist rules: - Scope the Agents view's body (Setup task CTA, Connections, Auto-start, Sources, MCP servers) into the manifest every run. - The cloud Inbox toolbar gear button is always labelled "Configure agents", not "Edit sources" / "Signal sources" / "Manage integrations". - Planning must call `AskUserQuestion` before finalizing the surface shape (modal / scene / drawer), autonomy granularity, setup-task CTA treatment, MCP servers handling, and (conditionally) Connections layout, since these vary per run as desktop's IA shifts. - Inspect step must enumerate `ConfigureAgentsSection`'s sections so the planner can ask the right questions. Skipped sections go under "Skipped" in the final report with a product reason. This is the WIP that was stashed during the inbox-v2-pr re-revert; landed here so the inbox-v2-pr branch can stay free of the scaffold while the sync skill keeps evolving on its own branch.
|
React Doctor found no issues in the changed files. 🎉 Reviewed by React Doctor for commit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Don't merge, just for easy reference
Keep this draft open until the new Cloud Inbox is built and mostly migrated, then close and delete it. It's a scaffold I want to be able to check out from anywhere - not something to ship to main.
What it is
A
/sync-inbox-to-cloudskill that orchestrates six sub-skills as one uninterrupted pass, porting desktop Inbox features and polish into PostHog Cloud:/inspect-inbox-surfaces- list both repos, build an inventory/plan-inbox-sync- diff inventories, produce a manifest plus slicing plan/implement-inbox-sync- dispatch parallel sub-agents, integrate centrally (Quill/Radix → Lemo nUI, Zustand/TanStack Query → Kea translation etc.)/simplify- existing repo skill, on touched cloud files/finalize-inbox-sync- typecheck, format, tests, structured report/reflect-on-inbox-sync- audit against hard rules, propose skill-text refinementsEach sub-skill ends with a "do not stop, invoke
/<next>" closer so the whole thing runs as one pass.Plus three mock screenshots from
posthog-self-driving.pages.devas supplementary direction.