Skip to content

chatfuel-lab/wizard / content/modules/channels/skill

FileKindSize
SKILL.mdskill md4.0 KB
playbooks/customize.mdmarkdown1.9 KB
playbooks/embed.mdmarkdown1.7 KB
references/guide.mdmarkdown5.7 KB

playbooks/embed.md

View on GitHub
# Embedding this module

Follow `../chatfuel-core/playbooks/embed.md` first — aliases, styles, proxy and
the mounting pattern all live there. This file only adds what is specific to
this module.

- Entry component: `<ChannelsApp />` from `src/chatfuel/modules/channels/`.
- There are no views. The module ignores `view`, and the only params it reads
  are the two the return leg of a hand-off writes (`result`, `channel`), which
  it clears from the address as soon as it has said what they said.
- **Connecting leaves the app in the same tab** and comes back by redirect, to
  this module's own address. A host that mounts it somewhere `window.location`
  cannot describe — inside a cross-origin iframe, say — gets the hand-off out
  and no way home; mount it as a page.
- **Changing anything needs Configure: Edit.** The module asks `MyBotRole` and
  shows Connect, Refresh access and Disconnect only when the role holds it; a
  role without sees the connection state and nothing to change. That is a decision
  about what to offer, not an authorization boundary — through a proxy the API
  enforces the token owner's role, so a host that wants a harder line draws it
  in the proxy.
- **The module mounts its own `ToastProvider`.** Coming back from a hand-off
  with a channel connected is a toast, and so is a disconnect; a host that
  strips the provider loses both signals.
- Breakpoints are container-based: the module measures its own root and lays
  out correctly at any width the host gives it. No media queries are involved
  and none should be added.
- `ChannelsApp`'s root carries `relative` on purpose: the confirm dialogs
  portal to the design system's portal root, but anything the module positions
  absolutely anchors to this element.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall