Prox OS Internal Docs
DevelopmentTooling

Design And Ops Tooling Map

These tools may support design, decks, and operations. They are not all adopted

Candidate Tool Map

These tools may support design, decks, and operations. They are not all adopted by default.

Design And Presentation

ToolCurrent postureUse forAvoid using for
PowerPointFormal business delivery artifact.Investor, partner, and customer-facing documents when editability matters.Runtime UI truth or product requirements.
Canva ProExternal asset studio.Launch images, social cards, simple brand assets, deck polish, screenshots, marketing visuals.Defining OS runtime UI or component behavior.
Figma / Figma SlidesOptional specialist workspace.Brand systems, complex prototypes, multi-screen flows, paid designer collaboration, high-fidelity review.Default solo-founder workflow when React + Storybook + tokens are faster.
StorybookUI truth layer for implemented components.Component communication, state review, visual regression references, onboarding.Business decks, launch social campaigns, or non-UI project management.
Markdown / deck-as-codeNarrative source.Internal briefs, investor outlines, launch decks, AI-reviewable slide sources.Final visual polish when the audience expects a designed artifact.
GammaFast narrative prototype.Early deck exploration and narrative framing.Canonical product docs or legal/commercial claims.
Google SlidesLightweight collaboration.Team review and asynchronous comments.Long-term product source of truth.

See ../design/design-operating-system.md and ../design/deck-as-code.md.

Operations And Planning

  • Notion as optional knowledge workspace.
  • Linear or Jira as optional issue planning systems.
  • GitHub Projects as the current natural default for repo-linked work.
  • Cloudflare dashboards for deployment and Access once production paths exist.

Rule

Tooling should reduce cognitive load. If a tool creates another source of truth without a clear sync path, it should remain experimental.

On this page