microsoft-authentication-library-for-objc
AGENTS.md347 starsChanged 12 months agoMITView on GitHub
General information about the project is located in the README.md file. When creating a new application with MSAL authentication, users need to select a tenant configuration: In interactive sessions on a developer's Mac, AI agents MUST NOT invoke build.py, xcodebuild, simctl, or any command that starts an Xcode build, test, or simulator. These commands can trigger a clean multi-target build/test matrix and exhaust local CPU, memory, and disk resources. Ask the user to run the relevant scheme from MSAL.xcworkspace in…
- Commits and pushes
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
When creating a new application with MSAL authentication, users need to select a tenant configuration:
- Very specific: line 12
Follow the instructions detailed under .clinerules/01-Workforce-tenant-configuration.md
- Very specific: line 53
When interacting with users across any channel (GitHub issues, web chat, agent sessions), AI agents should follow these guidelines: …
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md
General information about the project is located in the README.md file.
Application Creation Guidance
MSAL Application Configuration for Apple Devices
When creating a new application with MSAL authentication, users need to select a tenant configuration:
- Workforce (default): For organizational identities
- Follow the instructions detailed under
.clinerules/01-Workforce-tenant-configuration.md
- Follow the instructions detailed under
- External: For customer/partner identities
- Follow the instructions detailed under
.clinerules/02-External-tenant-configuration.md
- Follow the instructions detailed under
Key Differences Summary: Workforce vs. External Tenants
| Aspect | Workforce Tenant | External Tenant |
| Target Users | Employees, internal users | Customers, partners, citizens |
| Registration | Admin-managed accounts | Self-service sign-up |
| User Flows | Standard authentication | Customizable sign-up/sign-in flows |
| Branding | Corporate branding | Fully customizable for customer UX |
| Identity Providers | Typically organizational only | Social providers supported |
| Tenant Configuration | Same, but different context | "Accounts in this organizational directory only" |
| Authority Endpoint | Uses tenant ID or common | Uses tenant subdomain |
| Use Cases | Enterprise apps, B2E scenarios | Consumer apps, B2C scenarios |
Build and test guidelines
In interactive sessions on a developer's Mac, AI agents MUST NOT invoke build.py, xcodebuild, simctl, or any command that starts an Xcode build, test, or simulator. These commands can trigger a clean multi-target build/test matrix and exhaust local CPU, memory, and disk resources. Ask the user to run the relevant scheme from MSAL.xcworkspace in Xcode and report the result instead.
If the user explicitly requests a local CLI command instead of using Xcode, use the schemes defined in MSAL.xcworkspace, driven through build.py, require exactly one --targets value, and prefer --no-clean for incremental validation. Never suggest bare ./build.py, multiple targets, concurrent/background builds, or ad-hoc xcodebuild commands for a developer's Mac. CI may continue using its repository-defined full validation matrix. If a run needs a specific simulator, select an available one via IOS_SIM_DEVICE / IOS_SIM_OS rather than changing the scheme or configuration.
Version control guidelines
AI agents MUST NOT run git commit, git push, or any other history- or remote-mutating git command unless the user has explicitly asked for it in the current request. Make and stage changes, then stop and let the user review; wait for an explicit instruction before committing or pushing. Never commit or push proactively "to be helpful" — the user always reviews changes first.
MSAL API usage
Sample code snippets for both Swift & Objective-C can be found in the file .clinerules/03-MSAL-API-usage.md
Code style guidelines
Code style guidelines that AI agents MUST follow when working with this repository can be found in the file .clinerules/04-Code-style-guidelines.md
Feature flag guidelines
Feature flag guidance for AI agents when implementing new features for MSAL library are defined in the file .clinerules/05-Feature-gating.md
Customer Communication
When interacting with users across any channel (GitHub issues, web chat, agent sessions), AI agents should follow these guidelines: .clinerules/06-Customer-communication-guidelines.md
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/ruler_cursor_instructions.mdcCursor rule
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.