awesome-agents 0.1.0 → 0.1.3

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.
@@ -1,45 +0,0 @@
1
- # Awesome Agents Flow Notes
2
-
3
- These are factual notes from the implementation request and current scaffold.
4
-
5
- ## Core Direction
6
-
7
- - The package is named `awesome-agents`.
8
- - It should be installable with `npx`.
9
- - Its command structure should mirror `npx skills`, but for agent profiles.
10
- - It should install profiles from `touch-grass`, both local
11
- `/Users/customer/touch-grass` and GitHub `pablof7z/touch-grass`.
12
- - Initial harness targets are Codex, Claude Code, and OpenCode.
13
- - The package should be published after the scaffold works.
14
-
15
- ## Source Model
16
-
17
- - Canonical profiles live at `agents/profiles/*.md`.
18
- - Harness adapters live at `agents/adapters/<harness>/*.md`.
19
- - Current touch-grass profiles include `ios-tester` and `ios-ux-ui-critic`.
20
- - The CLI should preserve canonical profile content and generate harness-specific
21
- install files.
22
-
23
- ## Command Model
24
-
25
- - `add` is the primary install command because `npx skills` uses `add`.
26
- - `install` is an alias because the user explicitly requested an install command.
27
- - `use` renders one profile without installing it.
28
- - `list`, `remove`, and `update` operate from an `awesome-agents` registry so
29
- the CLI manages only its own generated files.
30
- - `init` creates a starter profile source layout.
31
- - Install scope defaults to project to match the `npx skills` mental model.
32
-
33
- ## Safety Constraints
34
-
35
- - Default behavior should not overwrite or delete unmanaged harness files.
36
- - `--dry-run` should be available for install, remove, update, and init flows.
37
- - Tests should exercise fake homes and fixture sources instead of writing to real
38
- user harness directories.
39
-
40
- ## Open Questions
41
-
42
- - Whether future versions should also generate Codex `--profile` config layers in addition to Codex custom agents.
43
- - Whether touch-grass should add native Claude Code and OpenCode adapters instead
44
- of relying on generated defaults.
45
- - Whether future versions should include interactive prompts like `npx skills`.