agent-docs 1.1.0 → 1.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/PLAN.md +9 -9
- package/README.md +1 -0
- package/docs/A4DWORKFLOWS.md +121 -0
- package/docs/XPATH31.md +0 -5
- package/package.json +31 -32
package/PLAN.md
CHANGED
|
@@ -642,15 +642,15 @@ The plan should:
|
|
|
642
642
|
(patch/minor/major based on the greatest change in any docs file) compared to
|
|
643
643
|
the version in the latest commit in the `main` branch
|
|
644
644
|
- **Document initialization of existing docs:** The existing documentation files
|
|
645
|
-
in the `docs/` directory (A4DRULES.md,
|
|
646
|
-
|
|
647
|
-
FIELDSERVICE.md, GRAPHBINARY.md, GRAPHENGINE.md, GRAPHML.md,
|
|
648
|
-
GREMLIN.md, GRYO.md, HUSKY.md, JEST.md, JORJE.md, JSDOC.md,
|
|
649
|
-
|
|
650
|
-
VITEST.md, XPATH31.md) need to be initialized with version
|
|
651
|
-
appropriate version based on their current state) when the
|
|
652
|
-
is first implemented. These existing docs will be tracked
|
|
653
|
-
the same semver system.
|
|
645
|
+
in the `docs/` directory (A4DRULES.md, A4DWORKFLOWS.md, APEXANNOTATIONS.md,
|
|
646
|
+
APEXDOC.md, CML.md, CODEANALYZER.md, CONTEXTDEFINITIONS.md, ESLINT.md,
|
|
647
|
+
ESLINTJSDOC.md, FIELDSERVICE.md, GRAPHBINARY.md, GRAPHENGINE.md, GRAPHML.md,
|
|
648
|
+
GRAPHSON.md, GREMLIN.md, GRYO.md, HUSKY.md, JEST.md, JORJE.md, JSDOC.md,
|
|
649
|
+
PMD.md, PNPM.md, PRETTIER.md, PRETTIERAPEX.md, REVENUETRANSACTIONMANAGEMENT.md,
|
|
650
|
+
TINKERPOP.md, VITEST.md, XPATH31.md) need to be initialized with version
|
|
651
|
+
`1.0.0` (or appropriate version based on their current state) when the
|
|
652
|
+
versioning system is first implemented. These existing docs will be tracked
|
|
653
|
+
going forward using the same semver system.
|
|
654
654
|
- Describe how scripts can help with versioning by:
|
|
655
655
|
- Reading markdown files and detecting headers/sections
|
|
656
656
|
- Comparing current state with the latest commit in `main` branch
|
package/README.md
CHANGED
|
@@ -77,6 +77,7 @@ The `docs/` directory contains generated documentation files. Each doc follows a
|
|
|
77
77
|
structured format optimized for AI agent consumption:
|
|
78
78
|
|
|
79
79
|
- **[A4DRULES.md](docs/A4DRULES.md)** - Agentforce Rules Reference
|
|
80
|
+
- **[A4DWORKFLOWS.md](docs/A4DWORKFLOWS.md)** - Agentforce Workflows reference
|
|
80
81
|
- **[APEXANNOTATIONS.md](docs/APEXANNOTATIONS.md)** - Apex annotations reference
|
|
81
82
|
- **[APEXDOC.md](docs/APEXDOC.md)** - ApexDoc documentation tool reference
|
|
82
83
|
- **[CML.md](docs/CML.md)** - Constraint Modeling Language (CML) reference for
|
|
@@ -0,0 +1,121 @@
|
|
|
1
|
+
# Agentforce Workflows — Agent Guide
|
|
2
|
+
|
|
3
|
+
> **Version**: 1.0.0
|
|
4
|
+
|
|
5
|
+
## Overview
|
|
6
|
+
|
|
7
|
+
Workflows are reusable `.md` files defining multi-step Salesforce dev tasks. Invoke with `/[workflow-name.md]` in chat.
|
|
8
|
+
|
|
9
|
+
**Benefits:** Automation, consistency, error reduction, time savings, team sharing.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## Creating & Managing
|
|
14
|
+
|
|
15
|
+
| Action | Method |
|
|
16
|
+
|--------|--------|
|
|
17
|
+
| Access | Click **Rules & Workflows** (justice icon) in chat |
|
|
18
|
+
| Scope | Choose **Global** or **Workspace** workflows |
|
|
19
|
+
| Create | Click **+** |
|
|
20
|
+
| Storage | Workspace: `.a4drules/workflows/` folder |
|
|
21
|
+
|
|
22
|
+
Interface allows: view active workflows, toggle on/off, add/delete.
|
|
23
|
+
|
|
24
|
+
---
|
|
25
|
+
|
|
26
|
+
## Workflow Capabilities
|
|
27
|
+
|
|
28
|
+
- **Built-in tools:** `ask_followup_question`, `read_file`, `search_files`, `new_task`
|
|
29
|
+
- **CLI tools:** `sf` (Salesforce CLI), `git`
|
|
30
|
+
- **External:** MCP tool calls
|
|
31
|
+
- **Chaining:** Sequential action execution
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## Common Workflow Types
|
|
36
|
+
|
|
37
|
+
| Type | Purpose |
|
|
38
|
+
|------|---------|
|
|
39
|
+
| Deployment | Deploy/validate components across orgs |
|
|
40
|
+
| Testing | Run test suites, analyze results |
|
|
41
|
+
| Release | Package, validate, deploy releases |
|
|
42
|
+
| Component | Create/test/deploy Lightning components |
|
|
43
|
+
| Integration | Set up/validate external integrations |
|
|
44
|
+
|
|
45
|
+
---
|
|
46
|
+
|
|
47
|
+
## Example: `salesforce-deploy.md`
|
|
48
|
+
|
|
49
|
+
```text
|
|
50
|
+
You have access to the `sf` terminal command. Deploy components following this process:
|
|
51
|
+
|
|
52
|
+
1. **Gather Info**
|
|
53
|
+
<ask_followup_question>
|
|
54
|
+
<question>Which components to deploy and to which org?</question>
|
|
55
|
+
<options>["Specific files/folders", "All local changes", "Specific metadata types"]</options>
|
|
56
|
+
</ask_followup_question>
|
|
57
|
+
|
|
58
|
+
sf org display --target-org <target-org>
|
|
59
|
+
|
|
60
|
+
2. **Pre-Deployment Validation**
|
|
61
|
+
sf project retrieve start --dry-run --target-org <target-org>
|
|
62
|
+
sf apex test run --code-coverage --result-format human
|
|
63
|
+
sf project deploy start --dry-run --target-org <target-org>
|
|
64
|
+
|
|
65
|
+
3. **Confirm**
|
|
66
|
+
<ask_followup_question>
|
|
67
|
+
<question>Validation complete. Proceed with deployment?</question>
|
|
68
|
+
<options>["Yes, deploy now", "No, make changes first", "Show details"]</options>
|
|
69
|
+
</ask_followup_question>
|
|
70
|
+
|
|
71
|
+
4. **Execute**
|
|
72
|
+
sf project deploy start --target-org <target-org>
|
|
73
|
+
sf project deploy report --target-org <target-org>
|
|
74
|
+
|
|
75
|
+
5. **Post-Validation**
|
|
76
|
+
sf apex test run --target-org <target-org> --code-coverage --result-format human
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
---
|
|
80
|
+
|
|
81
|
+
## SF CLI Quick Reference
|
|
82
|
+
|
|
83
|
+
### Org Commands
|
|
84
|
+
```bash
|
|
85
|
+
sf org list # List authorized orgs
|
|
86
|
+
sf org display --target-org <alias> # Display org info
|
|
87
|
+
sf config set target-org <alias> # Set default org
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
### Deployment
|
|
91
|
+
```bash
|
|
92
|
+
sf project deploy start --target-org <alias> # Deploy
|
|
93
|
+
sf project deploy start --dry-run --target-org <alias> # Validate only
|
|
94
|
+
sf project deploy report --target-org <alias> # Check status
|
|
95
|
+
sf project retrieve start --target-org <alias> # Retrieve metadata
|
|
96
|
+
```
|
|
97
|
+
|
|
98
|
+
### Testing
|
|
99
|
+
```bash
|
|
100
|
+
sf apex test run --target-org <alias> --code-coverage --result-format human
|
|
101
|
+
sf apex test run --class-names "Test1,Test2" --target-org <alias>
|
|
102
|
+
sf apex test report --target-org <alias>
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
### Data
|
|
106
|
+
```bash
|
|
107
|
+
sf data query --query "SELECT Id FROM Account LIMIT 10" --target-org <alias>
|
|
108
|
+
sf data import tree --plan data/plan.json --target-org <alias>
|
|
109
|
+
sf data export tree --query "SELECT Id FROM Account" --target-org <alias>
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
---
|
|
113
|
+
|
|
114
|
+
## Custom Workflow Ideas
|
|
115
|
+
|
|
116
|
+
| Workflow | Key Steps |
|
|
117
|
+
|----------|-----------|
|
|
118
|
+
| **Release** | Gather merged changes → Build changelog → Bump version → Create/validate package |
|
|
119
|
+
| **New Component** | Create folder structure → Generate boilerplate files → Set up Jest tests → Deploy to dev |
|
|
120
|
+
| **Integration Test** | Validate credentials → Test endpoints → Check error handling → Generate reports |
|
|
121
|
+
| **Code Quality** | Run PMD analysis → Check accessibility → Validate naming → Generate reports |
|
package/docs/XPATH31.md
CHANGED
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
````markdown
|
|
2
1
|
# XPath 3.1 Reference
|
|
3
2
|
|
|
4
3
|
> **Version**: 1.0.0
|
|
@@ -207,7 +206,3 @@ $seq ! (./child/@attr) # apply to each, flatten
|
|
|
207
206
|
- Document order preserved
|
|
208
207
|
- Namespaces: prefixes or `Q{uri}local`
|
|
209
208
|
- Errors: `try/catch` in 3.1
|
|
210
|
-
|
|
211
|
-
```
|
|
212
|
-
|
|
213
|
-
```
|
package/package.json
CHANGED
|
@@ -1,33 +1,32 @@
|
|
|
1
1
|
{
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
}
|
|
2
|
+
"name": "agent-docs",
|
|
3
|
+
"version": "1.2.0",
|
|
4
|
+
"type": "module",
|
|
5
|
+
"description": "A tool for generating reusable, low-token AI agent instruction documents",
|
|
6
|
+
"keywords": [
|
|
7
|
+
"ai",
|
|
8
|
+
"agent",
|
|
9
|
+
"documentation",
|
|
10
|
+
"docs",
|
|
11
|
+
"ide",
|
|
12
|
+
"cursor"
|
|
13
|
+
],
|
|
14
|
+
"author": "starch-uk",
|
|
15
|
+
"license": "MIT",
|
|
16
|
+
"repository": {
|
|
17
|
+
"type": "git",
|
|
18
|
+
"url": "https://github.com/starch-uk/agent-docs.git"
|
|
19
|
+
},
|
|
20
|
+
"devDependencies": {
|
|
21
|
+
"prettier": "^3.7.4"
|
|
22
|
+
},
|
|
23
|
+
"engines": {
|
|
24
|
+
"node": ">=20.0.0"
|
|
25
|
+
},
|
|
26
|
+
"scripts": {
|
|
27
|
+
"format": "prettier --write \"**/*.{ts,md,json,yml,yaml}\"",
|
|
28
|
+
"format:fix": "prettier --write \"**/*.{ts,md,json,yml,yaml}\"",
|
|
29
|
+
"format:check": "prettier --check \"**/*.{ts,md,json,yml,yaml}\"",
|
|
30
|
+
"postinstall": "node postinstall.mjs"
|
|
31
|
+
}
|
|
32
|
+
}
|