Skip to content

Latest commit

 

History

History
146 lines (111 loc) · 6.78 KB

CLAUDE.md

File metadata and controls

146 lines (111 loc) · 6.78 KB

CLAUDE.md

Table of Contents

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

📁 Workspace Context: This repo is part of a multi-repo VS Code workspace. See ../CLAUDE.md for workspace-level guidance.

Repository Overview

This is a Power Fx snippets repository containing reusable code patterns, formulas, and components for Microsoft Power Platform development. The repository serves as a comprehensive collection of Power Apps development resources.

🔀 Dual Repository Structure

This repository is part of a two-repo system:

  1. PowerFxSnippets/ (THIS REPO - Public)

    • Published to: GitHub as public repository
    • Contains: Generic, shareable Power Fx patterns and components
    • Use for: Community-facing snippets, general best practices, reusable code
    • No client-specific or proprietary content

  2. PowerFxSnippets-Private/ (Sibling Repo - Private)

    • Location: ../PowerFxSnippets-Private/
    • Contains: Client-specific implementations, proprietary patterns, internal tools
    • Use for: NDA-protected work, client projects, private configurations
    • Has .specify/ folder with spec-kit for project specifications

When working across both repos:

  • Generic/reusable patterns → Public repo (PowerFxSnippets)
  • Client-specific implementations → Private repo (PowerFxSnippets-Private)
  • Check both repos when searching for existing patterns
  • Reference public snippets from private implementations where possible

Editing Markdown Files

When adding or updating any .md file in this repository:

  1. Update the History section at the bottom of the file (create one if it doesn't exist)
  2. Use this format: 
    ## History

| Date       | Author      | Changes                          |
|------------|-------------|----------------------------------|
| YYYY-MM-DD | Author Name | Brief description of changes     |
  3. Add new entries at the top of the table (most recent first)

Repository Structure

PowerFxSnippets/
├── app-lifecycle/       # App initialization, lifecycle, formulas, error handling
├── ui-controls/         # Control-specific snippets (gallery, buttons, inputs)
├── ui-patterns/         # Reusable UI patterns (theming, dialogs, components)
├── visual-assets/       # SVGs, icons, colors, fonts, emojis, unicode
├── data-operations/     # Data sources, samples, JSON, geocoding
├── functions/           # UDFs, algorithms, string manipulation, encoding
├── integrations/        # Connectors, Office 365, Power Automate
├── learning/            # Tutorials, certification, best practices
├── utilities/           # Validation tools, templates, scripts, project docs
└── .github/             # Actions workflows, issue/PR templates

Key File Types

  • .md files: Documentation and code snippets in markdown format
  • .yaml files: Power Fx formula definitions and configurations
  • .msapp files: Power Apps application packages
  • .csv files: Sample data sets
  • .svg files: Scalable vector graphics for UI elements
  • .json files: Configuration and schema definitions

Working with Power Fx Code

⚠️ MANDATORY: Check Gotchas Before Writing Code!

Before giving advice OR writing ANY Power Fx code (especially date formatting, function behavior, etc.):

  • ALWAYS read learning/reference/power-fx-gotchas.md FIRST
  • Power Fx is NOT the same as .NET, Excel, or JavaScript — don't assume!
  • This applies to: code snippets, examples, fixes, refactors — ALL Power Fx output

🔍 Power Fx Verification Workflow

When uncertain about ANY Power Fx syntax or function behavior:

  1. Check local gotchas first: Read learning/reference/power-fx-gotchas.md
  2. Verify with official docs: Use ref_search_documentation with query like "Power Fx [function name]"
  3. Read the result: Use ref_read_url on the returned URL
  4. Official docs base: https://learn.microsoft.com/en-us/power-platform/power-fx/overview

Never guess confidently about Power Fx syntax — verify first!

Formula Patterns

  • Power Fx formulas are typically stored in .yaml files or documented in .md files
  • Named formulas use the prefix fx (e.g., fxMenuItems.yaml)
  • User-defined types and schemas follow specific syntax patterns documented in the repository

Common Tasks

  1. Adding New Snippets: Create markdown files in the appropriate category folder with clear examples
  2. Documenting Components: Include both the Power Fx code and usage instructions
  3. Sample Data: Place CSV files in data-operations/samples/ with descriptive names
  4. SVG Resources: Store in visual-assets/svgs/ organized by provider (Azure, Fabric, Power BI)
  5. Error Handling: Place patterns in app-lifecycle/error-handling/
  6. Tools/Scripts: Place in utilities/tools/ (Python) or utilities/tools/node/ (Node.js)

Documentation Standards

  • Use clear, descriptive file names
  • Include code examples with proper Power Fx syntax highlighting
  • Document any dependencies or prerequisites
  • Add images/screenshots where helpful for visual components

AI Session Documentation

Document AI-assisted work sessions in ai-chats/ using the format: YYYY-MM-DD-XX-description.md

Related Resources

History

Date Author Changes
2026-02-18 Cleanup Remove Reference/ and docs/ from structure; update all paths
2026-02-17 Cleanup Updated directory structure and paths to match v2.0 layout
2026-01-08 Claude Added workspace context reference to parent CLAUDE.md