AI Agent Hub
Back to skills
Dimension Table Intelligence System Design Plan icon

Dimension Table Intelligence System Design Plan

Business Operations Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @org-gpgr8p77/dimens-plan following the guide at https://skillhub.cn/install/skillhub.md.

About this skill

Problem It Solves

In Dimens projects, system-level asks are often reduced to fragmented actions: create tables, add fields, upload covers, build reports. When the requirement includes roles, approval, business canvases, permission boundaries, or page integration, unclear sequencing can cause missing resources, empty reports, or over-permissive access. @org-gpgr8p77/dimens-plan addresses this by structuring the plan before execution.

How It Works

  • Classify the request: full system, retrofit, resource query, single-domain task, or SDK integration.
  • Route the main line: dimens-cli operations go to dimens-manager; custom pages, Web/BFF, or mobile integration go to dimens-sdk or the custom-page scaffold.
  • For new projects, normalize input or existing documents into a dimension-table design document covering system positioning, menu tree, core objects, fields, sample data, permissions, and acceptance criteria.
  • Emit requirement class, system blueprint, deliverables, execution order, routing target, and acceptance evidence.
  • Add a business canvas for approval or collaboration flows, while keeping it separate from executable workflows that require definition, publishing, and mounting.

Boundaries and Notes

This skill is a planning and routing layer, not a universal executor. Links can only resolve teamId, projectId, sheetId, or viewId; they cannot replace login. Real CLI execution still requires exchanging API credentials for a token. Do not treat a default name field, empty report, or role creation without permissions as completed.

Use Cases

  • Before building a CRM or approval system, decompose the request into blueprint, menus, fields, permissions, and acceptance checks.
  • For a new Dimens project, decide whether to use CLI resource operations or SDK custom pages and route to the correct skill path.
  • When designing approval or support flows, add a business canvas for roles, stages, data flow, and exceptions instead of only tables.
  • Before creating reports, verify sample data, field mapping, and filters to avoid empty report shells.

Best For

  • Operations leads turning a one-line business need into a complete Dimens system blueprint.
  • Product or tech leads deciding between CLI table setup and SDK custom pages.
  • Solution consultants adding approval, support, or CRM flows with business canvas coverage.
  • Team owners standardizing requirements docs, menus, permissions, and acceptance before project creation.