acek-skills 1.0.0

package/skills/sf-admin/SKILL.md

@@ -0,0 +1,245 @@
+---
+name: sf-admin
+description: >
+  Use this skill for ANY Salesforce administration task that does not involve custom code.
+  Triggers when the user asks about creating or modifying custom objects, custom fields, picklist
+  values, page layouts, record types, profiles, permission sets, roles, sharing rules, validation
+  rules, workflow rules, flows (Screen Flow, Record-Triggered Flow, Schedule-Triggered Flow),
+  approval processes, reports, dashboards, email templates, app manager, or any declarative
+  Salesforce configuration. Also use when the user asks about org setup, security model, OWD
+  (Org-Wide Defaults), or data management tasks (import, export, data loader).
+---
+
+# Salesforce Administrator Skill
+
+## Environment Context
+- API Version: **61.0**
+- Org Type: Enterprise (single org: sandbox + production)
+- Tooling: **SF CLI** for metadata retrieval; most admin tasks done declaratively in Setup UI
+- Any metadata changes intended for production must go through the DevOps deployment process
+
+---
+
+## Naming Conventions
+
+| Artifact | Convention | Example |
+|---|---|---|
+| Custom Object | PascalCase, singular | `Project__c`, `WorkOrder__c` |
+| Custom Field | PascalCase__c | `ProjectStatus__c`, `DueDate__c` |
+| Custom Tab | Match object label | — |
+| Permission Set | Descriptive, Title Case | `Project Manager Access` |
+| Flow | Action + Object, Title Case | `Create Project Record`, `Update Opportunity Stage` |
+| Validation Rule | OBJECT_DescriptionOfRule | `ACCOUNT_RequireIndustry` |
+| Report/Dashboard | Descriptive, audience-first | `Sales Team — Pipeline by Stage Q3` |
+
+---
+
+## Custom Objects
+
+### Checklist when creating a Custom Object
+- [ ] **Label**: singular (e.g. `Project`), plural auto-generated
+- [ ] **API Name**: PascalCase + `__c` (e.g. `Project__c`)
+- [ ] **Record Name field**: meaningful (not just "Project Name" — be specific)
+- [ ] **Record Name type**: Text (most cases) or Auto Number if human-readable ID needed
+- [ ] **Sharing model (OWD)**: decide upfront — Public Read/Write, Public Read Only, or Private
+- [ ] **Allow Reports**: enable if business needs visibility
+- [ ] **Allow Activities**: enable if users need Tasks/Events on this object
+- [ ] **Track Field History**: enable for audit trail (select key fields)
+- [ ] **Allow in Chatter**: based on collaboration needs
+- [ ] Add to relevant **App** via App Manager after creation
+
+### Relationships
+| Type | Use When |
+|---|---|
+| Master-Detail | Child cannot exist without parent; sharing & rollup summary needed |
+| Lookup | Loose coupling; child can exist independently |
+| Many-to-Many | Use Junction Object with two Master-Detail fields |
+| Hierarchical | Self-referential (User only) |
+
+---
+
+## Custom Fields
+
+### Field Type Selection Guide
+| Data | Recommended Type |
+|---|---|
+| Short text (<255 chars) | Text |
+| Long text / notes | Long Text Area (set char limit intentionally) |
+| Controlled list of values | Picklist |
+| Currency amounts | Currency (respects org currency settings) |
+| Calculated value | Formula |
+| Running total from child | Roll-Up Summary (Master-Detail only) |
+| True/False | Checkbox |
+| Date only | Date |
+| Date + Time | Date/Time |
+| External system ID | Text, mark as External ID + Unique |
+| Reference to another record | Lookup or Master-Detail |
+
+### Field Creation Checklist
+- [ ] API Name: PascalCase__c — **no spaces, no special characters**
+- [ ] Help Text: always fill — explain purpose and expected format
+- [ ] Field-Level Security (FLS): set explicitly per profile/permission set after creation
+- [ ] Add to **Page Layout** after creation
+- [ ] Add to relevant **List View** if needed
+- [ ] Consider **Required** at field level vs. at Validation Rule level (VR gives better error messages)
+
+---
+
+## Security Model
+
+### Layers (top to bottom)
+1. **OWD** — baseline access for all users (most restrictive)
+2. **Role Hierarchy** — opens access up the hierarchy
+3. **Sharing Rules** — criteria-based or ownership-based exceptions to OWD
+4. **Manual Sharing** — record-by-record sharing
+5. **Profiles** — object/field/tab access + app access (legacy, prefer Permission Sets)
+6. **Permission Sets** — additive permissions on top of Profile
+7. **Permission Set Groups** — bundle multiple Permission Sets
+
+### Best Practice
+- Keep Profiles minimal (baseline access only)
+- Use **Permission Sets** for feature/role-based access
+- Group Permission Sets into **Permission Set Groups** for easy assignment
+- Never grant "Modify All" or "View All" without documented business justification
+
+### Permission Set Creation Checklist
+- [ ] Name: descriptive, audience-clear (`Project Manager Access`)
+- [ ] Object permissions: only what role needs (CRUD individually)
+- [ ] FLS: explicitly set for each relevant field
+- [ ] Assigned Apps: if needed
+- [ ] System Permissions: minimal — document any elevated permissions
+
+---
+
+## Flows
+
+### Flow Type Selection
+| Scenario | Flow Type |
+|---|---|
+| User-facing guided process | Screen Flow |
+| Trigger on record create/update/delete | Record-Triggered Flow |
+| Run on a schedule | Schedule-Triggered Flow |
+| Called from another flow or Apex | Autolaunched Flow (No Trigger) |
+| Triggered by platform event | Platform Event-Triggered Flow |
+
+### Flow Best Practices
+- **Bulkification**: avoid SOQL/DML elements inside loops — use Collection variables + Loop
+- **Error handling**: add Fault paths on every DML element; log or notify on failure
+- **Governor limits**: one Flow can do max 150 DML + 100 SOQL per transaction
+- Label all elements clearly — what it does, not just the element type
+- Use **Constants** for hardcoded values (labels, thresholds) — never hardcode in element properties
+- **Test before activating**: use Flow's built-in debug tool + write test coverage if invoked from Apex
+
+### Record-Triggered Flow — Run Order Awareness
+- Fast Field Updates run before triggers
+- Actions and Related Records run after triggers (same transaction)
+- Async paths run in new transaction — cannot roll back
+
+---
+
+## Validation Rules
+
+### Pattern
+```
+/* Rule Name: OBJECT_DescriptionOfRule */
+/* Error Message: user-friendly, actionable */
+
+/* Example: Require Close Date in future for new Opportunities */
+AND(
+    ISNEW(),
+    CloseDate <= TODAY()
+)
+/* Error: "Close Date must be in the future for new opportunities." */
+/* Error Location: CloseDate field */
+```
+
+- Always set **Error Location** to the specific field (not top of page) when possible
+- Error message: tell user **what to do**, not just what went wrong
+- Test with both positive (should save) and negative (should be blocked) scenarios
+
+---
+
+## Reports & Dashboards
+
+### Report Types to Know
+| Type | Use |
+|---|---|
+| Tabular | Simple lists, exports |
+| Summary | Grouped data with subtotals |
+| Matrix | Cross-tabulation (rows + columns grouping) |
+| Joined | Multiple report blocks in one |
+
+### Dashboard Checklist
+- [ ] Meaningful title that says what decision it helps make
+- [ ] Running User set appropriately (dynamic dashboards for self-service)
+- [ ] Refresh schedule configured
+- [ ] Filters exposed for end-user flexibility
+- [ ] Each component has a clear label — no "Count of Records" without context
+
+---
+
+## Data Management
+
+### Import Options
+| Tool | Best For |
+|---|---|
+| Data Import Wizard | Standard objects, <50K records, no relationships |
+| Data Loader | Any object, large volumes, automation, relationships |
+| `sf data import tree` | Dev/test JSON datasets |
+
+### SOQL via CLI (for admin queries)
+```bash
+# Query via SF CLI
+sf data query --query "SELECT Id, Name, CreatedDate FROM Account LIMIT 10" --target-org <alias>
+
+# Export to CSV
+sf data export bulk --query "SELECT Id, Name FROM Contact" --output-file contacts.csv --target-org <alias>
+```
+
+---
+
+## Metadata Retrieval for Admin Artifacts
+
+When an admin config needs to be deployed (e.g. to production via DevOps), retrieve it first:
+
+```bash
+# Retrieve specific metadata
+sf project retrieve start \
+  --metadata CustomObject:Project__c \
+  --metadata CustomField:Project__c.ProjectStatus__c \
+  --target-org <sandbox-alias>
+
+# Then hand off to DevOps skill for deployment
+```
+
+### Common Metadata Type Names
+| Artifact | Metadata Type |
+|---|---|
+| Custom Object | `CustomObject` |
+| Custom Field | `CustomField` |
+| Permission Set | `PermissionSet` |
+| Profile | `Profile` |
+| Flow | `Flow` |
+| Validation Rule | `ValidationRule` |
+| Page Layout | `Layout` |
+| Compact Layout | `CompactLayout` |
+| Custom Tab | `CustomTab` |
+| App | `CustomApplication` |
+
+---
+
+## Admin Task Quick Reference
+
+```bash
+# List all orgs
+sf org list
+
+# Open Setup in sandbox
+sf org open --target-org <sandbox-alias>
+
+# Retrieve Flow metadata
+sf project retrieve start --metadata Flow:Create_Project_Record --target-org <alias>
+
+# Retrieve full object (all fields, layouts, etc.)
+sf project retrieve start --metadata CustomObject:Project__c --target-org <alias>
+```

package/skills/sf-ba/SKILL.md

@@ -0,0 +1,297 @@
+---
+name: sf-ba
+description: >
+  Use this skill when creating Business Analysis documents for Salesforce projects: PRDs (Product
+  Requirements Documents), User Stories, Feature Specs, Functional Requirements, or any instruction
+  document intended to guide Salesforce admins or developers. Trigger when the user asks to
+  "write a PRD", "document requirements", "write user stories", "create a feature spec", "document
+  this feature", or "write instructions for the dev/admin team". Also use when the user describes
+  a business problem or process and wants it turned into structured documentation that others can
+  execute. Output is always Markdown.
+---
+
+# Salesforce Business Analyst Skill
+
+## Core Principle
+BA documents bridge the gap between business intent and technical execution. Every document must be:
+- **Actionable** — admin/dev can start work immediately after reading
+- **Unambiguous** — one possible interpretation only
+- **Testable** — every requirement can be verified with a concrete pass/fail test
+- **Scoped** — clearly states what is IN and OUT of scope
+
+Output format: **Markdown** (`.md`), stored in `instructions/` directory of the project repo.
+
+---
+
+## Document Types
+
+### 1. PRD (Product Requirements Document)
+Use for: new features, significant enhancements, cross-team work
+File path: `instructions/prd/YYYYMMDD-<feature-slug>.md`
+
+### 2. User Stories
+Use for: sprint-ready work items, Jira/GitHub issues
+Can be standalone or embedded in PRD
+File path: `instructions/stories/YYYYMMDD-<feature-slug>-stories.md`
+
+### 3. Admin Spec
+Use for: declarative-only changes (objects, fields, flows, permissions)
+File path: `instructions/admin/YYYYMMDD-<feature-slug>-admin-spec.md`
+
+### 4. Dev Spec
+Use for: custom code requirements (Apex, LWC, integrations)
+File path: `instructions/dev/YYYYMMDD-<feature-slug>-dev-spec.md`
+
+---
+
+## PRD Template
+
+```markdown
+# PRD: [Feature Name]
+
+**Date:** YYYY-MM-DD
+**Author:** [Name / Role]
+**Status:** Draft | Review | Approved
+**Target Release:** [Salesforce Season + Year, e.g. Summer '26]
+
+---
+
+## 1. Background & Problem Statement
+[1–3 sentences: what problem exists today, what pain it causes, and for whom.]
+
+## 2. Goals
+- [Goal 1 — measurable outcome]
+- [Goal 2]
+
+## 3. Non-Goals (Out of Scope)
+- [Explicitly list what this feature does NOT cover]
+- [This prevents scope creep]
+
+## 4. Users & Personas
+| Persona | Role | Primary Need |
+|---|---|---|
+| [Name] | [Job title / profile] | [What they need from this feature] |
+
+## 5. Functional Requirements
+
+### 5.1 [Sub-feature or Process Name]
+**As a** [persona], **I want to** [action], **so that** [benefit].
+
+| # | Requirement | Priority | Implementor |
+|---|---|---|---|
+| FR-01 | [Specific, measurable requirement] | Must Have | Admin / Dev |
+| FR-02 | ... | Should Have | Admin |
+
+**Priority scale:** Must Have (launch blocker) / Should Have (important) / Nice to Have (if time allows)
+
+### 5.2 [Next sub-feature]
+...
+
+## 6. Non-Functional Requirements
+- **Performance:** [e.g. Page must load within 2 seconds for up to 500 records]
+- **Security:** [e.g. Only users with Project Manager Permission Set may edit]
+- **Data integrity:** [e.g. Record cannot be deleted if child records exist]
+
+## 7. Data Model Changes
+| Object | Field / Change | Type | Notes |
+|---|---|---|---|
+| `Project__c` | `ProjectStatus__c` | Picklist | Values: Draft, Active, Closed |
+
+## 8. UI/UX Notes
+[Describe screen layouts, user flows, or link to wireframes/mockups if available.]
+
+## 9. Integration Points
+[Any external systems, APIs, or Salesforce features (e.g. email, DocuSign) involved.]
+
+## 10. Acceptance Criteria
+| # | Scenario | Given | When | Then |
+|---|---|---|---|---|
+| AC-01 | [Happy path] | [Starting state] | [User action] | [Expected result] |
+| AC-02 | [Edge case] | ... | ... | ... |
+
+## 11. Open Questions
+| # | Question | Owner | Due |
+|---|---|---|---|
+| Q-01 | [Unresolved decision] | [Name] | YYYY-MM-DD |
+
+## 12. Revision History
+| Date | Author | Change |
+|---|---|---|
+| YYYY-MM-DD | [Name] | Initial draft |
+```
+
+---
+
+## User Story Template
+
+### Format (standard)
+```markdown
+## Story: [Short Title]
+
+**Story ID:** US-[number]
+**Epic:** [Epic name]
+**Priority:** High / Medium / Low
+**Estimate:** [Story points or t-shirt size]
+**Assignee:** Admin / Dev
+
+---
+
+**As a** [persona],
+**I want to** [specific action or capability],
+**So that** [business value or outcome].
+
+### Acceptance Criteria
+- [ ] **Given** [initial context], **When** [user action], **Then** [expected result]
+- [ ] **Given** ..., **When** ..., **Then** ...
+- [ ] Error state: [what happens when X goes wrong]
+
+### Technical Notes
+[Any constraints, API callout involved, metadata affected — for dev/admin reference]
+
+### Out of Scope
+- [What this story does NOT cover]
+```
+
+### Story Writing Rules
+- One user story = one deliverable unit of value
+- Acceptance Criteria: **minimum 3** (happy path, edge case, error/permission case)
+- Avoid technical jargon in the story itself — put it in Technical Notes
+- Stories must be independently testable
+- No story should take more than 3 days to implement — if it does, split it
+
+---
+
+## Admin Spec Template
+
+```markdown
+# Admin Spec: [Feature Name]
+
+**Date:** YYYY-MM-DD  
+**PRD Reference:** [link to PRD]  
+**Status:** Draft | Ready for Build | Done
+
+---
+
+## Objects to Create / Modify
+### New Object: `ObjectName__c`
+- Label: [singular / plural]
+- Sharing: [OWD setting]
+- Features: [Activities / Reports / History Tracking / etc.]
+
+### Modified Object: `ExistingObject__c`
+- [What changes and why]
+
+## Fields
+| Object | Field API Name | Type | Values / Formula | Required | FLS |
+|---|---|---|---|---|---|
+| `Project__c` | `ProjectStatus__c` | Picklist | Draft; Active; Closed | Yes | Read: All, Edit: Manager |
+
+## Flows
+| Flow Name | Type | Trigger | Purpose |
+|---|---|---|---|
+| `Create_Project_Record` | Screen Flow | User-initiated | Guide user through project creation |
+
+### Flow: [Flow Name] — Step-by-Step Logic
+1. [Step 1]
+2. [Step 2 — decision: if X then Y, else Z]
+3. [Step 3]
+
+## Permission Changes
+| Permission Set | Object | CRUD | Fields |
+|---|---|---|---|
+| `Project Manager Access` | `Project__c` | CRUD | All fields: Read/Edit |
+
+## Validation Rules
+| Object | Rule Name | Condition (plain English) | Error Message |
+|---|---|---|---|
+| `Project__c` | `PROJ_RequireOwner` | Owner is blank on save | "Please assign an owner before saving." |
+
+## Page Layouts
+- Add `ProjectStatus__c` to `Project Layout` — Section: Details, Position: top right
+```
+
+---
+
+## Dev Spec Template
+
+```markdown
+# Dev Spec: [Feature Name]
+
+**Date:** YYYY-MM-DD  
+**PRD Reference:** [link to PRD]  
+**Status:** Draft | Ready for Build | Done
+
+---
+
+## Overview
+[1 paragraph: what needs to be built and why, from a technical angle]
+
+## Components to Build / Modify
+| Component | Type | Action | Notes |
+|---|---|---|---|
+| `ProjectHelper` | Apex Class | Create | Business logic for project operations |
+| `projectCard` | LWC | Create | Display project summary on record page |
+| `ProjectTrigger` | Apex Trigger | Create | Entry point — delegates to handler |
+
+## Apex: [ClassName]
+### Purpose
+[What this class does]
+
+### Methods
+| Method | Visibility | Params | Returns | Description |
+|---|---|---|---|---|
+| `getProjects` | `@AuraEnabled public static` | `Id accountId` | `List<Project__c>` | Returns active projects for an account |
+
+### Key Logic
+1. [Step 1]
+2. [Step 2]
+3. [Error handling: ...]
+
+### SOQL Involved
+```apex
+SELECT Id, Name, ProjectStatus__c, OwnerId
+FROM Project__c
+WHERE AccountId = :accountId AND ProjectStatus__c != 'Closed'
+```
+
+## LWC: [componentName]
+### Purpose
+[What the component displays / does]
+
+### @api Properties
+| Property | Type | Description |
+|---|---|---|
+| `recordId` | String | The parent Account ID |
+
+### Events Fired
+| Event Name | When | Payload |
+|---|---|---|
+| `projectselected` | User clicks a project card | `{ detail: { projectId } }` |
+
+### Wire / Apex Calls
+- `@wire(getProjects, { accountId: '$recordId' })` → renders project list
+
+## Integration / Callout (if applicable)
+- Endpoint: `callout:Named_Credential/resource`
+- Method: GET/POST
+- Payload: [structure]
+- Error handling: [how failures are surfaced]
+
+## Test Coverage Plan
+| Test Class | Scenarios to Cover |
+|---|---|
+| `ProjectHelperTest` | Happy path, no records, insufficient permission |
+```
+
+---
+
+## BA Workflow
+
+When asked to write BA documentation:
+
+1. **Clarify scope** — confirm what's in/out before writing
+2. **Choose document type** — PRD for new features, Story for sprint items, Spec for execution
+3. **Fill all sections** — never leave a section blank; write "N/A — [reason]" if not applicable
+4. **Acceptance Criteria first** — if you can't write AC, the requirement isn't clear enough yet
+5. **Flag open questions** — better to surface uncertainty than assume
+6. **Always specify the implementor** — Admin, Dev, or Both for each requirement