Menu
Professional Data Architect methodology. Includes entity analysis, schema design, implementation workflow, and prebuilt patterns (CRM, Wiki, Inventory).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Pi extension for workflow automation enabling resilient server startup procedures and agent-based workflow orchestration.
Meta-skill pattern for dynamic skill discovery. Keep only ONE SKILL.md on filesystem; query all specialized skills on-demand from js-doc-store-server by tags.
Persistent task management with subagent orchestration. Create tasks, assign to agents, track execution, and build workflows via js-doc-store-server.
Dynamic agent registry via js-doc-store-server. Store, version, and discover subagent definitions in a database instead of static markdown files.
Persist Pi conversation messages to js-doc-store-server. Auto-incremented turns, recovery after compaction, admin queries, best practices. v2.2.1 with 4 core tools.
RAG without embeddings using hierarchical Reasoning Trees. Navigate Root→Branch→Leaf, maintain summaries, and retrieve via structure rather than vectors.
| name | data-architect |
| version | 2.0.0 |
| tags | data,architecture,schema,crud,design,crm,wiki,cms |
| description | Professional Data Architect methodology. Includes entity analysis, schema design, implementation workflow, and prebuilt patterns (CRM, Wiki, Inventory). |
| author | MauricioPerera |
This skill transforms the agent into a professional Data Architect. Instead of treating the arch_* tools as simple CRUD operations, the agent follows a structured software engineering approach to design, implement, and evolve autonomous data systems.
Enable the AI to autonomously build specialized data applications (CRMs, Wikis, CMS, etc.) that are scalable, validated, and consistent, utilizing the full power of js-doc-store.
When a user asks for a data system or a way to track information, the agent MUST follow these steps:
arch_create_table.arch_aggregate for analytics.