pailat/pai-console-production

Model a system's C4 architecture in Pai Console Knowledge using component nodes by level (context, container, component, code) and actor nodes for people, with descriptions and technology on relationships. Use for architecture, C4, context or container diagrams, components, or a system map.

Use Pai Agent chats through MCP: list/read own sessions, create or resume a chat, send a message, cancel a running turn and close with a summary. Use for New Chat, My Chats or delegating an explicitly requested task to Pai Agent.

Pai Console CRM for users with effective granular CRM permissions through corp MCP: leads, qualification, workspaces, opportunities, forecasting, submission-to-project traceability, and CRM tasks. Use for Forms submissions, duplicate-safe lead creation/import, contacting/qualifying/disqualifying prospects, Discovery workspaces, pipeline stages, holds/wins/losses, contacts/probability, attention queues, or task details, priorities, tags, scheduling, assignment, and completion.

Model an ERD in Pai Console project Knowledge with data_model and entity nodes, typed columns, and relationships derived from foreign keys. Use for data models, ERDs, tables, entities, database schemas, or importing schema.sql or migrations into Pai.

Pai Console project flows (ATE-230): entity-backed steps, labeled branches, actor/screen/action/integration refs, and role-based tests. Covers flow_list/get/create/save with CAS and graph or Mermaid, version bumps, flow_run_* tests, simulated integrations with sampleResponse/sampleCases, test readiness, and client publication order. Use to create, correct, simulate, test, or prepare a branched journey or process for clients.

Inspect and manage Pai IAM access through actual grants: principals, groups, roles, resource policies/bindings, deny rules, organization boundaries, access tests, audit and member visibility settings. Use for access diagnosis or explicitly requested permission changes.

Create and maintain Pai Console project or product Knowledge graphs: kinds, strict templates, sources, human-confirmed proposals, CAS with expectedRevision, ontology links including implemented_by, structured knowledge_query, atomic knowledge_batch, and resolve/supersede/archive lifecycle. Use for decisions, business rules, risks, questions, assumptions, facts, glossary, modules, other nodes, or graph queries. ERD, C4, screens, and flows have dedicated skills.

Base workflow for Pai Console through MCP (mcp__plugin_pai-console_pai__*, mcp__pai-console__*, mcp__pai__*, or mcp__claude_ai_pai__*). Read before any Pai operation: environment, organization/project discovery, search before create, CAS with expectedRevision, idempotency, English identifiers, errors, and citations. Domain skills assume this guidance has been read. Supports Claude invocation and Codex generated environment packages.

Show or switch the installed Pai Console environment; only switch when the user explicitly requests it.

Read-only Pai Console exploration: searches, inventories, catalogs and context with exact references.

Manage Pai Console project products and lifecycle: registration, approval-gated states, Pai App provisioning (GitHub/Railway), variables, staging/production deploys, domains, team, and production access. Use to register, provision, deploy, configure, inspect logs, grant access, or move a product to live.

Manage Pai Console project SOW proposals and collections: compose/save/send proposals, record acceptance or rejection, link billing milestones, import income CFDI, record payment complements, and void payments. Use for proposals, quotations, SOWs, investment, invoices, CFDI, payment complements, received payments, collections, or voids.

Create and maintain Pai Console project Resources: typed pages, canvas view blocks, HTML prototypes, Excalidraw whiteboards, live Knowledge projections, attributes and filters, notes, folders, suggestions, comments, image/video assets, and files. Use for documents, reports, PRDs/SOWs, dashboards, mockups, editable diagrams, page approval/ownership/filtering, suggestions, comments, uploads, asset reuse/deletion, or moving/restoring/deleting pages and empty folders.

Plan and maintain Pai Console project schedules: milestones, dates, amounts, acceptance criteria, baseline, milestone/task dependencies, unified tasks, legacy Knowledge task compatibility, task board, and project closure/reopening. Use for work plans, schedules, milestones, tasks, kanban, dependencies, baselines, progress, delays, or closing/reopening projects.

Document product screens, actions, and actors in Pai Console project Knowledge (screen v3, action, actor; flows use the flows skill). Use for screen inventories, navigation maps, screen behavior and users, available actions, or connecting screens to their data.

Set up a Pai Console Codex package, inspect activation and explain OAuth and hook review.

Manage Pai's unified tasks across CRM, projects and product backlogs: discover, create, assign, schedule, complete, cancel, archive and restore with revision checks. Use for My Tasks, follow-ups, task boards, priorities, tags or product work.

Organization branding in Pai Portal Appearance through staff-only corp organization_theme_* tools: light/dark colors, font, radius, shadow, logos, Portal shell, and AA contrast. Read/extract real product or brand tokens, convert to OKLCH, map Portal tokens, preview, save drafts, publish/revert versions, upload theme/organization logos, and verify both modes in Portal. Use for themes, branding, white-label, design tokens, typography, logos, Portal colors/layout, or matching a client's brand.

Propose or repair Pai organization themes through reads and at most eight preview attempts; never save or publish.

Compose Pai generative UI with pai-view@1: real Portal/Console/pai.lat screens, region layouts, forms/chat/commerce, data components, and Knowledge diagrams. Use view_render for conversational dashboards, comparisons, or summaries, or save canvas-page view blocks in Resources for dashboards, screen mockups, and visual reports. Applies to visual Pai data requests, dashboards, wireframes, app/Portal/Console/site screens, ERD/C4/graph rendering, or editing existing views.