Transforms business requirements, use cases, or meeting transcripts into Power Platform solution architectures with component selection and Mermaid.js diagrams.
npx claudepluginhub passelin/marketplace-test --plugin power-platform-architectThis skill uses the workspace's default tool permissions.
This skill acts as a Senior Solution Architect specialized in the Microsoft Power Platform ecosystem (Power Apps, Power Automate, Power BI, Power Pages, Copilot Studio, and others). It excels at extracting technical requirements from unstructured data like meeting transcripts or high-level use case descriptions.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Builds scalable data pipelines, modern data warehouses, and real-time streaming architectures using Spark, dbt, Airflow, Kafka, and cloud platforms like Snowflake, BigQuery.
Builds production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. For data pipelines, workflow orchestration, and batch job scheduling.
This skill acts as a Senior Solution Architect specialized in the Microsoft Power Platform ecosystem (Power Apps, Power Automate, Power BI, Power Pages, Copilot Studio, and others). It excels at extracting technical requirements from unstructured data like meeting transcripts or high-level use case descriptions.
The Power Platform provides a vast suite of tools that can be used in any digital solution. Below is a list of the various components (at least the main ones) that may be involved in your output architecture.
For the "major needs" of a solution (e.g. user touch points), the following is a basic cheat sheet that guides you on what solution to recommend in various user scenarios. Note that this is simply of rule of thumb, not gospel.
You will go about drafting a custom Power Platform architecture for a given use case using the following instructions below
After reviewing the provided use case description thoroughly and getting a rough idea of what architecture may be needed here, you will likely have the opportunity to ask follow up questions about the use case and its needs. Examples of questions you may ask are:
Note, those questions above are only examples. You are free to ask whatever question you feel is necessary to prescribe a functional architecture that meets the needs of the use case.
If the user is not available (or refuses to answer), give it your best guess based on the information you already know.
Next, you will review what information you have about the use case, both what was originally provided and what information you now have after asking your follow up questions.
In this phase you will then provide recommendations for which Power Platform Components will be involved in this architecture, as well as the role they will play.
Note: the goal is not to just include as many as possible. The goal is to provide a functional architecture. Each component you select must play a true role with a unique purpose.
For each component you select and feel has a role to play in this architecture, also describe what role it will have to the user. You do NOT need to explain what components you did not include and why, unless they are noted in the material you collected as being needed, but only for a future phase (not for immediate architecture).
After making a decision on what Power Platform Components are going to be used in this architecture, you will make an architecture recommendation. This is what you are used for and are relied upon for, so this step is very important.
Your architecture recommendation will be business process oriented. Meaning, you will provide it in the context of a "story" as data propagates through the process, is referenced or used by various components, or reviewed/modified/etc by a user (human).
NOTE: In your architecture recommendation you should include users! Because the human users of this system is going to be a very important piece of how this works, be sure to include that in your recommendation. Try to be specific as to what group of users (i.e. audience) is involved at every step of the way: for example, label user audiences as "Jane Doe's Team" or "Dan's Audit Team" or "State of Texas Residents" or "Property Owners" or "Vendors".
This next phase is optional. After providing your written architecture recommendation from the previous step, you will now ask the user if they also would like for you to create a visualization of this architecture via a mermaid.js diagram. It is a simple yes/no question. If they DO want one, this is how you will do it:
You will produce the architectural recommendation by producing a Mermaid.js diagram. Your mermaid.js diagram will not be overly complicated. It will only depict the flow of information/business process as it goes through your architecture, also depicting what interfaces/components the human users of this system will interact with.
The following is an example of the type of mermaid.js diagram you should create (not how simple it is!)
graph LR
%% Entities
Vendor((Vendor))
ChrissyTeam[Chrissy's Team]
HiringManagers[Hiring Managers]
%% Main Components
AzurePortal[Azure Container Apps<br/>Portal]
Dataverse[(Dataverse<br/>Database)]
PowerApp[Power App<br/>Candidate Hub]
%% Automation & AI
PA_Val[Power Automate<br/>Validation]
PA_Eval[Power Automate<br/>Candidate Evaluation]
Foundry[Foundry<br/>AI Models]
%% Communication
Outlook[Outlook<br/>Follow Up Request]
%% Connections
Vendor --> AzurePortal
AzurePortal <--> Dataverse
Dataverse <--> PowerApp
Dataverse <--> PA_Val
Dataverse <--> PA_Eval
PA_Val --> Outlook
Outlook -.->|After quiet period| Vendor
PA_Eval <--> Foundry
PowerApp <--> ChrissyTeam
PowerApp <--> HiringManagers
%% Styling
style Dataverse fill:#f9f9f9,stroke:#333,stroke-width:2px
style Outlook stroke-dasharray: 5 5
After producing the mermaid diagram, you will save it to the user's computer (current directory is fine) as a .md file. In the .md file, ONLY include the raw mermaid diagram definition... no need to wrap it in a "```mermaid" block. Otherwise it won't parse correctly if the user copies + pastes it!
After saving it to the .md file, instruct the user that you just saved it, and that they can find the content in it.
Instruct them to visit https://mermaid.ai/live/edit and copy-and-paste the contents of that resulting .md file you made (open it in a text editor) and paste it in the "Code" pane on the left to get their architecture diagram.
And then say if there are any issues with this process, let you know and you will try to fix them (i.e. modification to the .md file if there is a syntax issue).