54a675c838
* Add building-ui-bundle-app orchestration skill New orchestration skill that coordinates all UI bundle skills in proper dependency order to build complete React applications on Salesforce. Follows the generating-lightning-app pattern with explicit skill load calls for each phase: scaffolding → features → data access → UI → integrations → deployment → experience site. * Clean up building-ui-bundle-app skill @W-21338965@ - Remove Skill Registry section (redundant with Dependency Graph + Execution Workflow) - Remove "Skill to load" lines from Dependency Graph phases (duplicated in per-phase execution steps) - Remove Best Practices 2 & 3 (duplicated in Execution Workflow and Phase 2 description) - Fix SKILL LOAD ORDER numbering: flat 1-8 → 5a/5b to match phase numbering in Dependency Graph - Clarify GraphQL schema re-fetch in Phase 6 is a post-deployment remote schema fetch - Add parallel execution guidance to Phase 5 execution block * Make Phase 2 (Features) optional @W-21338965@ * Address review feedback: use non-LWC terminology instead of React-specific Co-authored-by: dme722 * Fix building-ui-bundle-app skill: remove special chars, align with actual skills - Replace non-ASCII characters (arrows, circled numbers, checkmarks, em dashes) that cause silent failures in Cline - Fix incorrect skill name generating-ui-bundle-ui -> building-ui-bundle-frontend - Align phase diagrams with actual skill workflows (add missing steps for scaffolding npm install, features search-first flow, data validation step, deployment final build and full post-deploy config) - Fix Phase 4 diagram to match building-ui-bundle-frontend task categories Made-with: Cursor |
||
|---|---|---|
| .github | ||
| rules | ||
| samples | ||
| scripts | ||
| skills | ||
| .gitignore | ||
| .nvmrc | ||
| .template-versions.json | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| DOCS_ONLY.md | ||
| LICENSE.txt | ||
| manifest.json | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| sfdx-project.json | ||
Agentforce Vibes Library
AI skills and rules library for Agentforce Vibes development of Salesforce metadata.
📚 About
This repository curates Salesforce-focused skills and system rules from the wider developer community to accelerate Agentforce Vibes agentic workflows.
🗂️ Structure
afv-library/
├── rules/ # Single-file guardrails and standards
├── skills/ # Directory-based executable workflows
│ ├── generating-apex/
│ ├── generating-custom-object/
│ ├── generating-flow/
│ └── ...
├── samples/ # Synced sample apps (e.g. from npm)
│ └── ui-bundle-template-app-react-sample-b2e/
│ └── ...
├── scripts/
│ └── ...
└── README.md
Manual Usage
Browse the repository and copy/paste any rule or skill directly into Agentforce Vibes or your preferred AI tool.
Samples
The samples/ folder contains synced sample apps. For example, samples/ui-bundle-template-app-react-sample-b2e/ is kept in sync with the npm package @salesforce/ui-bundle-template-app-react-sample-b2e (nightly and on manual trigger via GitHub Actions). To run the same sync locally from the repo root:
npm install
npm run sync-react-b2e-sample
The GitHub Action runs these same commands and opens a PR only when the npm package version has changed. See samples/README.md for details.
🛠️ Agent Skills
Agent Skills extend rules by bundling executable workflows, scripts, and reference materials into self-contained directories. Skills follow the open Agent Skills specification and are portable across many agent tools (Cursor, Claude Code, VS Code extensions, etc.).
Directory Structure
Each skill is a folder containing:
SKILL.md(required) - instructions + YAML frontmatterscripts/(optional) - executable Python/Bash/JSreferences/(optional) - additional documentationassets/(optional) - templates, schemas, lookup data
🤝 Contributing
See Contributing for complete details.
Feedback
Found an issue or have a suggestion?
- Open an issue in GitHub
- Suggest improvements via pull request
- Start a discussion in GitHub Discussions or the pull request thread