About

About me

I’m Lukáš Oplt. I build practical solutions at the intersection of Microsoft Power Platform and AI.

My work focuses on Power Apps, Power Automate, Dataverse, Copilot Studio, and AI-assisted development. I turn recurring problems into open-source tools, practical articles, and conference sessions.

Selected projects

  • Easel Static analysis and developer tooling for Power Apps canvas source.
  • AI Notebook A privacy-first, local-first research notebook for your own documents.

Find me online

I’m always interested in practical Power Platform and AI challenges, open-source collaboration, and lessons from real implementations.

Comments

Post a Comment

Popular posts from this blog

Let AI build the flow. Never outsource the blast radius

Image
Power Automate · FlowAgent MCP Let AI build the flow. Never outsource the blast radius. Microsoft’s Power Automate plugin can build, edit, run, and diagnose cloud flows from Claude Code or GitHub Copilot CLI. The useful question is no longer whether AI can do it. It is when we should let it. By Lukáš Oplt 12 min read Power Automate & AI 01 Describe the outcome 02 Inspect the context 03 Build and validate 04 Review before impact A natural-language request can now become a real Power Automate cloud flow. The agent can discover connectors, map dynamic values, validate the definition, create the flow, inspect failed runs, and even repair individual actions. That is a meaningful change in how automation can be built. It is also exactly where teams can make a dangerous category error: confusing the ability to generate a workflow with the authority to decide what that workflow s...
Read more

Power Apps Accessible Labels: AI Removed the Excuse

Image
Power Apps accessibility The repetitive part can now be generated by AI. Leaving hundreds of interactive controls unnamed is no longer a scheduling problem; it is a decision not to care. By Lukáš Oplt 7 min read Power Apps Three hundred and six. That is not an obscure edge case buried in a complex formula. It is the same basic accessibility omission repeated across an application: interactive controls that a screen reader cannot name properly. The Accessibility Checker found 306 missing accessible labels in a single canvas app. Teams often explain this away with familiar phrases: the deadline was tight, accessibility was scheduled for later, or there was no capacity for manual cleanup. Those arguments were already weak. With coding agents able to inspect a canvas app, infer control intent, write AccessibleLabel formulas, and validate the result, they have become indefensible. ...
Read more