powerhouse-inc

Architect Agent for the Apeiron workflow. Transforms structured requirements into document model designs — GraphQL state schemas, module/operation plans, subgraph type definitions, and editor component specs. Use when (1) requirements are ready and a schema needs designing, (2) a new document model needs modules and operations planned, (3) an existing model needs schema changes proposed, (4) subgraph types need to be designed for new fields, or (5) you need to plan how a feature maps to Powerhouse primitives. Triggers on: schema design, document model architecture, operation planning, module design, type design, subgraph planning, model proposal, specs.

Analyst Agent for the Apeiron workflow. Transforms raw business ideas, stakeholder input, and SME knowledge into structured requirements for Powerhouse document models. Use when (1) a new feature or document model is proposed but requirements are vague, (2) stakeholder needs must be captured and prioritized, (3) a PRD needs to be created or refined, (4) frontend data needs must be communicated to backend, or (5) starting any new workstream that will eventually become a document model. Triggers on: new feature request, requirements gathering, stakeholder analysis, PRD creation, business requirements, problem statement, feature proposal, demand signal.

Developer Agent for the Apeiron workflow. Implements document model changes — reducers, editors, subgraph resolvers — from an Architect's spec. Use when (1) a spec is ready and needs implementing, (2) reducers need to be written or updated, (3) editor components need to be built, (4) subgraph resolvers need mapping, (5) MCP actions need dispatching for schema changes, or (6) you're in the implementation phase of any document model workstream. Triggers on: implement spec, write reducer, build editor, implement operation, dispatch actions, code the schema, wire up subgraph, implement feature.

Reviewer Agent for the Apeiron workflow. Schema hygiene, document state verification, delivery checklist, and query field mapping for ALL Powerhouse document models in this repo. Use when (1) an implementation needs reviewing before merge, (2) checking a live document's state against its schema for unused/empty fields, (3) auditing a document model for dead weight, (4) verifying subgraph query types match the schema, (5) preparing a schema delivery for backend consumers, (6) running a weekly backend sync, or (7) running TypeScript/ESLint checks. Triggers on: schema audit, dead weight, field mapping, query fields, backend sync, delivery checklist, apeiron check, subgraph query, document state check, unused fields, review implementation, approve schema.

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

Build document models, editors, processors, subgraphs, and drive-apps for the Powerhouse/Vetra ecosystem. Use when Claude needs to (1) create or modify document models with GraphQL schemas and operations, (2) build React-based document editors with dispatch hooks, (3) work with Reactor-MCP tools for document and drive management, (4) implement pure synchronous reducers, (5) use the Powerhouse CLI (ph vetra, ph generate, ph connect), (6) design GraphQL state and input schemas with Powerhouse scalar types, (7) create subgraphs or processors, (8) deploy or publish Powerhouse packages, or any Powerhouse/Vetra development task. Triggers on mentions of: Powerhouse, Vetra, document model, reactor, MCP reactor, ph vetra, ph generate, switchboard, Connect Studio, drive, PHID, OID, document-engineering, reducer, dispatch, addActions.

Business analysis: requirements engineering, stakeholder analysis, process modeling.

Google Sheets API via curl. Use this skill to read, write, and manage spreadsheet data programmatically.

Migrate a Powerhouse op-hub editor (packages/op-hub/editors/*) to the Achra design system. Swap @powerhousedao/document-engineering primitives for @achra/ui, replace hardcoded Tailwind palette colors (gray-*, slate-*, stone-*, emerald-*, raw hex) with semantic tokens, and fix light/dark theming for the third-party components an editor renders inside Connect (document-engineering ObjectSetTable, Sidebar, DatePicker & Select, @uiw/react-md-editor, design-system widgets). Use when updating design tokens in an op-hub editor, fixing dark-mode contrast (dark-on-dark text, white hover/selection flashes, light borders, near-black widget surfaces), fixing a document-engineering DatePicker (unreadable days, black nav arrows/icon, dead arrow buttons, collapsed month/year views, double border) or Select (white trigger hover, dark-on-dark options, black selection boxes, banding between options), or porting an editor's colors to semantic tokens. Proven on builder-profile, builder-team-admin (incl. the subscriptions dashboa

Enforce modern React 19 best practices (2026) when working on React components, hooks, editors, and UI logic. Use for any React/TSX editing, refactoring components, extracting hooks, state management, effects, and forms. Trigger on: react, component, hook, useState, useEffect, editor, jsx, tailwind in react files, following package versions (React 19.2.6, @types/react ^19.2). Slash command: /react-best-practices-2026

Enforce modern TypeScript 5.9+ best practices (2026) for strict typing, module resolution, and safety. Use on any .ts/.tsx changes, especially when touching types from document-models, actions, state schemas, or editor logic. Follow exact versions: typescript ^5.9.3, @types/node ^24, zod 4.3.6. Project tsconfig: nodenext + strict + verbatimModuleSyntax. Slash command: /typescript-best-practices-2026

Use when migrating a Powerhouse Reactor project to a new stack version, validating a Reactor project (runs lint:fix, tsc, build, publint), or inspecting project state. Triggers on "migrate reactor", "powerhouse migrate", "validate reactor project", "ph-porter ...". Do NOT use for non-Powerhouse projects, generic dependency bumps, or general npm publish workflows.

Reference for the Powerhouse Reactor API two-layer authorization system. Use this skill when configuring authentication, managing roles and permissions, troubleshooting access issues, or implementing auth-related features in a Powerhouse project.

Master modern GraphQL with federation, performance optimization, and enterprise security. Build scalable schemas, implement advanced caching, and design real-time systems. Use PROACTIVELY for GraphQL architecture or performance optimization.

When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.

Draft and prepend a new entry to RELEASE-NOTES.md for an upcoming production release of this monorepo, and produce a copy-paste-ready Discord announcement for the

Migrate a Powerhouse op-hub editor (packages/op-hub/editors/*) to the Achra design system. Swap @powerhousedao/document-engineering primitives for @achra/ui, replace hardcoded Tailwind palette colors (gray-*, slate-*, stone-*, emerald-*, raw hex) with semantic tokens, and fix light/dark theming for the third-party components an editor renders inside Connect (document-engineering ObjectSetTable & Sidebar, @uiw/react-md-editor, design-system widgets). Use when updating design tokens in an op-hub editor, fixing dark-mode contrast (dark-on-dark text, white hover/selection flashes, light borders, near-black widget surfaces), or porting an editor's colors to semantic tokens. Proven on builder-profile, builder-team-admin (incl. the subscriptions dashboard and charts), and service-offering-app.

Author or edit a vetra agent skill under `vetra-cli/prompts/skills-tpl/<skill>/` — `.preamble.md`, scenario refs, build pipeline, and the runtime `skill` / `skill_read` contract. Triggers on "edit skill", "the agent isn't reading <reference>", "skill preamble", "add a reference to <skill>", changes under `prompts/skills-tpl/`. NOT for Claude Code skills under `.claude/skills/` or generic prompt-engineering.

Automate browser interactions, test web pages and work with Playwright tests.