Feels

| ID | Confidence | Domain | Trigger | Scope |
|----|------------|--------|---------|-------|
| prefer-tdd | 0.7 | testing | when implementing features | project |
| use-server-actions | 0.6 | architecture | when creating mutations | project |
| always-validate | 0.8 | security | when handling input | global |

Also read ~/.abilities/feels/index.yaml for global feels.

If no feels exist: "No feels yet. Run /feels analyze to extract patterns from your sessions, or /feels add 'pattern' to create one manually."

Claude Code users: Suggest running /insights first to refresh session data.

Subcommand: add "description"

Create a manual feel. Load references/manual-capture.md for the full pattern.

1. Parse description for intent
2. Infer domain from keywords
3. Generate kebab-case id
4. Create .abilities/feels/{id}.yaml with confidence 0.7, source: manual
5. Update index.yaml
6. Confirm: "Created feel: {id} (confidence: 0.7, domain: {domain})"

Subcommand: forget <id>

Remove a feel by id:

1. Delete .abilities/feels/{id}.yaml
2. Remove from index.yaml
3. Confirm: "Removed feel: {id}"

If id not found, check ~/.abilities/feels/ (global). If global, confirm before deleting.

Subcommand: promote <id>

Copy a project feel to global scope:

1. Read .abilities/feels/{id}.yaml
2. Change scope: global, remove project_id
3. Write to ~/.abilities/feels/{id}.yaml
4. Update ~/.abilities/feels/index.yaml
5. Keep the project copy (now exists in both scopes)
6. Confirm: "Promoted {id} to global scope"

Subcommand: analyze

Run the feels analyzer. Reads from all available sources:

bash scripts/feels-analyze.sh

If on Claude Code, suggest running /insights first: "For best results, run /insights first to refresh your session data."

To force re-read of all usage-data (reset watermark):

bash scripts/feels-analyze.sh --from-usage-data

Subcommand: observe "note"

Add a manual observation to .abilities/feels/observations.jsonl:

{"ts":"<now>","type":"preference","context":"manual observation","after":"<note>","domain":"workflow","source":"manual"}

Subcommand: status

Display summary stats:

Feels Status
─────────────
Project feels: 5 (in .abilities/feels/)
Global feels:  2 (in ~/.abilities/feels/)
Observations:  23 (observations.jsonl)
Last analyzed: 2026-03-16
Usage-data:    available (last read: 2026-03-16)

Top domains: testing (3), workflow (2), architecture (1), security (1)
Avg confidence: 0.58

Initialization

If .abilities/feels/ doesn't exist when any subcommand is invoked:

bash scripts/feels-init.sh project

Then proceed with the subcommand.