project-notes

Included with Lifetime

$97 forever

This skill should be used when creating, updating, or organizing pages and documentation in the notes/ directory. It covers notes/ conventions, INDEX.md curation, wikilinks, and routing guidance for choosing between notes pages, journal entries, and decision log entries. Triggers on: "write a note", "document this", "create a page about", "add to notes", "where should I document this", "what type of note should this be".

General

What this skill does

# Project Notes

All project knowledge lives in `notes/` at the repository root. For durable reference content, prefer `docs/`.

## Conventions

- **Format**: plain markdown files, organized by topic in subdirectories
- **Cross-references**: use `[[wikilinks]]` for internal links between notes; use relative markdown links `[text](path.md)` for everything else
- **Entry point**: `notes/INDEX.md` is the curated index of high-value content -- human-maintained, links to what matters

## Creating a Page

Create pages as plain `.md` files under `notes/`. Organize by topic in subdirectories when a cluster of related pages emerges. There is no prescribed directory structure beyond:

- `notes/INDEX.md` -- curated entry point
- `notes/DECISIONS.md` -- decision log (see decision-log skill)
- `notes/journal/` -- timestamped entries (see journal skill)

For durable reference content that will be maintained long-term, prefer `docs/`.

## Routing: Which Type of Note?

| What you're capturing | Use |
|---|---|
| Timestamped observation, discovery, or insight | Journal entry in `notes/journal/` |
| Concise record of a decision made | Decision log entry in `notes/DECISIONS.md` |
| Working notes, scratch pages, topic clusters | Page in `notes/` |
| Durable reference content | `docs/` |

**Journal entries** are timestamped snapshots -- they capture a moment. **Decision log entries** are one-liners -- they record what was decided, not the full reasoning. **Notes pages** are working knowledge -- they evolve but may go stale. **`docs/`** is durable reference -- maintained and authoritative.

When a journal entry proves durable, promote it: extract the lasting content into `docs/` and link to it from `INDEX.md`.

## INDEX.md

`notes/INDEX.md` serves as the curated entry point. It is not auto-generated -- a human (or agent, with human review) maintains it by linking to the most valuable content.

A page gains authority by being linked from `INDEX.md`. Unlinked pages are still searchable but are not actively trusted as current.

## What Notes Are (and Aren't)

`notes/` is shared, human-readable project knowledge -- what happened, what was learned, what was decided. It's the place for context that matters to anyone working on the project, human or AI.

Things that look similar but serve different purposes:

- **`specs/`** (if available) has a stronger contract. Gherkin scenarios in specs are verified before shipping; notes carry no such guarantee. If something must be enforced as behavior, it belongs in a spec, not a note.
- **`.agents/memory/`** (if available) is operational context for AI sessions -- how to work here, what to watch out for. It's AI-private and not meant for human consumption. Notes are shared and human-facing.
- **`docs/`** is durable reference. Notes may go stale; docs are expected to stay current.

When in doubt: if it's a behavioral contract, use specs. If it's an agent working pattern, use auto-memory. If it's lasting reference, use docs. Everything else -- observations, research, working knowledge -- belongs in notes.

## Searching Notes

```
# Find pages by name
Glob: notes/**/*.md

# Search content
Grep: pattern="<keyword>" path="notes/"
```

Files: 1

Size: 3.6 KB

Complexity: 15/100

Category: General

Source: https://github.com/a3lem/my-claude-plugins/tree/main/plugins/project-notes/skills/project-notes

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts