acek-skills 1.0.0

package/skills/sf-devops/SKILL.md

@@ -0,0 +1,372 @@
+---
+name: sf-devops
+description: >
+  Use this skill for Salesforce DevOps tasks: code review, generating deployment manifests
+  (package.xml), running dry-run validations, deploying from sandbox to production, writing
+  Change Requests (CR), managing Git workflow, and creating deploy documentation. Trigger when
+  the user mentions deployment, deploy to production, package.xml, manifest, code review, PR review,
+  dry-run, quick deploy, Change Request, deploy doc, git push, or anything related to the
+  sandbox-to-production pipeline. Also use for SF CLI deployment commands and GitHub workflow
+  steps. Target org alias for production: {{PROD_ORG_ALIAS}}.
+---
+
+# Salesforce DevOps Skill
+
+## Environment Context
+- API Version: **61.0**
+- Branching: `main → staging → develop → feature/*`
+- Production org alias: **`{{PROD_ORG_ALIAS}}`**
+- Sandbox/dev org alias: **`{{DEV_ORG_ALIAS}}`**
+- Tooling: **SF CLI** (`sf` commands)
+- CI/CD: GitHub (static analysis: PMD + ESLint before every PR)
+- Org type: Single org (1 sandbox + 1 production)
+
+---
+
+## Deployment Workflow — Standard Order
+
+```
+1. Code Review
+2. Generate scoped manifest (package-deploy-<feature>.xml)
+3. Dry-run validation
+4. Create Change Request (CR)
+5. Actual deploy
+6. Push to GitHub + update CR with Deploy ID
+```
+
+Never skip steps. Never deploy to `{{PROD_ORG_ALIAS}}` without a CR.
+
+---
+
+## Code Review
+
+### Apex Review Checklist
+- [ ] No SOQL inside loops (governor limit violation)
+- [ ] No DML inside loops
+- [ ] Test coverage ≥ 85% (check with: `sf apex run test ...`)
+- [ ] All public methods have ApexDoc (`@description`, `@param`, `@return`)
+- [ ] No hardcoded IDs, org-specific values, or credentials
+- [ ] `with sharing` declared on all classes
+- [ ] CRUD check uses `Schema.getGlobalDescribe()` (not compile-time SObject reference)
+- [ ] All `@AuraEnabled` methods wrapped in try-catch → `AuraHandledException`
+- [ ] Helper methods throw `CalloutException` (not `AuraHandledException`)
+
+### LWC Review Checklist
+- [ ] Component folder: camelCase (not PascalCase)
+- [ ] No `@wire` adapter inside a loop
+- [ ] All public `@api` properties have JSDoc
+- [ ] CSS includes `:host` brand token block (see Developer skill)
+- [ ] CSS uses `var(--brand)`, `var(--r-*)`, `var(--t)` — no hardcoded hex colors
+- [ ] Version badge present in HTML + CSS
+
+### Git / General Checklist
+- [ ] No `Co-Authored-By` trailers in commit messages
+- [ ] No Salesforce Deploy IDs, Record IDs, API keys, or session tokens in commits
+- [ ] Commit message: lowercase type prefix + imperative sentence (`feat:`, `fix:`, `refactor:`, `docs:`, `chore:`)
+- [ ] No unnecessary `package.xml` changes — use scoped manifest only
+
+---
+
+## Manifest Generation
+
+### Rule: Always use scoped manifests
+- **Never** deploy with `manifest/package.xml` (global) unless explicitly instructed
+- Create a new file: `manifest/package-deploy-<feature>.xml` for each deployment
+- Include only components relevant to the feature being deployed
+
+### package.xml Template
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<Package xmlns="http://soap.sforce.com/2006/04/metadata">
+
+    <!-- Apex Classes -->
+    <types>
+        <members>MyApexClass</members>
+        <members>MyApexClassTest</members>
+        <name>ApexClass</name>
+    </types>
+
+    <!-- Apex Triggers -->
+    <types>
+        <members>MyTrigger</members>
+        <name>ApexTrigger</name>
+    </types>
+
+    <!-- LWC -->
+    <types>
+        <members>myComponent</members>
+        <name>LightningComponentBundle</name>
+    </types>
+
+    <!-- Custom Objects -->
+    <types>
+        <members>Project__c</members>
+        <name>CustomObject</name>
+    </types>
+
+    <!-- Custom Fields -->
+    <types>
+        <members>Project__c.ProjectStatus__c</members>
+        <name>CustomField</name>
+    </types>
+
+    <!-- Flows -->
+    <types>
+        <members>Create_Project_Record</members>
+        <name>Flow</name>
+    </types>
+
+    <!-- Permission Sets -->
+    <types>
+        <members>Project_Manager_Access</members>
+        <name>PermissionSet</name>
+    </types>
+
+    <version>61.0</version>
+</Package>
+```
+
+### Common Metadata Type Names (quick reference)
+| Artifact | Metadata Type Name |
+|---|---|
+| Apex Class | `ApexClass` |
+| Apex Trigger | `ApexTrigger` |
+| LWC | `LightningComponentBundle` |
+| Aura Component | `AuraDefinitionBundle` |
+| Custom Object | `CustomObject` |
+| Custom Field | `CustomField` |
+| Permission Set | `PermissionSet` |
+| Profile | `Profile` |
+| Flow | `Flow` |
+| Validation Rule | `ValidationRule` |
+| Page Layout | `Layout` |
+| Custom Tab | `CustomTab` |
+| Custom App | `CustomApplication` |
+| Static Resource | `StaticResource` |
+| Named Credential | `NamedCredential` |
+
+---
+
+## Deployment Commands
+
+### Dry-Run (always first)
+```bash
+sf project deploy start \
+  --dry-run \
+  --manifest manifest/package-deploy-<feature>.xml \
+  --test-level RunSpecifiedTests \
+  --tests MyApexClassTest \
+  --target-org {{PROD_ORG_ALIAS}}
+```
+
+- Review dry-run output carefully before proceeding
+- If test failures: fix before actual deploy — never bypass
+
+### Actual Deploy
+```bash
+sf project deploy start \
+  --manifest manifest/package-deploy-<feature>.xml \
+  --test-level RunSpecifiedTests \
+  --tests MyApexClassTest \
+  --target-org {{PROD_ORG_ALIAS}}
+```
+
+- Same command, without `--dry-run`
+- **Record the Deploy ID** from the output — required for CR and deploy doc
+
+### Quick Deploy (72-hour window only)
+```bash
+sf project deploy quick \
+  --job-id <ValidationJobId> \
+  --target-org {{PROD_ORG_ALIAS}}
+```
+- Only valid within 72 hours of successful validation
+- Use the Job ID from the dry-run validation, not from a previous deploy
+
+### Check Deployment Status
+```bash
+sf project deploy report --job-id <DeployId> --target-org {{PROD_ORG_ALIAS}}
+```
+
+### Retrieve Metadata (before deploying admin changes)
+```bash
+sf project retrieve start \
+  --manifest manifest/package-deploy-<feature>.xml \
+  --target-org {{DEV_ORG_ALIAS}}
+```
+
+---
+
+## Change Request (CR)
+
+### When: Required before EVERY production deploy
+File: `instructions/change-request/YYYYMMDD-<feature>-cr.md`
+Language: **English**
+
+### CR Template
+```markdown
+# Change Request: [Feature Name]
+
+**Date:** YYYY-MM-DD
+**Feature:** [short feature name]
+**Deploy Manifest:** `manifest/package-deploy-<feature>.xml`
+**Deploy ID:** [filled after successful deploy]
+
+---
+
+## Purpose
+[1 sentence: what this change does]
+
+## Change Tasks
+- [Component name] — [what was changed and why]
+- [Component name] — [what was changed and why]
+
+## Impact
+[1 paragraph or bullet points: what changes for users and the system after this deploy]
+
+## Rollback
+If the deployment causes issues, perform the following:
+
+1. [Step 1 — e.g. Deactivate the new Flow]
+2. [Step 2 — e.g. Redeploy previous version of Apex class from `main` branch]
+3. [Step 3 — e.g. Notify affected users]
+
+Rollback timeline estimate: [X minutes/hours]
+```
+
+---
+
+## Deploy Documentation
+
+File: `instructions/deploy-doc/YYYYMMDD-<feature>-deploy.md`
+
+```markdown
+# Deploy Doc: [Feature Name]
+
+**Date:** YYYY-MM-DD
+**Manifest:** `manifest/package-deploy-<feature>.xml`
+**Target Org:** {{PROD_ORG_ALIAS}}
+**Test Classes:** [list all test classes included]
+
+---
+
+## Pre-Deploy Checklist
+- [ ] Dry-run completed successfully
+- [ ] All specified tests passed (≥85% coverage)
+- [ ] CR created at `instructions/change-request/`
+- [ ] Code review approved on GitHub PR
+
+## Deploy Steps
+1. Run dry-run → confirm success
+2. Create CR
+3. Run actual deploy
+4. Verify in production (spot-check key components)
+5. Update CR with Deploy ID
+6. Push to GitHub + merge PR
+
+## Post-Deploy Verification
+- [ ] [Specific thing to verify in production, e.g. "Open projectCard LWC on a Project record — confirm version badge displays"]
+- [ ] [Another verification step]
+
+## Result
+**Deploy ID:** [filled after deploy]
+**Status:** Success / Partial / Failed
+**Notes:** [any issues encountered]
+```
+
+---
+
+## Order of Work (full cycle)
+
+```
+1. Create deploy doc  →  instructions/deploy-doc/YYYYMMDD-<feature>-deploy.md
+2. Create CR          →  instructions/change-request/YYYYMMDD-<feature>-cr.md
+3. Run /deploy pipeline:
+   a. Dry-run
+   b. Confirm output
+   c. Actual deploy
+   d. Record Deploy ID
+4. Update deploy doc + CR with Deploy ID
+5. Push to GitHub
+```
+
+---
+
+## Git Workflow
+
+### Commit Message Format
+```
+<type>: <short imperative description>
+
+Types: feat | fix | refactor | docs | chore
+```
+
+Examples:
+```
+feat: add project status field to Project__c
+fix: handle null owner in ProjectHelper getProjects
+refactor: extract SOQL to helper method in OpportunityService
+docs: update deploy doc for case-ai-assistant v2.1.0
+chore: update package-deploy manifest for summer release
+```
+
+### Rules
+- ❌ Never add `Co-Authored-By` trailers
+- ❌ Never commit Deploy IDs, Record IDs, API keys, session tokens
+- ❌ Never commit org credentials or Named Credential values
+- ✅ One logical change per commit
+- ✅ Reference the feature/ticket in commit body if relevant (not subject line)
+
+### Commands Reference
+```bash
+# Stage and commit
+git add .
+git commit -m "feat: add projectCard lwc with brand token support"
+
+# Push to feature branch
+git push origin feature/my-feature
+
+# Open PR (GitHub CLI)
+gh pr create --base develop --title "feat: project card component" --body "..."
+```
+
+---
+
+## Static Analysis (pre-PR)
+
+### PMD (Apex)
+```bash
+# Run PMD — must pass before PR
+pmd check --dir force-app --ruleset rulesets/apex/ruleset.xml --format text
+```
+
+Key rules enforced:
+- `AvoidSoqlInLoops`
+- `AvoidDmlStatementsInLoops`
+- `ApexUnitTestClassShouldHaveAsserts`
+- `NcssMethodCount` (method complexity)
+
+### ESLint (LWC)
+```bash
+# Run ESLint
+npx eslint force-app/main/default/lwc --ext .js
+```
+
+Both must pass cleanly before a PR can be merged.
+
+---
+
+## Quick Reference — Org Aliases
+
+| Environment | Alias |
+|---|---|
+| Production | `{{PROD_ORG_ALIAS}}` |
+| Sandbox | `{{DEV_ORG_ALIAS}}` |
+
+```bash
+# List all configured orgs
+sf org list
+
+# Check current default org
+sf config get target-org
+```

package/skills/sf-ideation/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: sf-ideation
+description: >
+  Use this skill when the user wants to brainstorm, explore, or generate enhancement ideas for
+  existing Salesforce components/features OR new feature concepts. Trigger when the user says
+  "ide enhancement", "ada ide baru?", "kira-kira bisa ditambah apa?", "what can we improve?",
+  "fitur baru", "improve this component", "enhancement ideas", or asks for creative suggestions
+  about LWC components, Apex classes, flows, or the overall platform. Also use when reviewing
+  a component and proactively spotting improvement opportunities.
+---
+
+# Salesforce Ideation Skill
+
+## Purpose
+Generate actionable, prioritized enhancement ideas — either for existing components/features
+or as proposals for new features — grounded in the project's current codebase and tech stack.
+
+---
+
+## Existing Components in This Project
+
+### LWC
+| Component | Purpose |
+|---|---|
+| `caseAIAssistant` | AI chat interface for Case — async response via Platform Event |
+| `projectAssetImport` | Form/modal UI for importing project assets |
+| `activityHistoryEnhanced` | Enhanced activity timeline display |
+
+### Apex
+| Class | Purpose |
+|---|---|
+| `CaseAssistantController` | Backend for caseAIAssistant — handles AI callout, TXT attach |
+| `AIAssistantWrapper` | Wrapper/model for AI response data |
+| `AssetImportController` | Backend for projectAssetImport |
+
+---
+
+## Ideation Framework
+
+### For Existing Components — 5 Lenses
+When exploring enhancements for an existing component, evaluate through these lenses:
+
+1. **UX / Interaction** — Is the user flow intuitive? Can loading states, empty states, or error
+   messages be improved? Can interactions be made faster or more delightful?
+
+2. **Performance** — Are there unnecessary re-renders, redundant wire calls, or heavy SOQL that
+   could be optimized? Can we lazy-load data or paginate?
+
+3. **Functionality Gap** — What can users NOT do today that they logically would want to? What
+   edge cases are unhandled?
+
+4. **Integration Opportunity** — Can this component connect to another object, system, or
+   Salesforce feature (e.g. Einstein, Flows, Platform Events) to add value?
+
+5. **Observability / Admin Control** — Can admins configure behavior without code? Are there
+   useful metrics or logs missing?
+
+### For New Features — Discovery Questions
+Before generating ideas for net-new features, consider:
+- What pain point does this solve for the end user?
+- Does Salesforce have a native feature that partially solves this? (avoid reinventing)
+- Which existing components/objects would this touch?
+- Is this declarative (Flow/admin) or requires custom code?
+- What is the rough build complexity: S / M / L / XL?
+
+---
+
+## Output Format
+
+### Enhancement Ideas Output
+Always structure ideas in a prioritized table:
+
+```
+## Enhancement Ideas — [Component/Feature Name]
+
+### Quick Wins (Low effort, High impact)
+| # | Idea | Why | Effort | Impact |
+|---|------|-----|--------|--------|
+| 1 | ... | ... | S | High |
+
+### Medium Term
+| # | Idea | Why | Effort | Impact |
+|---|------|-----|--------|--------|
+
+### Big Bets (High effort, transformative)
+| # | Idea | Why | Effort | Impact |
+|---|------|-----|--------|--------|
+
+### Effort Scale: S=hours, M=days, L=week+, XL=sprint+
+```
+
+After the table, pick the **top 1-2 ideas** and write a short paragraph on how to implement them
+using the project's stack (LWC + Apex + SF CLI).
+
+### New Feature Proposal Output
+```
+## Feature Proposal — [Feature Name]
+
+**Problem:** one sentence
+**Solution:** one sentence
+**Target Users:** who benefits
+**Key Capabilities:** 3-5 bullet points
+**Tech Approach:** LWC / Apex / Flow / Platform Event / etc.
+**Complexity:** S / M / L / XL
+**Dependencies:** existing components or objects it touches
+```
+
+---
+
+## Ideation Rules
+
+- **Always ground ideas in the existing stack** — LWC + Apex + Salesforce declarative tools.
+  Do not suggest third-party tools unless explicitly asked.
+- **Reference existing components** where relevant — e.g. "extend `caseAIAssistant` to also..."
+- **Follow project standards** — any LWC idea must include `:host` brand tokens + version badge.
+  Any Apex idea must follow bulkification + try-catch + CRUD check patterns.
+- **No gold-plating** — ideas should solve a real need, not add complexity for its own sake.
+- **Be opinionated** — don't just list options, recommend the best one and explain why.
+- **Think Salesforce seasons** — flag if an idea aligns with an upcoming Salesforce release
+  feature (Summer '26, Winter '27) that could reduce build effort.
+
+---
+
+## Quick Triggers
+
+| User says... | What to do |
+|---|---|
+| "ide untuk [component]" | Run all 5 lenses on that component, output enhancement table |
+| "fitur baru apa yang bisa kita buat?" | Ask 2-3 discovery questions, then propose 3 feature ideas |
+| "kira-kira [component] bisa ditambah apa?" | Focus on Functionality Gap + UX lenses first |
+| "prioritas enhancement mana yang paling worth it?" | Rank by impact/effort ratio, recommend top 1 |
+| "ada yang bisa diimprove dari sisi performance?" | Focus on Performance lens across all components |