forcedotcom/sf-skills / skills/external-diagram-mermaid-generate
external-diagram-mermaid-generate
UnverifiedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user asks about non-Salesforce systems.
assets/oauth/authorization-code-pkce.md
View on GitHub# Authorization Code + PKCE Flow Template
OAuth 2.0 Authorization Code flow with Proof Key for Code Exchange (PKCE) for public clients.
## When to Use
- Single Page Applications (SPAs)
- Mobile native applications
- Desktop applications
- Any client that cannot securely store a client_secret
## Mermaid Template
```mermaid
%%{init: {'theme': 'base', 'themeVariables': {
'actorBkg': '#ddd6fe',
'actorTextColor': '#1f2937',
'actorBorder': '#6d28d9',
'signalColor': '#334155',
'signalTextColor': '#1f2937',
'noteBkgColor': '#f8fafc',
'noteTextColor': '#1f2937',
'noteBorderColor': '#334155'
}}}%%
sequenceDiagram
autonumber
box rgba(165,243,252,0.3) USER DEVICE
participant U as š¤ User
participant App as š± Mobile App<br/>or SPA
end
box rgba(167,243,208,0.3) SALESFORCE
participant SF as āļø Salesforce<br/>Authorization Server
end
Note over U,SF: Authorization Code + PKCE Flow (RFC 7636)
U->>App: 1. Tap "Login with Salesforce"
App->>App: 2. Generate PKCE Parameters
Note over App: code_verifier = random(128 bytes)<br/>code_challenge = BASE64URL(SHA256(code_verifier))
App->>App: 3. Generate state (CSRF protection)
App->>SF: 4. Open browser/webview to /authorize
Note over App,SF: response_type=code<br/>client_id=CONSUMER_KEY<br/>redirect_uri=CALLBACK_URL<br/>scope=api refresh_token<br/>state=RANDOM_STATE<br/>code_challenge=CODE_CHALLENGE<br/>code_challenge_method=S256
SF->>U: 5. Display Login Page
U->>SF: 6. Enter Username & Password
SF->>SF: 7. Authenticate User
SF->>U: 8. Display Consent Screen
Note over SF,U: "App requests access to:<br/>⢠API Access<br/>⢠Refresh Token"
U->>SF: 9. Grant Consent (Allow)
SF->>SF: 10. Generate Authorization Code
Note over SF: Store code_challenge with code
SF->>App: 11. Redirect to callback with code
Note over SF,App: scheme://callback?code=AUTH_CODE<br/>&state=RANDOM_STATE
App->>App: 12. Verify state matches
App->>SF: 13. POST /services/oauth2/token
Note over App,SF: grant_type=authorization_code<br/>code=AUTH_CODE<br/>client_id=CONSUMER_KEY<br/>redirect_uri=CALLBACK_URL<br/>code_verifier=CODE_VERIFIER
SF->>SF: 14. Validate Code & PKCE
Note over SF: Verify: BASE64URL(SHA256(code_verifier))<br/>== stored code_challenge
SF->>App: 15. Return Tokens
Note over SF,App: {<br/> access_token: "...",<br/> refresh_token: "...",<br/> instance_url: "https://...",<br/> token_type: "Bearer"<br/>}
App->>App: 16. Store tokens securely
Note over App: Use Keychain (iOS)<br/>or Keystore (Android)
App->>U: 17. ā
Successfully Logged In
```
## ASCII Fallback Template
```text
āāāāāāāāāāāā āāāāāāāāāāāāāāāāā āāāāāāāāāāāāāāāāāāāāāā
ā User ā ā Mobile App ā ā Salesforce ā
ā ā ā or SPA ā ā (Auth Server) ā
āāāāāā¬āāāāāā āāāāāāāāā¬āāāāāāāā āāāāāāāāāāā¬āāāāāāāāāāā
ā ā ā
ā 1. Tap Login ā ā
āāāāāāāāāāāāāāāāāāā>ā ā
ā ā ā
ā ā 2. Generate PKCE: ā
ā ā code_verifier ā
ā ā code_challenge ā
ā ā ā
ā 3. Open Browser/WebView to /authorize ā
ā<āāāāāāāāāāāāāāāāāāā ā
ā ā ā
ā 4. GET /authorize ā
ā (client_id, code_challenge, state) ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā>ā
ā ā ā
ā 5. Login Page ā
ā<āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā ā ā
ā 6. Enter Credentials ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā>ā
ā ā ā
ā 7. Consent Screen ā
ā<āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā ā ā
ā 8. Grant Consent ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā>ā
ā ā ā
ā 9. Redirect with ?code=ABC123 ā
ā<āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā ā ā
ā 10. Deliver Code ā ā
āāāāāāāāāāāāāāāāāāā>ā ā
ā ā ā
ā ā 11. POST /token ā
ā ā (code_verifier) ā
ā āāāāāāāāāāāāāāāāāāāāāāā>ā
ā ā ā
ā ā 12. Verify PKCE: ā
ā ā SHA256(verifier) ā
ā ā == challenge ā
ā ā ā
ā ā 13. Access Token + ā
ā ā Refresh Token ā
ā ā<āāāāāāāāāāāāāāāāāāāāāāā
ā ā ā
ā 14. Logged In ā
ā ā
ā<āāāāāāāāāāāāāāāāāāā ā
```
## PKCE Parameter Generation
### JavaScript/TypeScript
```javascript
// Generate code_verifier (43-128 characters)
const codeVerifier = base64URLEncode(crypto.getRandomValues(new Uint8Array(32)));
// Generate code_challenge
const encoder = new TextEncoder();
const data = encoder.encode(codeVerifier);
const digest = await crypto.subtle.digest('SHA-256', data);
const codeChallenge = base64URLEncode(new Uint8Array(digest));
function base64URLEncode(buffer) {
return btoa(String.fromCharCode(...buffer))
.replace(/\+/g, '-')
.replace(/\//g, '_')
.replace(/=+$/, '');
}
```
### Python
```python
import hashlib
import base64
import secrets
# Generate code_verifier
code_verifier = base64.urlsafe_b64encode(secrets.token_bytes(32)).rstrip(b'=').decode()
# Generate code_challenge
code_challenge = base64.urlsafe_b64encode(
hashlib.sha256(code_verifier.encode()).digest()
).rstrip(b'=').decode()
```
## Key Differences from Standard Auth Code
| Aspect | Standard | PKCE |
|--------|----------|------|
| Client Secret | Required | Not required |
| code_challenge | Not used | Required in /authorize |
| code_verifier | Not used | Required in /token |
| Security | Secret-based | Cryptographic proof |
| Client Type | Confidential | Public |
## Security Considerations
1. **Generate new PKCE values** for each authorization request
2. **Use S256 method** (SHA-256), never "plain"
3. **Store code_verifier securely** until token exchange
4. **Use secure storage** for tokens (Keychain/Keystore)
5. **Implement refresh token rotation** for additional security
## Customization Points
Replace these placeholders:
- `CONSUMER_KEY` ā Your Connected App's Consumer Key
- `CALLBACK_URL` ā Your registered callback URL (custom scheme for mobile)
- `CODE_VERIFIER` ā Generated 43-128 character random string
- `CODE_CHALLENGE` ā BASE64URL(SHA256(CODE_VERIFIER))
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why ā repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" ā or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself ā your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |